How Amazon Promotion Documents Work

At most tech companies, your promotion case lives in your manager's head. At Amazon, it lives in a document. And if that document is weak, nothing else you've done matters.

Amazon's promotion process above L4 is built around a formal written case called the promo doc. Your manager writes it, a panel reviews it adversarially, and the quality of that document determines whether you advance. Engineers who understand how promo docs work and actively feed their manager the raw material consistently move up faster than those who assume their work will speak for itself.

What the Promo Doc Is

The promo doc is a structured written argument that your manager builds to prove you're already operating at the next level. It's not a performance review. It's not a list of things you did. It's a case with evidence, structured around Amazon's Leadership Principles and measured impact.

For SDE1 to SDE2 promotions, the doc is typically 6-8 pages. For SDE2 to SDE3, it grows to 15+ pages. The level of detail scales with the level of the promotion because the panel's scrutiny scales too.

Your manager writes the doc, but you are the primary source of evidence. If you don't track your wins, your manager doesn't have material to work with.

What Goes Into a Promo Doc

Every Amazon promo doc follows a recognizable structure. The sections vary slightly by org, but the core looks like this:

Summary. A single paragraph that makes the case in compressed form. Who you are, what level you're being promoted to, and the 2-3 strongest reasons why.

Role and scope. What you own, the team you're on, and the context that makes your work meaningful. This sets the stage for everything that follows.

Leadership Principles evidence. This is the core of the doc. 3-5 Leadership Principles, each backed by a specific example using the STAR format (Situation, Task, Action, Result). Not every LP needs to appear. The strongest promo docs pick the 3-5 LPs where the evidence is most compelling and go deep.

The LPs that matter most for SDE promotions vary by level, but these show up consistently: Ownership, Deliver Results, Dive Deep, Bias for Action, and Earn Trust. At SDE3 and above, Have Backbone; Disagree and Commit and Think Big carry more weight.

Impact. Measurable business and technical outcomes. Latency improvements with numbers. Cost savings with dollar amounts. Reliability gains with concrete before/after metrics. The panel discounts vague impact claims like "improved system performance." They want to see: reduced p99 latency from 450ms to 180ms, eliminating approximately $2.1M in annual compute overhead.

Scope and complexity. Evidence that the work goes beyond your current level. For SDE1 to SDE2, this means owning features end-to-end. For SDE2 to SDE3, it means cross-team influence and designing systems that span multiple services.

Stakeholder feedback. Your manager collects endorsements from people at the target level or above. For SDE2 to SDE3, that means at least 6 L6-level endorsers: other SDE3s, SDMs, TPMs, and PMs who can speak specifically to your impact. Weak endorsements from people who barely know your work hurt more than they help.

Development areas. A short section acknowledging where you're still growing. Counterintuitively, this strengthens the doc. It signals self-awareness and gives the panel confidence that the promotion is grounded in reality, not hype.

Who Actually Writes the Promo Doc

Your manager writes it. You don't. But the best promo docs at Amazon are built from raw material the engineer provides. Here's how the dynamic actually works:

You maintain a running log of your accomplishments with specific metrics, Leadership Principle connections, and cross-team examples. When promotion season approaches, you package this into a 3-5 page input document. Your manager takes your input, combines it with their own observations, gathers stakeholder feedback, and writes the formal promo doc.

"I gave my manager a five-page list of everything I did with metrics. She turned it into the promo doc. Without that list, she would have had nothing."

Engineers who don't provide detailed input get thin promo docs. And thin promo docs die in panel review.

The time investment is real. Managers report spending 40+ hours on a strong SDE2-to-SDE3 promo doc. This is why your relationship with your manager matters so much. If they're not willing to invest that time, or if they don't have the material to work with, the doc won't be competitive.

How the Panel Reviews Your Doc

The promotion panel is adversarial by design. This is intentional. Amazon wants to ensure the bar stays high and promotions are consistent across orgs.

Panelists read your doc cold. They don't know you. They're looking for specific things:

1. Is the evidence concrete or vague? Claims without metrics or specifics get flagged immediately.
2. Does the scope match the target level? If every example is within your immediate team and the target level requires cross-team influence, the case is weak.
3. Are the stakeholder endorsements credible? Endorsers who can't point to specific work they observed undermine the case. The panel can tell when endorsements are favors rather than genuine signals.
4. Can the manager defend the case? Your manager presents the doc and answers questions from the panel. If they stumble on follow-ups or can't provide detail behind a claim, it creates doubt.
5. Are the Leadership Principle stories specific enough? "Showed ownership" isn't evidence. "Identified that our deployment pipeline was the bottleneck for the entire org, built and launched an automated rollback system without being asked, reduced deployment failures by 73% in Q3" is evidence.

The panel's default posture is skepticism. They actively look for reasons to deny, not approve. Your doc needs to be so well-evidenced that the panel runs out of objections.

How to Build a Promo Doc That Survives Panel Review

Track your wins as they happen

The single most common failure mode is an engineer who does strong work but doesn't document it. By the time promotion season arrives, you're reconstructing six months of accomplishments from memory. Start logging wins weekly: what you did, what the impact was, which Leadership Principle it maps to, and who observed it.

Quantify everything

For each win, find the number. Latency reductions, cost savings, incident response times, adoption rates, lines of code reduced, build time improvements. If a win can't be quantified directly, quantify the proxy: "12 engineers across 3 teams now use the framework I built" or "reduced oncall pages by 60% in the first month."

Map wins to Leadership Principles explicitly

Don't leave this to your manager. When you share your accomplishments, include the LP connection: "This is a Dive Deep story because I traced the root cause through three layers of abstraction when the first two explanations turned out to be wrong." Your manager should not have to guess which principle your work demonstrates.

Name your stakeholders early

Identify people at the target level or above who've seen your strongest work. Tell your manager: "Here are the people who can speak to what I've done." Give them at least a quarter of lead time. Rushed endorsement requests produce weak endorsements.

Give your manager a head start

Don't wait until promotion season to hand over material. Start feeding your manager input 6 months before the expected promo window. Send monthly win summaries. Make their job easier. Engineers on Team Blind consistently report that the quality of a promo doc correlates directly with how much raw material the manager had to work with.

Common Promo Doc Mistakes

Vague impact statements. "Improved system reliability" means nothing to the panel. "Reduced production incidents from 14/month to 3/month by implementing circuit breakers across all customer-facing services" tells a story with evidence.

Missing LP connections. A list of accomplishments without Leadership Principle mapping forces the panel to do the interpretation. They won't. They'll just mark the case as unclear.

All results, no mechanism. Describing what happened without explaining how you drove it. The panel wants to understand your role specifically, not what your team shipped.

Weak stakeholder endorsements. Endorsers who write "great engineer, would recommend" without specifics signal that they don't actually know your work. Pick endorsers who can describe specific situations where they saw you operate at the next level.

Too short. For SDE2-to-SDE3, docs under 10 pages are a red flag. The length should reflect the depth of evidence. Brevity at this level reads as a thin case, not efficiency.

Manager wrote it alone. If your manager is guessing at your accomplishments, the doc will have gaps the panel will find. The engineer's input document is what separates a strong promo doc from a weak one.

---

CareerClimb tracks your wins, maps them to Amazon's Leadership Principles, and tells you exactly what evidence your promo doc is missing. When promotion season comes, your manager has everything they need to build the case. Download CareerClimb