When I was a product manager, the worst part of every annual review was not having had enough time for myself to prepare a brag document. As a product manager working on a massive, cross-functional team, there's already so many documents and people to keep track of and follow up with that I didn't have much time to record my accomplishments, let alone refine them into a brag document. This was a double edged sword, because my reviews were with a more senior PM who experienced the things I did on a much higher level of intensity so he would have even less of a clue what was going on in my day to day.
What is a brag document?
A brag document is a curated, shareable summary of your professional accomplishments — usually one page, organized by impact, written in your own voice. Julia Evans popularized the term in 2019; the format has been used for decades inside engineering and product orgs under different names (impact doc, accomplishments memo, self-marketing log).
The brag document is downstream of a private record. You do not write a brag document from memory — you write it from your career journal, where the dates and links and specifics already live. If you don't keep a journal, the brag document becomes fiction within ninety days.
100% of Bloom users who do 3 entries a week have a Performance Insights report ready for them at review time.
When to use a brag document
- Performance reviews — your self-review is just the brag document, expanded.
- Promotion packets — the brag doc is the evidence section.
- 1:1s with a new manager — the fastest way to onboard them on what you've shipped.
- Resume updates — every line in your resume should map to a line in the brag doc.
- Interview prep — 'tell me about a time' answers come from this list, not from memory.
- Layoff insurance — if you're suddenly job-hunting, you need this updated, not started.
The five-section brag document template
Most working brag documents have the same five sections. Copy this structure into a doc, fill in the bullets from your journal, keep it to one page (two if you're senior).
1. Header — name, role, period, link to current resume
Top of page: your name, current title, the period the document covers (e.g., 'Q1 2026' or 'last 12 months'), and a link to whatever your latest resume is. This sounds obvious; people skip it and then can't tell at a glance which version they handed someone.
2. Top three impact items
The three accomplishments you would want a stranger to remember if they read nothing else. Lead each with a one-line headline, then two or three lines of evidence: dates, metrics, the artifact. Example: 'Led migration to new auth provider — reduced login latency 40%, zero downtime cutover April 3, 2026, runbook here.'
3. Wins by category
Group your other accomplishments under whatever categories match your role. For an engineer: shipped, scaled, fixed, mentored. For a PM: shipped, researched, decided, aligned. For a designer: shipped, prototyped, taught, repaired. Keep each bullet to one line. The categories matter less than the consistency — pick four and stick with them.
4. Growth and learning
Two or three bullets on what you learned, what you got better at, what you changed your mind about. This is the section managers read most carefully because it tells them you are still growing — which is the implicit question behind every promotion conversation.
5. Quotes and praise
Three to five direct quotes of feedback you've received: from a manager, a peer, a customer, a stakeholder. Paraphrased and dated. This section feels uncomfortable to write the first time; it is the highest-leverage section in the whole doc.
A worked example: software engineer, mid-level
Below is a condensed, anonymized brag document for a mid-level engineer at a 200-person company, covering one half of 2026. The template above generated the structure; the entries came straight from a working career journal.
- Header: Maya Patel · Senior Software Engineer · H1 2026 · resume link
- Top impact #1: Owned auth provider migration end-to-end — 40% login latency drop, zero downtime, runbook adopted by platform team.
- Top impact #2: Cut p99 checkout latency from 2.1s to 480ms — three commits, full writeup in eng wiki, presented at all-hands.
- Top impact #3: Designed and shipped feature flag service v2 — 11 teams onboarded, replaced 4 in-house systems.
- Wins / shipped: 27 PRs merged, 9 RFCs authored, 3 cross-team launches.
- Wins / scaled: on-call rotation runbook (12 pages), incident review process used in 4 incidents.
- Wins / fixed: 6 production bugs resolved with postmortems, 2 longstanding flaky tests stabilized.
- Wins / mentored: paired weekly with two new hires, both ramped to first solo PR within 3 weeks.
- Growth: started reviewing infra PRs (was strictly app-layer before), got better at writing RFCs that named tradeoffs early.
- Quotes: '[Maya's] runbook saved the on-call last weekend' — Sam, SRE, Mar 2026.
A worked example: product manager, senior
- Header: Devon Liu · Senior PM, Growth · 2025 in review · resume link
- Top impact #1: Led onboarding redesign — activation rate from 38% to 51%, $1.4M annual revenue impact.
- Top impact #2: Shipped pricing experiment platform — 12 tests run by 4 teams in Q4, replaced 6-week vendor process.
- Top impact #3: Closed 3 strategic partnerships — added 2 distribution channels worth ~22% of new signups.
- Wins / shipped: 4 major launches, 11 PRDs, 2 strategy docs adopted by leadership.
- Wins / decided: killed the legacy referral program (saved 2 eng quarters), narrowed roadmap from 14 to 6 bets.
- Wins / aligned: facilitated 8 cross-functional planning sessions, got eng+design+marketing aligned on Q3 goals doc.
- Wins / researched: 41 user interviews, 3 quant studies, hypothesis log with 9 falsified bets and the lessons.
- Growth: stopped writing prescriptive specs, started writing problem statements — eng pushed back twice and was right both times.
- Quotes: 'This is the cleanest PRD I've reviewed all year' — VP Product, July 2025.
How to fill in your brag document
Block 30 minutes. Open your career journal. Skim every entry from the period the brag doc covers. Pull each candidate accomplishment into a working list — don't filter yet. When the list is done, sort by impact (not by chronology) and pick the top three. Everything else either fits a category bucket or gets cut. The hardest part is cutting; aim for one page at first, two pages only if every line earns it.
Common mistakes
- Writing it in one all-nighter from memory the day before review season — you will forget the most important wins.
- Including every PR you opened — the brag doc is curated, not exhaustive.
- Vague verbs like 'helped with' or 'contributed to' — name the artifact and the outcome instead.
- Numbers without baselines — '40% faster' is meaningless without 'from 2.1s to 1.3s'.
- Skipping the quotes section because it feels self-promotional — it is the section managers trust most.
- Using the same brag doc for an internal promotion and an external recruiter — the audiences need different framing.
How often to update it
Once a month is the right cadence. First Friday is a useful default — it's far enough from end-of-month chaos and close enough to remember the previous four weeks. Spend 15 minutes pulling the month's wins from your journal into the doc. Twice a year (before each review cycle), spend a longer block re-sorting and rewriting the top-three section.
Bloom not only reduces the friction of recording your work through verbal entries which are automatically cleaned and tagged, but it also prepares performance reports for you for your reference come review time, for one-on-ones, for interviews, and natural resume refinements that actually sound like you and are based on your work. It's the ultimate weapon for future you when it comes to career advancement and for present you when it comes to career planning.
Bloom is the career journal app for this exact workflow.
Track wins, generate Period Recaps, get a performance review draft on demand.
Frequently asked questions
What is a brag document?▾
A brag document is a one- or two-page summary of your professional accomplishments, organized by impact, written in your own voice, and updated continuously. It exists so you can answer 'what have you been doing?' with a link instead of a panicked recall session.
How long should a brag document be?▾
One page if you can — two if you are senior or covering more than a year. Length is the wrong constraint to optimize. The right constraint is: every line earns its spot. If you cannot defend a line as worth a busy person's three seconds, cut it.
How is a brag document different from a resume?▾
A resume is for outsiders (recruiters, hiring committees) and is written in industry-standard formatting. A brag document is for insiders (your manager, skip-level, peer reviewers) and is written in your own voice with internal context, links, and dated specifics. Most resumes are downstream of a brag document.
When should I share my brag document with my manager?▾
Two natural moments: at the start of your performance review cycle (so they have it before writing your review), and at any 1:1 where you discuss promotion. Sharing it more often than that is fine — most managers welcome the visibility into work they would otherwise miss.
Brag document vs career journal — which one do I keep?▾
Both, but the career journal is the source. The journal is private, daily or weekly, full context, messy. The brag document is curated, shareable, organized by impact, ruthlessly trimmed. You generate the brag doc from the journal once a month. If you only keep one, keep the journal — the brag doc can be built from a journal in 30 minutes; the journal cannot be reconstructed from memory.
Should the brag document include failures?▾
The growth-and-learning section is where failures earn their place. A bullet like 'killed the referral program after it missed targets — saved 2 eng quarters and learned to set kill criteria up front' is stronger than any pure win, because it shows judgment. Pure failure lists belong in your journal, not the brag doc.