Performance review accomplishments — examples that get you promoted
Short answer
Each accomplishment should compress into one sentence: verb + outcome + metric + scope. "Led migration of [system] from [X] to [Y], reducing [metric] by [N%] across [N teams]." Three to five of these — across reliability, leverage, mentorship, and one cross-team item — is more powerful than ten generic bullets. Real examples below.
You're here because
- Your review is in 24–72 hours and the accomplishments box is empty
- You did good work but can't recall what specifically
- You don't know how to phrase impact without bragging
- Your manager said "just put down a few wins" and that's the whole guidance
- You want the rating to land Meets+ or Exceeds
The exact email to send
Reliability / Quality
Reduced p99 latency on the checkout service by 38% (from 820ms → 510ms) by introducing per-region read replicas; eliminated 4 quarterly P1 incidents across Q2–Q4.
Leverage / Productivity
Cut team CI runtime by 62% (24min → 9min); estimated dev-hours saved: ~25/week across 8 engineers; pattern adopted by 2 other teams in Q3.
Mentorship / People
Onboarded 2 new hires from week-1 to first-shipped-PR in <2 weeks (team baseline: 4 weeks); wrote the onboarding doc now used by the next 4 hires.
Cross-team / Strategic
Led the cross-team [PROJECT_NAME] migration affecting 3 services and 4 teams; delivered 3 weeks ahead of schedule; cited as the reference implementation in the Q4 architecture review.
Customer / External
Shipped [FEATURE] in Q3; adoption hit [N%] of target accounts within 60 days; tied to $[REVENUE] in expansion ARR.
(The kit includes 12+ accomplishment examples across IC, lead, manager, and IC4–IC6 levels.)
- Built for the moment a written offer or deadline lands — not casual browsing.
- Written for the 24–72 hour decision window.
- Designed for people who don't negotiate often.
- Real workplace register — not internet bravado.
What NOT to say
- "I worked hard on…" — invisible to a calibration committee.
- "I helped with…" — never own outcomes vaguely.
- Long paragraphs. One-sentence bullets convert; paragraphs get skimmed.
- Vague metrics ("a lot", "significant"). Always a number or a count.
- Listing low-leverage activities (meetings attended, emails sent). Outcomes only.
An illustrative example
An engineer wrote 5 accomplishment bullets using the format above. Their manager copy-pasted three of them into the calibration deck. The skip-level cited the "38% p99 reduction" item as the deciding factor for Meets+. Meets+ rating + an unexpectedly accelerated promo track to Senior.
Why this works
Calibration committees see hundreds of bullet points. The ones that survive committee are the ones that compress into a single sentence: verb + outcome + metric + scope.
What to do next
Block 60 minutes today. List your top 5 wins. Convert each to one sentence in this format. The Performance Review Kit includes the full STAR-version of each, plus the "areas for growth" section that doesn't tank your rating.
Before you send — quick check
- Have you listed 3 outcomes in STAR format with numbers?
- Have you mapped them to the next level's scope?
- Have you removed every adjective ("great", "strong") and replaced with metrics?
If you answered "not sure" to any of these, the Performance Review Kit walks you through all three.
Related reads
FAQ
How many accomplishments should I list?
3 to 5. More dilutes the message. Calibration committees skim.
Do accomplishments need to be quantified?
Yes. If something can't be quantified, it's a task, not impact. Use leverage metrics if direct numbers aren't available.
What format do calibration committees actually read?
Whatever the manager pastes into the calibration deck — typically one-line bullets. Write for that medium.