Answer first
- State the decision and result in the first thirty seconds.
- Use “I” for your actions and “we” only for the team's collective outcome.
Amazon · Product manager · Leadership Principles III
Tell me about a time you strongly disagreed with a senior leader and did not back down.
Build a defensible answer, then pressure-test it in the same workspace where you can save the attempt.
See this question in OfferHack Browse the question first. Premium opens the complete worked answer and coaching when you need them.This is a constructed rehearsal, not an official company answer or a prediction of what an interviewer will ask. A company-specific practice prompt synthesized from published interview guidance, candidate reports, official product material, role descriptions, and company values; it is not a claim that this exact question will be asked.
Start with a position
Give the interviewer your decision before the framework.
For “Tell me about a time you strongly disagreed with a senior leader and did not back down.” at Amazon, I would answer with an adoption turnaround: a specific decision in which I narrowed the problem, aligned the team, and produced measurable value while explicitly managing a locally successful launch that damages trust, unit economics, employees, sellers, or downstream communities at scale.
Preview the reasoning
Three moves to make the answer concrete.
Situation and stakes
- Primary stakeholder: a clearly defined Amazon customer whose repeated job is underserved.
- Decision risk: a locally successful launch that damages trust, unit economics, employees, sellers, or downstream communities at scale.
My decision
- Write down the rejected alternatives and opportunity cost.
- Make the decider and escalation path explicit.
Measurement check
A metric is useful only when it changes the decision.
- North star
- customer outcome and repeat behaviorMeasures the repeated user or customer outcome, not mere feature activity.
- Diagnostic
- controllable input metric movementExplains whether quality and the critical journey improved for the intended segment.
- Guardrail
- quality, cost-to-serve, trust, and operational defectsMakes the principal downside observable: a locally successful launch that damages trust, unit economics, employees, sellers, or downstream communities at scale.
Interviewer pressure test
Do not stop when the first answer sounds polished.
- Why prioritize a clearly defined Amazon customer whose repeated job is underserved, and who did you explicitly defer?
- How would your answer change with two weeks, three engineers, or a tenfold scale increase?
- What is the strongest rejected alternative and when would it win?
Turn reading into retrieval