Amazon is an unusual employer to write application advice about, because the company already tells you almost everything. The leadership principles are public — sixteen of them, posted on the careers site and recited in interviews. The expected answer format is public: STAR, with data. Even much of the interview mechanics are widely documented. Yet candidates keep failing in the same handful of ways, over and over, because they prepare for the process Amazon describes rather than the process Amazon runs.
This article is not a stage-by-stage tour of Amazon's pipeline — that is a different exercise. It is a list of the specific mistakes that sink otherwise qualified candidates, each paired with the countermeasure that fixes it. If you recognize yourself in one of these, the remedy is sitting right next to it.
Mistake 1: Spray-applying to every vaguely relevant posting
The mistake. A candidate opens amazon.jobs, sees dozens of postings that roughly match, and applies to fifteen of them in one sitting — SDE II here, solutions architect there, program manager just in case.
Why it backfires. Amazon's recruiting systems consolidate candidate records, and recruiters can see your application history across the company. A spray of applications reads as "I don't know what I want," and it creates practical problems too: different teams may contact you simultaneously, your story shifts from interview to interview, and if you are rejected on one posting, the pattern of near-miss applications becomes part of what the next recruiter sees.
The countermeasure. Apply to two or three roles, chosen deliberately. Before each application, write one sentence explaining why you fit this specific role — the skills, the scope, the level. If you cannot write that sentence, you are not ready to apply to that posting. A focused record with a coherent narrative beats a scattered one every time, at a company that prizes ownership and intent.
Mistake 2: A generic resume that never maps to the leadership principles
The mistake. The candidate sends the same resume everywhere: responsibility-style bullets ("responsible for backend services"), no numbers, nothing that would change if the target company changed.
Why it backfires. Amazon recruiters screen quickly, and they are looking for evidence of the leadership principles in your history — ownership, bias for action, delivering results, diving deep. A resume that describes duties instead of decisions gives them nothing to use. And at Amazon, your resume is not a marketing flyer; it functions as evidence. Interviewers reference it, and anything you claim on the page is fair game for probing.
The countermeasure. Rewrite each bullet as a decision plus a measurable outcome. "Cut checkout latency by rewriting the caching layer, reducing p99 from 800ms to 210ms" beats "improved system performance." Use principle-adjacent language only when it is true — "owned," "launched," "dug into the root cause" — because every claim becomes a question in a Dive Deep interview. Keep the format plain and readable; Amazon's culture prizes substance over polish, and an ornate resume can work against you. If you are unsure how your resume reads against a posting, comparing it side by side with the job description — manually or with a resume-to-job matching tool like CareerHelp's — is the fastest way to see the gap.
Mistake 3: STAR stories that collapse under probing
The mistake. Candidates arrive with stories, which is good — but the stories are thin. No numbers ("we improved efficiency"), team-level narration ("we decided to migrate"), no detail below the headline. The plan is to deliver the prepared monologue and move on.
Why it backfires. Amazon interviewers deliberately follow up. Dive Deep is a leadership principle, not a slogan: expect "what was the error rate?", "walk me through exactly what you did," and "how did you know that was the root cause and not a symptom?" A rehearsed-but-hollow story collapses on the second or third question, and the interviewer records it as weak evidence rather than nerves.
The countermeasure. Build a grid of eight to twelve stories mapped across the principles most relevant to your target role — for most corporate and technical roles that includes Customer Obsession, Ownership, Dive Deep, Bias for Action, Deliver Results, and Learn and Be Curious. Every story needs real numbers, a clearly defined individual contribution (you can credit the team for the outcome, but you must own the actions), and the set should include at least one honest failure or learning story. Then practice each story to three levels of follow-up. Illustrative scenario: a candidate whose latency story survives "why 210ms?", "what did you reject along the way?", and "what would you do differently?" has just converted one story into evidence for three different principles.
Mistake 4: Underestimating the writing sample and work sample
The mistake. For roles that require one, candidates treat the writing sample or work sample like homework to be rushed — or worse, they submit prose that reads like a slide deck: fragments, buzzwords, assertions with no data behind them.
Why it matters more at Amazon than anywhere else. Amazon runs on written narrative memos. New proposals begin as structured, written narratives — famously, six-page memos read silently at the start of meetings — a practice Jeff Bezos describes in his 2017 letter to shareholders as the reason the company favors essays over presentations. Writing is not an auxiliary skill at Amazon; it is the operating system. An interviewer who asks for a work sample is testing whether you can reason in prose.
The countermeasure. Practice structured writing the way Amazon does: open with the claim or recommendation, support it with data, name the trade-offs and the alternatives you rejected, and close with what you would do and what would change your mind. Write one or two pages under time pressure before interview day, so the format is not new to you. And strip out anything you have not actually reasoned through yourself — reviewers at a company that reads for a living are good at spotting filler.
Mistake 5: Misreading the debrief and the Bar Raiser
The mistake. Candidates treat the interview loop like a vote, where a majority carries and a charming overall impression can compensate for one shaky round.
Why it backfires. After the loop, Amazon runs a debrief in which interviewers compare evidence — and the conversation is designed to be skeptical, not supportive. The panel includes a Bar Raiser: an interviewer from outside the hiring team, trained and certified, whose explicit job is to protect the hiring bar and who carries outsize influence in the decision. Debriefs spend their time on the weakest evidence, not the strongest. A red flag in one round does not get averaged away; it gets examined.
The countermeasure. Prepare as if every round is decisive, because in the debrief, every round is. That means your failure story must be genuinely self-aware rather than performative, your claims must survive scrutiny, and you should not argue with an interviewer who pushes back — pushback is often the test itself. If you leave one round knowing you botched a question, recover in the next one instead of unraveling; interviewers write up what they observed, and a candidate who stays steady gives the debrief a coherent story to defend.
The pattern underneath
Look at the five mistakes together and a pattern emerges: Amazon's process punishes vagueness and rewards specificity. Spray-applying is vague intent. A duty-style resume is vague evidence. Number-free stories are vague impact. Deck-style prose is vague thinking. And assuming charisma beats scrutiny is a vague reading of the room. The countermeasures are all versions of one move — be concrete, be honest, and know exactly why you fit — which happens to be the same thing the leadership principles ask of employees every day.