Tell me about a time you stopped a release that other people wanted to ship.
What they are really testing: Whether you can exercise a gate responsibly. They want evidence you had a specific reason, communicated it well, and did not simply enjoy the authority.
A real interview question
Tell me about a time you stopped a release that other people wanted to ship.
What most people say
drag me
“I blocked it because the test coverage was below our standard and rules are rules.”
It appeals to a policy rather than a risk, which makes it easy to overrule and hard to respect. A gate defended by a number rather than a consequence teaches people that the gate is bureaucratic rather than protective.
The follow-ups they ask next
What if the test had passed and there was no bug?
Then the delay was the price of the check, and I would say so plainly. Calibration matters: a blocker who is right half the time is valuable, one who is right a tenth of the time is an obstacle.
How do you avoid becoming the person everyone routes around?
Block rarely and specifically, always with a path forward, and spend most of your effort making the safe path fast. If your gate is the only thing standing between a team and shipping, they will eventually go around it.
Who should own that decision, you or the team shipping?
Ideally the team, with the risk made visible by tooling rather than by a person. A human gatekeeper does not scale and creates resentment, so my long-term goal is to encode the check and get out of the path.
What the interviewer is listening for
- Names a specific failure mode, not a policy
- Verified before escalating
- Offered a condition rather than a veto
- Wants to encode the check and remove themselves
What sinks the answer
- Cites policy as the reason
- Blocks without a path forward
- Enjoys the gatekeeper role
- No calibration awareness
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 stopped [release X] because [specific failure mode: this exact partial-failure case had no coverage]. I [verified it was real first, since a false block costs credibility]. I raised it [directly with the engineer and product owner, framed as the customer consequence not a coverage number] and offered [a condition: ship Monday with the test, or ship now behind a disabled flag]. Outcome: [the test found the bug].”
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