Watch the full debrief

Two voices. One question. The insider reaction you don't usually see.

Also on YouTube 5–7 min 2026

Question decoded

"Tell me about a time you put customer needs first even under pressure"

Competency tested

Customer Obsession

Who asks it

Bar Raiser · HM · Peer

What they're really asking

What did you give up for the customer?

Answers compared

The answer that fails — and why

Candidate answer Does not raise the bar — Customer Obsession

On a project to revamp our checkout flow, we were two weeks from launch and QA flagged that the new UI was slower on older mobile devices. My manager wanted to ship anyway and address it post-launch, but I pushed to delay by three days so we could optimize the rendering path. I profiled the bottleneck, made the fix, and we shipped on the revised date. Customer satisfaction scores for the flow improved after launch, and we didn't get the spike in support tickets we had seen with previous releases.

Bar Raiser evaluation

⚑ No evidence of pressure absorbed — manager agreed quickly

⚑ Sacrifice unclear: a three-day slip is not a real trade-off named

⚑ Customer impact described in outcomes, not in candidate's stated motivation

Prefer to hear it? Watch the video for the two-voice delivery with live reaction commentary.

Amazon debrief · SWE loop · Bar Raiser evaluation Below Bar

Leadership Principle: Customer Obsession

Does not demonstrate Customer Obsession.

✗ No real sacrifice named — three-day slip lacks stakes or consequence

✗ Pressure described but not absorbed; manager capitulated without pushback

✗ Customer harm was hypothetical future tickets, not a named customer impact

✗ Motivation framed as quality hygiene, not a deliberate customer-first choice

interview101.com · Customer Obsession · Amazon SWE · 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

Six days before a major feature launch, our data pipeline silently started dropping roughly twelve percent of order-status events. Customers weren't seeing real-time updates. My manager wanted to ship and patch post-launch to protect the date. I disagreed — I pulled the error logs, quantified the drop rate, and walked him through what that meant for a customer waiting on a delivery. He pushed back hard. I held the position, documented the customer impact in writing, and escalated to the team lead with data. We delayed four days. I wrote a detection runbook so the same failure mode could never silently reach launch again.

Bar Raiser evaluation

✓ Specific metric cited — twelve percent drop rate, not vague degradation

✓ Real pressure absorbed — manager pushed back and candidate held position with data

✓ Customer harm named concretely, not framed as a hypothetical risk

✓ Mechanism created — runbook prevents recurrence, shows Ownership alongside Customer Obsession

Amazon debrief · SWE loop · Bar Raiser evaluation Raises Bar

Leadership Principle: Customer Obsession

Strong signal. Raises the bar.

✓ Quantified customer harm with data — twelve percent event drop rate named

✓ Held position against manager pressure; escalated with written documentation

✓ Customer impact framed from customer's perspective, not engineering metrics

✓ Created detection runbook — converted single incident into a repeatable mechanism

interview101.com · Customer Obsession · Amazon SWE · Bar Raiser debrief reference

Fix your answer before your loop

Run your story through these three questions

1

What did you give up or risk to put the customer first?

If nothing was at stake, you described good engineering, not Customer Obsession.

2

Did someone push back, and did you hold your position with data?

Pressure with no resistance is just a story about a decision, not a conviction.

3

Can you name the specific customer harm in concrete, human terms?

Vague risk language tells the Bar Raiser you were optimizing for the system, not the customer.

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 Software Development Engineer report →

More Amazon Software Development Engineer debriefs