Master self-review vocabulary, accomplishment bullet structure, calibration terms, and how to frame feedback professionally. Intermediate
0 / 10 completed
1 / 10
You are writing your self-review and need to document your impact on the deployment pipeline. Which option is a correctly written performance self-review accomplishment bullet?
Option B is a correctly quantified accomplishment bullet. Self-review bullets are evaluated on specificity and verifiable impact, not on effort described.
Element
Weak version
Strong version (B)
Action verb
"worked on", "improved"
"Reduced" — specific, measurable verb
Baseline
Missing
"from 22 minutes" — anchors the before state
Result
Vague ("faster")
"to 9 minutes" — the after state
Method
Missing
"by parallelising the build stage" — shows the how
Business impact
Missing
"400+ engineer-hours per quarter" — translates to organisational cost
The formula:Action verb + metric (baseline → result) + method + business impact. Both calibrators and managers use this structure to assess the scope of your contribution. Vague bullets are scored lower because they provide nothing to calibrate against peers.
2 / 10
In a calibration meeting, your manager says you "exceed expectations" this cycle. A colleague asks what distinguishes this rating from "meets expectations." Which statement is most accurate?
Option C is the standard calibration-room definition used at most tech companies. The key distinction:
Rating
What it means
Evidence required
Meets expectations
Performing well at the current level. Reliable, complete, predictable.
Assigned work delivered at quality. Team contributions.
Exceeds expectations
Demonstrating impact at the next level, not just doing current-level work excellently.
Option A describes "meets expectations" — completing assigned tasks on time is the baseline, not a differentiator.
Option B describes bias, not a legitimate evaluation criterion. Calibration systems are designed to reduce this.
Option D describes a forced ranking (stack ranking) system — most modern tech companies explicitly avoid these.
Key vocabulary:calibration — the cross-manager session where ratings are compared and normalised; levelling rubric — the explicit criteria for each performance level at each job grade.
3 / 10
In your self-review, you need to address an area for growth: public speaking and presenting to large groups. Which framing is most professionally appropriate?
Option D follows the professional growth-edge framing standard used in effective self-reviews. The key pattern is: present-tense ownership + evidence of progress already made + forward goal with a timeline.
What to avoid
Why
"I am bad at X"
Absolute self-deprecation with no forward motion — reviewers read this as a fixed mindset signal
"I need to improve X"
Admission without evidence of action — no proof you are already working on it
"I will try harder"
Vague effort commitment, not a SMART goal
The correct formula:
Label the skill area positively — "actively developing my X skills" not "I am weak at X"
Show what you already did — proof you are not waiting, and that this is a growth trajectory, not a static gap
State the next measurable goal — specific, time-bound, observable
Calibrators reading side-by-side reviews respond better to evidence of velocity on a growth edge than to candid self-criticism with no action behind it.
4 / 10
Your manager writes in your performance review: "On several occasions this quarter, deliverables required significant rework after initial submission." Which performance dimension is being flagged?
Option C correctly identifies the performance dimension being flagged. Breaking down the feedback phrase:
Phrase
What it signals
"on several occasions"
Pattern, not a one-off incident — the manager is noting recurring behaviour
"deliverables required significant rework"
The output was below the expected quality bar at time of submission
"after initial submission"
The problem was caught downstream (by reviewers, QA, or stakeholders) — not caught by the author first
Relevant quality vocabulary in performance reviews:
craftsmanship — the standard of care applied to work before handoff
done vs. done-done — the distinction between "it works for me" and "it is ready for release"
rework rate — an informal metric for how often work is returned for revision
self-review — the expectation that you review your own work before submitting it to others
The appropriate response to this feedback in your self-reflection section: acknowledge the pattern, name the specific root cause (e.g. "I was not running the full test suite before PR submission"), and describe what you changed.
5 / 10
A new engineer starts their first role and receives a "90-day check-in" meeting invite three months in. Which statement best describes the purpose and nature of a 90-day review?
Option A correctly describes the standard 90-day check-in. The vocabulary distinction matters because new engineers often mistake it for a high-stakes formal evaluation.
Rating recorded, may affect bonus / promotion eligibility
Probation note (Option C): In some jurisdictions and companies, a formal probationary period exists, but it is usually documented separately and uses explicit language ("you are currently in a 90-day probationary period"). A "check-in" invitation without probationary language is not a probation review.
6 / 10
David: 'I spent 8 hours debugging this issue. It was incredibly complex and required deep investigation into the database schema.' You're writing a comment on Sarah's code review of this fix. Which phrasing best communicates your assessment while acknowledging her effort?
The key here is to balance appreciation for effort with constructive feedback. Option A is irrelevant. Option B focuses solely on quantity and ignores potential design flaws. Option C gently raises concerns about the initial design while still acknowledging David's hard work and prompting a discussion. Option D is overly dismissive.
7 / 10
Liam sends this Slack message to the team: 'Just finished implementing the new authentication flow. It's rock solid and handles thousands of requests per second! 🔥'. You need to respond professionally in a team channel. Which response is most appropriate?
Liam's message is enthusiastic but lacks specifics and doesn't invite further discussion. Option A is overly casual. Option B demonstrates a professional interest in metrics and security considerations, prompting Liam to provide more information. Options C and D are too general and don't address the potential for performance issues at scale.
8 / 10
You're writing a PR description for a new feature that improves API response times. The description should be concise and informative. Which of the following is the best approach?
A good PR description needs to clearly articulate the *impact* of the changes. Option A is vague and doesn't quantify the improvement. Option B provides specific details about the optimization and its measurable effect (30% reduction). Options C and D are too brief and lack context.
9 / 10
Maria: 'I've been struggling to get this automated test suite to run consistently. It fails intermittently, even though the code hasn't changed.' You are reviewing her report and need to offer constructive feedback. Which statement is most helpful?
Maria needs guidance to diagnose the intermittent failures. Option A offers no assistance. Option B proactively suggests investigating potential causes (dependencies, environment) and proposes a collaborative approach. Options C and D are unhelpful and potentially dismissive of her concerns.
10 / 10
During a standup meeting, you state: 'I spent the last two days debugging an issue with the payment gateway integration.' Your manager asks for more detail. Which response demonstrates effective communication and provides valuable context?
Providing details about *what* went wrong (incorrect transaction processing) and *why* it caused an issue (user errors) demonstrates accountability and understanding. Option A is too dismissive. Option B offers a clear explanation of the problem, its impact, and the solution. Options C and D are overly brief or lack crucial information.
This exercise, "📊 Performance Review Language", tests your understanding of workplace english vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Workplace English exercise for?
It's designed for IT professionals and learners who want to sound natural discussing workplace english topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Workplace English exercises?
Browse the full Workplace English exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.