Why brag documents
Important work isn't always visible. A brag document makes sure yours is remembered — by you, your manager, and your reviewers.
There's an idea that great work speaks for itself. In practice, some contributions are easier to see and remember than others. A brag document fixes that — and helps you reflect on what matters.
At review time, it's easy to think "wait, what did I do in the last six months?" You end up digging through PRs, tickets, and emails to rediscover work you forgot — including mentoring, security fixes, and migrations you helped ship.
If you don't remember everything, your manager probably doesn't either. They need concrete material to advocate for you in promotion and calibration discussions — not just "X's work is awesome."
Instead of relying on memory at review season, keep a document that lists your accomplishments as they happen. Refer back to it when it's time to write your self-review or prep for a 1:1.
Handing your manager a brag document makes their job easier — they can read it when writing your review instead of reconstructing the year from memory. It also helps during manager transitions.
If your company collects peer feedback, share your brag document with reviewers. It reminds them of your contributions and shows which areas you'd most like feedback on.
Beyond a task list, a brag document lets you write the narrative: what you've been focused on — security, product skills, code review culture — even when individual actions feel small.
Brag documents aren't just for hype. They help you reflect: what are you most proud of? What themes run through your work? What do you want more or less of? Which projects had the impact you wanted?
Work like improving code quality, making on-call easier, or driving down tech debt often falls under the radar because it's hard to quantify. A brag document is where you explain why it mattered and what changed.
How AI helps
Julia Evans' tactic works — but maintaining a doc by hand is painful. AI handles the structure so you focus on what you did.
Describe what you did in your own words — "helped with billing migration in Q3" is enough. No rigid templates or blank fields to fight with.
Desmos extracts project, contribution, impact, and period from free-form text — the fields that actually matter in a brag document.
If something's missing, AI asks a single clarifying question — never an interrogation. You lead; AI assists.
Hard-to-quantify contributions — code review culture, on-call improvements, refactors — get follow-ups that help you explain the goal and the effect, not just the task.
Inspired by Get your work recognized: write a brag document
Start building your brag document today. Free, private, and designed for how you actually work.
Get started — it's free