The Brag Document: The Interview Prep Tool Every 2026 Candidate Should Keep

A resume is a highlight reel. A brag document is the raw material behind it. When your manager asks in a 1:1 what you have delivered this quarter, or a recruiter asks for a STAR example, or a promotion committee asks for evidence of scope, you cannot rely on memory. Humans overestimate recent work and forget everything older than 60 days. A brag document eliminates that failure mode.

It also compounds. After 2 years of weekly entries you have 100 concrete examples, feedback quotes, metrics and stories. Any interview or promotion case becomes a matter of selection, not creation.

Set a 15 minute recurring block on Friday afternoons. Answer four questions in writing.

• What did I ship or complete this week?
• What was the measurable outcome? (metric, dollar, percentage, count)
• What feedback did I get, in whose words? (paste verbatim if possible)
• What did I learn or teach someone else?

Every soft-looking outcome has a metric hiding behind it. 'I improved team morale' becomes 'I ran 6 retros and eNPS moved from 6.2 to 7.8'. 'I mentored a junior' becomes 'I onboarded 2 hires in 4 weeks vs the 8 week baseline'. 'I fixed a flaky test suite' becomes 'CI green rate went from 71 to 96 percent, saving an average of 42 minutes per PR'.

If you cannot find a number, log the counterfactual: what would have gone wrong if you had not done this? That question surfaces value that dashboards miss.

Quarterly and yearly, refactor the raw weekly log into a structured document with named sections: Impact, Scope, Leadership, Craft, Communication, Culture. Under each, keep 3 to 5 top examples with metrics and quotes. This structure maps directly to how promotion rubrics are written at Amazon, Google, Meta, Microsoft and most other companies in 2026.

For interviews, do the same mapping against the target company's leadership principles or values. Amazon LPs, Google Googliness, Stripe operating principles, Meta values, all can be pre-mapped so you never scramble in the room.

Two weeks before your review, filter the last 12 to 18 months of entries and produce a 2 page self-review draft. Send it to your manager 48 hours before the meeting so they can pre-read. Managers who receive a structured self-review write markedly better formal reviews, because they now have the raw material to defend a strong rating to calibration committees.

Two days before a behavioural interview, extract 8 to 10 stories from the brag doc that map to the interviewer's rubric. Write each in STAR: Situation, Task, Action, Result. Read them out loud once. During the interview you will now retrieve them naturally rather than freeze on the classic 'tell me about a time' prompt.

For technical interviews, the brag doc gives you tangible portfolio material to reference: architecture decisions you made, migrations you led, incidents you handled. Interviewers remember specific detail, not generic claims.

Any tool you will actually open works: Notion, Obsidian, a plain markdown file in a private GitHub repo, Apple Notes, even a Google Doc. Do not use your work laptop or work SaaS account, you will lose it the day you leave. The anti-pattern is over-tooling: candidates who spend 3 weeks building a fancy Airtable brag doc rarely maintain it. A boring text file, updated every Friday, beats an elegant tool used twice.