Brag Doc Template for Amazon SDE3 Promotion

Most Amazon SDE3 candidates spend 40 hours building brag docs that committees discard in 90 seconds. The problem isn’t your achievements—it’s the judgment signal your documentation creates. A brag doc isn’t a list of accomplishments. It’s a narrative about how you operate at scale, how you raise the bar, and how you make other engineers better. This template is built from promotion committee patterns, not resume-writing advice.

What Is a Brag Doc and Why Does It Matter for Amazon SDE3?

A brag doc is a living document that tracks your impact across Amazon’s 14 Leadership Principles throughout the year. For SDE3 promotion, it serves two functions: it structures your self-review for the calibration meeting, and it provides your manager with ammunition during the bar raiser discussion. The document typically runs 3-5 pages and gets submitted 6-8 weeks before your promotion cycle closes.

The critical insight from three promotion cycles I’ve debriefed: committees don’t read brag docs sequentially. They scan for scope, then anchor on 2-3 examples that demonstrate L6-level judgment. Your template must front-load your highest-impact work. Candidates who bury their best examples in paragraph four lose the reader before the calibration meeting starts.

What Does the Amazon SDE3 Promotion Timeline Look Like?

The SDE3 promotion cycle runs on a fixed calendar that governs every decision. The nomination window opens in January and closes by mid-February. Your manager submits your name with a preliminary impact statement. The actual documentation window spans March through May, when you draft, revise, and finalize your brag doc. Calibration meetings occur in June. Bar raiser interviews happen in July. Final decisions land by August or carry to the next cycle.

The compensation stakes are significant. An SDE3 promotion typically moves base salary from the L5 range of $175,000-$195,000 to $195,000-$225,000. Total compensation including equity refresh and sign-on adjustments often lands between $280,000 and $380,000 depending on tenure and stock appreciation. The timeline pressure is real: candidates who submit drafts after May 15th receive significantly less manager feedback and produce weaker final documents.

How Do I Structure My Brag Doc for Maximum Impact?

Structure your brag doc in three distinct sections that map to how promotion committees actually evaluate candidates. Lead with the Executive Summary—three paragraphs maximum that answer “what did you do, at what scale, and why did it matter?” Follow with Impact Metrics, organized by project or initiative, each with concrete numbers tied to business outcomes. Close with Leadership Principle Evidence, where you explicitly connect your actions to specific Amazon principles with behavioral evidence.

The template structure that performs consistently in calibration meetings:

Section 1: Executive Summary (1 page)

• Opening paragraph: One sentence describing your scope, one sentence on your biggest delivery, one sentence on organizational impact
• Three bullet points of headline metrics (revenue influenced, systems scaled, team members developed)
• One paragraph on how you raised the bar for your team or organization

Section 2: Impact Evidence (2-3 pages)

• Project 1: The problem, your specific contribution, the measurable outcome, the technical decision that enabled it
• Project 2: The cross-team complexity you navigated, your leadership role, the customer or business impact
• Project 3: The innovation or mechanism you created that outlasted your direct involvement

Section 3: Leadership Principles (1 page)

• 2-3 specific behavioral examples per principle, drawn from the projects above
• Focus on Bias for Action, Ownership, and Learn and Be Curious—these three appear in 80% of calibration discussions

What Metrics and Examples Should I Include in My SDE3 Brag Doc?

The strongest SDE3 brag docs include metrics in three categories: scale, efficiency, and organizational leverage. Scale metrics answer “how big?”—systems touched, data processed, revenue influenced, users impacted. Efficiency metrics answer “how much better?”—latency reduced, costs saved, incidents prevented. Organizational leverage metrics answer “how many people did you multiply?”—engineers mentored, processes established, teams enabled.

Specific numbers that resonate in calibration: latency reductions in percentage terms with dollar-value conversion, cost savings expressed as percentage of relevant budget line, team productivity gains measured in story points or feature velocity. Vague claims like “improved performance” get flagged immediately. Precise claims like “reduced p99 latency from 340ms to 89ms, enabling 23% improvement in checkout conversion worth approximately $4.2M quarterly revenue” earn credibility.

The behavioral examples matter as much as the numbers. Committees want to see HOW you operated, not just what happened. Frame your examples using Amazon’s STAR format: Situation (the context), Task (your specific responsibility), Action (what you did, not what the team did), Result (the measurable outcome). The Action section deserves 60% of your word count. Most candidates write three sentences of context and one sentence of action. Reverse that ratio.

How Does the Amazon Promotion Committee Evaluate My Brag Doc?

The committee evaluates three dimensions: technical scope, organizational impact, and leadership maturity. Technical scope means the complexity and autonomy of the systems you own or influence. Organizational impact means how your work affected the broader company, not just your team. Leadership maturity means how you developed others, navigated ambiguity, and raised the bar.

In a Q3 calibration debrief I observed, an L5 engineer submitted a brag doc listing seven projects with strong individual metrics. The committee member’s feedback was direct: “You have seven individual contributor stories. I see no evidence of scope expansion beyond your own work.” The candidate had not documented any cross-team initiatives, any mentoring relationships, or any mechanism-building that outlasted their direct involvement. The promotion was deferred six months.

The evaluation happens in two passes. First pass: does the scope match L6 expectations? Second pass: does the evidence demonstrate judgment, not just execution? Committees are looking for candidates who made decisions, not just completed tasks. Every example in your brag doc should answer “what decision did you make, what alternatives did you consider, and why was your choice correct?”

When Should I Submit My Brag Doc for Maximum Promotion Chances?

Submit your first draft to your manager 10 weeks before the cycle closes. This creates time for three revision cycles. The first revision focuses on scope accuracy—does your manager agree this is L6-level work? The second revision focuses on evidence strength—are your metrics defensible under bar raiser scrutiny? The third revision focuses on narrative clarity—does the document tell a coherent story about your growth?

Candidates who submit final brag docs in the last two weeks before the deadline receive the lowest promotion rates. The correlation is direct: less manager feedback time equals weaker calibration outcomes. The sweet spot for first draft submission is mid-April for an August decision cycle. This gives your manager five weeks to provide structured feedback and you three weeks to incorporate it.

The submission itself happens through your manager to the promotion portal. You cannot submit directly. Your manager writes a separate Manager Summary that either reinforces or contradicts your narrative. Misalignment between your brag doc and your manager’s summary is the single biggest predictor of promotion denial. Have the alignment conversation explicitly before submission: “Does my document accurately represent your assessment of my impact?”

Preparation Checklist

• Track your metrics weekly in a running document, not retroactively. Systems handling over 100,000 requests per minute, teams of 8-12 engineers led, latency improvements measured in percentage terms with dollar conversion.
• Draft your Executive Summary first, then build supporting evidence. The forced clarity exposes gaps in your narrative before you’ve invested hours in detail work.
• Schedule a scope calibration conversation with your manager in January. Confirm whether your current work actually maps to L6 expectations before you invest in documentation.
• Review three successful SDE3 brag docs from engineers who received promotion. The PM Interview Playbook includes real examples with committee feedback annotations—study how successful candidates framed scope and leadership.
• Prepare for bar raiser questions on your top three examples. The bar raiser will probe for judgment, not just outcomes. Have your decision-making rationale ready.
• Align your brag doc narrative with your manager’s assessment before submission. Any gap between your document and their summary is a red flag.
• Time-box your documentation work. Four focused hours produces better output than eight scattered hours. Schedule it like a meeting.

Mistakes to Avoid

Mistake 1: Listing accomplishments without demonstrating judgment.

BAD: “Led the migration of the payment processing system to a new architecture, reducing latency by 40%.”

GOOD: “Identified that the payment processing system’s latency bottleneck stemmed from synchronous dependency chains during peak load. Proposed and drove adoption of a circuit-breaker pattern with async fallback, requiring negotiation with three dependent teams. The architectural decision reduced p99 latency from 280ms to 168ms while preserving data consistency guarantees. The pattern is now standard for all high-traffic services in the domain.”

Mistake 2: Including projects without explicit scope context.

BAD: “Improved the search relevance algorithm, increasing conversion by 12%.”

GOOD: “Drove a cross-functional initiative spanning three teams and two quarters to redesign search relevance for the core catalog. The project required establishing shared evaluation frameworks, coordinating offline testing, and managing staged rollout across 14 international markets. The 12% conversion improvement translated to $18M annual revenue impact and established the measurement methodology now used by all recommendation systems.”

Mistake 3: Writing in passive voice that obscures your contribution.

BAD: “The team was able to reduce costs through optimization efforts.”

GOOD: “Identified $2.3M in annual infrastructure cost by proposing a reserved instance strategy that required shifting deployment patterns across 47 services. Led the implementation over 8 weeks, negotiating capacity planning changes with platform teams. The cost reduction was achieved without service reliability degradation, validated by 6 months of production monitoring.”

FAQ

How long should my Amazon SDE3 brag doc be?

Your brag doc should be 4-6 pages total, single-spaced. The Executive Summary takes 1 page, Impact Evidence takes 2-3 pages, and Leadership Principles takes 1 page. Committees spend 2-3 minutes maximum on individual documents during calibration. Brevity forces clarity—every sentence must earn its place by demonstrating scope, judgment, or impact.

Should I include projects where I failed or faced setbacks?

Yes, but only when you can demonstrate learning and course correction. One or two examples of “here’s what I tried, here’s what went wrong, here’s what I changed” provides evidence of Learn and Be Curious and demonstrates intellectual honesty. However, frame these as learning moments with clear outcomes, not as excuses. The committee wants to see that you extract lessons, not that you experienced difficulty.

My manager is not supportive of my promotion. What do I do?

The documentation matters more when your manager is unsupportive. A strong brag doc gives your manager factual ammunition to make the case, even if their instinct is to defer. Request a specific calibration conversation: “I want to understand what evidence would change your assessment. Can we go through my draft together?” If the gap persists, escalate through your skip-level with documentation. The promotion decision ultimately involves your manager’s perspective, but your evidence shapes the conversation.

Related Tools

• AI Talent Demand by Skill Level
• AI Talent Demand by Experience Level
• AI Hiring Trends by Experience Level

Related Reading

How to Structure Your Amazon L6 Self-Review for Maximum Impact The Complete Guide to Amazon Bar Raiser Interviews for Senior Engineers Compensation Breakdown: Amazon SDE3 Total Rewards in 2024 Negotiating Your Amazon Offer: Equity Refresh and Signing Bonus Strategiesamazon.com/dp/B0GWWJQ2S3).