English for developers: performance reviews
How to Talk About Your Impact in English for Performance Reviews
October 21, 2026
The exact phrases to write a strong self-assessment and talk about your work in English, without underselling yourself or sounding arrogant.
Key Takeaways
- The formula: what you did, the measurable result, why it mattered. Most developers only write the first part.
- A qualitative result beats no result. You do not need a percentage for every line, you need a 'because of this, X changed'.
- Name your individual contribution even on a team project: 'I designed the rollback plan' credits you and the team at once.
- Pair a known mistake with what you changed afterward. It reads as ownership, not weakness.
- Lead a promotion ask with evidence, then make the ask explicit. A reviewer can agree with evidence, not with a feeling.
Most developers write a strong self-assessment in Spanish and a weak one in English. Not because the work was different, the language was. In Spanish, modesty and vague phrasing ('estuve trabajando en el proyecto de pagos') sound humble and normal. In English, the same phrasing ('I worked on the payments project') reads as low-impact, because it describes a task, not a result.
This guide gives you a three-part formula to describe your work's impact in English, with real before/after rewrites, plus the phrases for talking about mistakes and asking for a promotion without sounding uncertain.
The three-part formula for describing impact
La fórmula de tres partes para describir impacto
A strong self-assessment line has three parts: what you did, the measurable result, and why it mattered. Most developers only write the first part.
Formula: [what you did] + [the result, with a number if you have one] + [why it mattered, if it is not obvious].
Example: 'I profiled the API and found the N+1 query causing slow page loads' (what you did) + 'fixing it cut average response time from 800ms to 150ms' (the result) + 'which removed our top customer complaint that quarter' (why it mattered).
7 rewrites: vague task to quantified impact
7 reescrituras: de tarea vaga a impacto cuantificado
Instead of
"I worked on the payments project."
Write
"I led the redesign of the checkout flow, which reduced cart abandonment by 18% in the first month after launch."
Why it works: Names your specific contribution and a measurable business result, not just the project you were assigned to.
Instead of
"I helped improve performance."
Write
"I profiled the API and found the N+1 query causing slow page loads. Fixing it cut average response time from 800ms to 150ms."
Why it works: Shows the diagnosis, not just the fix, which signals technical judgment.
Instead of
"I did a lot of code reviews this quarter."
Write
"I reviewed 45 pull requests this quarter and caught three issues that would have caused production incidents, including one security vulnerability."
Why it works: A count plus a consequence is more convincing than 'a lot'.
Instead of
"I'm not sure I did that much this quarter."
Write
"This quarter I shipped two features, mentored one new hire, and reduced our CI build time by 30%."
Why it works: Replaces self-doubt with a factual list. Write the list before you write the feeling.
Instead of
"The team shipped the migration."
Write
"I was the main contributor on the database migration: I designed the rollback plan and handled the cutover with zero downtime."
Why it works: Credits the team's outcome while still naming your individual role in it.
Instead of
"I made some mistakes with the deployment process."
Write
"Early this quarter, I pushed a change that caused a 10-minute outage. I wrote the postmortem, added a staging gate to prevent it from happening again, and it has not recurred since."
Why it works: Pairs the mistake with the fix. This reads as ownership, not just an admission.
Instead of
"I think I'm ready for the next level."
Write
"Over the past two quarters I've been operating at a senior level: owning projects end to end, unblocking teammates, and making architectural decisions without supervision. I'd like to talk about what it would take to formalize that."
Why it works: States the evidence first, the request second. A reviewer can agree with evidence; they can't agree with a feeling.
How to talk about a mistake or a growth area
Cómo hablar de un error o un área de crecimiento
Omitting a known mistake from your self-assessment usually backfires if your manager brings it up first. Naming it yourself, with what you changed afterward, tends to read as more senior, not less.
- "I underestimated the complexity of ____, which pushed the timeline. Next time I'll scope more carefully before committing to a date."
- "My growth area this year is ____. I'm addressing it by ____."
- "I want to get stronger at ____. I've started doing ____ to work on it."
- "Looking back, I'd handle ____ differently: I'd ____ earlier instead of ____."
How to ask for a promotion or leveling up
Cómo pedir una promoción o subir de nivel
Asking for a promotion in your self-assessment is expected, not pushy, as long as it is backed by the evidence you already wrote above. Lead with the evidence, then make the ask explicit.
- "Based on the scope of what I've been doing this year, I'd like to talk about what it would take to move to ____."
- "I believe my work this year has been at the ____ level. Can we talk about a formal path to that title?"
- "I've been operating beyond my current level in ____ and ____. I'd like this review to include a conversation about leveling up."
For the live conversation (not just the written self-assessment), our guide on 1-on-1s has more phrases for asking for a promotion and negotiating the follow-up.
Related articles
Ready to practice your English at work?
Lingua-e has interactive exercises built around real developer conversations: standups, code reviews, retrospectives, and more. Practice until it comes naturally.
Try Lingua-e for free
Written by
Roxana LafuenteLingua-e's founder
Roxana Lafuente is a software engineer with 8+ years of experience. At the beginning of her career, even though she had already passed the First Certificate in English, she still froze every time she had to speak up in the daily standup. That was a gap nobody was fixing. After 2,000+ standups, she figured out what actually builds fluency: practice that looks like your real work. She built Lingua-e so other developers wouldn't have to take the long road to feel confident working in an international development environment.