Amazon engineering runs on a distinctive operating culture: narrative six-page memos replace slide decks, meetings often open with silent reading, and teams 'work backwards' from a mock press release and FAQ before building. Services are owned by small 'two-pizza' teams with strong on-call and operational ownership — you build it, you run it. Day-to-day, engineers write and review code, dive deep into metrics and dashboards (Amazon is relentlessly data-driven), and are accountable to weekly business reviews where numbers are scrutinized line by line. The rhythm rewards Ownership and Bias for Action over consensus-seeking. Junior engineers (SDE I/L4) ship well-scoped tasks; SDE II (L5) own components and features; Senior (L6) own systems and lead across teams; Principal (L7) set technical direction across an org and write the memos that shape strategy. Promotions require a written case mapped to Leadership Principles and scope — the same LP-and-metrics framing that your resume and interview loop are built around.

Saying "we" instead of "I"

The Bar Raiser probes STAR stories for your individual contribution. Team-focused phrasing hides your role and reads as coasting. Claim exactly what you decided, built, and owned — vague, collective answers are one of the most common rejection causes.

No Leadership Principle mapping

Recruiters map your resume to the 16 LPs before an interview; the loop then dedicates whole rounds to them. Bullets and stories that don't surface Customer Obsession, Ownership, Bias for Action, or Deliver Results give the loop nothing to score against.

Unquantified results

Amazon is data-obsessed; every STAR story needs a quantified Result — percentage, dollars, or time saved. 'Significantly improved' collapses under Dive Deep follow-ups. If you can't attach a number, the accomplishment reads as unverifiable.

No Ownership / short-term thinking

The Ownership principle explicitly rejects 'that's not my job' and short-term thinking that sacrifices long-term value. Resumes that only show narrowly-scoped execution, with no evidence of taking on ambiguity or company-wide problems, signal a weak Ownership bar.

Doesn't raise the bar

The Bar Raiser's mandate is to ensure each hire is better in at least one important way than the peers they'd join. A profile that looks merely adequate — no standout dimension, no evidence of raising standards around you — is exactly what the Bar Raiser is trained to veto.

1Writing 'we' instead of 'I'

The Bar Raiser is trained to probe STAR stories for your specific individual contribution. Team-focused phrasing ('we launched,' 'helped the team') hides your role and reads as coasting. Claim your part explicitly: what did you personally decide, build, and own? Save 'we' for genuine collaboration you led.

2Ignoring Leadership Principles entirely

Your resume is the first filter, and recruiters map your experience to Leadership Principles before you get an interview. If your bullets don't naturally reflect Customer Obsession, Ownership, Bias for Action, and Deliver Results, you'll likely be screened out regardless of qualifications.

3Using vague or unquantified metrics

Amazon is data-obsessed. 'Significantly improved performance' tells them nothing; 'improved API response time by 40% (from 850ms to 510ms)' or 'reduced operational costs by $1.2M annually' does. Every accomplishment needs a number — percentage, dollars, or time saved.

4Making your resume too long or too generic

Recruiters spend 15-30 seconds on the initial screen. A 3+ page resume of generic language won't survive it. Keep to 1-2 pages, lead with your strongest, most relevant accomplishments, and tailor every bullet to the specific role and team.