Amazon Interview Guide

Amazon is the one loop where the behavioural half can sink you outright. The Leadership Principles are not a warm-up before the real interview -- they are scored with the same seriousness as the code, every interviewer is assigned specific principles to probe, and a strong coder with thin LP answers is a common reject.

The coding bar itself is closer to "solid medium, cleanly implemented" than to Google's hard-problem ladder. Which means the marginal hour of preparation is often better spent on stories than on another hard graph problem.

Pitfalls

• Preparing code and not stories. Write out six to eight STAR stories in advance, each tagged to two or three principles. Improvising structure live is what makes LP answers ramble.
• Answering LP questions in the plural. "We decided..." scores nothing -- the Action step must be first person and specific. They are assessing you.
• Stories with no measurable Result. Attach a number or a concrete outcome. "It went well" is not a result.
• Reusing one story for every principle. Interviewers compare notes, and repetition reads as a thin history. Prepare a conflict, a failure, a data-driven decision, and a delivery-under-pressure story at minimum.
• Treating the coding round as easy because the bar is lower. "Solid medium, cleanly implemented" still means tested, named clearly, and complexity stated.

Interview follow-ups

They ask	What they're checking	The answer
"Tell me about a time you disagreed with your manager."	Have Backbone; Disagree and Commit	A real disagreement, your specific argument, and -- crucially -- what happened after the decision went the other way. Committing after losing the argument is the half people omit.
"Tell me about a time you failed."	Earn Trust; ownership	Pick a genuine failure with your own decision at its centre, not a failure caused by someone else. The recovery and the lesson are the answer; the failure is only the setup.
"Tell me about a time you had to decide without enough data."	Bias for Action	The trade-off you made explicit, what you shipped, and how you limited the downside. Deciding fast and reversibly is the shape they want.
"Why is your solution $O(n \log n)$?"	That the coding bar is still real	State the dominant term and why. A lower bar means fewer hard problems, not less rigour.

Recall card

• The Leadership Principles are scored like the code. A strong coder with thin LP answers is a common reject.
• Prepare 6-8 STAR stories, each tagged to 2-3 principles. Include a conflict, a failure, a data-driven call, and a delivery-under-pressure story.
• First person in the Action step. "We" scores nothing.
• Every story ends in a number or a concrete outcome.
• Coding bar is solid-medium, cleanly implemented -- tested, clearly named, complexity stated.

Self-check

quizCheck yourself

1. A candidate solves the coding problem perfectly but gives vague, 'we'-heavy behavioural answers. What is the most likely outcome at Amazon?

   AA likely reject, because Leadership Principles are scored with the same weight as code and 'we' scores nothingBA pass, because behavioural answers are only a tiebreakerCA re-interview of the coding round onlyDA pass, because coding is what is scored
   Show answer

   A — A likely reject, because Leadership Principles are scored with the same weight as code and 'we' scores nothing — Every interviewer is assigned specific principles to probe. Thin, non-first-person stories are a common reason strong coders are rejected.

2. How many STAR stories should you prepare, and how should you tag them?

   AOne perfect story that fits everythingBSix to eight, each mapped to two or three principlesCTwenty, one per principleDNone; improvise from the job description
   Show answer

   B — Six to eight, each mapped to two or three principles — A small bank covers the whole principle list by reuse. It should include a conflict, a failure, a data-driven call and a delivery-under-pressure story.

3. What makes the Action step of a STAR answer score well?

   AKeeping it under ten secondsBDescribing what the team didCDescribing what you personally did, ending in a number or concrete outcomeDListing the tools used
   Show answer

   C — Describing what you personally did, ending in a number or concrete outcome — Interviewers score your ownership. 'We' hides it, and an answer with no result gives them nothing to record.