Amazon Behavioral Interview Questions & the LP Bar

The behavioral bar at Amazon is not a single round you can save your energy for. The 16 Leadership Principles, Amazon's cultural rules for how employees are expected to act, are scored in every interview you sit, the coding and design rounds included. Your graph-algorithms interviewer is also grading whether your "tell me about a time you dug into a hard bug" answer showed the principle called Dive Deep. There is no soft round between the hard ones. Every round carries a behavioral grade alongside the technical one.

This lesson covers why the Leadership Principles carry so much weight and who the Bar Raiser is. Then the exact shape of answer that scores, with one worked example: the same story told well and told badly, side by side. The next two lessons go deeper, touring all 16 principles and then drilling a question bank.

What behavioral questions does Amazon ask?

Amazon behavioral interview questions almost always open with "Tell me about a time" and map to one Leadership Principle each. The ones a software loop repeats cover Customer Obsession, Ownership, Deliver Results, Dive Deep, and Bias for Action, answered in STAR shape. The list below groups the questions Amazon returns to under the principle each one scores.

Each group here shows one signature prompt; the wording shifts round to round but the principle behind it does not. The full set is grouped under every principle, with the follow-ups each one draws, in the question bank inside the guide. For the meaning of each principle see the 16 Leadership Principles, and for the pattern across companies, the behavioral interview questions hub.

Scored in Every Single Round

At most companies the behavioral interview is one slot, run by one person, walled off from the technical loop. Amazon does not work that way. Each of your four or five interviewers usually opens with 10 to 20 minutes of Leadership Principle questions before the technical problem. Some thread them across the round instead. Either way, each one files a behavioral grade. So a coding interviewer submits two verdicts on you. One on whether your solution was correct and clean. One on whether your story showed the principle they were assigned to probe.

Each interviewer is usually told to dig into one to three specific principles, so the loop fans out to cover most of the 16 across the day. On each principle you land below the bar, at the bar, or above it, and the read is subjective. There is no point-by-point rubric handed to interviewers. A concrete story is your only real lever.

The Amazon angle

One person in your loop is the Bar Raiser, a trained interviewer pulled from outside the hiring team. They have no stake in filling the seat, and they care about the principles above all. The Bar Raiser reads every interviewer's written notes before the debrief and runs that meeting. They also carry a veto on the hire that rarely needs firing. Google has no equivalent. Its hiring committee reviews paperwork after the fact and never sits in your interviews. You usually won't be told which of your interviewers holds the gavel, so treat all of them as if they could. Bring real Leadership Principle stories to every round, never just the one.

The Answer Shape That Scores

Amazon wants answers in STAR form. STAR is just four beats: situation, task, action, result. The trap is spending your two minutes evenly across them. Interviewers want roughly 80% of the answer on the Action and the Result, the parts that reveal what you did and what came of it. Keep the setup tight. A long Situation is the most common way a strong story turns into a rambling one.

Three habits separate a story that scores from one that flops, and all three are easy to drop under pressure.

The Amazon angle

The metrics rule is sharper at Amazon than almost anywhere because of who reads the notes. The Bar Raiser settles the hire from written feedback. A vote backed by "cut build time 40%, freed 200 engineer-hours a month" survives scrutiny. A vote backed by "delivered a great result" never does. Vague positive vibes evaporate by the time the interviewer is typing. So pre-load a real number onto every story before you walk in, even a rough one you can defend. The candidates who get cut on behavioral grounds rarely lacked good experiences. They lacked the figure that would have made an experience land in the debrief.

One Story, Two Ways

Take one real experience answered for the principle called Deliver Results. Most candidates reach for the version on the left on instinct. A raises-the-bar grade goes to the version on the right. Same underlying story. Only the telling changes.

The strong version also earns a fifth beat that Amazon rewards: what you learned, or would do differently. A clean win with no reflection reads flat and can even cost you on the principle called Learn and Be Curious. Close on the lesson.

The interviewer will not stop at the result. Expect a string of probes. Why chunk the backfill instead of throwing more machines at it? What did the rollback do if a chunk failed halfway? What would the on-call engineer say about being handed that runbook? Follow-ups mine the same story for depth. This is where back-pocket detail pays off, so have the layer below ready.

Build a Story Bank You Can Flex

A common mistake is preparing one story per principle, 16 in all. That way you arrive with 16 thin, half-remembered scripts and no depth in any of them. Prepare eight to ten strong stories instead. Each good story flexes across several principles depending on how you frame it. The checkout migration above is a Deliver Results story. Reframe it around the bottleneck hunt and it serves Dive Deep. Lead with the unattended runbook you built for the on-call and it serves Ownership.

Aim for about two solid stories on each high-weight principle, so that if an interviewer burns one with a question, you have a backup that fits. For software engineers the most-probed principles are Customer Obsession, which Amazon calls its north star, then Ownership, Deliver Results, Dive Deep, and Bias for Action. Weight your bank toward those.

The Amazon angle

The reuse strategy works at Amazon precisely because the principles are spread across the loop instead of crammed into one interview. Five interviewers each probe a different one to three principles, so over a day you might field a dozen distinct prompts. Score one story to a single principle and you run dry by the third round. A bank of eight to ten stories, each able to flex across three or four principles, leaves you with a fitting answer for almost any prompt. And every story stays deep enough to survive the follow-ups. Map each of your stories to the principles it can serve before the loop, so a question lands on a choice you already made instead of a scramble.

The 16 Principles, in Brief

The full list is below, with the last two added in 2021. The next lesson works through each principle in depth, what it really tests and where candidates fall down. Bolded ones carry the most weight in a software loop.