Brag documents

Julia Evans popularized the brag document: a living private (or semi-private) note of what you did, the impact, links, and kudos. Update it weekly for ten minutes. Review cycle you then compile, not invent.

The brag doc is not arrogance. It is instrumentation for your career. Managers change; memories fade; calibration is lossy. Write it down. The same BLUF habit that makes status updates readable makes brag bullets scannable.

Walking through a useful bullet

Useful sections: projects shipped (docs, PRs, dashboards, launch emails); incidents and operational wins; mentorship and glue with outcomes; feedback received (quotes with dates); goals and progress; extras such as talks, interview loops, hiring help, open source.

When a peer says "nice work on X" in Slack, paste it in with a link. Future you is an unreliable narrator. Contemporaneous notes are not.

Write for a skeptic who was not in the room.

Weak: "Worked on checkout performance." Good: "Owned checkout p99 project (design → launch). p99 820 ms → 140 ms on /checkout/submit; error budget burn from that endpoint dropped ~60% over two weeks (dashboard). Coordinated with mobile on client timeout changes."

Weak: "Helped the team." Good: "Mentored two new hires through first production on-call (shared shadow schedule + runbook fixes). Both handled a SEV-3 solo within six weeks; filed three runbook PRs from gaps we found."

Weak: "Good collaborator." Good: "Negotiated idempotency-key support with Payments (sketch PR + one-pager). Unblocked Notifications launch by 10 days vs dual-maintaining a side cache."

Write bullets while the links still work. Review-season archaeology always undercounts. Map bullets to the leveling rubric language your company uses — see engineering levels and promotion. Reusing their nouns ("owns ambiguous problems", "multiplies others") helps calibrators tick boxes without decoding your slang.

Common mistakes

• Starting the doc in review week. You will undercount.
• Adjectives without links. "Helped the team" is not evidence.
• Treating it as bragging. It is instrumentation. Managers change.

Check yourself

Your self-review bullet is "worked on checkout performance." What is missing?

The metric, the path, the before/after, and a dashboard link — like 820 ms → 140 ms.

When do you update the doc?

Weekly, about ten minutes, while links still work.

Key takeaways

• A brag document is a running log. Reviews compile it.
• Weak bullets name activity. Strong bullets name outcomes, numbers, and links.
• Paste kudos when they happen. Future you will not remember.
• Map language to the ladder so calibrators do not translate.

Further learning

Get your work recognized: write a brag document (Julia Evans)Get your work recognized: write a brag documentJulia Evans

Next: performance reviews.