Compensation & Offer Vocabulary
Master compensation vocabulary: total comp, base salary, equity, cliff, vesting, bonus, and negotiation language.
0 / 22 completed
1 / 22
Total Compensation (TC) includes:
Total compensation (TC) is the full package: base salary + target bonus + equity (annualised) + benefits. Comparing TC across offers gives a more accurate picture than base salary alone.
2 / 22
A 'cliff' in an equity grant means:
A one-year cliff means no equity vests in the first year — on the one-year anniversary, 25% vests immediately, then monthly or quarterly for the remaining 3 years.
3 / 22
RSUs (Restricted Stock Units) differ from stock options in that:
RSUs vest as actual shares — you receive shares when vested. Options give the right to buy shares at the strike price; if the share price is below the strike, options are worthless.
4 / 22
When negotiating a job offer, the phrase 'I have a competing offer' is used to:
A competing offer is legitimate negotiation leverage — it provides external market validation of your value and often prompts companies to improve their offer.
5 / 22
In a hiring context, 'levelling' refers to:
Levelling maps a candidate's experience and skills to the company's career ladder (e.g., L4/L5/L6 or Senior/Staff/Principal) — determining scope, compensation band, and expectations.
6 / 22
Sarah: 'Hey team, just finished reviewing PR#1234. The logic for handling user authentication is solid, but the error logging could be much more detailed. I've added a comment suggesting we use structured logging with timestamps and unique IDs to help debug issues quickly.'
Mark: 'Thanks, Sarah! I appreciate the feedback. We're aiming for a clean codebase, and verbose logging can add complexity. However, I understand your point about debugging. Could you elaborate on what specific information you think would be most valuable in those logs?'This scenario tests understanding of vocabulary related to constructive feedback in a code review. Option 2 demonstrates a resistance to adopting best practices (structured logging) and isn't a helpful response. Option 1 is overly simplistic and lacks the technical justification needed for a developer conversation. Option 3 shows an appropriate level of engagement, suggesting a specific tool and explaining why it's beneficial – this aligns with discussing compensation related to time invested in improving code quality. Option 4 is simply requesting clarification without adding value to the discussion.
7 / 22
PR Description
Subject: Refactor - User Profile API
Hi Team,
This PR updates the user profile API to improve performance and add rate limiting. I've implemented circuit breakers using Hystrix to prevent cascading failures under heavy load. The response times have been reduced by approximately 30% based on our initial testing.
I've included detailed documentation in the README, covering the new endpoints and configuration options. Please review and let me know if you have any questions or concerns.
Thanks,
JohnThis question tests your understanding of describing technical changes in a PR. The correct answer highlights the need for *clear* documentation – a common expectation when submitting code. Incorrect options focus on irrelevant aspects (account balance, purely performance-focused improvements, or overly simplistic interpretations of Hystrix). Good PR descriptions should clearly articulate the purpose, scope, and key features of the changes, alongside sufficient documentation.
8 / 22
Mark's follow-up question regarding the error logging in PR#1234 is primarily aimed at gathering more specific details to assess the potential impact of changes. He's not simply asking for reassurance that Sarah understands the need for detailed logs; he wants actionable information to help him evaluate whether the proposed solution—structured logging with timestamps and unique IDs—actually addresses a critical problem or introduces unnecessary complexity. The goal is to understand *what* specific data needs to be logged, and *why* it's important for troubleshooting.
Mark is probing for specifics. The initial statement about 'verbose logging adding complexity' is a common concern during code reviews, but it doesn't address the core issue: debugging. He needs to understand *what* information would be most useful in the logs – what specific data points are critical for diagnosing problems quickly and efficiently. Option A misinterprets Mark's intent; he isn't validating Sarah's understanding, but rather seeking concrete details. Options B and D represent a dismissive or overly simplistic approach to the request.
9 / 22
Sarah: 'Hey team, just finished reviewing PR#1234. The logic for handling user authentication is solid, but the error logging could be much more detailed. I've added a comment suggesting we use structured logging with timestamps and unique IDs to help debug issues quickly.'
Mark: 'Thanks, Sarah! I appreciate the feedback. We're aiming for a clean codebase, and verbose logging can add complexity. However, I understand your point about debugging. Could you elaborate on what specific information you think would be most valuable in those logs?'This scenario tests understanding of vocabulary related to constructive feedback in a code review. Option 2 demonstrates a resistance to adopting best practices (structured logging) and isn't a helpful response. Option 1 is overly simplistic and lacks the technical justification needed for a developer conversation. Option 3 shows an appropriate level of engagement, suggesting a specific tool and explaining why it's beneficial – this aligns with discussing compensation related to time invested in improving code quality. Option 4 is simply requesting clarification without adding value to the discussion.
10 / 22
PR Description
Subject: Refactor - User Profile API
Hi Team,
This PR updates the user profile API to improve performance and add rate limiting. I've implemented circuit breakers using Hystrix to prevent cascading failures under heavy load. The response times have been reduced by approximately 30% based on our initial testing.
I've included detailed documentation in the README, covering the new endpoints and configuration options. Please review and let me know if you have any questions or concerns.
Thanks,
JohnThis question tests your understanding of describing technical changes in a PR. The correct answer highlights the need for *clear* documentation – a common expectation when submitting code. Incorrect options focus on irrelevant aspects (account balance, purely performance-focused improvements, or overly simplistic interpretations of Hystrix). Good PR descriptions should clearly articulate the purpose, scope, and key features of the changes, alongside sufficient documentation.
11 / 22
Mark's follow-up question regarding the error logging in PR#1234 is primarily aimed at gathering more specific details to assess the potential impact of changes. He's not simply asking for reassurance that Sarah understands the need for detailed logs; he wants actionable information to help him evaluate whether the proposed solution—structured logging with timestamps and unique IDs—actually addresses a critical problem or introduces unnecessary complexity. The goal is to understand *what* specific data needs to be logged, and *why* it's important for troubleshooting.
Mark is probing for specifics. The initial statement about 'verbose logging adding complexity' is a common concern during code reviews, but it doesn't address the core issue: debugging. He needs to understand *what* information would be most useful in the logs – what specific data points are critical for diagnosing problems quickly and efficiently. Option A misinterprets Mark's intent; he isn't validating Sarah's understanding, but rather seeking concrete details. Options B and D represent a dismissive or overly simplistic approach to the request.
12 / 22
Sarah: 'Hey team, just finished reviewing PR#1234. The logic for handling user authentication is solid, but the error logging could be much more detailed. I've added a comment suggesting we use structured logging with timestamps and unique IDs to help debug issues quickly.'
Mark: 'Thanks, Sarah! I appreciate the feedback. We're aiming for a clean codebase, and verbose logging can add complexity. However, I understand your point about debugging. Could you elaborate on what specific information you think would be most valuable in those logs?'This scenario tests understanding of vocabulary related to constructive feedback in a code review. Option 2 demonstrates a resistance to adopting best practices (structured logging) and isn't a helpful response. Option 1 is overly simplistic and lacks the technical justification needed for a developer conversation. Option 3 shows an appropriate level of engagement, suggesting a specific tool and explaining why it's beneficial – this aligns with discussing compensation related to time invested in improving code quality. Option 4 is simply requesting clarification without adding value to the discussion.
13 / 22
PR Description
Subject: Refactor - User Profile API
Hi Team,
This PR updates the user profile API to improve performance and add rate limiting. I've implemented circuit breakers using Hystrix to prevent cascading failures under heavy load. The response times have been reduced by approximately 30% based on our initial testing.
I've included detailed documentation in the README, covering the new endpoints and configuration options. Please review and let me know if you have any questions or concerns.
Thanks,
JohnThis question tests your understanding of describing technical changes in a PR. The correct answer highlights the need for *clear* documentation – a common expectation when submitting code. Incorrect options focus on irrelevant aspects (account balance, purely performance-focused improvements, or overly simplistic interpretations of Hystrix). Good PR descriptions should clearly articulate the purpose, scope, and key features of the changes, alongside sufficient documentation.
14 / 22
Mark's follow-up question regarding the error logging in PR#1234 is primarily aimed at gathering more specific details to assess the potential impact of changes. He's not simply asking for reassurance that Sarah understands the need for detailed logs; he wants actionable information to help him evaluate whether the proposed solution—structured logging with timestamps and unique IDs—actually addresses a critical problem or introduces unnecessary complexity. The goal is to understand *what* specific data needs to be logged, and *why* it's important for troubleshooting.
Mark is probing for specifics. The initial statement about 'verbose logging adding complexity' is a common concern during code reviews, but it doesn't address the core issue: debugging. He needs to understand *what* information would be most useful in the logs – what specific data points are critical for diagnosing problems quickly and efficiently. Option A misinterprets Mark's intent; he isn't validating Sarah's understanding, but rather seeking concrete details. Options B and D represent a dismissive or overly simplistic approach to the request.
15 / 22
Sarah: 'Hey team, just finished reviewing PR#1234. The logic for handling user authentication is solid, but the error logging could be much more detailed. I've added a comment suggesting we use structured logging with timestamps and unique IDs to help debug issues quickly.'
Mark: 'Thanks, Sarah! I appreciate the feedback. We're aiming for a clean codebase, and verbose logging can add complexity. However, I understand your point about debugging. Could you elaborate on what specific information you think would be most valuable in those logs?'This scenario tests understanding of vocabulary related to constructive feedback in a code review. Option 2 demonstrates a resistance to adopting best practices (structured logging) and isn't a helpful response. Option 1 is overly simplistic and lacks the technical justification needed for a developer conversation. Option 3 shows an appropriate level of engagement, suggesting a specific tool and explaining why it's beneficial – this aligns with discussing compensation related to time invested in improving code quality. Option 4 is simply requesting clarification without adding value to the discussion.
16 / 22
PR Description
Subject: Refactor - User Profile API
Hi Team,
This PR updates the user profile API to improve performance and add rate limiting. I've implemented circuit breakers using Hystrix to prevent cascading failures under heavy load. The response times have been reduced by approximately 30% based on our initial testing.
I've included detailed documentation in the README, covering the new endpoints and configuration options. Please review and let me know if you have any questions or concerns.
Thanks,
JohnThis question tests your understanding of describing technical changes in a PR. The correct answer highlights the need for *clear* documentation – a common expectation when submitting code. Incorrect options focus on irrelevant aspects (account balance, purely performance-focused improvements, or overly simplistic interpretations of Hystrix). Good PR descriptions should clearly articulate the purpose, scope, and key features of the changes, alongside sufficient documentation.
17 / 22
Mark's follow-up question regarding the error logging in PR#1234 is primarily aimed at gathering more specific details to assess the potential impact of changes. He's not simply asking for reassurance that Sarah understands the need for detailed logs; he wants actionable information to help him evaluate whether the proposed solution—structured logging with timestamps and unique IDs—actually addresses a critical problem or introduces unnecessary complexity. The goal is to understand *what* specific data needs to be logged, and *why* it's important for troubleshooting.
Mark is probing for specifics. The initial statement about 'verbose logging adding complexity' is a common concern during code reviews, but it doesn't address the core issue: debugging. He needs to understand *what* information would be most useful in the logs – what specific data points are critical for diagnosing problems quickly and efficiently. Option A misinterprets Mark's intent; he isn't validating Sarah's understanding, but rather seeking concrete details. Options B and D represent a dismissive or overly simplistic approach to the request.
18 / 22
"Mark: 'Hey team, just finished reviewing PR#1234. The logic for handling user authentication is solid, but the error logging could be much more detailed. I've added a comment suggesting we use structured logging with
Mark is not simply asking if Sarah understands. He's seeking specifics – what does 'structured logging with ti…' actually mean in this context? This demonstrates a desire for technical detail and understanding the practical implications of the proposed change. Option A is too broad; option C reflects dissatisfaction without identifying the core issue, and option D is incorrect.
19 / 22
"During a standup meeting, David says: 'I've just finished implementing the new rate limiting feature for the user profile API. It uses Hystrix to prevent cascading failures.' What does David likely mean by 'Hystrix' in this context?"
Hystrix is a popular open-source library (now deprecated but relevant) that provides circuit breaker patterns. Circuit breakers are a design pattern used to prevent cascading failures in distributed systems – in this case, the user profile API. Option A describes a database; option C refers to computing clusters and option D describes a testing framework.
20 / 22
"A PR description reads: 'This PR updates the user profile API to improve performance and add rate limiting. I've implemented circuit breakers using Hystrix to prevent cascading failures...'. Which of the following is a key benefit of implementing circuit breakers in this scenario?"
Circuit breakers are designed to *prevent* cascading failures. By temporarily stopping requests when a dependency fails, they protect the system from being overwhelmed. Option A is incorrect because it's the opposite of circuit breaker functionality; option C describes the core purpose, and option D is an undesirable outcome (simplifying code at the expense of resilience).
21 / 22
"You receive a Slack message from a teammate: 'Just saw some weird spikes in API latency. Looks like Hystrix might be tripping and blocking legitimate requests.' What immediate action should you take?"
The teammate's observation suggests a problem with Hystrix. The immediate action should be to investigate the root cause of the latency spikes – this likely means examining the dependent services that Hystrix is protecting. Simply disabling Hystrix could mask a serious underlying issue and potentially lead to further problems.
22 / 22
Elena: 'I've submitted a compensation request for a 10% raise. I believe my recent contributions to the Project Phoenix migration have significantly increased our team's velocity.' Which of the following best describes Elena's statement regarding her compensation?Elena's statement is partially correct. While stating a desired increase and justification is important, a truly effective request needs to quantify the impact of her work (e.g., 'increased velocity by X%', or 'reduced deployment time by Y days'). Options A and C highlight missing elements, while option D overstates the completeness of the statement.
Frequently Asked Questions
What does the "Compensation & Offer Vocabulary" exercise cover?
Master compensation vocabulary: total comp, base salary, equity, cliff, vesting, bonus, and negotiation language.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Compensation & Offer Vocabulary"?
This exercise has 22 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Developer Hiring exercises?
Browse the full Developer Hiring hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.