Tell me about a time you did not know something important and had to act anyway.
What they are really testing: Comfort with uncertainty, which is most of operations. They want to see you make a reasoned decision under incomplete information rather than freezing or bluffing.
A real interview question
Tell me about a time you did not know something important and had to act anyway.
What most people say
drag me
“I researched it thoroughly until I was confident, then made the decision.”
It dodges the question, which is specifically about acting without certainty. In operations you frequently cannot wait for confidence, and an answer that only describes the comfortable path suggests either inexperience or a tendency to freeze.
The follow-ups they ask next
What if the snapshot had not been possible?
Then the risk is unbounded and the calculus changes: prefer the reversible option even if it is slower, or escalate to someone with the knowledge before acting rather than after.
How do you decide between acting now and waiting for expertise?
Compare the cost of the delay against the cost of being wrong. If users are actively harmed and the action is reversible, act. If the action is irreversible, the bar for waiting is much lower.
Is saying "I am 80% confident" risky in front of stakeholders?
It is far less risky than false certainty. Calibrated confidence lets others calibrate their own decisions, and people trust someone who is right about their uncertainty more than someone who is confidently wrong once.
What the interviewer is listening for
- Bounds the risk before acting
- Closes the knowledge gap in parallel rather than serially
- States a confidence level out loud
- Learned something about behaviour, not only technology
What sinks the answer
- Claims to always research to certainty
- Acted irreversibly while guessing
- Hid the uncertainty
- No mechanism for making the mistake survivable
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I did not know [X] and it mattered because [Y]. So I [bounded the risk first: took a snapshot, stopped the write path], then [closed the gap fast: docs plus a colleague who had seen it]. I [stated my confidence level out loud rather than claiming certainty] and named my rollback. I learned [the technical thing, and that stating uncertainty made others more useful].”
Keep going with behavioural
Mid
Tell me about a time you broke production. What happened and what did you do?
Mid
Tell me about a time you disagreed with a developer about how something should be deployed.
Mid
Tell me about a time you were on call and it went badly.
Mid
Tell me about a mistake that cost the company money.
Mid
Walk me through a time you inherited a system nobody understood. Where did you start?
Mid
Tell me about something repetitive you automated. How did you decide it was worth it?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free