Back to Blog
big techSoftware Engineer

Amazon SDE Promotion Guide: L4 to L5 to L6 and the Promo Doc

Master Amazon's promotion process. Learn how to write an effective promo doc, demonstrate Leadership Principles, and navigate calibration to advance from SDE I to SDE II to SDE III.

PromoReady TeamJanuary 7, 20257 min read

Amazon's promotion process is documentation-heavy and deeply tied to their Leadership Principles. Understanding how promo docs work and how to demonstrate LPs is essential for advancing your career at Amazon.

Here's what you need to know.

Amazon's Engineering Levels

Amazon uses L4-L8 for Software Development Engineers (SDEs):

| Level | Title | Typical Experience | |-------|-------|-------------------| | L4 | SDE I | New grad, 0-2 years | | L5 | SDE II | 2-5 years | | L6 | SDE III / Senior SDE | 5-10 years | | L7 | Principal SDE | 10+ years | | L8 | Senior Principal SDE | Varies |

The L4 to L5 jump is considered the fastest progression point. The L6 to L7 jump is exponentially harder.

The Promo Doc: Your Most Important Artifact

Unlike Google or Meta where managers compile your packet, Amazon expects you to heavily contribute to your own "promo doc." This document is the foundation of your promotion case.

What Goes in a Promo Doc

A promo doc is a detailed narrative that:

  • Demonstrates you've exceeded current-level expectations
  • Shows capabilities required for the next level
  • Provides specific examples tied to Leadership Principles
  • Includes business metrics and quantified impact

Document Length

The docs are substantial:

  • SDE I → SDE II: 5+ pages
  • SDE II → SDE III: 15+ pages

The 40-Hour Reality

On average, writing a solid promo doc takes ~40 hours. SDEs CAN and SHOULD own much of the doc writing, but it's a skill many engineers haven't developed.

Pro tip: Start documenting early. Use a brag document throughout the year so you have material when promo doc time comes.

Leadership Principles: The Evaluation Framework

Amazon's 16 Leadership Principles (LPs) are the criteria for promotions and performance reviews. Your promo doc must frame accomplishments in LP terms.

Key LPs for Promotions

Ownership: Think long-term. Act on behalf of the entire company.

Bias for Action: Speed matters. Take calculated risks.

Invent and Simplify: Expect and require innovation. Find ways to simplify.

Deliver Results: Focus on key inputs and deliver them with the right quality.

Earn Trust: Listen attentively. Speak candidly. Treat others respectfully.

Dive Deep: Stay connected to details. Audit frequently.

Have Backbone; Disagree and Commit: Respectfully challenge decisions. Commit wholly once decided.

How to Use LPs in Your Promo Doc

For each major accomplishment, explicitly connect it to relevant LPs:

"Demonstrated Ownership by identifying a latency issue affecting checkout conversion and leading the fix across three teams. Showed Bias for Action by shipping an initial mitigation within 48 hours while developing the long-term solution. Result: 23% reduction in P99 latency, contributing to $2M ARR improvement."

Engineers who proactively document work using LP language are better positioned for promotion.

The Rating System

Amazon uses a rating system where certain ratings unlock promotion eligibility:

  • TT (Top Tier): Promotion candidate
  • HV3 (Highly Valued 3): Strong performance, promotion possible
  • Lower ratings: Not promotion-eligible

What Blocks Promotions

  • SDE I → SDE II: Usually blocked by lack of technical complexity
  • SDE II → SDE III: Usually blocked by lack of scope, influence, and impact

This tells you where to focus: early career, focus on technical depth. Later career, focus on scope and influence.

Calibration Sessions

Final promotion decisions happen in calibration sessions where:

  • Managers present promo docs
  • Peers and Bar Raisers debate candidates
  • Cross-team comparisons happen
  • Decisions are made collectively

Your manager's ability to write and present a strong promo doc directly affects your outcome.

How to Position Yourself for Promotion

Start Documenting Early

Don't wait until promo doc time. Throughout the year, track:

  • Projects with specific metrics
  • LP demonstrations with concrete examples
  • Peer feedback and testimonials
  • Impact at increasing scope

Maximize Peer Feedback

Amazon allows extensive peer feedback—15-30 peers if you want. At minimum, request feedback from 5-6 peers. Include:

  • Engineers you've worked closely with
  • Cross-team collaborators
  • People who've seen your LP demonstrations

Find Increasing Scope

For SDE II → SDE III, scope is critical. You need to show:

  • Influence beyond your immediate team
  • Technical leadership on complex problems
  • Impact at the organizational level

Look for opportunities to:

  • Lead cross-team initiatives
  • Own technical strategy for your area
  • Mentor and develop other engineers

Work Your Promo Doc Like a Project

Treat writing your promo doc as a project:

  1. Gather raw material (brag doc, metrics, feedback)
  2. Draft early—don't wait until the deadline
  3. Get feedback from your manager
  4. Revise based on input
  5. Polish the narrative

Partner Closely with Your Manager

Your manager presents your case. Help them by:

  • Sharing your brag document regularly
  • Being explicit about promotion goals
  • Asking what gaps exist
  • Drafting parts of the promo doc they can use

Promotion Timeline

  • L4 to L5: 9 months to 2 years for high performers
  • L5 to L6: 2-4 years, highly dependent on scope
  • L6 to L7: Exponentially harder—requires organizational strategy and visionary leadership

The key to L4 → L5 is demonstrating independence, reliability, and execution quality. You need to operate as an L5 before getting the promotion.

Common Mistakes

Not owning your promo doc. Don't expect your manager to write it for you. The more you contribute, the stronger it will be.

Generic LP examples. "I demonstrated Ownership" isn't enough. Give specific stories with measurable results.

Waiting too long to document. You will forget details. Track wins throughout the year.

Not enough peer feedback. Amazon allows many peer reviewers. Use this to your advantage.

Underestimating scope requirements. At SDE II+, scope matters as much as execution quality.

How PromoReady Helps Amazon Engineers

Amazon's promo doc process is documentation-heavy and LP-focused. PromoReady is built to handle exactly this:

Map Evidence to Leadership Principles

Amazon evaluates everything through LPs. PromoReady helps you:

Tag wins to specific LPs: When you log "Reduced build time from 45 minutes to 8 minutes by redesigning the CI pipeline," PromoReady helps you map it to relevant LPs (Invent and Simplify, Deliver Results, Bias for Action).

Identify LP gaps: The matrix view shows which LPs have strong evidence and which need more examples. If you have 5 examples of Deliver Results but zero for Have Backbone, you know where to focus.

Example: An SDE II targeting SDE III sees that their Ownership and Dive Deep examples are strong, but they lack evidence for Earn Trust (cross-team influence) and Have Backbone (pushing back on decisions). This directs their next quarter's focus.

Build Your Promo Doc Efficiently

Amazon promo docs take ~40 hours to write. PromoReady cuts this dramatically:

Pre-organized evidence: Every win you've tracked is already tagged with LPs, metrics, and context. You're not trying to remember 12 months of work.

Generate LP narratives: PromoReady can generate draft narratives for each LP based on your evidence. You edit and refine rather than write from scratch.

Example narrative: "Demonstrated Ownership by identifying a critical gap in our disaster recovery process and driving a cross-team initiative to implement automated failover. Showed Bias for Action by shipping an initial mitigation within 48 hours while developing the long-term solution. Result: Reduced potential downtime from 4 hours to 15 minutes, earning recognition from L8 leadership."

Track Scope Expansion

The L5 to L6 jump requires organizational influence. PromoReady tracks:

  • Single-team vs. cross-team impact
  • Collaboration with senior engineers and managers outside your team
  • Evidence of setting direction, not just executing

Manage Peer Feedback Strategy

Amazon allows 15-30 peer reviewers. PromoReady tracks your cross-functional collaborations, helping you identify the right mix of peers who can speak to different LPs.

Ready to build your promotion case?

PromoReady helps you track wins, map them to your rubric, and stress-test your packet before the real committee.

Try PromoReady Free

Related Guides

Sources

Amazonpromotionsoftware engineerSDEpromo docLeadership PrinciplesFAANG

Ready to put this into practice?

PromoReady helps you track wins, map them to your rubric, and get AI-powered feedback before the real committee.

Start Building Your Case