How do I write a self-assessment as a developer?

Structure it as Impact, Growth, and Goals. For each accomplishment use a strong verb plus a quantified result (e.g. 'I led the migration, cutting build time by 40%'). Pair each growth area with the concrete action you are taking.

How do I ask about a promotion in a performance review?

Make it about evidence and expectations: ask what the path to the next level looks like, where the gaps are, and what specific evidence over the next cycles would support a promotion.

How should I respond to critical feedback?

Stay open. Acknowledge it, ask for a specific example, commit to a concrete action, and offer to check in later to confirm you have improved.

Performance Review & Self-Assessment Phrases

30 English phrases for writing a self-assessment, describing your impact in numbers, discussing growth areas without selling yourself short, and opening the promotion conversation.

Last reviewed: 29 May 2026

Self-assessment structure: Impact / Growth / Goals

Most reviews fit this three-part shape. Use it as a skeleton, then drop the phrases below into each part.

IMPACT — what I delivered this cycle
  • [Strong verb] + [what] + [quantified result]
  • [Strong verb] + [what] + [quantified result]
  • Theme / through-line of the period

GROWTH — what I'm developing
  • [Area] — and the concrete action I'm taking
  • [Area] — and the concrete action I'm taking

GOALS — what I'll focus on next
  • [Specific, measurable goal] by [when]
  • [Specific, measurable goal] by [when]
  • Path toward [next level], if relevant

Describing accomplishments

Lead with strong verbs and quantify wherever you can. Numbers make impact undeniable.

I led the migration of [system] to [tech], cutting [metric] by [X]%. 💡 Verb + what + measurable result. This is the gold standard.
I delivered [feature] ahead of schedule, which unblocked [team/launch].
I owned [project] end to end, from design through rollout.
I reduced [build/page/query] time from [X] to [Y].
I drove adoption of [practice/tool] across [N] teams.
I mentored [N] junior engineers, two of whom shipped their first production feature.
I improved test coverage from [X]% to [Y]%, cutting regressions by [Z]%.

Self-assessment framing

Be confident without overstating. "I" for ownership; "we" only when the win was genuinely shared.

This cycle, my biggest impact was [X], which mattered because [business reason].
I consistently delivered against my goals, and exceeded expectations on [area].
Beyond my core work, I contributed by [cross-team / hiring / docs].
A theme this period was [reliability / velocity / collaboration].
I took on more scope than last cycle, particularly around [area].

Discussing growth areas

Frame development positively. Name the area, show self-awareness, and state the action — never apologise or undersell yourself.

An area I'm actively developing is [X]; I've started [concrete action] to improve. 💡 Always pair a growth area with the action you are taking.
I want to get sharper at [skill] — I've set a goal to [specific step].
I'd like more practice with [area], and I'm looking for projects that stretch me there.
I'm working on delegating earlier so I scale my impact through others.
I recognise I can communicate progress more proactively, and I've started [weekly updates / demos].

Asking about promotion

Make it a conversation about evidence and expectations, not entitlement.

I'd like to understand what the path to [next level] looks like for me.
Based on the [level] rubric, I believe I'm already operating at the next level in [areas]. Where do you see gaps?
What would you need to see from me over the next [two cycles] to support a promotion?
Could we align on the specific evidence that would make the case for [next level]?
I'd appreciate your honest read on how close I am, and where to focus.

Giving upward feedback

Be specific, kind, and forward-looking. Describe behaviour and impact, then suggest.

One thing that would help me: clearer priorities when several things land at once.
I get the most value from our 1:1s when we [spend time on / unblock X].
It would help the team if decisions on [area] were communicated a bit earlier.
I'd love more context on the 'why' behind [roadmap changes] so I can make better trade-offs.

Responding to critical feedback

Stay open and curious. Acknowledge, ask for specifics, then commit to an action.

Thank you — that's useful. Can you give me a specific example so I understand it concretely? 💡 Specifics turn vague criticism into something you can act on.
I hear you. Here's what I'll do differently going forward: [action].
That's fair. I hadn't seen it from that angle — thanks for raising it.
I'd like to check in on this in a month to make sure I've improved. Does that work?

How to use this cheatsheet

Before writing, list your wins from notes, PRs, and incident reports — facts beat memory.
Turn each win into a "verb + what + number" sentence using the accomplishment phrases.
Choose one or two real growth areas and pair each with an action.
Practise the promotion and feedback phrases out loud before the live conversation.