Most engineers have heard the advice: keep a running document of your accomplishments, so when review season or a job search arrives, you aren't relying on memory. Julia Evans helped popularize it as the brag document. [1] It's good advice, and I follow it.
But I've noticed a problem. Brag docs drift.
Over months, "I helped with" becomes "I led." An estimate becomes a metric. A team result becomes a personal one. Not because anyone sets out to lie, but because a document written for self-promotion slowly bends toward it.
That matters for two reasons. First, people can tell. A reviewer or interviewer who probes one inflated claim will discount the rest. Second, and more important, an inflated record stops being useful to you. If you can't trust your own evidence, you can't use it to make real decisions about where you're growing and where you're not.
So I keep a different kind of brag doc. Here's how it works.
Label Every Claim by How Sure You Are
Every entry gets one of three labels:
Confirmed
I can point to evidence: a shipped change, a document, a written decision, a message acknowledging the result.
Ready to use.
Inferred
I believe it's true, but I'm reasoning from indirect signals.
"This probably reduced on-call load."
Next: get the data or ask someone.
Missing
I know this matters, but I don't have the evidence yet.
"Impact on incident volume: not measured."
Next: decide if it's worth measuring.
The labels do two things. They keep me honest when I write the entry, because I have to decide which bucket it belongs in. And they give me a to-do list. Every Inferred or Missing item is a question: Can I get the data? Should I ask someone? Is this worth measuring at all?
Over time, the ratio tells a story. If most of my entries are Inferred, I'm doing work whose impact I can't see, and that's worth fixing.
Lesson: A claim without a confidence level is a claim waiting to be inflated.
Never Take Credit for Team Work
The second rule is simple: be precise about what you did versus what the team did.
That doesn't mean underselling yourself. It means writing entries like these:
Inflated
Delivered the new alerting system.
Sounds big. Falls apart at the first follow-up question.
Precise
Proposed the design and wrote the first version; two teammates extended it to cover the remaining cases.
Led the review that found the gap; another engineer implemented the fix.
Coordinated the rollout across three teams; I didn't write the core change.
Shows judgment, collaboration and self-awareness, and holds up under questioning.
Interviewers for senior roles often probe for exactly this: can you separate your contribution from your team's?
What Goes in an Entry
A good entry is short. Mine have five parts:
- Date and a one-line summary.
- What I did, in specific verbs: designed, wrote, reviewed, led, escalated, unblocked, decided.
- What happened as a result, with a label: Confirmed, Inferred or Missing.
- Evidence: where the proof lives. A link, a document title or a person who saw it.
- What it shows: the skill or behavior it demonstrates, such as technical depth, influence or delivery.
That last field turns a log into a career tool. When I review the doc, I can see which skills have lots of evidence and which have almost none.
Template
Copy this and adapt it. Gergely Orosz's work log template is another good starting point. [2]
## [Date]: [One-line summary] What I did: [specific verbs, specific scope] Result: [outcome] ([Confirmed / Inferred / Missing]) Evidence: [link, doc title or person] Team context: [who else contributed and how] Shows: [skill or behavior]
A Rhythm That Sticks
The doc only works if you keep it current.
I also keep a short summary on top: a one- or two-page snapshot of where I was, where I am and where I want to be, with a few concrete next actions. The detailed log backs it up. The snapshot is what I actually read.
Turning It Outward Safely
If you use your brag doc for a résumé, a professional profile or interviews, there's one more step: make it safe to share outside your company.
Internal project names, unreleased products, customer names and confidential numbers don't belong in public. Translate each entry into the pattern it represents.
Internal note
cut 's incident volume by % before the launch.
Codename, customer, confidential number, unreleased product.
Safe to share
Built a system that detected a class of reliability issue and proposed fixes automatically.
The pattern, not the project. A number only if you can stand behind it publicly.
Use relative claims like "cut review time roughly in half" only if you can stand behind them, and leave numbers out if you can't share them.
Lesson: A public claim that falls apart under one follow-up question costs more than it gains.
Why Bother
The real benefit isn't a better review or a stronger résumé, though you'll get both. It's that you end up with an accurate picture of your own work. You can see which bets paid off, which skills you're actually building and where your story has gaps. That's the information you need to decide what to work on next.
A brag doc that inflates feels good for a week. One that tells the truth is useful for years.
References
- Julia Evans, Get your work recognized: write a brag document.
- Gergely Orosz, A Work Log Template for Software Engineers, The Pragmatic Engineer.