What English level do I need to read "English for Performance Review Conversations in Tech"?

This article is tagged Intermediate. If you find the vocabulary difficult, start with a related Career vocabulary exercise first, then come back — technical reading gets much easier once the core terms feel familiar.

Is this article free to read?

Yes. Every article on CoderSlingo, including this one, is free to read with no account, sign-up, or paywall.

How is reading this article different from doing an exercise?

Articles like this one explain concepts and vocabulary in context through prose, while exercises are interactive drills — fill-in-the-blank, matching, and multiple-choice — that test and reinforce specific terms. Reading builds understanding; exercises build recall.

Can I practice the vocabulary used in this article?

Yes — this article's topic lines up with our #career exercises. Use the "Practice this vocabulary" link below to jump straight into a matching drill.

How long does this article take to read?

About 8 min. Most CoderSlingo articles are written to be read in one sitting, without needing a dictionary open in another tab.

Do I need to create an account to read or save this article?

No account is required to read any article. If you complete exercises elsewhere on the site, your progress is saved locally in your browser — no login needed.

What if I don't understand a technical term used in the article?

Check the site Glossary for plain-English definitions of common IT terms — HTTP status codes, Git commands, design patterns, and more — or look up the related vocabulary module for this topic.

Can I share or link to this article?

Yes — use the Twitter/X or LinkedIn share buttons at the end of the article, or copy the page URL directly. Attribution back to CoderSlingo is appreciated but the content is free to reference.

How often is new content like this published?

New articles are added regularly across all categories, alongside new vocabulary sets and exercises. Tag pages (like this article's tags) are a good way to find related content as it's published.

Where can I find more articles like this one?

See the "Related Articles" section below for hand-picked follow-ups, or browse all Career articles from the main Blog index.

English for Performance Review Conversations in Tech

Performance reviews are high-stakes conversations. For engineers working in English as a second language, the challenge is not just doing great work — it is articulating that work confidently and precisely in a 1:1 or written self-assessment.

Self-Assessment Language

The self-assessment is your opportunity to frame your contributions before your manager does. Use strong, specific language.

Describing impact

“I delivered the new authentication service ahead of schedule, reducing login errors by 40%.”
“I led the migration to the new observability stack, resulting in 30% faster incident resolution.”
“I contributed to three cross-team initiatives and drove the adoption of our internal SDK.”

Acknowledging growth areas

Be honest but constructive:

“I recognise that I could improve my stakeholder communication, particularly around setting expectations early.”
“I struggled with prioritisation in Q2 when several high-priority items landed simultaneously — I am actively working on this.”
“I identified this gap and have taken steps to address it by…”

Avoid vague self-deprecation (“I’m not great at…”). Name the specific skill, describe what you did about it, and show progress.

Discussing Technical Contributions

Use precise technical language paired with business impact:

Contribution	Weak phrasing	Strong phrasing
Bug fix	”Fixed some bugs"	"Resolved a critical race condition that caused 2% of checkout failures.”
Code review	”Did code reviews"	"Reviewed 34 pull requests, mentoring two junior engineers on testing patterns.”
Architecture	”Helped with design"	"Authored the system design document for the event streaming refactor.”
On-call	”Was on call"	"Handled 12 incidents on call, all resolved within SLA, with three contributing to post-mortems.”

Receiving Feedback

Performance reviews involve receiving feedback, which requires specific language skills.

Asking clarifying questions

“Could you give me a specific example of when my communication fell short?”
“When you say I need to raise visibility — what would that look like in practice?”
“I want to make sure I understand — are you saying the quality or the timeliness is the concern?”

Responding to critical feedback

“That’s fair feedback. I can see how that landed differently from how I intended.”
“I hear what you’re saying. What would success look like going forward?”
“Thank you for raising this. I’d like to take some time to reflect and come back with a plan.”

Phrase: “I hear what you’re saying” — this is a professional way to acknowledge feedback without immediately agreeing or disagreeing.

Discussing Promotions and Career Growth

Asking about promotion criteria

“What evidence would you need to see to support a case for promotion?”
“Is there a gap between where I am now and the next level that I should focus on?”
“Could we align on two or three areas to prioritise for the next half?”

Advocating for yourself

“I believe I am operating at the next level in these areas: [X, Y, Z].”
“I’d like to make a case for a promotion conversation at the next cycle.”
“Over the past year, I have consistently delivered at a level above my current role.”

Asking for a stretch opportunity

“I am keen to take on more architectural responsibility.”
“I’d like to own an initiative end-to-end in the next quarter.”
“Could I shadow you in the next architecture review to develop that skill?”

Talking About Goals

Setting SMART goals in English:

Vague: “I want to get better at system design.”

SMART: “By the end of Q3, I will author one system design document for a medium-complexity project and present it in a design review. I will use the feedback to identify two areas for improvement.”

Key Phrases Cheat Sheet

Situation	Phrase
Describing impact	”…resulting in a 30% reduction in…”
Owning a gap	”I recognise that I could improve my…”
Receiving feedback	”That’s fair — could you give me a specific example?”
Asking about promotion	”What evidence would support a case for promotion?”
Advocating for yourself	”I believe I am operating at the next level in…”
Setting a goal	”By the end of [period], I will [action] [measurable outcome].”

Key Takeaways

Self-assessments should pair contributions with quantified impact — not just activities.
Use strong action verbs: led, delivered, drove, authored, resolved — not helped with or worked on.
Receiving feedback well is itself a professional skill. Clarify before reacting.
When advocating for promotion, use the language of evidence: “I believe… because…”
Goal conversations are more productive when you propose specific, measurable outcomes.