If you're preparing for an Amazon interview — for any role, at any level — the single biggest factor in whether you get an offer isn't your technical skills, your resume, or even the questions you get. It's how well your stories map to Amazon's 16 Leadership Principles (LPs).

Every Amazon interviewer is trained to evaluate you against the LPs specifically. They take notes using an LP-tagged rubric. Your bar raiser consolidates that LP-tagged feedback in the debrief. A "strong no" on Customer Obsession beats two "solid yeses" on obscure technical signals, every time.

This guide is practical, not theoretical. We'll skip the corporate summary of what each LP "means" (Amazon's own site covers that) and focus on what actually matters in the interview: which LPs are weighted most, how your stories get graded, and the specific structure that separates a weak answer from a hired one.

The 16 Leadership Principles — but only 6 really matter in the interview

Amazon officially lists 16 LPs. In practice, the ones you'll be asked about in a standard behavioral loop are consistently the same 5–6. The others show up in bar raiser rounds or for specific roles.

The "always on" LPs (expect 1–2 questions each)

Customer Obsession — Leaders start with the customer and work backward. Asked in nearly every loop.
Ownership — Leaders act on behalf of the entire company, not just their team. They never say "that's not my job."
Dive Deep — Leaders operate at all levels and stay connected to the details. They audit frequently. They're skeptical when metrics and anecdotes disagree.
Deliver Results — Leaders focus on the key inputs and deliver with the right quality and on time. Despite setbacks, they rise to the occasion.

The "frequently tested" LPs

Bias for Action — Speed matters. Many decisions and actions are reversible; you don't need extensive study.
Are Right, A Lot — Strong judgment. Good instincts. Actively seek out diverse perspectives to disconfirm your own beliefs.
Earn Trust — Listen attentively, speak candidly, treat others respectfully. Even when it's awkward or embarrassing.
Have Backbone; Disagree and Commit — Respectfully challenge decisions you disagree with, even when uncomfortable. Once a decision is made, commit fully.

The "sometimes tested, role-dependent" LPs

Invent and Simplify — Heavy for product and eng roles, lighter for operations.
Learn and Be Curious — Often embedded in other questions rather than a standalone prompt.
Hire and Develop the Best — Expected for any role with direct reports or mentorship scope.
Insist on the Highest Standards — Often combined with Deliver Results.

The newer LPs — Strive to be Earth's Best Employer and Success and Scale Bring Broad Responsibility — are rarely asked directly in 2026 loops, though they may appear in executive interviews.

How Amazon interviewers actually grade your answers

Amazon uses a structured rubric that scores you on four dimensions for every LP story. Knowing this rubric is the single biggest edge you can get, because most candidates unknowingly fail on the last two dimensions:

Specificity — "We had a customer complaint" is useless. "A top-10 seller in our marketplace hit a 14% refund rate in Q3 2024, triggering our account-health threshold" is scorable.
Ownership of action — Did you act, or did "the team" act? Use "I" deliberately. Give the team credit, but be clear on what you personally did.
Measurable impact — Numbers or a defensible estimate. "Improved customer satisfaction" is not an impact. "Reduced ticket volume 34% QoQ, saving ~$180K in CX headcount" is.
Self-reflection — What would you do differently? This is where 60% of candidates lose points. Interviewers want to see you learned something specific, not just that you succeeded.

A story that scores high on 1 and 2 but fails 3 and 4 is graded as "inclined no." This is why candidates frequently walk out feeling they nailed the interview and get rejected — they told good stories, but not gradable stories.

The STAR+R structure that works for Amazon

Standard STAR (Situation, Task, Action, Result) is a good skeleton but misses what Amazon specifically wants. Use STAR+R:

Situation (15 seconds) — Where, when, what role. Company name, rough timeframe, scope. Don't over-explain; the interviewer will ask if they need more.
Task (15 seconds) — What specifically was your responsibility? Distinguish it from "my team's task." If you were the one on the hook, say so.
Action (60–90 seconds, the bulk) — What you did, step by step. Use "I" verbs: "I analyzed…", "I decided…", "I proposed…", "I escalated…". Include at least one tradeoff or hard judgment call.
Result (20–30 seconds) — Quantified outcome. Include both the headline metric and at least one downstream effect (retention, cost, follow-on project, etc.).
Reflection (15–20 seconds) — What you learned and would do differently. This is the unique Amazon ask. Don't say "nothing, it went great." Nothing ever goes perfectly; interviewers who hear that mark you down on Dive Deep and Learn and Be Curious.

Story inventory: how many you actually need

The math: a typical Amazon loop is 5 rounds, 2 LP questions per round, so 10 behavioral answers. You can reuse stories across LPs (recommended — one good story often hits 3–4 LPs from different angles), but you cannot reuse the same story twice with the same interviewer.

Aim for:

8–10 core stories, each polished to under 3 minutes, each confidently tagged to 3–4 LPs.
2–3 failure/conflict stories — for Earn Trust, Disagree and Commit, Are Right A Lot. These are the ones most candidates underprep.
1–2 "I changed my mind based on data" stories — explicitly for Are Right, A Lot.
1 story where you advocated up and got overruled, then committed — this is the Disagree and Commit gold standard.

The 5 most common answer patterns that kill your interview

The "we" pronoun trap. You say "we decided", "we built", "we shipped". Interviewer has no idea what you did. Use I. Add we sparingly for context.
The conflict-avoidant story. Every single candidate has a story about disagreeing with a peer. Very few have a good one about disagreeing with their manager or skip-level. The latter is what Amazon is actually testing.
The unquantified win. "It went really well" without numbers. Even "roughly 20% faster, based on our internal dashboard" is better than nothing.
The humble-brag reflection. "If I had to do it again, I'd probably just do it faster." That's not a reflection, that's a compliment to yourself. Real reflection names a specific thing you missed or got wrong.
Question mismatch. You get asked "tell me about a time you disagreed with your manager" and you tell a story about disagreeing with a peer because it's your only polished story. The interviewer notes "did not answer the question" — that's an auto-fail, regardless of story quality.

The 2-week Amazon prep plan

This is the minimum effective dose. Less than this and you're gambling; more than this and you're overfitting.

Week 1 — Story inventory and first pass

Day 1–2: List every significant project from the last 4–5 years. Pick 10 that have quantified outcomes, a real hard decision, or a meaningful conflict. These are your raw material.
Day 3–4: Write each story in STAR+R format. No shortcuts — fully written out. Aim for 400 words per story. You will cut this heavily, but first write the long version.
Day 5–6: Tag each story to 3–4 LPs. If you can't tag any story to Dive Deep or Are Right A Lot, go find one — those are frequently tested and lacking them is a known failure pattern.
Day 7: First out-loud run-through. Record yourself. Listen back. Almost every story will be too long and too vague.

Week 2 — Pressure-test under real conditions

Day 8–10: Tighten each story to under 3 minutes. Cut anything that isn't situation, action, impact, or reflection. This is the single biggest improvement most candidates make.
Day 11–12: Practice under audio pressure. Record, not type. The muscle memory of saying it out loud, with a 90-second ticker in your head, is what you need on interview day. Mock interviews with friends work; AI mock interviews (honest plug — this is exactly what InterviewPilot is built for) work even better because you can run 5 in an evening.
Day 13: Review your weakest 2 stories. Rewrite the action section. Add a real reflection if it's weak.
Day 14: Light review only. Don't cram new material the day before. Sleep is worth more than a 5th rehearsal of a story you already know.

What if you have less than a week?

Compressed plan, assuming a 4–5 day window:

Pick your 6 strongest stories. Tag each to 3 LPs. Don't try to cover all 16.
Focus on Customer Obsession, Ownership, Dive Deep, Deliver Results, Bias for Action. These are 80%+ of what you'll be asked.
Practice out loud, with a timer, at least 10 reps total. Reps matter more than polish at this point.
Explicitly prepare one story about disagreeing with a manager and one about failure. These are the ones that catch most candidates flat-footed.

Final point: what Amazon is actually hiring for

Under the surface of the LPs, Amazon is evaluating two things: will this person act like an owner, and will this person make decisions fast enough. Every LP question is a different angle on those two. When in doubt about which LP to lean into for an ambiguous question, lean into Ownership or Bias for Action — you'll rarely be wrong.

The interview is not an IQ test. It's not a knowledge test. It's a pattern-matching exercise where trained interviewers are checking whether you've demonstrated behaviors that map to their principles. Specific stories, specifically told, specifically reflected on.

If you want realistic audio practice against Amazon-style prompts with STAR+R scoring built in, InterviewPilot has company-specific question sets for Amazon loops — behavioral, bar-raiser, and role-specific. Your first 3 sessions are free.