Amazon Behavioral Interview Questions: The Complete LP Guide

Amazon behavioral interview questions are not optional filler in the loop. By the time you leave, you've answered 25 to 35 of them. Most candidates prepare for three.

Think about that gap for a second.

Every round, coding rounds included, burns roughly half its time on Leadership Principle questions. The Bar Raiser round burns nearly all of it. Every interviewer walks in pre-assigned two to three LPs and a set of follow-ups. The five-person panel collectively covers all 16 before you leave the building. That's the format. You don't get to skip Frugality because you liked Customer Obsession better.

This guide covers the six LPs that appear in almost every loop, what a strong STAR answer actually looks like, and the four patterns that sink otherwise capable candidates.

For the coding side of the loop, see the Amazon software engineer interview guide.

You'll Answer 30 Questions. Prepare 15 Stories.

Most loops run four to six rounds, 45 to 60 minutes each. Behavioral questions take roughly half the time per round.

Each interviewer is pre-assigned two to three LPs and asks two to three questions per principle. Four to nine behavioral questions per round, times five rounds.

The constraint that reshapes everything about your prep: interviewers compare notes before the debrief, and you cannot reuse the same story across rounds. If you tell your payment-migration story to the first interviewer, you cannot tell it to the Bar Raiser two hours later. The stories must be distinct. Prepare twelve to fifteen before you walk in.

Yes, twelve to fifteen. No, there is no shortcut. You are basically writing your professional memoirs before a job interview.

All 16 Leadership Principles, Translated

Amazon's Leadership Principles are the scoring rubric every interviewer uses. Published in the 1990s, expanded in 2021 with two additions (principles 15 and 16). Every question maps to one of these. Every score maps to one of these. You cannot out-charm the rubric.

#	Principle	What the interviewer is really asking
1	Customer Obsession	Did you start from the customer's need or rationalize backward?
2	Ownership	Did you act on something outside your assigned scope?
3	Invent and Simplify	Did you find a meaningfully simpler path?
4	Are Right, A Lot	How do you sharpen your judgment and update it?
5	Learn and Be Curious	What have you deliberately learned and applied at work?
6	Hire and Develop the Best	How did you make the people around you stronger?
7	Insist on the Highest Standards	Where did you refuse to accept "good enough"?
8	Think Big	Did you set a goal others thought was too ambitious?
9	Bias for Action	Can you tell the difference between a reversible and irreversible decision?
10	Frugality	Did you accomplish more with fewer resources?
11	Earn Trust	Did you self-criticize publicly, or just privately in your head?
12	Dive Deep	Did you get into details everyone else delegated?
13	Have Backbone; Disagree and Commit	Did you push back on data, then fully commit to the outcome?
14	Deliver Results	Did you ship meaningful outcomes despite real obstacles?
15	Strive to Be Earth's Best Employer	How did you invest in the people around you?
16	Success and Scale Bring Broad Responsibility	Did you think about impact beyond your team?

Six LPs Show Up in Every Loop

Not every LP has equal probability. Customer Obsession, Ownership, Dive Deep, Deliver Results, Bias for Action, and Earn Trust appear in nearly every loop regardless of level or team.

Prepare two distinct stories for each of these six before you prep anything else. Then cover the remaining ten with at least one story each.

The most neglected group: Frugality, Have Backbone, Hire and Develop the Best, Insist on the Highest Standards, Success and Scale, and Strive to Be Earth's Best Employer. Candidates over-prepare Customer Obsession and Deliver Results, then go blank when the interviewer assigned Frugality asks about working with a limited budget. "Well... we didn't really have a budget conversation" is not a strong answer. Your Customer Obsession story will not save you in that room.

What Good Looks Like, Per Principle

Customer Obsession

Common questions:

• "Tell me about a time you worked backward from a customer need to build something."
• "Describe a time when a customer's stated request was different from what they actually needed."
• "Tell me about a time you pushed your team to prioritize the customer over an internal metric."

The test is whether you started from the customer or rationalized backward. A weak answer picks something you shipped and tacks on "the customer wanted this." A strong answer shows you discovered the need first, often against internal resistance, and the work followed from that discovery.

Strong STAR shape: Your team's retention metric looked fine. You read 300 support tickets personally, found a recurring friction point nobody had filed a bug for, built the fix yourself, and cut customer-reported churn 8% the following quarter. Customer outcome, not an internal win.

See also: the Customer Obsession interview guide.

Ownership

Common questions:

• "Tell me about a time you took on something outside your scope because you saw it needed to be done."
• "Describe a situation where you made a significant decision without your manager's input."
• "Tell me about a time you spotted a long-term risk your team wasn't thinking about."

The "outside your scope" clause is the whole signal. If your story describes doing your assigned job well, it fails Ownership. The story must show you noticed something that wasn't yours and acted on it anyway, without being asked. "I stayed late to finish my sprint tickets" is your job. It's not Ownership.

Our Ownership LP guide breaks down what separates a score of 3 from a score of 4.

Bias for Action

Common questions:

• "Tell me about a time you acted on incomplete information."
• "Describe a time you had to make a call without full consensus."
• "Tell me about a calculated risk you took and how you decided to take it."

Candidates confuse Bias for Action with recklessness. Moving fast and breaking things is not the LP. Amazon is asking whether you can identify when waiting costs more than acting. Reversibility is what matters. One-way doors (permanent consequences) warrant more data. Two-way doors (easily undone) warrant fast action. If your story doesn't name the reversibility, the interviewer cannot credit you for the judgment.

Dive Deep

Common questions:

• "Tell me about a time you dug into data because something didn't add up."
• "Describe a situation where you challenged your team's assumption and found a different root cause."
• "Tell me about a time you found a detail that changed your direction."

Dive Deep is about intellectual rigor past the first explanation. The story must show a specific data point or anomaly you found that others had delegated away, and a clear change in direction from what you uncovered. "I dug into the logs and something was off" scores a 2. What exactly was off? What did you find at layer three? That's the story.

For how this plays in the Bar Raiser round specifically, see the Dive Deep guide.

Earn Trust

Common questions:

• "Tell me about a time you openly admitted a mistake to your team or stakeholders."
• "Describe a time you gave feedback that was uncomfortable to deliver."
• "Tell me about a time you changed your position based on someone else's input."

Most candidates miss the "vocally self-critical" requirement. A strong Earn Trust answer shows you were wrong about something in public, not privately in your head. "I realized I had the wrong approach" is not enough. Showing that you said that to your team during a live project, absorbed the pushback, and moved on is the signal the interviewer writes down. Quietly updating your mental model in the shower does not count.

Deliver Results

Common questions:

• "Tell me about a time you delivered a project despite significant obstacles."
• "Describe a time you had to reprioritize to hit a key goal."
• "Tell me about a situation where you had fewer resources than needed and still shipped."

The word "despite" is doing a lot of work in that first question. A clean delivery story tells the interviewer nothing useful. They want your prioritization logic, not confirmation that you shipped. What did you cut? What did you push back on? Who did you disappoint to protect the actual goal?

See the Deliver Results guide for STAR structures at each level.

The Bar Raiser Is Testing Story Depth, Not Story Shape

The Bar Raiser is a trained interviewer from outside your target team. Their job is not to hire you for this role. Their job is to decide whether you raise Amazon's average bar. That is a materially different evaluation.

Bar Raisers probe past your prepared story. After your STAR answer, expect questions like:

• "What would you do differently?"
• "Who disagreed with your approach, and what was their argument?"
• "What data did you not have that would have changed your decision?"
• "What happened six months later?"

These follow-ups are not small talk. They separate candidates who lived the experience from candidates who rehearsed a narrative. If you only know the top-level answer, you will get stuck on the first one and it will be visible. You need four to five layers of depth for each story. The surface STAR shape gets you to the follow-up. The follow-up is where you're actually evaluated.

For the full Bar Raiser breakdown, see our dedicated guide.

Four Patterns That Kill Good Candidates

Using "we" throughout. Amazon evaluates you, not your team. Even in collaborative work, name your specific contribution: "I proposed," "I escalated," "I disagreed and explained why." Interviewers cannot assess individual contribution from "we built." Engineers are trained to default to "we" because it feels humble. In this specific room, it reads as evasion. Your feedback write-up has your name on it, not your team's.

Front-loading the situation. Most STAR answers spend 60% of their time on Situation and Task, the least-evaluated parts. The Action section is where you live or die. Target 15% for S+T, 60% for Action, 25% for Result. If you find yourself three minutes in and still explaining the context, you are spending time in the wrong place.

Picking safe, small stories. A story about fixing a minor logging bug demonstrates nothing at the LP level. Interviewers need enough evidence to write "Strong Hire" in the feedback form. Small stories don't give them the raw material. Use the highest-stakes experience you have for each principle. The instinct to pick a "safe" story is understandable. It's also a reliable way to score a 2.

Gaps on the neglected LPs. If your assigned interviewer probes Frugality and Have Backbone and you only prepared Customer Obsession and Deliver Results stories, you score on two dimensions and gap out on the rest. Cover all sixteen before your loop. No exceptions.

Amazon Behavioral Interview Prep: The Plan That Works

Start with your story inventory. List twelve to fifteen real experiences and tag each with the LPs it demonstrates. A good story covers two to three principles. If your list clusters around Customer Obsession and Deliver Results, fill the gaps before you polish anything.

For each story, write the STAR structure and then practice saying it out loud. Time yourself. The target is two to three minutes for the top-level answer plus five minutes of follow-up depth. If you can only tell it from written notes, you don't own it yet.

Practice with someone who will interrupt mid-story with "but what did the data actually say?" That is exactly what the Bar Raiser will do. SpaceComplexity offers on-demand behavioral mock interviews with rubric-based feedback, so you can find where your LP answers lose signal before the actual loop. Getting blindsided by a layer-three follow-up in a practice session is recoverable. Getting blindsided in the real thing is not.

Further Reading

• Amazon Leadership Principles, official list
• How to use Leadership Principles in your interview, About Amazon
• Amazon interview loop format, Amazon Jobs
• Learnings from conducting 1,000 Amazon interviews, Pragmatic Engineer
• Amazon (company), Wikipedia