Self-review examples
What strong ones have in common
Your self-review is the one document your manager reads before deciding your rating — and often the raw material for what they write about you. A weak one lists activities. A strong one states impact and lets the evidence carry it.
The formula
Every good self-review bullet has the same shape: what you did → why it mattered → what changed. Never stop at the first part.
Weak: "Worked on improving the API."
Strong: "Redesigned the auth token flow, which cleared a six-week support backlog and unblocked the mobile team's launch."
Example — an engineer
"This half I owned the reliability of the auth service. I shipped token rotation with a safe migration path for legacy sessions — session failures under load went to zero, and the support backlog they generated cleared within two weeks. I also fixed the flaky CI pipeline that was costing the team roughly a day per sprint, and ran sprint planning for the first time while our lead was out."
Example — a manager
"I grew the team from four to six, closing both roles in under eight weeks without lowering the bar. I introduced a weekly written status ritual that cut our standing sync time in half, and coached one report through a promotion that landed this cycle. Delivery stayed on track through the reorg: all three committed epics shipped."
Example — a designer
"I redesigned onboarding after usability sessions showed users stalling at the permissions step — activation improved and the confusion we saw in testing disappeared. I also built the first shared component library for the team, which three squads adopted this quarter, and mentored our new designer through her first end-to-end feature."
Group by theme, not by month
Reviewers think in themes: delivery, collaboration and influence, craft, growth. Organize your review the same way, two to four bullets each. A chronological list reads like a diary; a thematic one reads like a case.
Steal the rubric's words
If your company has a leveling guide or competency rubric, quote it back. When the ladder says "influences beyond their team" and your review says "influenced the roadmap of two other teams," the person scoring you doesn't have to translate — the match is checked for them. Reviewers pattern-match your words against the rubric's; make the pattern impossible to miss.
The real problem is the raw material
None of the examples above can be written from memory in one evening. The detail — the backlog cleared, the day per sprint, who was unblocked — is exactly what evaporates by review season. That's why the standard advice is to keep a brag document all year, and to frame the big wins as STAR stories.
Or let the draft write itself
Nisshi is a private work journal for your Mac built for exactly this. You log a few lines a day; it generates weekly recaps as you go and drafts a complete self-review for any date range — grounded in what you actually did, in your own words, with the details intact. Come review season, you edit instead of excavate. Everything stays on your Mac.