Performance Review Vocabulary
Practice performance review vocabulary: rating scales, calibration sessions, review cycles, meets/exceeds expectations, and manager summaries.
0 / 25 completed
1 / 25
Your company uses 'a 5-point performance rating scale.' Your manager gives you a 4. What does knowing the scale distribution help you understand?
On a 5-point scale where 3 = 'meets expectations', a 4 = 'exceeds expectations' — above average and often tied to higher bonuses or merit increases. Understanding the intended distribution and what each level means helps you interpret your rating and career trajectory.
2 / 25
Your HR manager says 'The calibration session normalizes ratings.' What happens in a calibration session?
Calibration sessions bring together managers to discuss and align ratings across teams. The goal is consistency — ensuring a '4 exceeds expectations' means the same thing across departments, and preventing systematic leniency or harshness bias.
3 / 25
A performance summary says an employee 'meets expectations.' How is this typically interpreted in tech companies?
'Meets expectations' means solid, expected performance — the employee is doing their job well at their level. In many companies, this is the most common rating and is tied to standard merit increases. It is not negative, but 'exceeds expectations' is needed for maximum rewards.
4 / 25
Your offer letter says 'The review cycle is semi-annual.' What does this mean for your compensation?
A semi-annual review cycle means two formal performance reviews per year (often mid-year and year-end). These are typically the decision points for merit salary increases, bonus payouts, and promotion considerations.
5 / 25
Your performance review process says 'The manager writes the summary; the employee responds.' What is the purpose of the employee response?
The employee response section (also called a self-assessment response) gives employees a voice in the formal record. They can contextualize achievements, provide missing context the manager may not have had, acknowledge areas for improvement, or respectfully disagree with assessments.
6 / 25
Mark isn't dismissing Sarah entirely. He's grounding the discussion in objective data – the response time itself. The core issue isn't whether Sarah *feels* it's acceptable; rather, it's that 500ms exceeds a clearly defined performance target (200ms). This demonstrates the importance of using metrics to evaluate performance and address deviations from expected standards during code reviews.
7 / 25
Mark is discussing a newly deployed feature with his team. He states, 'The API response time for this endpoint is consistently exceeding our SLO of 1 second.' A junior developer, David, replies, 'Okay, but the system's overall CPU utilization is only at 60% – that seems low considering the load.' What is David likely implying about the root cause of the performance issue? David's comment isn't about whether the SLO itself is appropriate; instead, he's highlighting a potential bottleneck. Despite low CPU utilization, high API response times often indicate that another component – perhaps database queries, network latency, or resource contention – is limiting performance. This suggests the problem isn't solely related to the code being executed but rather a broader system constraint, which is a key concept in understanding SLOs and performance troubleshooting.
8 / 25
Your manager isn't dismissing the raw latency number (300ms), but rather emphasizing that it's not effectively addressing the business goals. A key aspect of performance reviews and discussions around SLOs is understanding how technical metrics translate into tangible impacts – in this case, likely a degraded user experience or unmet service level objectives. Focusing solely on the 300ms figure ignores the bigger picture of whether that latency is causing problems for users or impacting business value.
9 / 25
PR Description: "Implemented the new user authentication flow. Initial tests show response times are consistently under 100ms."While
100ms might seem good initially, a developer focusing on performance would recognize that it could still impact user experience, especially considering factors like network latency and device capabilities. The PR description should include metrics to assess the actual performance impact and identify potential areas for optimization – this is about proactively addressing bottlenecks before they become issues. The question highlights the importance of going beyond just 'functioning correctly' in a performance context.10 / 25
You're reviewing a PR for a new database query. The developer includes the following comment: 'This query is performing well – it's consistently under 200ms.' Your team lead responds with, 'Let's dig deeper. We need to consider the cardinality of the data being queried and whether we can optimize the indexes.' What does your team lead *most* likely want you to investigate further regarding the query's performance?
The team lead's response highlights a critical aspect of performance tuning: indexing. A low raw response time (under 200ms) doesn't guarantee good performance if the query isn't efficiently utilizing indexes to access the data. The cardinality of the data – how many rows are being returned – and index effectiveness directly impact query execution speed, making them key areas for investigation. Options A, C, and D are less relevant to the immediate concern about optimizing the query itself.
11 / 25
Mark isn't dismissing Sarah entirely. He's grounding the discussion in objective data – the response time itself. The core issue isn't whether Sarah *feels* it's acceptable; rather, it's that 500ms exceeds a clearly defined performance target (200ms). This demonstrates the importance of using metrics to evaluate performance and address deviations from expected standards during code reviews.
12 / 25
Mark is discussing a newly deployed feature with his team. He states, 'The API response time for this endpoint is consistently exceeding our SLO of 1 second.' A junior developer, David, replies, 'Okay, but the system's overall CPU utilization is only at 60% – that seems low considering the load.' What is David likely implying about the root cause of the performance issue? David's comment isn't about whether the SLO itself is appropriate; instead, he's highlighting a potential bottleneck. Despite low CPU utilization, high API response times often indicate that another component – perhaps database queries, network latency, or resource contention – is limiting performance. This suggests the problem isn't solely related to the code being executed but rather a broader system constraint, which is a key concept in understanding SLOs and performance troubleshooting.
13 / 25
Your manager isn't dismissing the raw latency number (300ms), but rather emphasizing that it's not effectively addressing the business goals. A key aspect of performance reviews and discussions around SLOs is understanding how technical metrics translate into tangible impacts – in this case, likely a degraded user experience or unmet service level objectives. Focusing solely on the 300ms figure ignores the bigger picture of whether that latency is causing problems for users or impacting business value.
14 / 25
PR Description: "Implemented the new user authentication flow. Initial tests show response times are consistently under 100ms."While
100ms might seem good initially, a developer focusing on performance would recognize that it could still impact user experience, especially considering factors like network latency and device capabilities. The PR description should include metrics to assess the actual performance impact and identify potential areas for optimization – this is about proactively addressing bottlenecks before they become issues. The question highlights the importance of going beyond just 'functioning correctly' in a performance context.15 / 25
You're reviewing a PR for a new database query. The developer includes the following comment: 'This query is performing well – it's consistently under 200ms.' Your team lead responds with, 'Let's dig deeper. We need to consider the cardinality of the data being queried and whether we can optimize the indexes.' What does your team lead *most* likely want you to investigate further regarding the query's performance?
The team lead's response highlights a critical aspect of performance tuning: indexing. A low raw response time (under 200ms) doesn't guarantee good performance if the query isn't efficiently utilizing indexes to access the data. The cardinality of the data – how many rows are being returned – and index effectiveness directly impact query execution speed, making them key areas for investigation. Options A, C, and D are less relevant to the immediate concern about optimizing the query itself.
16 / 25
Mark isn't dismissing Sarah entirely. He's grounding the discussion in objective data – the response time itself. The core issue isn't whether Sarah *feels* it's acceptable; rather, it's that 500ms exceeds a clearly defined performance target (200ms). This demonstrates the importance of using metrics to evaluate performance and address deviations from expected standards during code reviews.
17 / 25
Mark is discussing a newly deployed feature with his team. He states, 'The API response time for this endpoint is consistently exceeding our SLO of 1 second.' A junior developer, David, replies, 'Okay, but the system's overall CPU utilization is only at 60% – that seems low considering the load.' What is David likely implying about the root cause of the performance issue? David's comment isn't about whether the SLO itself is appropriate; instead, he's highlighting a potential bottleneck. Despite low CPU utilization, high API response times often indicate that another component – perhaps database queries, network latency, or resource contention – is limiting performance. This suggests the problem isn't solely related to the code being executed but rather a broader system constraint, which is a key concept in understanding SLOs and performance troubleshooting.
18 / 25
Your manager isn't dismissing the raw latency number (300ms), but rather emphasizing that it's not effectively addressing the business goals. A key aspect of performance reviews and discussions around SLOs is understanding how technical metrics translate into tangible impacts – in this case, likely a degraded user experience or unmet service level objectives. Focusing solely on the 300ms figure ignores the bigger picture of whether that latency is causing problems for users or impacting business value.
19 / 25
PR Description: "Implemented the new user authentication flow. Initial tests show response times are consistently under 100ms."While
100ms might seem good initially, a developer focusing on performance would recognize that it could still impact user experience, especially considering factors like network latency and device capabilities. The PR description should include metrics to assess the actual performance impact and identify potential areas for optimization – this is about proactively addressing bottlenecks before they become issues. The question highlights the importance of going beyond just 'functioning correctly' in a performance context.20 / 25
You're reviewing a PR for a new database query. The developer includes the following comment: 'This query is performing well – it's consistently under 200ms.' Your team lead responds with, 'Let's dig deeper. We need to consider the cardinality of the data being queried and whether we can optimize the indexes.' What does your team lead *most* likely want you to investigate further regarding the query's performance?
The team lead's response highlights a critical aspect of performance tuning: indexing. A low raw response time (under 200ms) doesn't guarantee good performance if the query isn't efficiently utilizing indexes to access the data. The cardinality of the data – how many rows are being returned – and index effectiveness directly impact query execution speed, making them key areas for investigation. Options A, C, and D are less relevant to the immediate concern about optimizing the query itself.
21 / 25
Mark isn't dismissing Sarah entirely. He's grounding the discussion in objective data – the response time itself. The core issue isn't whether Sarah *feels* it's acceptable; rather, it's that 500ms exceeds a clearly defined performance target (200ms). This demonstrates the importance of using metrics to evaluate performance and address deviations from expected standards during code reviews.
22 / 25
Mark is discussing a newly deployed feature with his team. He states, 'The API response time for this endpoint is consistently exceeding our SLO of 1 second.' A junior developer, David, replies, 'Okay, but the system's overall CPU utilization is only at 60% – that seems low considering the load.' What is David likely implying about the root cause of the performance issue? David's comment isn't about whether the SLO itself is appropriate; instead, he's highlighting a potential bottleneck. Despite low CPU utilization, high API response times often indicate that another component – perhaps database queries, network latency, or resource contention – is limiting performance. This suggests the problem isn't solely related to the code being executed but rather a broader system constraint, which is a key concept in understanding SLOs and performance troubleshooting.
23 / 25
Your manager isn't dismissing the raw latency number (300ms), but rather emphasizing that it's not effectively addressing the business goals. A key aspect of performance reviews and discussions around SLOs is understanding how technical metrics translate into tangible impacts – in this case, likely a degraded user experience or unmet service level objectives. Focusing solely on the 300ms figure ignores the bigger picture of whether that latency is causing problems for users or impacting business value.
24 / 25
PR Description: "Implemented the new user authentication flow. Initial tests show response times are consistently under 100ms."While
100ms might seem good initially, a developer focusing on performance would recognize that it could still impact user experience, especially considering factors like network latency and device capabilities. The PR description should include metrics to assess the actual performance impact and identify potential areas for optimization – this is about proactively addressing bottlenecks before they become issues. The question highlights the importance of going beyond just 'functioning correctly' in a performance context.25 / 25
You're reviewing a PR for a new database query. The developer includes the following comment: 'This query is performing well – it's consistently under 200ms.' Your team lead responds with, 'Let's dig deeper. We need to consider the cardinality of the data being queried and whether we can optimize the indexes.' What does your team lead *most* likely want you to investigate further regarding the query's performance?
The team lead's response highlights a critical aspect of performance tuning: indexing. A low raw response time (under 200ms) doesn't guarantee good performance if the query isn't efficiently utilizing indexes to access the data. The cardinality of the data – how many rows are being returned – and index effectiveness directly impact query execution speed, making them key areas for investigation. Options A, C, and D are less relevant to the immediate concern about optimizing the query itself.
Frequently Asked Questions
What does the "Performance Review Vocabulary" exercise practise?
Practice performance review vocabulary: rating scales, calibration sessions, review cycles, meets/exceeds expectations, and manager summaries.
How many questions are in this exercise?
This exercise has 25 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Compensation Leveling category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Performance Review Vocabulary" part of a larger series?
Yes — it's one exercise in the Compensation Leveling category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Compensation Leveling category page for related exercises, or browse the main Exercises hub for other IT English topics.