Self-assessment examples for your annual review
Short answer
Use the STAR format for each accomplishment: Situation, Task, Action, Result โ each in one sentence. Pick three accomplishments tied to business outcomes, lead with a metric where you have one, and end each with the impact in dollar, time-saved, or risk-reduced terms. Calibration committees skim. STAR + numbers is the format they read.
You're here because
- Your annual review is due in 24โ72 hours
- Your form is empty and you don't know where to start
- You did good work but can't articulate it on paper
- You're worried about underselling yourself
- You want adaptable examples, not generic advice
The exact email to send
Example 1 โ IC engineer (STAR):
Situation: Production incident response was averaging 47 minutes from page to mitigation across the team.
Task: Lead the post-incident review and define a runbook update process.
Action: Wrote the runbook update template, ran 4 mock incidents with the team, integrated runbook links into the alerting tool.
Result: Median page-to-mitigation dropped to 22 minutes in Q3 โ a 53% reduction, saving an estimated ~$140K in incident-driven SLA credits over the year.
Example 2 โ Marketing manager (STAR):
Situation: Inbound lead-to-MQL conversion stalled at 12% in H1.
Task: Identify the friction and rebuild the qualification flow.
Action: A/B tested 3 form variants, replaced the lead-routing rules, retrained the SDR team on the new qualification criteria.
Result: Lead-to-MQL conversion rose to 19% in Q3, contributing roughly $420K in incremental pipeline.
Example 3 โ IC designer (STAR):
Situation: The onboarding flow had a 38% drop-off between step 2 and step 3.
Task: Diagnose and redesign the flow.
Action: Ran usability tests with 8 new users, redesigned the step transition, shipped the change with the engineering team in 6 weeks.
Result: Drop-off reduced to 17%, lifting D7 activation by 14% across new signups.
- 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 this year." Replace with a result.
- "I was responsible for X." Responsibility โ impact. Show the impact.
- Listing every project. Three sharp STAR examples beat ten vague ones.
- Modifiers without metrics ("significantly improved"). Pick a number or skip the claim.
- Crediting only the team. Calibration evaluates you โ name your specific contribution.
An illustrative example
Used three STAR examples with one numeric result each. Manager forwarded the self-assessment verbatim into calibration. Rating moved from "Meets" the previous cycle to "Exceeds" โ unlocking a 12% comp adjustment + accelerated promo eligibility. The numbers in the STAR results were what calibration cited as the deciding evidence.
Why this works
Calibration committees compare candidates across teams. They look for evidence, not enthusiasm. STAR format gives them the evidence; numeric results give them the comparison axis. The format is the same format senior engineers and execs use in their own self-assessments.
What to do next
Adapt the three examples to your work today. The Performance Review Kit includes the full STAR template, the goal-setting language for next period, the manager-feedback request, and the unfair-review response if your draft rating undersells you.
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
What if I don't have hard metrics?
Use process metrics (time saved, errors reduced, stakeholders served), team metrics (people supported, projects unblocked), or quality metrics (rework reduced, SLAs met). Most contributions can be quantified once you look.
How many examples should I include?
Three is the sweet spot. One reads thin; five gets skimmed. Calibration committees retain the top three.
Should I include things that went wrong?
Yes โ briefly, with what you learned. "Growth area" wording in 1โ2 sentences signals self-awareness without undermining the case.