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 Data Scientist

"Tell me about a time you analysis that changed a product decision in favour of the customer"

Customer Obsession Data Scientist 5–7 min
Why candidates fail: Candidates describe the analysis itself in technical detail but never prove the customer was actually better off — they confuse influencing a decision with validating an outcome.
Two voices. One question. The insider reaction you don't usually see.
Also on YouTube 5–7 min 2026
"Tell me about a time you analysis that changed a product decision in favour of the customer"
Competency tested
Customer Obsession
Who asks it
Bar Raiser · HM · Peer
What they're really asking
Did you own the outcome, not just the slide?
The answer that fails — and why
Candidate answer Does not raise the bar — Customer Obsession

On my last team, we were planning to launch a new checkout flow. I ran an A/B test comparing the existing flow against the redesign and found the new version reduced drop-off by about twelve percent. I put together a detailed analysis deck covering statistical significance, segment breakdowns, and edge cases, and presented it to the product team. Based on my findings, they decided to roll back the redesign and keep the original flow. The customers were better served by a more familiar experience, and the PM thanked me for the rigorous work.

Bar Raiser evaluation
Outcome attributed to PM decision, not candidate's ownership
No post-launch measurement — impact assumed, not validated
Customer benefit asserted verbally, no behavioural data cited
Prefer to hear it? Watch the video for the two-voice delivery with live reaction commentary.
Amazon debrief · DS loop · Bar Raiser evaluation Below Bar
Leadership Principle: Customer Obsession
Does not demonstrate Customer Obsession.
Candidate described analysis output, not customer outcome — conflated the two.
No evidence of post-decision measurement or follow-through on customer impact.
Decision credit deferred to PM — candidate did not own the loop end-to-end.
Customer benefit stated as assertion; no behavioural or metric evidence provided.
interview101.com · Customer Obsession · Amazon DS · 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 — Customer Obsession

Our product team was planning to replace a well-used filter feature with a new discovery module. I noticed in our event logs that customers who used that filter had a thirty-one percent higher repeat-purchase rate — a signal no one had quantified before. I proactively brought it to the roadmap review before engineering kicked off, modelled the projected revenue loss, and proposed a holdout experiment instead of a hard cutover. The PM initially pushed back, but the data held. We ran the holdout, confirmed a fourteen percent drop in repeat purchases in the treatment arm, and the feature was preserved. I tracked the metric for two more quarters to confirm the baseline held.

Bar Raiser evaluation
Proactively surfaced insight — not asked, not prompted
Owned the decision loop: from signal to experiment to post-launch tracking
Customer impact validated through behavioural metric, not stakeholder opinion
Held position under pushback — Have Backbone aligned to Customer Obsession
Amazon debrief · DS loop · Bar Raiser evaluation Raises Bar
Leadership Principle: Customer Obsession
Strong signal. Raises the bar.
Proactively identified customer risk before roadmap was locked — strong ownership signal.
Designed and executed holdout experiment; did not rely on PM to act on a slide.
Customer impact validated through repeat-purchase behaviour over multiple quarters.
Pushed back on PM decision with data and committed to outcome tracking — LP-consistent.
interview101.com · Customer Obsession · Amazon DS · Bar Raiser debrief reference
Run your story through these three questions
1
Did you measure what happened to customers after the decision was made?
If not, you influenced a meeting — you did not demonstrate Customer Obsession.
2
Did you proactively surface this insight, or wait to be asked?
Reactive analysis is table stakes — Amazon DSs are expected to own the signal.
3
Can you name a specific customer behaviour metric that moved as a result?
Stakeholder approval is not a customer outcome — the Bar Raiser will push past it.
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 Data Scientist report →
Other questions from the same loop
Each video covers a different competency tested in the Amazon Data Scientist loop
Explore the full Amazon Data Scientist prep hub