· Valenx Press  · 8 min read

Brag Doc Template for PM Promotion: Downloadable Example

Brag Doc Template for PM Promotion: Downloadable Example

The most effective Brag Docs are not summaries — they are strategic narratives designed to trigger specific judgment calls in promotion committees. In a recent Q3 People Manager promotion cycle at a late-stage tech company, a product manager’s Brag Doc failed not because of weak achievements, but because it read like a project status update instead of a leadership narrative. The document was technically accurate but structurally inert.

Most candidates waste time formatting instead of focusing on narrative architecture. The problem isn’t what you write — it’s how you frame what you’ve already done. A Brag Doc that gets traction does three things: (1) isolates 3–5 leadership moments, (2) ties each to measurable business impact, and (3) aligns them with the company’s leadership competencies.

The first counter-intuitive truth is that your Brag Doc should read like a case study, not a resume. In one debrief, a senior PM’s promotion packet was delayed because her Brag Doc listed “led cross-functional teams” without defining what that meant in terms of scope or outcome. The second insight is that vague verbs like “improved” or “scaled” are judgment signals for weak impact. The third is that formatting matters more than you think — a clean, left-aligned structure with bullet points under clear headers gets processed faster by busy reviewers.

This article explains how to build a Brag Doc that triggers positive judgment signals in FAANG-level promotion committees. It includes a downloadable template and real debrief examples.

What Should a Brag Doc Include for a PM Promotion?

A Brag Doc for PM promotion should include 3–5 leadership narratives, each with measurable business impact, tied to company-defined leadership competencies. In a 2023 Google L7 promotion packet, the successful candidate structured each narrative using the STAR-L framework: Situation, Task, Action, Result, and Leadership. Each section was no more than 3–4 bullet points, with one key metric per story.

The document was 2 pages, single-spaced, and used left-aligned headers with consistent formatting. The candidate included a one-sentence summary at the top that read: “This document outlines key leadership contributions toward Google’s mission of organizing the world’s information, with measurable impact on user growth, team velocity, and product-market fit.”

Not a list of projects, but a narrative of leadership.

In a debrief with the People Manager, one reviewer commented that the candidate “demonstrated clear L7 readiness by showing initiative beyond role scope.” Another noted that the Brag Doc “read like a product leadership case study, not a project log.”

The key insight is that your Brag Doc should not just describe what you did — it should show how you thought about the business impact. A strong Brag Doc answers: What was the situation? What was your role? What did you do? What was the outcome? And what leadership principle does this demonstrate?

How Do You Structure a Brag Doc for Maximum Impact?

Structure your Brag Doc like a consulting case writeup, not a resume. In a 2024 Meta L6 promotion packet, the winning candidate used a 4-section structure: (1) Leadership Summary, (2) Business Impact Narratives, (3) Cross-functional Influence, and (4) Appendix with raw data. Each narrative was limited to 150 words and tied to a specific OKR.

The candidate used the “What? So what? Now what?” framework to structure each story. For example:

  • What: Led a team of 5 engineers and 2 designers to launch a new checkout experience.
  • So what: Increased conversion by 12% quarter-over-quarter, contributing $2.3M in incremental revenue.
  • Now what: Rolled out to 3 additional markets, with a 20% increase in A/B test engagement.

This structure made the document scannable and persuasive. Reviewers could quickly grasp the candidate’s impact without needing to decode jargon or infer leadership scope.

Not a list of responsibilities, but a case for promotion.

The structure of a Brag Doc should mirror a decision-maker’s mental model. In a debrief for a Stripe Product Lead promotion, the hiring committee noted that the candidate’s Brag Doc “read like a pitch deck for their own leadership.” This is the standard you should aim for.

Each section should include:

  • A clear header (e.g., “Drove 20% revenue growth through new market expansion”)
  • 2–3 bullet points of action
  • 1–2 bullet points of outcome with metrics
  • 1 bullet point linking to company leadership principles

What Are the Key Metrics to Highlight in a PM Brag Doc?

Key metrics in a PM Brag Doc should reflect business impact, not just output. In a 2023 Amazon Senior PM promotion packet, the candidate listed “Increased user engagement by 18% in 6 months” under a section titled “Led cross-functional team to redesign onboarding flow.” The metric was specific, time-bound, and tied to a business outcome.

Not a vanity metric like “improved UX,” but a revenue or user growth number.

In another case, a candidate at a Series C startup used “Drove 32% MoM user growth by launching a referral program” as a headline. Below it, they listed:

  • Partnered with growth and engineering to design incentive structure
  • Launched in 4 weeks with $0 engineering cost (leveraged existing referral API)
  • Scaled from 500 to 2,100 users in 6 weeks

This structure showed initiative, cross-functional influence, and measurable impact.

The third counter-intuitive truth is that metrics without context are noise. In a debrief for a Microsoft L61 promotion, one reviewer said: “The candidate listed ‘Increased DAUs by 15%,’ but didn’t explain what that meant for retention or revenue. It read like a vanity metric, not a business outcome.”

Strong metrics answer three questions:

  1. What changed?
  2. By how much?
  3. Why does it matter?

A good Brag Doc doesn’t just report what happened — it explains why it mattered.

How Long Should a Brag Doc Be?

A Brag Doc should be 1–2 pages, single-spaced, with clear headers and bullet points. In a 2024 Google L7 promotion packet, the candidate’s Brag Doc was exactly 1.5 pages. It used a 12pt font, 1.15 line spacing, and had 1-inch margins. The document was easy to scan in under 2 minutes.

Not a 10-page essay, but a 90-second pitch.

In a debrief, one Google hiring manager said: “The document was concise, but every line had a purpose. I could tell within 30 seconds this person understood what we care about.”

A Brag Doc that gets read is better than one that gets skimmed. The key is to front-load the most important information and use formatting to guide the reader’s eye.

How to Align Your Brag Doc with Company Leadership Principles?

Align your Brag Doc with company leadership principles by mapping each narrative to a specific principle. In a 2023 Amazon Senior PM packet, the candidate created a table mapping each story to one of Amazon’s 14 leadership principles. For example:

StoryLeadership Principle
Drove 20% increase in user engagement by redesigning onboardingCustomer Obsession
Led cross-functional team to reduce latency by 35%Insist on the Highest Standards

This structure made it easy for reviewers to map the candidate’s impact to Amazon’s values.

Not a generic list of accomplishments, but a tailored case for promotion.

In a debrief, one Amazon Bar Raiser said: “The candidate didn’t just list what they did — they showed how it aligned with our principles. That’s rare.”

The key is to use the company’s language. If your company has published leadership principles, use them. If not, create your own — but make sure each story maps to one.

Preparation Checklist

  • Create a 1–2 page document with clear headers and bullet points
  • Use the STAR-L or What/So What/Now What framework for each story
  • Include 3–5 leadership narratives with measurable business impact
  • Map each story to a company leadership principle
  • Work through a structured preparation system (the PM Interview Playbook covers Brag Doc strategy with real debrief examples)

Mistakes to Avoid

BAD: Listing projects without leadership context
GOOD: Framing each project as a leadership story with business impact

BAD: Using vague verbs like “improved” or “scaled” without metrics
GOOD: Using specific, time-bound metrics like “increased conversion by 12% in Q2”

BAD: Writing a 5-page essay with dense paragraphs
GOOD: Creating a 1.5-page document with bullet points and headers

FAQ

How do I start writing my Brag Doc?
Start with 3–5 leadership stories that show measurable business impact. For each, write 2–3 bullet points of action, 1–2 of outcome, and 1 linking to a leadership principle. This structure works across FAANG and startup promotions.

What format should I use for my Brag Doc?
Use a clean, left-aligned format with headers and bullet points. Each story should be 3–4 bullet points max. The entire document should fit on 1–2 pages. This format is easy to scan and aligns with how busy reviewers process information.

How do I make my Brag Doc stand out?
Tie each story to a specific business outcome and leadership principle. Use metrics that matter to the business — revenue, user growth, retention, or efficiency. Avoid vanity metrics like “improved UX” or “scaled team.”amazon.com/dp/B0GWWJQ2S3).

    Share:
    Back to Blog