Amazon's interview process is unlike any other major tech company's. Google tests algorithms. Meta tests product sense. Apple tests domain depth. Amazon tests character — and they do it through a structured behavioral framework called the Leadership Principles.
This isn't performative culture talk. Amazon interviewers are trained to probe for LP-aligned behavior, they use a standardized scoring rubric, and LP feedback carries significant weight in the hiring committee debrief. Candidates who understand the system go in with a structural advantage. Candidates who don't often get screened out despite strong technical skills.
This guide covers all 16 LPs with real interview questions, what interviewers are actually measuring, and full STAR examples for the highest-frequency principles.
Why Amazon Is LP-Obsessed
Jeff Bezos built Amazon's culture around the idea that principles, not rules, scale. Rules require enforcement. Principles, if internalized, guide decisions autonomously. Amazon has 16 principles because they found rules created local optimization — people followed the rule and missed the intent. Principles require judgment.
In practice, this means that behavioral interviews at Amazon aren't a formality. A strong technical candidate with weak LP signals will not get an offer. Interviewers at Amazon are explicitly asked: "Would you be okay if this person was on your team?" LP fit is the core of that question.
In 2021, Amazon added two new LPs — Strive to be Earth's Best Employer and Success and Scale Bring Broad Responsibility — bringing the total to 16. As of 2026, both appear in interviews for senior and above roles, and increasingly for mid-level positions.
The STAR Method, Amazon-Style
STAR stands for Situation, Task, Action, Result. It's a widely used behavioral interview framework. Amazon uses it, but with a critical twist: results must be quantified whenever possible.
| Component | What Amazon Wants | |-----------|-------------------| | Situation | Specific context — team size, timeline, stakes. Not vague. | | Task | Your specific responsibility, not the team's goal. | | Action | What you did. Use "I," not "we." Show your reasoning. | | Result | Quantified outcome. Numbers, percentages, revenue, time saved. |
The most common mistake candidates make is using "we" throughout. Amazon interviewers are scoring you, not your team. When you say "we shipped the feature," the interviewer hears "I don't know what I personally contributed."
A second Amazon-specific requirement: explain your reasoning. Don't just say what you did — say why you chose that approach over alternatives. Amazon values judgment, not just execution.
All 16 Leadership Principles: Questions, Signals, and Examples
1. Customer Obsession
Leaders start with the customer and work backwards.
Interview questions:
- "Tell me about a time you made a decision that was unpopular internally but was the right call for the customer."
- "Describe a situation where you advocated for a customer when it wasn't in your team's immediate interest."
What Amazon is scoring: Do you prioritize customer outcome over internal convenience? Can you give a specific example where you pushed back on a decision because it would hurt the customer?
STAR example (abbreviated):
S: Our team was planning to deprecate a legacy API endpoint to reduce maintenance burden. About 12% of our external customers were still using it.
T: I was the tech lead for the migration project and had final sign-off on the cutoff date.
A: Rather than enforce the deadline, I pulled the customer usage data myself and identified which customers were still on the old endpoint. I reached out to their developer contacts directly, offered migration support, and pushed the cutoff back 45 days. I also built a lightweight migration guide that reduced onboarding time from 3 days to about 4 hours.
R: We retained all 12% of affected customers. Two of them ended up upgrading to our paid tier within 90 days of the migration. The internal team was frustrated at the delay, but the customer retention data made the case clearly.
2. Ownership
Leaders act on behalf of the entire company, not just their team.
Interview questions:
- "Tell me about a time you took on something outside your job description because you saw it needed to be done."
- "Describe a time you noticed a problem that wasn't your responsibility and what you did about it."
What Amazon is scoring: Did you step up without being asked? Did you see a problem as yours to solve, even when it technically wasn't? Ownership stories often involve friction — you're looking for candidates who ran toward a problem, not away from it.
STAR example (abbreviated):
S: During a quarterly review, I noticed that our on-call runbook hadn't been updated in 18 months. We had three new services running in production with no documented failure modes.
T: This wasn't my team's runbook — I was a guest on that on-call rotation while helping with a cross-team migration.
A: I flagged it in the team Slack and when nobody picked it up in a week, I drafted the missing sections myself, documented the failure modes for all three new services, and ran a 30-minute review session with the team to validate my understanding.
R: The following quarter, the team had their fastest incident resolution time in two years. The runbook I wrote was directly credited in the post-mortem for two of the three incidents resolved that quarter.
3. Invent and Simplify
Leaders expect and require innovation and find ways to simplify.
Interview questions:
- "Tell me about a time you simplified a process that was unnecessarily complex."
- "Describe a situation where you came up with an innovative solution to a problem others had accepted as intractable."
What Amazon is scoring: Real simplification stories, not incremental improvement stories. Amazon wants to see that you question the premise, not just optimize the existing approach.
STAR example (abbreviated):
S: Our deployment process required four manual approval steps across three teams, taking an average of 2.5 days from code merge to production.
T: I was asked to reduce deployment friction as part of an engineering velocity initiative.
A: Instead of automating the approvals (the obvious path), I audited why each approval existed. Two of the four turned out to be historical — nobody knew why they were still there. I removed them, converted the third to an async automated check, and kept only the security review as a required gate. I ran the proposal through a risk review with our security team first.
R: Average time to production dropped from 2.5 days to 4 hours. We deployed 3x more frequently in the following quarter with zero increase in production incidents.
4. Are Right, A Lot
Leaders have strong judgment and good instincts.
Interview questions:
- "Tell me about a time you had to make a high-stakes decision with incomplete information."
- "Describe a time you disagreed with the direction your organization was heading and what you did."
What Amazon is scoring: Quality of judgment, not just outcome. They want to understand how you process information and form views. Be prepared to walk through your reasoning in detail.
5. Learn and Be Curious
Leaders are never done learning.
Interview questions:
- "Tell me about something technical you taught yourself in the past year and why."
- "Describe a time you realized you were wrong about something important and how you updated your thinking."
What Amazon is scoring: Intellectual humility and initiative. They want candidates who actively close their own skill gaps and change their minds when the evidence demands it.
6. Hire and Develop the Best
Leaders raise the performance bar with every hire and develop people.
Interview questions:
- "Tell me about the best hire you ever made and what you saw in them."
- "Describe how you've helped someone on your team grow in their career."
What Amazon is scoring: Do you invest in people, or just delegate tasks to them? Senior candidates especially need a strong story here. Weak answers describe logistical management. Strong answers describe deliberate development.
7. Insist on the Highest Standards
Leaders have relentlessly high standards that others may find unreasonably high.
Interview questions:
- "Tell me about a time you refused to cut corners despite pressure to do so."
- "Describe a situation where you raised the quality bar on your team."
What Amazon is scoring: Are your standards genuinely high, or do you lower them under pressure? The strongest answers involve a moment of friction — someone else pushed back on your standards, and you held the line.
8. Think Big
Leaders create and communicate a bold direction.
Interview questions:
- "Tell me about a time you proposed a vision or direction that was bigger than what the team was originally thinking."
- "Describe a project where you had to get others aligned around an ambitious goal."
What Amazon is scoring: Can you operate at a strategic level? Think Big stories should involve something that felt risky or unconventional at the time, not just an aggressive timeline.
9. Bias for Action
Speed matters in business. Many decisions are reversible.
Interview questions:
- "Tell me about a time you had to make a quick decision without having all the data you wanted."
- "Describe a situation where you moved faster than others thought was wise and it paid off."
What Amazon is scoring: Do you default to action or analysis? Amazon values decisiveness, especially for reversible decisions. Strong answers show calculated risk-taking, not recklessness.
10. Frugality
Accomplish more with less.
Interview questions:
- "Tell me about a time you achieved a goal with fewer resources than you thought you'd need."
- "Describe a situation where you found a creative way to reduce cost without reducing quality."
What Amazon is scoring: Resourcefulness. This LP comes up most often in interviews for roles that involve budget ownership or engineering infrastructure decisions. The best stories involve an unconventional constraint that led to a better solution.
11. Earn Trust
Leaders listen attentively and are vocally self-critical.
Interview questions:
- "Tell me about a time you made a mistake and how you handled it."
- "Describe a situation where you had to rebuild trust with a teammate or stakeholder after something went wrong."
What Amazon is scoring: Self-awareness and accountability. Amazon is explicitly testing whether you can admit fault, explain what you learned, and demonstrate that you've changed your behavior. Candidates who can't give a genuine mistake story are a red flag.
12. Dive Deep
Leaders operate at all levels and stay connected to the details.
Interview questions:
- "Tell me about a time you had to get into the weeds on a problem that wasn't normally in your scope."
- "Describe a situation where a data point surprised you and what you did with that information."
What Amazon is scoring: Intellectual engagement with detail. Dive Deep stories often involve catching something that would have been missed by someone who stayed at a high level. The key signal is curiosity-driven, not micromanagement-driven.
STAR example (abbreviated):
S: We were planning to sunset a feature based on usage data that showed less than 1% of users had interacted with it in the past 90 days.
T: I was the PM for the team and owned the deprecation decision.
A: Before signing off, I dug into which users made up that 1%. It turned out they were all enterprise accounts — our highest-value tier. I ran an analysis and found that while 1% of users used the feature, those users represented 22% of our annual contract value.
R: We paused the deprecation, interviewed six of those enterprise customers, and rebuilt the feature with a new interface tailored to their workflow. It became a key differentiator in two new enterprise sales the following quarter.
13. Have Backbone; Disagree and Commit
Leaders respectfully challenge decisions they disagree with, then commit once a decision is made.
Interview questions:
- "Tell me about a time you strongly disagreed with a decision your manager made and what you did."
- "Describe a situation where you pushed back on a direction and ultimately lost the argument — how did you handle it?"
What Amazon is scoring: Two things simultaneously: that you push back constructively (not silently), and that you commit fully once the decision is made. Interviewers often probe both ends of this — they want to see the disagreement and the commitment.
14. Deliver Results
Leaders focus on the key inputs and deliver with the right quality and in a timely fashion.
Interview questions:
- "Tell me about a time you had to fight through obstacles to deliver on a commitment."
- "Describe the most challenging deadline you've hit and what it took."
What Amazon is scoring: Execution under pressure. This LP rewards candidates who can identify what matters most, remove blockers efficiently, and close. Every Deliver Results story should end with a number.
STAR example (abbreviated):
S: We were six weeks from a contractual product launch deadline with a key enterprise customer. Three weeks in, our primary vendor had an outage that wiped out two weeks of work.
T: I was the engineering manager responsible for on-time delivery.
A: I immediately re-scoped the project with the product team to identify which features were contractually required versus which were nice-to-have. We cut three non-contractual features and moved two engineers from another project to cover the gap. I set daily standups and a shared tracking doc so every blocker was visible.
R: We launched 3 days ahead of the revised deadline. The customer signed a two-year renewal eight weeks after launch.
15. Strive to Be Earth's Best Employer
Leaders work to create a safer, more productive, higher-performing work environment.
Interview questions:
- "Tell me about a time you improved the working conditions or culture of your team."
- "Describe how you've handled a situation where a team member was struggling."
What Amazon is scoring: Empathy with accountability. This LP is common in manager and senior IC loops. Strong answers show proactive investment in team health, not just reactive management.
16. Success and Scale Bring Broad Responsibility
Amazon's success brings greater responsibilities to the world.
Interview questions:
- "Tell me about a time you made a decision with significant downstream impact on others outside your team."
- "Describe a situation where you considered the broader societal or ethical implications of something you were building."
What Amazon is scoring: Systems thinking and ethical awareness. This LP shows up most often in senior and principal-level interviews. Amazon is looking for candidates who think beyond their immediate business KPIs.
Quick Reference Table
| Leadership Principle | Most Common Question | Key Signal Amazon Wants | |---------------------|---------------------|------------------------| | Customer Obsession | "Time you advocated for the customer vs. internal pressure" | Customer-first decision-making under friction | | Ownership | "Time you stepped up outside your role" | Proactive, cross-boundary responsibility | | Invent and Simplify | "Time you simplified a complex process" | Questioning premises, not just optimizing | | Are Right, A Lot | "High-stakes decision with incomplete data" | Quality of reasoning, not just outcome | | Learn and Be Curious | "Something you taught yourself recently" | Intellectual initiative and humility | | Hire and Develop the Best | "Best hire you made or person you developed" | Deliberate investment in others | | Insist on Highest Standards | "Time you refused to cut corners" | Standards held under pressure | | Think Big | "Vision bigger than what team was thinking" | Strategic ambition backed by action | | Bias for Action | "Quick decision without full data" | Calculated decisiveness | | Frugality | "Achieved a goal with less than expected" | Resourcefulness and creative constraint | | Earn Trust | "A mistake you made and how you handled it" | Self-awareness and accountability | | Dive Deep | "Dug into details that others missed" | Curiosity-driven depth, not micromanagement | | Have Backbone; Disagree and Commit | "Disagreed with manager, then committed" | Push back + full commitment once decided | | Deliver Results | "Fought through obstacles to hit a deadline" | Execution under pressure, quantified outcomes | | Strive to Be Earth's Best Employer | "Improved team culture or helped someone struggling" | Proactive investment in team health | | Success and Scale Bring Broad Responsibility | "Decision with broad downstream impact" | Systems thinking, ethical awareness |
Common Mistakes in Amazon LP Interviews
Using "We" Instead of "I"
This is the most frequent failure. When you say "we built the system" or "our team decided," the interviewer cannot assess your individual contribution. Use "I" and be specific: "I made the call to..." "I proposed..." "I pushed back on..."
Not Quantifying Results
"The project was successful" is not a result. "We reduced error rate from 4.2% to 0.3% and cut customer-reported incidents by 60% in the following quarter" is a result. If you can't quantify the outcome, you need to dig deeper in your prep. Almost every outcome has a number attached — find it.
Generic Stories That Could Apply to Any Company
"Tell me about a time you showed customer obsession" answered with a generic customer service story does not demonstrate Amazon-level thinking. Amazon wants to see that your instinct is to start with the customer and work backwards — not just to be polite to customers. The framing and the stakes need to match the LP's actual definition.
Over-Crediting the Team
Generosity is a virtue in the real world. In an Amazon behavioral interview, excessive team credit is a liability. You can acknowledge collaboration without diluting your individual contribution: "I owned the final architecture decision, though I ran the options by the team before committing."
Preparing Too Few Stories
Candidates who prep five to seven stories and try to reuse them for every question get caught in loops. Amazon interviewers will ask follow-up questions that require you to go deeper. If your story is borrowed or vague, the follow-up will expose it.
How to Build Your Story Bank
How Many Stories Do You Need?
For an SDE2/L5 loop (typically 5 interviews, each covering 2–3 LPs): prepare 12–15 strong stories. For a senior/L6 or staff loop: prepare 18–20 stories, with stronger emphasis on cross-team scope, strategic decisions, and people development.
Story Selection Criteria
Each story should meet three criteria:
- It's specific — you can name dates, people, outcomes, and metrics.
- It's yours — you were the primary decision-maker or actor, not a supporting character.
- It covers multiple LPs — a great story about a hard deadline that involved an unpopular decision and required you to get into the technical details can cover Deliver Results, Have Backbone, and Dive Deep.
The Story Bank Template
For each story, write out:
- One-line summary: "Led migration of payment processor under 6-week deadline with 40% team turnover"
- LPs it covers: Deliver Results, Ownership, Frugality
- Full STAR writeout (250–300 words)
- Key metrics: the numbers you'll cite
- Likely follow-up questions: "What would you do differently?" "How did the team react?" "How did you handle the conflict?"
Prepare your stories in a doc. Review them 48 hours before the interview. Rehearse the openings and the metrics — those are the parts that go blank under pressure.
The Day-Before Rule
Don't try to memorize stories word for word. That produces stilted, unnatural answers. Instead, memorize: the three key metrics, the single most important decision you made, and the outcome in one sentence. The narrative will come naturally from those anchors.
Amazon's LP framework is demanding, but it's predictable. The interviewers are not trying to trick you. They're running a structured process designed to surface real behavior, not hypothetical responses. The candidates who do well are the ones who understand what's being measured and come in with specific, quantified, first-person stories that demonstrate genuine LP alignment.
Build the story bank. Practice the STAR structure with metrics. And when the interviewer asks "tell me more about that" — have the depth to go further.