Top 40 Amazon Behavioral Interview Questions (2026)

Amazon’s behavioral interviews are built entirely around its 16 Leadership Principles, and every question maps to one of them. Below are 40 questions Amazon actually asks, grouped by principle, plus three complete STAR answers you can model yours on. If you prepare two stories per principle, you will cover more than 90% of what any Amazon loop throws at you.

How Amazon’s Behavioral Interviews Work

Amazon interviewers are trained to test specific Leadership Principles, take verbatim notes, and grade your answers against a bar: was this candidate better than half of the people currently in the role? Each interviewer in your loop (usually 4-6 people) is assigned 2-3 principles. One of them, the Bar Raiser, is a trained interviewer from outside the team with veto power.

Two things follow from this. First, you cannot wing it: interviewers will drill into your story with follow-ups (“What was the metric? What did your manager say? What would you do differently?”). Second, generic answers fail. Amazon wants specific situations, real numbers, and your individual contribution, not your team’s.

You can read the official list of all 16 principles on Amazon’s Leadership Principles page. Here are the questions each one generates.

The 40 Questions, Grouped by Leadership Principle

Customer Obsession

1. Tell me about a time you went above and beyond for a customer.
2. Describe a time you had to balance customer needs against business needs.
3. Tell me about a time you received tough customer feedback. What did you do?

Ownership

4. Tell me about a time you took on something outside your job description.
5. Describe a time you saw a problem nobody owned and fixed it.
6. Tell me about a time you made a short-term sacrifice for a long-term gain.

Invent and Simplify

7. Tell me about the most innovative thing you’ve done.
8. Describe a time you simplified a complex process.
9. Tell me about a time you found a creative solution with limited resources.

Are Right, A Lot

10. Tell me about a time you made a decision with incomplete data.
11. Describe a time you were wrong. How did you find out, and what did you do?
12. Tell me about a decision your team disagreed with that turned out well.

Learn and Be Curious

13. Tell me about a time you learned a skill quickly because the job demanded it.
14. What’s something you taught yourself in the last year, and why?

Hire and Develop the Best

15. Tell me about a time you coached someone who was underperforming.
16. Describe a time you gave difficult feedback to a colleague or report.
17. Tell me about the best hire you ever made. What did you see?

Insist on the Highest Standards

18. Tell me about a time you refused to ship or accept work that wasn’t good enough.
19. Describe a time you raised the quality bar on your team.
20. Tell me about a time you were dissatisfied with your own work.

Think Big

21. Tell me about a time you proposed something bold that others thought was unrealistic.
22. Describe your biggest professional bet. How did it play out?

Bias for Action

23. Tell me about a time you made a decision quickly without full information.
24. Describe a time speed mattered more than perfection.
25. Tell me about a calculated risk you took. What was the outcome?

Frugality

26. Tell me about a time you delivered results with a limited budget.
27. Describe a time you did more with less.

Earn Trust

28. Tell me about a time you had to rebuild trust with a colleague or stakeholder.
29. Describe a time you admitted a mistake publicly.
30. Tell me about a time you disagreed with your manager. What did you do?

Dive Deep

31. Tell me about a time you dug into data and found something everyone else missed.
32. Describe a time a surface-level explanation didn’t satisfy you.

Have Backbone; Disagree and Commit

33. Tell me about a time you strongly disagreed with a decision but committed to it anyway.
34. Describe a time you pushed back on a senior leader.
35. Tell me about a time you defended an unpopular position.

Deliver Results

36. Tell me about a time you delivered a project under serious time pressure.
37. Describe a time you missed a deadline or goal. What happened?
38. Tell me about your most significant professional accomplishment.

Strive to Be Earth’s Best Employer / Success and Scale Bring Broad Responsibility

39. Tell me about a time you improved your team’s morale, safety, or working conditions.
40. Describe a decision where you weighed impact on people beyond your immediate team.

3 Full STAR Example Answers

Model the structure, not the content. Your stories must be yours; interviewers probe details and will notice a borrowed one immediately.

Example 1: Ownership — “Tell me about a time you took on something outside your job description.”

Situation: “At my last company, a mid-size logistics SaaS, our churn reports were assembled manually by whoever had time, and they were consistently two weeks late. I was a product analyst; reporting infrastructure wasn’t my job.”

Task: “Leadership was making retention decisions on stale data. I decided that if nobody owned it, I would.”

Action: “I spent two weekends building an automated churn dashboard pulling directly from our billing and usage databases. I validated the numbers against three months of manual reports to earn finance’s trust, then presented it to the VP of Product with a proposal to kill the manual process.”

Result: “The dashboard became the company’s standard churn view. Report lag went from 14 days to same-day, and within a quarter we caught a churn spike in our SMB segment early enough to launch a save campaign that recovered about $180K in ARR. I was later given formal ownership of retention analytics.”

Example 2: Have Backbone; Disagree and Commit — “Tell me about a time you strongly disagreed with a decision but committed anyway.”

Situation: “My engineering director decided to rewrite our checkout service in a new framework mid-quarter. I believed the migration risk during our peak season was too high.”

Task: “As the tech lead on checkout, I had to either change the decision or make it succeed.”

Action: “I put my objection in writing with data: our error budget, the two prior migrations that had slipped, and a proposal to delay eight weeks. The director heard me out and still decided to proceed for valid platform reasons. So I committed fully. I built the rollback plan, set up canary deployments at 1% of traffic, and personally reviewed every migration PR.”

Result: “The migration shipped one week late but with zero customer-facing incidents, largely because of the canary setup I insisted on. My director later told me the disagreement made the plan better. That’s the point of the principle: dissent hard, then execute like it was your idea.”

Example 3: Deliver Results — “Tell me about a time you delivered under serious time pressure.”

Situation: “Three weeks before a contractual go-live with our largest client, a security audit found our authentication flow didn’t meet their SSO requirements. Missing the date carried a six-figure penalty.”

Task: “I owned the integration and had to close the gap without breaking existing customers.”

Action: “I cut scope ruthlessly: we deferred two nice-to-have features, negotiated with the client’s security team to accept a phased rollout, and I paired daily with our identity engineer instead of communicating through tickets. I sent a one-paragraph status update to both leadership teams every evening so nobody was surprised.”

Result: “We went live on the contract date with the compliant SSO flow. The client renewed at a 40% larger contract the following year, and our daily-status format became the team template for at-risk projects.”

Tips From the Other Side of the Table

Prepare 10-12 stories, not 40 answers. One strong story usually covers 3-4 principles. Build a matrix: stories down the side, principles across the top, and make sure every principle has at least two checkmarks. Interviewers in the same loop compare notes, so don’t reuse a story across interviews if you can avoid it.

Use “I,” not “we.” The single most common failure at Amazon is describing team accomplishments without isolating your contribution. When a candidate says “we decided,” a trained interviewer immediately asks “what did you do?” Beat them to it.

Quantify everything. Revenue, percentages, time saved, headcount, ticket volume. Approximations are fine; vagueness is not.

Have a real failure story. “My weakness is perfectionism” gets you rejected. Amazon explicitly probes for times you were wrong (Are Right, A Lot; Earn Trust). A candid failure with a clear lesson scores higher than a disguised win.

Expect follow-up drilling. Amazon interviewers routinely ask five or more follow-ups on one story. If your story can’t survive “why,” “how exactly,” and “what was the number,” it isn’t ready. Practicing these answers out loud under questioning is what separates prepared candidates from rehearsed ones, and Alex, an AI interview coach lets you run realistic Amazon-style mock interviews with follow-up questions until your stories hold up.

Match story altitude to the level. L4-L5 candidates can tell execution stories. L6+ candidates need stories about influencing across teams, making judgment calls with ambiguity, and raising the bar for others.

FAQ

How many Leadership Principles should I prepare for?

All 16, but weight your prep. Customer Obsession, Ownership, Deliver Results, Dive Deep, and Disagree and Commit come up in nearly every loop. The two newest principles (Earth’s Best Employer, Broad Responsibility) appear mostly in senior and people-manager interviews.

Can I reuse the same story in different interviews during the loop?

Avoid it. Interviewers debrief together and compare notes, and a repeated story reads as thin experience. Prepare enough stories that each interviewer hears fresh material.

How long should a STAR answer be?

About two minutes uninterrupted, then let the interviewer drive with follow-ups. Spend most of that time on Action and Result; candidates who spend 90 seconds on Situation lose the room.

Does Amazon ask behavioral questions in technical interviews too?

Yes. Even coding and system design rounds at Amazon typically open with one or two Leadership Principle questions. Never walk into any Amazon interview without behavioral stories ready.