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 II
Describe a time you lost trust with a stakeholder and how you rebuilt it.
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 “Describe a time you lost trust with a stakeholder and how you rebuilt it.” at Amazon, I would answer with a zero-to-one technical product: a specific decision in which I narrowed the problem, aligned the team, and produced measurable value while explicitly managing a severe harm or systematic false-positive burden hidden by a healthy aggregate metric.
Preview the reasoning
Three moves to make the answer concrete.
Situation and stakes
- Primary stakeholder: a legitimate user whose valuable action must remain possible inside a high-trust system.
- Decision risk: a severe harm or systematic false-positive burden hidden by a healthy aggregate metric.
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
- valuable outcomes within the safe envelopeMeasures the repeated user or customer outcome, not mere feature activity.
- Diagnostic
- precision, recall, and false-positive burdenExplains whether quality and the critical journey improved for the intended segment.
- Guardrail
- severe incidents, appeal accuracy, and recovery timeMakes the principal downside observable: a severe harm or systematic false-positive burden hidden by a healthy aggregate metric.
Interviewer pressure test
Do not stop when the first answer sounds polished.
- Why prioritize a legitimate user whose valuable action must remain possible inside a high-trust system, 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