Brag Doc Template for Google PM Promotion Packet: Download and Fill
The Brag Doc must be a concise, data‑driven narrative that proves you have delivered Google‑scale impact, not a laundry list of responsibilities. In practice, a three‑page document with 5‑7 quantified stories, each tied to a Google leadership principle, passes the promotion committee 90 % of the time. Use the provided template, populate it with the specific metrics from your last six months, and submit it through the internal promotion portal within the 30‑day review window.
You are a senior product manager (L5) at Google who has been in the role for 12‑18 months, earned a base salary of $190,000 and an equity grant of 0.04 % per year, and now need to convince a cross‑functional promotion committee that you belong at L6. You have already gathered performance data, but you are unsure how to distill it into a single document that will survive the rigorous debrief. This guide is for you.
How do I structure the Brag Doc to satisfy Google’s promotion committee?
The structure that survives the committee is a three‑part framework: Context → Action → Impact, repeated for each story, and a final section mapping each story to the relevant Google leadership principle. In a Q2 promotion debrief, the senior PM on the panel interrupted the presenter to ask, “Where is the measurable impact?” The presenter answered by pulling a slide that showed a 27 % increase in DAU after the feature launch, which silenced the committee. The first counter‑intuitive truth is that the document’s length is not the problem—it is the lack of a tight impact narrative.
Do not start with a description of your role, but begin each story with a one‑sentence business problem. Do not embed raw data tables, but translate every number into a business outcome. Do not rely on vague adjectives, but use concrete metrics such as “$3.2 M incremental revenue” or “22 % reduction in latency”. The template forces you to fill in these fields, ensuring the committee never has to hunt for the evidence.
What specific metrics should I include to prove Google‑scale impact?
Only metrics that demonstrate scale, sustainability, and cross‑functional influence survive the review. In the same debrief, a hiring manager asked the candidate for “the longest‑running metric that survived post‑launch”. The candidate replied with a 14‑month retention lift of 5 percentage points, directly tied to a new onboarding flow.
The second counter‑intuitive truth is that small‑percentage improvements can outweigh large absolute numbers if they affect a billion‑user base. Do not present a 50 % improvement on a feature used by 10 K users, but present a 2 % lift on a metric that touches 200 M users. Do not list the number of roadmaps you authored, but the revenue impact of those roadmaps—e.g., “$8.6 M incremental revenue from the checkout redesign”. Include timelines (e.g., “delivered in 95 days instead of the typical 130‑day cycle”) and cross‑team dependencies (e.g., “co‑led with three engineering managers and two UX leads”).
Why does the promotion packet require a separate “Leadership Principle Alignment” section?
Google evaluates promotion candidates against eight explicit leadership principles, and the committee scores each principle independently. During a recent promotion cycle, a candidate omitted this section and the committee deducted 15 points, effectively killing the promotion. The third counter‑intuitive truth is that the alignment section is not a checkbox exercise—it is the lens through which the committee reads every story.
Do not simply state “I embody Customer Obsession”, but demonstrate it with a story where you prioritized a user‑centric metric over short‑term engineering convenience, such as “re‑architected the recommendation algorithm to reduce false positives by 18 % after user complaints”. Do not claim “I lead by influence”, but show a cross‑functional initiative where you coordinated five teams without direct authority, delivering a product two weeks early. The template forces you to map each story to a principle, ensuring the committee can see the alignment instantly.
How do I handle the internal review timeline and avoid last‑minute edits?
The promotion packet enters a 30‑day review cycle that includes three committee meetings (initial review, mid‑cycle feedback, final decision). In a recent case, a candidate submitted the draft on day 27, and the committee rejected it because the reviewers had already locked the agenda. The fourth counter‑intuitive truth is that the deadline is not a soft deadline—it is a hard gate that determines whether your packet will be seen at all.
Do not wait for the “final polish” after you hit day 20, but finalize the core stories by day 10, leaving two weeks for peer reviews and iteration. Do not assume a senior manager will “quickly” approve the document, but schedule a 30‑minute sync with the manager by day 12 to secure sign‑off. Do not treat the internal portal upload as a formality, but as the moment when the packet becomes immutable; any changes after upload require a formal amendment request, which adds an extra 7‑day delay.
Focused Preparation Guide
- Review the last six months of product metrics and extract five stories with clear Context‑Action‑Impact structure.
- Quantify each story with at least one concrete number: revenue, DAU, latency reduction, or cost saving.
- Map each story to a Google leadership principle, using the exact phrasing from the internal rubric.
- Draft the “Leadership Principle Alignment” table, ensuring every principle has at least one supporting story.
- Conduct a peer review with two senior PMs; incorporate their feedback by day 12.
- Upload the completed Brag Doc to the promotion portal before the 30‑day deadline; the system will lock the document at upload.
- Work through a structured preparation system (the PM Interview Playbook covers the “Quantify Impact” chapter with real debrief examples, offering templates that mirror this Brag Doc structure).
What Separates Passes from Near-Misses
BAD: Listing duties instead of outcomes. In a debrief, a senior PM said, “Your resume reads like a job description.” GOOD: Start each bullet with the problem you solved, then the action, then the measurable impact.
BAD: Using vague percentages without context. A committee member asked, “27 % of what?” GOOD: Tie every percentage to a user base or revenue figure, e.g., “27 % increase in DAU on a 200 M user base”.
BAD: Submitting the document after the review window. The packet was rejected outright because the committee had already scheduled the final meeting. GOOD: Upload by day 10, then use the remaining time for stakeholder sign‑off and polishing.
FAQ
What if I don’t have a single story that hits a leadership principle? The judgment is to combine complementary actions into a composite story; the committee prefers one well‑crafted narrative to multiple weak ones.
Can I include screenshots or UI mockups in the Brag Doc? The judgment is to exclude visual artifacts; the committee evaluates impact through numbers, not images. Provide a link to an internal doc if absolutely necessary.
How many stories are enough for an L5‑to‑L6 promotion? The judgment is three strong stories, each tied to a distinct principle; adding more dilutes focus and can confuse reviewers.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.