Tell me about a time you argued against your own proposal or changed your mind on a significant technical decision.
What they are really testing: Intellectual honesty at a level where you have enough authority that nobody will stop you. They want evidence you update on data rather than defending a position because it is yours.
A real interview question
Tell me about a time you argued against your own proposal or changed your mind on a significant technical decision.
What most people say
drag me
“I usually think things through carefully first, so I have not really had to reverse a major decision.”
At principal level this reads as either not making consequential decisions or not tracking their outcomes. Every significant technical bet has a chance of being wrong, and the valuable skill is noticing early.
The follow-ups they ask next
How do you decide when to persist versus reverse?
Set the success criteria before starting and a checkpoint date. Then it is a comparison against a pre-committed bar rather than a fight against sunk cost in the moment.
How did the team react?
The honest answer usually includes some frustration about wasted work, plus increased trust. Naming the frustration rather than claiming universal applause is far more credible.
What the interviewer is listening for
- Set criteria and tracked them
- Reversed publicly with data
- Frames it as making reversal safe for others
What sinks the answer
- Cannot recall changing their mind
- Reversed only because someone senior pushed
- No cost acknowledged
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 proposed [X] for [these reasons]. Then [specific evidence] showed the benefits were not landing for us: [concrete signals]. I [argued against my own proposal publicly, with the data], despite [sunk cost and it being my idea]. We [did the simpler thing instead] and [got most of the value faster]. I did it publicly because [it makes reversal safe for everyone else].”
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