How to Answer: "Tell Me About a Time You Went Above and Beyond for a Customer (Amazon Customer Obsession)"
Customer Obsession is Amazon's first and most heavily weighted Leadership Principle. Nearly every Amazon loop includes at least one question probing it, and Bar Raisers return to it often.
Do you start from the customer and work backwards, or from your own roadmap and work forwards? They want proof you've sacrificed convenience, metrics, or short-term gains for a customer outcome. Use the STAR method.
Grade a STAR answer free
~30 seconds, no signup, no card. Paste an answer, get an instant score.
💡 What They're Really Asking
Do you start from the customer and work backwards, or from your own roadmap and work forwards? They want proof you've sacrificed convenience, metrics, or short-term gains for a customer outcome.
🎯 The Framework
Use the STAR method. Anchor the Situation in a specific customer's problem, make the Action show you working backwards from their need, and land a Result measured in customer terms first, business terms second.
✅ Do's and ❌ Don'ts
✅ Do
- Name a specific customer (or segment) and the concrete pain they felt
- Show how you discovered the need — direct contact, support tickets, watching real usage
- Include a moment where the customer's interest beat an internal convenience or metric
- Measure the result from the customer's side: time saved, problem gone, trust kept
- Show genuine empathy plus action — feelings alone don't pass the bar
❌ Don't
- Don't tell a generic "good service" story — Amazon wants above-and-beyond, not adequate
- Don't define the customer vaguely; internal customers count, but name them
- Don't make the story about hitting YOUR metric that happened to help customers
- Don't exaggerate heroics — Bar Raisers drill into details
- Don't forget the longer-term outcome: did the fix become standard practice?
📝 Example Answer
How would your own answer score?
Paste a STAR answer below and get instant, specific feedback — free, no signup.
💎 Pro Tips
Amazon interviewers ask "how did you know what the customer wanted?" — have the discovery mechanism ready
Stories where you fixed something for customers who hadn't complained yet score especially well
Quantify in customer terms first; revenue impact is supporting evidence, not the headline
Practice this with OfferStory AI in strict STAR order — Amazon explicitly evaluates structure
Frequently Asked Questions
Does an internal customer count for Customer Obsession?
Yes — another team that consumes your work is a customer. But if you have an end-customer story of similar strength, prefer it; it maps more directly to the principle.
How many Customer Obsession stories should I prepare for Amazon?
Two. It's the most-asked LP, and follow-up questions may exhaust your first story. Make them different in kind — one reactive (fixing a problem) and one proactive (anticipating a need).
What if my role never touched customers?
Work backwards to whoever ultimately used your output — internal teams, downstream systems with end users. Show that you sought out that contact rather than waiting for requirements.
Ready to see how your answer scores?
Free AI grader — ~30 seconds, no signup, no card required.
This is one of Amazon's Leadership Principles. See all of them in one place, or read the full Amazon interview overview.