Tell me about a time you disagreed with a developer about how something should be deployed.
What they are really testing: You are being hired to gate other people work, so they need to know you can hold a line without becoming an obstacle. They are watching for whether you sought to understand and whether you would ever change your mind.
A real interview question
Tell me about a time you disagreed with a developer about how something should be deployed.
What most people say
drag me
“They wanted to deploy without tests so I told them that is not how we do things and blocked the pull request.”
It is a correct position delivered as authority rather than persuasion. It makes you the compliance department, and the developer will route around you next time rather than bring you in early.
The follow-ups they ask next
What if they had gone ahead anyway?
Do not fight it in the moment during a customer incident. Raise it afterwards with the team and fix the underlying reason people bypass the process, since a rule people route around is not a control.
Tell me about a time you were the one who was wrong.
Have a real example ready. Being able to name a case where you updated your position on evidence is one of the strongest signals in a senior loop.
What the interviewer is listening for
- States their position fairly
- Reframes around blast radius rather than policy
- Takes the underlying process problem as their own
What sinks the answer
- Wins by authority or policy citation
- No middle path explored
- Never been wrong
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.
“They wanted [X] because [their legitimate reason]. My concern was [the specific risk, in blast radius terms]. I [acknowledged their constraint], then [made the risk concrete rather than procedural]. We landed on [the middle path] and [afterwards I fixed the process condition that caused the pressure].”
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 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