Master the vocabulary for promotion justification, levelling frameworks, scope and impact language for senior engineers. Advanced
0 / 30 completed
1 / 30
A staff engineer writes in their promotion document: "I expanded my scope from the payments team to leading the cross-team checkout infrastructure redesign, coordinating three engineering teams and delivering a 60% reduction in checkout latency."
Which promotion dimension does this statement most directly evidence?
Option A is correct. Scope expansion is the single most important signal in a senior IC promotion case at most tech companies. The statement contains two key promotion signals:
Promotion dimension
Evidence in the statement
Why it matters
Scope expansion
"From the payments team to cross-team checkout infrastructure" — 1 team → 3 teams
Demonstrates operating at the next level before being given the title
Measurable impact
"60% reduction in checkout latency" — quantified business outcome
Impact at scale distinguishes staff-level from senior-level contribution
Why not the other options?
Technical complexity (B) is a secondary signal — it shows depth but not scope. A same-team refactoring, however clever, does not demonstrate staff-level scope.
People management (C) is the EM track, not the IC track. "Coordinating three teams" describes technical leadership and influence, not direct reports management.
Communication (D) is a supporting skill, not a primary promotion dimension for Staff IC.
Vocabulary to know:sphere of influence — the scope of problems an engineer defines and drives without being asked; operating at the next level — demonstrating the next grade's responsibilities before the promotion decision.
2 / 30
During a promotion calibration meeting, an engineering manager says: "Promoting Ana to Staff would be bar-raising for the team."
What does "bar-raising" mean in a promotion calibration context?
Option C reflects the standard use of "bar-raising" in promotion calibration discussions across the industry. While Amazon formalized the term in hiring, it has spread broadly.
Context
What "bar-raising" means
Hiring context
A designated interviewer whose role is to reject candidates who wouldn't raise the team's overall talent level
Promotion calibration context
Promoting this person sets a visible new standard for what Senior/Staff-level work looks like — other engineers will calibrate their expectations against this person's promotion
Why this matters in calibration: In a calibration session, managers must argue their promotion case by comparing the candidate to the current team roster and recent promotions. Saying a promotion is "bar-raising" is positive — it argues that the candidate is exceptional enough to shift the team's quality expectations upward, not just meet the existing bar.
Contrast: A promotion that is "at the bar" (meets the existing standard) is still a valid promotion, just not an unusually strong one. "Below the bar" means the candidate should not be promoted yet.
3 / 30
An engineer is told: "You're on track for Staff IC, not Engineering Manager."
What does this distinction mean in terms of how each role exercises influence?
Option B correctly describes the two distinct influence models. Understanding this distinction is essential when building a promotion case, because the evidence you need differs entirely:
Dimension
Staff IC track
Engineering Manager track
Influence mechanism
Technical authority — architecture, design decisions, mentorship through code and documentation
Organisational authority — team composition, career development, delivery accountability
Key promotion evidence
Cross-team technical problems owned, systems designed, standards set, engineers levelled up through technical mentorship
Team health, hiring, retention, project delivery, reports' career growth
Common mistake
Using people management language ("I managed X engineers") in an IC promotion case
Using technical output metrics ("I wrote 10,000 lines of code") in an EM promotion case
Vocabulary:IC ladder — the individual contributor promotion path (SWE → Senior → Staff → Principal → Distinguished/Fellow); M-ladder — the management track; dual ladders — organisations that offer both, with equivalent compensation at corresponding levels.
4 / 30
Which statement correctly describes the expected scope and influence model of a Principal-level engineer at a large tech company?
Option D reflects the standard Principal-level definition used across Google, Meta, Amazon, Microsoft, and most large tech companies. The key attributes that distinguish Principal from Staff:
Level
Typical scope
Influence model
Senior SWE
Team-level
Feature ownership, code quality within team
Staff SWE
Multi-team / cross-functional
Drives cross-team technical decisions, unblocks teams
Defines direction for the entire company or industry; rare
Key phrase: "leverage through decisions and documentation rather than personal output" — at Principal level, the engineer's impact is multiplied through the systems and standards they establish, not through the lines of code they write directly.
5 / 30
After a promotion review cycle, an engineer is told: "Your promotion was tabled at calibration."
What do "tabled" and "calibration" each mean in this North American promotion context?
Option A is correct. Both terms have precise meanings in promotion contexts that differ from everyday usage:
Term
British English
North American English
tabled
To table = to bring forward for discussion (positive)
To table = to defer, postpone, remove from current agenda
What "tabled at calibration" means operationally:
The manager submitted the promotion case but it did not pass in this cycle's calibration discussion
Reasons: insufficient evidence relative to peers promoted at the same level, insufficient calibration consensus, timing (too soon since last promotion), headcount constraints
It is not a permanent rejection — it signals the case needs strengthening for the next cycle
Calibration: The cross-manager session (often involving HR and skip-level leadership) where all promotion cases for a grade are reviewed together. Calibration ensures: (1) consistent standards across managers; (2) no one manager's ratings are systematically inflated or deflated; (3) promotion decisions can be compared against a cohort, not just evaluated in isolation. Getting calibrated refers to the normalisation of one's rating against the broader distribution.
6 / 30
Reviewer: "This PR introduces a significant performance regression. The new caching logic isn't properly handling edge cases and is leading to increased database load. Consider adding more robust error handling."
This scenario tests your ability to understand the nuances of a code review comment. The reviewer isn't just pointing out an issue; they're offering specific suggestions for improvement – adding error handling is a standard recommendation in this situation. The key difference here is constructive feedback versus simply stating a negative outcome, which would be a less helpful response.
7 / 30
"Sarah: Hey team, just wanted to let you know I'm hitting a wall with the API integration. The rate limiting is causing intermittent failures, and I've exhausted my initial troubleshooting steps. Anyone have experience with this provider? #apiintegration #help"
This exercise focuses on effective communication in a collaborative environment. Sarah is proactively seeking support, which is crucial when facing technical roadblocks. Her message clearly states the problem and asks for assistance – this is an example of good practice and demonstrates she's taking responsibility.
This question tests your understanding of API responses and rate limiting. The `429 Too Many Requests` status code combined with the `retry_after` value clearly indicates the user is exceeding their allowed requests per time window. It's a standard mechanism for controlling API usage, not an indication of a system error.
9 / 30
"PR Description: 'Fixed bug in user authentication flow. Added validation to prevent invalid login attempts.'"
This question assesses your ability to write effective PR descriptions. A good PR description focuses on *what* was changed and *why*, providing context for reviewers. Simply stating that a bug was fixed isn't sufficient; adding validation details is beneficial, but the core focus should be on the purpose of the change.
10 / 30
"Mark: 'Yesterday I spent most of my time investigating the intermittent latency issues in the payment processing service. I've identified a potential bottleneck in the database query and am currently working on optimizing it.'"
This scenario focuses on delivering concise and informative updates during a stand-up meeting. Mark is providing enough detail about his investigation, the identified bottleneck, and his current actions. A good stand-up update answers the key questions: What did you do yesterday? What are you working on today? This demonstrates proactive communication.
11 / 30
Reviewer: "This PR introduces a significant performance regression. The new caching logic isn't properly handling edge cases and is leading to increased database load. Consider adding more robust error handling."
This scenario tests your ability to understand the nuances of a code review comment. The reviewer isn't just pointing out an issue; they're offering specific suggestions for improvement – adding error handling is a standard recommendation in this situation. The key difference here is constructive feedback versus simply stating a negative outcome, which would be a less helpful response.
12 / 30
"Sarah: Hey team, just wanted to let you know I'm hitting a wall with the API integration. The rate limiting is causing intermittent failures, and I've exhausted my initial troubleshooting steps. Anyone have experience with this provider? #apiintegration #help"
This exercise focuses on effective communication in a collaborative environment. Sarah is proactively seeking support, which is crucial when facing technical roadblocks. Her message clearly states the problem and asks for assistance – this is an example of good practice and demonstrates she's taking responsibility.
This question tests your understanding of API responses and rate limiting. The `429 Too Many Requests` status code combined with the `retry_after` value clearly indicates the user is exceeding their allowed requests per time window. It's a standard mechanism for controlling API usage, not an indication of a system error.
14 / 30
"PR Description: 'Fixed bug in user authentication flow. Added validation to prevent invalid login attempts.'"
This question assesses your ability to write effective PR descriptions. A good PR description focuses on *what* was changed and *why*, providing context for reviewers. Simply stating that a bug was fixed isn't sufficient; adding validation details is beneficial, but the core focus should be on the purpose of the change.
15 / 30
"Mark: 'Yesterday I spent most of my time investigating the intermittent latency issues in the payment processing service. I've identified a potential bottleneck in the database query and am currently working on optimizing it.'"
This scenario focuses on delivering concise and informative updates during a stand-up meeting. Mark is providing enough detail about his investigation, the identified bottleneck, and his current actions. A good stand-up update answers the key questions: What did you do yesterday? What are you working on today? This demonstrates proactive communication.
16 / 30
Reviewer: "This PR introduces a significant performance regression. The new caching logic isn't properly handling edge cases and is leading to increased database load. Consider adding more robust error handling."
This scenario tests your ability to understand the nuances of a code review comment. The reviewer isn't just pointing out an issue; they're offering specific suggestions for improvement – adding error handling is a standard recommendation in this situation. The key difference here is constructive feedback versus simply stating a negative outcome, which would be a less helpful response.
17 / 30
"Sarah: Hey team, just wanted to let you know I'm hitting a wall with the API integration. The rate limiting is causing intermittent failures, and I've exhausted my initial troubleshooting steps. Anyone have experience with this provider? #apiintegration #help"
This exercise focuses on effective communication in a collaborative environment. Sarah is proactively seeking support, which is crucial when facing technical roadblocks. Her message clearly states the problem and asks for assistance – this is an example of good practice and demonstrates she's taking responsibility.
This question tests your understanding of API responses and rate limiting. The `429 Too Many Requests` status code combined with the `retry_after` value clearly indicates the user is exceeding their allowed requests per time window. It's a standard mechanism for controlling API usage, not an indication of a system error.
19 / 30
"PR Description: 'Fixed bug in user authentication flow. Added validation to prevent invalid login attempts.'"
This question assesses your ability to write effective PR descriptions. A good PR description focuses on *what* was changed and *why*, providing context for reviewers. Simply stating that a bug was fixed isn't sufficient; adding validation details is beneficial, but the core focus should be on the purpose of the change.
20 / 30
"Mark: 'Yesterday I spent most of my time investigating the intermittent latency issues in the payment processing service. I've identified a potential bottleneck in the database query and am currently working on optimizing it.'"
This scenario focuses on delivering concise and informative updates during a stand-up meeting. Mark is providing enough detail about his investigation, the identified bottleneck, and his current actions. A good stand-up update answers the key questions: What did you do yesterday? What are you working on today? This demonstrates proactive communication.
21 / 30
Reviewer: "This PR introduces a significant performance regression. The new caching logic isn't properly handling edge cases and is leading to increased database load. Consider adding more robust error handling."
This scenario tests your ability to understand the nuances of a code review comment. The reviewer isn't just pointing out an issue; they're offering specific suggestions for improvement – adding error handling is a standard recommendation in this situation. The key difference here is constructive feedback versus simply stating a negative outcome, which would be a less helpful response.
22 / 30
"Sarah: Hey team, just wanted to let you know I'm hitting a wall with the API integration. The rate limiting is causing intermittent failures, and I've exhausted my initial troubleshooting steps. Anyone have experience with this provider? #apiintegration #help"
This exercise focuses on effective communication in a collaborative environment. Sarah is proactively seeking support, which is crucial when facing technical roadblocks. Her message clearly states the problem and asks for assistance – this is an example of good practice and demonstrates she's taking responsibility.
This question tests your understanding of API responses and rate limiting. The `429 Too Many Requests` status code combined with the `retry_after` value clearly indicates the user is exceeding their allowed requests per time window. It's a standard mechanism for controlling API usage, not an indication of a system error.
24 / 30
"PR Description: 'Fixed bug in user authentication flow. Added validation to prevent invalid login attempts.'"
This question assesses your ability to write effective PR descriptions. A good PR description focuses on *what* was changed and *why*, providing context for reviewers. Simply stating that a bug was fixed isn't sufficient; adding validation details is beneficial, but the core focus should be on the purpose of the change.
25 / 30
"Mark: 'Yesterday I spent most of my time investigating the intermittent latency issues in the payment processing service. I've identified a potential bottleneck in the database query and am currently working on optimizing it.'"
This scenario focuses on delivering concise and informative updates during a stand-up meeting. Mark is providing enough detail about his investigation, the identified bottleneck, and his current actions. A good stand-up update answers the key questions: What did you do yesterday? What are you working on today? This demonstrates proactive communication.
26 / 30
Reviewer: "This PR introduces a significant performance regression. The new caching logic isn't properly handling edge cases and is leading to increased database load. Consider adding more robust error handling."
This scenario tests your ability to understand the nuances of a code review comment. The reviewer isn't just pointing out an issue; they're offering specific suggestions for improvement – adding error handling is a standard recommendation in this situation. The key difference here is constructive feedback versus simply stating a negative outcome, which would be a less helpful response.
27 / 30
"Sarah: Hey team, just wanted to let you know I'm hitting a wall with the API integration. The rate limiting is causing intermittent failures, and I've exhausted my initial troubleshooting steps. Anyone have experience with this provider? #apiintegration #help"
This exercise focuses on effective communication in a collaborative environment. Sarah is proactively seeking support, which is crucial when facing technical roadblocks. Her message clearly states the problem and asks for assistance – this is an example of good practice and demonstrates she's taking responsibility.
This question tests your understanding of API responses and rate limiting. The `429 Too Many Requests` status code combined with the `retry_after` value clearly indicates the user is exceeding their allowed requests per time window. It's a standard mechanism for controlling API usage, not an indication of a system error.
29 / 30
"PR Description: 'Fixed bug in user authentication flow. Added validation to prevent invalid login attempts.'"
This question assesses your ability to write effective PR descriptions. A good PR description focuses on *what* was changed and *why*, providing context for reviewers. Simply stating that a bug was fixed isn't sufficient; adding validation details is beneficial, but the core focus should be on the purpose of the change.
30 / 30
"Mark: 'Yesterday I spent most of my time investigating the intermittent latency issues in the payment processing service. I've identified a potential bottleneck in the database query and am currently working on optimizing it.'"
This scenario focuses on delivering concise and informative updates during a stand-up meeting. Mark is providing enough detail about his investigation, the identified bottleneck, and his current actions. A good stand-up update answers the key questions: What did you do yesterday? What are you working on today? This demonstrates proactive communication.
This exercise, "🚀 Building a Promotion Case", tests your understanding of workplace english vocabulary and phrasing through 30 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 30 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.