Tell me about a time you broke production. What happened and what did you do?
What they are really testing: Not whether you break things, everyone does. They are testing ownership, how you behave under pressure, and whether you convert an incident into a systemic fix rather than a promise to be careful.
A real interview question
Tell me about a time you broke production. What happened and what did you do?
What most people say
drag me
“I have not really broken production, I am pretty careful with changes.”
It reads as either inexperience or dishonesty, and both are worse than the incident. Anyone who has operated production for a year has broken something, and the refusal to discuss it removes the chance to demonstrate ownership.
The follow-ups they ask next
What did you say to the team afterwards?
Concrete and non-defensive: what happened, impact, what you changed. Volunteering it publicly builds far more trust than being asked, and it models the blameless behaviour you want from others.
Has that guardrail actually stopped anything since?
A specific example is the strongest possible close, because it proves the fix was real rather than a postmortem action item that quietly expired.
What the interviewer is listening for
- Owns it in the first sentence
- Gives specific impact numbers
- Ends with a systemic guardrail, not "I was more careful"
What sinks the answer
- Claims never to have broken anything
- Blames staging, another team, or bad luck
- Fix is a promise to be careful
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 X specific thing] which caused [Y impact for Z minutes]. I [restored service by doing A] and [communicated in the channel while doing it]. The root cause was [B, and the system made that easy to get wrong]. Afterwards we [added guardrail C so it cannot happen again].”
Keep going with behavioural
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?
Mid
Tell me about a time you did not know something important and had to act anyway.
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