Tell me about a code review that turned into an argument. How did it end?
What they are really testing: They want to know if you can separate a standard from a preference, and whether you can de-escalate a thread that has stopped being about the code.
A real interview question
Tell me about a code review that turned into an argument. How did it end?
What most people say
drag me
“The other engineer was being really defensive about my comments, so I just approved the pull request to keep the peace and moved on.”
Approving to avoid conflict tells the interviewer that your review signal is worthless under pressure, and it hides a problem in the codebase rather than resolving it.
The follow-ups they ask next
How do you decide when a review comment is a blocker versus a nit?
Give a concrete rule. Security, data loss and on-call pain are blockers. Style is a nit and should be labelled as one or automated away.
What if the other engineer had refused the call?
Say you would state the blocker, the reason and the standard once, then escalate the decision, not the person, to a tech lead.
Did you apologise for your part in the tone?
Yes is the right answer, and say it plainly. Owning half of a tone problem costs nothing and buys a lot.
What the interviewer is listening for
- Noticed the thread had stopped being technical
- Changed medium instead of escalating volume
- Converted the fight into a written standard
- Labelled blockers separately from preferences
What sinks the answer
- Approving a change you believe is unsafe to end the conflict
- Piling on comments to win by attrition
- Framing the other engineer as the entire problem
- Treating style preferences as blockers
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 had a review go bad, but here is how I would reason about it. I would ask whether my comment is a standard or a preference, and if a thread runs past a few rounds I would move it to a short call.”
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