← Forward Deployed Engineer
Forward Deployed Engineer

Debugging Inside Someone Else’s Infra

4 Nov 2026·3 min read

In your own stack you know what changed. Inside a customer’s infra, you often cannot see the logs you want, cannot restart the service you suspect, and cannot assume anything about what else is running nearby.

What to establish first

  • What you are actually allowed to see and touch — ask before you assume.
  • What changed most recently, since that is still the most common cause of a new break.
  • Who else is affected, so your fix does not quietly break something else they depend on.
Why "ask before you assume" is the real skillIn your own system, a wrong assumption costs you a few minutes. In a customer’s system, acting on a wrong assumption about access or ownership can break something you cannot see and cannot easily undo — so the habit of asking first is not caution for its own sake, it is the job.
Do this in 60 secondsNext time something breaks in a system you only partly control — even a shared home Wi-Fi router or a family member’s laptop counts — write down your first three questions before you touch any setting. Compare them afterward to what you actually ended up needing to know.
Today’s AI angleWhen an AI agent misbehaves inside a customer’s system, the same rule applies doubly — you need to know exactly what the agent was allowed to touch before you can tell whether it did something wrong or something it was never supposed to be able to do at all.
Interview prepYou are debugging inside a customer's infrastructure and you do not have the log access you need. What now? I ask, specifically, for exactly the access or the specific log output I need, rather than requesting broad access "to be safe" — that request is both faster to approve and less risky for them. If that access genuinely cannot be granted, I ask them to reproduce the issue with me watching over a screen share instead of insisting on direct access.
Debugging Inside Someone Else’s Infra · Ali Huzaifa