performance review

feedback language

one-on-one

hiring panel

sprint retrospective

How to Describe Colleagues in English at Work Reviews

ESL English learning: Master performance review vocabulary to describe engineer strengths, weaknesses, and growth areas professionally.

Pronunciation Guide: Trait Vocabulary

Many performance vocabulary words are mispronounced in spoken feedback. Use this guide to sound confident in 1:1s and hiring panels.

conscientious /ˌkɒn.ʃiˈen.ʃəs/

con-shi-EN-shus

Saying 'con-SHENT-ious' — the stress is on the third syllable

diligent /ˈdɪl.ɪ.dʒənt/

DIL-i-jent

Pronouncing the 'g' as /g/ instead of /dʒ/

methodical /məˈθɒd.ɪ.kəl/

muh-THOD-i-kul

Stressing the first syllable: *METH-od-i-cal

astute /əˈstjuːt/

uh-STYOOT

Saying 'ASS-toot' with wrong stress and vowel

brusque /brʊsk/

BRUSK (one syllable)

Adding a second syllable: *'bru-SKAY'

Why Word Choice Matters in Performance Reviews

When you write a 360-degree review or give sprint feedback, every word carries weight. Calling someone 'resolute' signals a strength; calling them 'stubborn' flags a problem. Both describe someone who doesn't change their mind easily — but the connotation is completely different.

In tech workplaces, written feedback lives in HR systems for years. Choosing vocabulary carefully protects your colleague's reputation and demonstrates your own communication maturity.

Culture Note: Direct vs. Diplomatic Feedback

In many Western tech companies, feedback is expected to be direct but constructive. However, 'direct' doesn't mean 'harsh.' A phrase like 'tends to be tactless in code reviews' is too blunt for most performance docs. Try: 'Could benefit from more diplomatic phrasing when giving feedback.'

Positive vs. Negative Trait Vocabulary for Engineers

Many personality traits exist on a spectrum. The same behavior can be framed positively or negatively depending on your word choice. Use the table below to select vocabulary that matches your intended message.

Positive Framing	Negative Framing	What It Describes	Tech Example
diligent, industrious	work-obsessed, workaholic	works very hard	She's diligent about testing edge cases vs. He's work-obsessed and burns out teammates
resolute, dogged	stubborn, obstinate	doesn't give up easily	He was resolute in debugging the memory leak vs. She's stubborn and won't consider alternative approaches
shrewd, astute	cunning, sly	makes clever decisions	Our PM is astute at prioritizing features vs. He's cunning about taking credit for team wins
methodical, conscientious	inflexible, dogmatic	careful and systematic	She's methodical in her code reviews vs. He's inflexible about coding standards
thrifty, frugal	stingy, parsimonious	careful with resources	The team is frugal with cloud costs vs. Management is stingy with the training budget
witty, pithy	brusque, terse	speaks concisely	Her RFC summaries are pithy and clear vs. His Slack replies are brusque and feel dismissive

Grammar Tip: Adjective + Preposition Patterns

Many trait adjectives take specific prepositions. Learn these patterns: 'diligent about (quality)', 'astute at (skill)', 'tolerant of (difference)', 'supportive of (colleagues)'. Wrong prepositions sound unnatural: *'She is diligent at testing' → 'She is diligent about testing.'

Scenario 1: Writing a 360-Degree Performance Review

In 360 reviews, you describe a colleague's strengths, growth areas, and impact. Avoid vague words like 'nice' or 'good.' Use specific vocabulary paired with evidence.

Weak / Vague	Strong / Specific
She is a good engineer.	She is a methodical engineer who consistently catches edge cases in code review.
He is bad at communication.	He tends to be brusque in written feedback, which can feel dismissive to junior engineers.
She works too much.	She is diligent to a fault — I'd encourage her to delegate more to avoid burnout.
He's nice to work with.	He is obliging and supportive — always willing to unblock teammates during on-call rotations.

obliging — ready to help others; willing to do favors
supportive — gives encouragement and practical help
altruistic — puts team needs above personal recognition
conscientious — takes responsibilities seriously; thorough
down-to-earth — practical, sensible, not pretentious

Scenario 2: Giving Structured Feedback After a Sprint

Sprint retros and 1:1s require real-time feedback vocabulary. You need phrases that are honest but constructive. Here's how to reframe negative traits diplomatically.

Heard at Work (Too Direct)	Better English (Diplomatic)
You got carried away with the refactor and missed the deadline.	You're enthusiastic about code quality — let's discuss scoping refactors to stay on timeline.
You're stubborn about your technical opinions.	You're resolute in defending your architecture choices. Could you also explore alternatives the team suggests?
Your Slack messages are terse and rude.	Your messages are efficient, but adding context would help the team understand your reasoning.
You're a perfectionist and it slows us down.	Your attention to detail is valuable. Let's calibrate what 'good enough' looks like for MVP features.

Phrase Pattern: [Positive Trait] + 'Let's discuss [growth area]'

This pattern acknowledges strength before addressing growth: 'You're intuitive about user needs — let's discuss how to document that intuition in your design docs so others can learn from it.'

Scenario 3: Describing a Candidate to a Hiring Panel

When debriefing after interviews, your vocabulary shapes hiring decisions. Be precise about strengths and concerns. Avoid words that sound biased or unprofessional.

Trait to Describe	Professional Vocabulary	Example Sentence
Good instincts	intuitive, astute	She was intuitive about system design trade-offs without needing detailed prompts.
Very experienced	shrewd, seasoned	He's a shrewd debugger — he isolated the race condition in minutes.
Friendly personality	magnetic, personable	She has a magnetic presence that would energize the team.
Lacks confidence	insecure, uncertain	He seemed insecure when defending his design choices under pressure.
Overconfident	tactless, dismissive	She was tactless when the interviewer challenged her assumptions.
Inexperienced	naive, green	He's a bit naive about production scale, but trainable.

intuitive — understands things instinctively without needing explanation
magnetic — has a personality that naturally attracts and engages others
tactless — says things that unintentionally upset or offend people
naive — lacks experience; trusts too easily
insecure — not confident; uncertain about own abilities

Register: Slack vs. Performance Documents

The same trait needs different vocabulary depending on where you're writing. Slack tolerates casual language; performance docs and hiring feedback require professional register.

Meaning	Casual (Slack / Chat)	Formal (Docs / Reviews)
Works very hard	She's a total workhorse	She is exceptionally diligent
Practical, sensible	He's super down-to-earth	He takes a pragmatic, grounded approach
Helps others	She's always got your back	She is reliably supportive and obliging
Talks too much	He rambles a lot	He can be somewhat verbose in meetings
Makes clever decisions	She's sharp	She demonstrates shrewd judgment

Frequently asked questions

How do I describe a colleague who is stubborn without sounding rude in a performance review?

Replace 'stubborn' with positive-frame alternatives like 'resolute,' 'principled,' or 'steadfast'—then add evidence and impact. Example: 'He is resolute in his technical decisions; he pushed back on a risky database migration, which protected our stability.' If you must note inflexibility as a growth area, use behavioral language: 'She can improve by soliciting peer input earlier in the design phase,' not 'She is stubborn.' This protects your colleague's reputation while keeping the feedback actionable and professional.

What's the difference between 360 review language and how I talk to a colleague in Slack?

360 reviews and formal performance documents require elevated, precise vocabulary—use trait words like 'meticulous,' 'proactive,' or 'astute' with specific examples. Slack allows casual phrasing like 'great catch on that bug' or 'you crushed that deadline.' In 360 reviews, write 'She demonstrated exceptional attention to detail by identifying edge cases in the payment flow,' whereas in Slack you might say 'Nice work spotting that edge case!' Always match your register to the document's permanence: HR systems demand professional vocabulary that will protect both you and your colleague.

How do I give negative feedback about an engineer's performance without damaging their reputation?

Frame growth areas behaviorally and future-focused, not as character flaws. Instead of 'He lacks communication skills,' write 'He can improve stakeholder alignment by sharing progress updates twice weekly' or 'She would benefit from documenting decisions earlier in the sprint.' Use this pattern: specific behavior + impact + clear improvement action. Avoid loaded words like 'lazy,' 'careless,' or 'difficult'; instead use 'can prioritize,' 'would benefit from a checklist,' or 'can collaborate more actively.' This approach signals professionalism and helps your colleague improve without creating a negative permanent record.

What vocabulary should I use when describing a colleague to a hiring panel after an interview?

Use precise, evidence-backed trait vocabulary without bias: 'methodical,' 'collaborative,' 'detail-oriented,' or 'innovative.' Always pair traits with concrete examples: 'She is methodical—she walked through her debugging approach step-by-step and caught the root cause quickly.' Avoid vague words ('nice,' 'good') and subjective judgments ('she seemed nervous'). For concerns, use professional language: 'His system design approach could be more scalable' rather than 'He's not a strong architect.' This vocabulary demonstrates your credibility to the hiring panel and ensures fair, bias-resistant candidate feedback.

How do I follow up or correct feedback I gave about a colleague that might have sounded too negative?

If your feedback was too harsh, request a brief follow-up conversation with the recipient and reframe it constructively: 'I want to clarify—what I meant was that you have the opportunity to improve X by doing Y.' Resubmit written feedback if it's still in draft form in your HR system. Use this template: acknowledge the original statement + reframe with positive intent + provide actionable path forward. Example: 'When I said you need to improve documentation, I meant: your technical work is solid, and adding more detailed comments would make code reviews faster for the team.' This shows maturity and protects both your professional reputation and engineer performance relationships.