Brag document examples by role
What makes a line good
A line in a brag document has three parts: the date, what you did, and what changed because of it. A link to the evidence closes it.
- Weak. Worked on the checkout redesign.
- Better. 2026-10-08: Shipped the new checkout. Payment errors fell from 3.1% to 0.9% in two weeks. (dashboard)
The first line says where your time went. The second says what the company got for it, and it is the one your manager can repeat when your review is discussed.
The examples below are invented, and each follows that shape. Change the nouns and the numbers to yours.
Backend engineer
- 2026-10-21: Moved the invoice job from cron to the queue. Month-end close went from 6 hours to 40 minutes. (pull request) - 2026-10-14: Found the query behind the slow orders page. The slowest loads fell from 2.4 seconds to 300 milliseconds. (dashboard) - 2026-10-09: Wrote the design doc for webhooks that can be retried safely. The payments team adopted it instead of building their own. (doc) - 2026-10-02: Led the fix for the duplicate charge incident. 212 customers were refunded the same day, and a test now covers the case. (postmortem)
Engineering manager
- 2026-10-23: Hired a senior backend engineer after 14 interviews. The platform team is at full size for the first time this year. (offer thread) - 2026-10-16: Cut the roadmap from nine projects to five with product. Both teams shipped their quarter goal. (planning doc) - 2026-10-10: Wrote Priya's promotion case to senior. It was approved in this cycle. (packet) - 2026-10-03: Changed the on-call rotation from one week to three days. Pages answered after midnight fell by half. (on-call report)
Product designer
- 2026-10-22: Redesigned the sign-up form from four steps to two. Completion went from 61% to 78%. (experiment) - 2026-10-15: Ran eight interviews about exports. We dropped the PDF builder, which nobody asked for, and saved a quarter of work. (research notes) - 2026-10-08: Added the table and filter components to the design system. Three teams shipped screens without a new design review. (library) - 2026-10-01: Fixed contrast and focus order in checkout. The accessibility audit passed with no blocking issue. (audit)
Data analyst or data scientist
- 2026-10-20: Found that 30% of cancellations came from one billing error. The fix keeps about 40 accounts a month. (analysis) - 2026-10-13: Built the weekly retention dashboard. The Monday metrics meeting went from an hour to twenty minutes. (dashboard) - 2026-10-07: Showed that the pricing test had too few accounts to decide. The team ran it two more weeks and reversed the call. (notebook) - 2026-10-01: Wrote one definition of an active user with finance and product. Three reports now show the same number. (doc)
Product manager
- 2026-10-24: Shipped team invites with engineering and design. 18% of new accounts invited someone in the first week. (launch notes) - 2026-10-17: Stopped the mobile rewrite after talking to twelve customers. Two engineers moved to the API that six of them asked for. (decision doc) - 2026-10-09: Closed the pricing decision that had been open since July. Sales stopped quoting three different prices. (decision doc) - 2026-10-02: Wrote the migration plan for the old plans. Support tickets about billing fell by a third the month after. (plan)
Invisible work, by role
This is the work no board shows, and the first you forget. Give it its own section.
- Backend engineer. The review that caught a data loss before it shipped, the night on call, the runbook you wrote after it.
- Engineering manager. The conflict you settled before it reached anyone's review, the person you convinced to stay, the weekly meeting you ended for good.
- Product designer. The critique that improved someone else's screens, the handoff notes that saved engineering a week of questions.
- Data analyst or data scientist. The question you answered in chat that stopped a wrong decision, the pipeline you fixed before anyone saw a wrong number.
- Product manager. The customer call that calmed an escalation, the scope you cut so the date held.
- Every role. Interviews, the first weeks of a new colleague, mentoring.
When you have no number
Not every line has a metric, and an invented one makes the whole document less credible. Write what changed for a person instead: who could deploy, which decision closed, what stopped happening.
If you do not know the outcome yet, keep the line and mark it with (impact?). Come back when the result is in.
How Zebra writes these lines for you
Zebra keeps the one-line reason behind the top task of each day, and the promises you made in meetings and chats. On Friday, your assistant checks which of them you finished and adds one line for each to your brag document. Nothing unfinished goes in, and you can edit every line.
Set up with Claude Set up with ChatGPT