Customer Focus: Going Above and Beyond and Shipping a Customer-Driven Change
AmazonSoftware Engineer · OnsiteLast updated
An Amazon behavioral question on customer focus: describe a time you went above and beyond for a customer, and a change you made that was driven by customer needs. It tests how you discover customer problems, act on them beyond expectations, and measure the impact.
This entry collects the loop's customer-focused leadership-principle prompts. Answer each part with a different real story, and expect the interviewer to probe for specifics: who the customer was, what you personally did, and what changed for them.
Clarifying Questions
- Does an internal customer, such as another engineering team that depends on my service, count, or should it be an external user?
- For Part 2, should the change be something I built myself, or can it be a change I drove that others implemented?
Part 1 — Going above and beyond for a customer
Tell me about a time when you went above and beyond for a customer.
What This Part Should Cover
- Who the customer was and what problem they faced
- The normal response compared with the extra steps you took, and why
- How you balanced the extra effort against other commitments and avoided unsustainable promises
- The outcome for the customer, with evidence
Part 2 — A customer-focused change
Tell me about a change you made that was customer-focused. What made you see the need, how did you decide on the change, and how did you know it worked?
What This Part Should Cover
- The customer signal that triggered the change
- How you weighed the change against other priorities and won support for it
- What you built or changed, and your specific role
- Measured impact on customers, and anything you adjusted afterwards
Hints
Hint 1
Beyond what, exactly: Be clear about what the normal expectation was, what you did beyond it, why you judged it worth the extra effort, and what it cost you or the team.
Hint 2
Start from evidence: Think about how you learned what customers actually needed (data, support tickets, conversations) rather than what the team assumed, and how you measured the result.
Follow-up questions
- Tell me about a time a customer asked for something you decided not to build. How did you handle it?
- How did you make sure the fix helped other customers with the same problem, not only the one who reported it?
- What did going above and beyond cost, and would you do it again?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.