Tell me about a time you were overruled on a technical decision and it later went wrong. What did you do next?
What they are really testing: This is a maturity test. They want to see whether you commit properly after losing an argument, and whether you handle being right without punishing anyone.
A real interview question
Tell me about a time you were overruled on a technical decision and it later went wrong. What did you do next?
What most people say
drag me
“I told them it would not scale, they ignored me, and then it fell over exactly like I said it would. I had already warned everyone.”
The whole answer is about being vindicated, which tells the interviewer you would rather be right than have the system stay up, and that you are unpleasant to lose an argument to.
The follow-ups they ask next
Why did you build the dead-letter queue if you disagreed with the design?
This is the heart of the answer. Say that committing means making the path you disagreed with as safe as you can, not sabotaging it by omission.
Did you feel resentful when it broke?
Be human. Say yes for about a minute, then say what you did with it, which was nothing public.
How do you record a dissent without it reading as covering yourself?
One or two neutral lines in the design doc, phrased as a risk with a trigger condition, agreed with the decision maker at the time.
What the interviewer is listening for
- Recorded the risk before the decision, not after the outage
- Committed fully and made the chosen path safer
- Did not claim vindication in the postmortem
- Turned the incident into a two-day fix, not a blame thread
What sinks the answer
- Building the disliked design badly on purpose
- Saying I told you so, in any form
- Never writing the concern down and only raising it after the failure
- Treating the postmortem as a chance to relitigate the original argument
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 have not been overruled on something that then broke, but here is how I would reason about it. I would put the risk and its trigger in the design doc, then commit fully and build the failure mode so it is loud, not silent.”
Keep going with behavioural
Foundation
Tell me about a time you had to learn a new technology quickly. How did you go about it?
Foundation
So, why cloud? You have not worked in cloud before, so walk me through what actually pulled you here.
Foundation
Why are you leaving your current job?
Foundation
Tell me about a time you noticed something was broken, wasteful or risky, and nobody seemed to own it. What did you actually do?
Junior
You join a team and inherit a service with no documentation and the original author has left. Walk me through your first week.
Junior
Describe a time you were blocked and there was genuinely nobody available to ask. What did you do?
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