Prep by Company
Software Dev Engineer SDE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Data Engineer DE ML Engineer MLE Technical PM TPM
Software Engineer SWE Product Manager PM Data Scientist DS Solutions Architect SA ML Engineer MLE Technical PM TPM
Guides About Get Your Playbook →
The Bar Raiser's Debrief · Amazon Product Manager

"Tell me about a product decision you made that turned out to be wrong."

Are Right, A Lot Product Manager 5–7 min
Why candidates fail: Candidates either pick a trivial failure to seem safe or over-apologize for the outcome instead of demonstrating the sharper judgment they developed as a result.
Two voices. One question. The insider reaction you don't usually see.
Also on YouTube 5–7 min 2026
"Tell me about a product decision you made that turned out to be wrong."
Competency tested
Are Right, A Lot
Who asks it
Bar Raiser · HM · Peer
What they're really asking
Did the miss actually sharpen your decision process?
The answer that fails — and why
Candidate answer Does not raise the bar — Are Right, A Lot

Early in my tenure as PM for our mobile checkout flow, I pushed to add a guest checkout option based on user research showing friction at the login step. We shipped it, and conversion did improve slightly — but cart abandonment on the back end actually increased because guest users didn't save payment info and dropped off at confirmation. I should have looked at the full funnel, not just the login step. We eventually rolled it out with a smarter save-card prompt and recovered the numbers. It was a good learning experience about thinking end-to-end.

Bar Raiser evaluation
Reasoning process at the time of decision not explained
Failure attributed to oversight, not a named judgment gap
'Good learning experience' — no concrete process change stated
Prefer to hear it? Watch the video for the two-voice delivery with live reaction commentary.
Amazon debrief · PM loop · Bar Raiser evaluation Below Bar
Leadership Principle: Are Right, A Lot
Does not demonstrate Are Right, A Lot.
Cannot articulate what evidence anchored the original decision and why it felt sufficient.
Missed signal framed as an oversight, not a named gap in reasoning or information model.
Recovery described as a team outcome — candidate's specific judgment role is unclear.
No durable process change stated; 'learning experience' language signals reflection without mechanism.
interview101.com · Are Right, A Lot · Amazon PM · Bar Raiser debrief reference
Now here's what a strong answer actually sounds like
The answer that works — in full
Strong answer Raises the bar — Are Right, A Lot

I made the call to de-prioritize offline mode for our mobile app, arguing that less than eight percent of sessions showed connectivity issues in our telemetry. Three months post-launch, NPS for users in low-bandwidth regions dropped eleven points — a segment our aggregate data had masked. My error was trusting average connectivity metrics instead of segmenting by geography before deciding. I owned a post-mortem, identified the segment gap, and introduced a standing rule on my team: any decision affecting infrastructure must include a segmented usage cut before sign-off. That rule is still in the team's decision checklist today.

Bar Raiser evaluation
Original reasoning clearly articulated — decision was defensible, not reckless.
Specific missed signal named precisely: aggregate data masking a geographic segment.
Candidate owns the post-mortem and the fix — not diffused to the team.
Durable mechanism created — checklist rule outlasts the individual decision.
Amazon debrief · PM loop · Bar Raiser evaluation Raises Bar
Leadership Principle: Are Right, A Lot
Strong signal. Raises the bar.
Articulates original rationale clearly — decision was data-anchored and defensible at the time.
Names the exact reasoning flaw: aggregate metric masking a critical user segment.
Takes singular ownership of post-mortem and solution — no diffusion to the team.
Installs a durable decision mechanism that outlasts the incident — strong Are Right, A Lot signal.
interview101.com · Are Right, A Lot · Amazon PM · Bar Raiser debrief reference
Run your story through these three questions
1
Can you name the specific evidence that made your original decision feel sound?
If not, the Bar Raiser hears recklessness, not judgment — and Are Right, A Lot collapses.
2
Can you name the exact signal you missed and why your process didn't surface it?
Vague answers like 'I should have looked more broadly' show reflection without self-awareness.
3
Did the miss produce a named mechanism that changed your team's decision process permanently?
A story that ends with a lesson and not a system tells the Bar Raiser the learning didn't stick.
Get your personalized report
How do your real stories score?
Get a personalized report scored against the interview rubric Amazon uses for your role.
Get your Amazon Product Manager report →
Other questions from the same loop
Each video covers a different competency tested in the Amazon Product Manager loop
Explore the full Amazon Product Manager prep hub