Offer Letter Vocabulary
Practice offer letter vocabulary: base salary, signing bonus, RSU vesting schedule, offer expiry, counter-offer, and formal offer extension language.
0 / 25 completed
1 / 25
An offer letter states: 'Your ___ salary will be £85,000 per annum.' What word fits?
'Base salary' is the fixed annual compensation before bonuses, equity, or other variable components. It is always stated explicitly in an offer letter as the foundation of the compensation package.
2 / 25
What is a 'signing bonus'?
A signing bonus (also called a 'joining bonus') is a one-time payment given at the time of hire. It is commonly used to compensate candidates for unvested stock or bonuses they forfeit by leaving their current employer.
3 / 25
An offer includes '10,000 RSUs vesting over 4 years with a 1-year cliff.' What does '1-year cliff' mean?
A 1-year cliff means zero RSUs vest during the first year. After 12 months, 25% vest at once (the cliff), and the remaining 75% vest monthly or quarterly over the following 3 years. This protects the company from very short-tenure hires.
4 / 25
An HR message says 'this offer ___ on Friday at 5pm.' What word fits?
Offer letters include an expiry date to create a decision deadline. 'The offer expires on Friday' means the candidate must accept or decline before that time, after which the offer may be withdrawn or renegotiated.
5 / 25
A candidate responds to a job offer with a higher salary request. This is called a:
A counter-offer is the candidate's response proposing different terms — typically higher base salary, more equity, or a larger signing bonus. Counter-offers are a normal part of negotiation and recruiters expect them.
6 / 25
Liam: 'Hey team, just submitted PR #1234. It addresses the reported memory leak in the user authentication module. The tests all pass, and I've added a detailed comment explaining the changes.'
Maya (Lead Developer) replies: 'Great job, Liam! Can you include a line about the potential impact on API response times in your PR description?'This scenario focuses on the importance of clear communication within a code review process. 'Clarification' accurately reflects Maya's request for additional information related to the PR – specifically, how the changes might affect API response times. The other options misinterpret Maya's intent; she isn't asking Liam to change his compensation or formally amend the PR, and she isn't escalating a problem without justification.
7 / 25
PR #5678 describes a new feature: 'Implemented the fetchUserPreferences() endpoint for the mobile app. This utilizes GraphQL and returns user settings data in JSON format.' During a code review with Sarah, your team lead asks, 'Could you add some context about the expected API response times for this endpoint?' What phrasing would be most appropriate to include in your PR description to address her concern? The key here is anticipating potential concerns during a code review. Option 2 demonstrates proactive communication by acknowledging the possibility of impact on API response times – a common consideration for developers. Options A and D miss this crucial step; option B overcomplicates the description with unnecessary detail while option C doesn't directly address Sarah's question about performance.
8 / 25
PR #9123 describes a change to the payment processing service. 'Refactored the logic for handling recurring payments using a new asynchronous queue.' During a standup update, David (another developer) asks, 'Can we get some details on how this impacts the latency of our payment confirmations?' What phrasing should you add to your PR description to best address David's concern?The key here is anticipating David's question about latency. Option 1 focuses on error handling, which is important but not directly related to the impact on confirmation times. Option 2 – 'Include an estimate of the expected latency increase' – is precisely what's needed to address his concern. Options 3 and 4 are irrelevant to the question posed. It's crucial in a technical discussion to proactively consider potential performance implications, especially when refactoring payment processing.
9 / 25
PR #3456 describes a database migration: 'Updated the schema for the `users` table to include a new `last_login` timestamp column. This was done as part of GDPR compliance and ensures we can accurately track user activity for reporting purposes.' During a code review with Ben, your senior engineer asks, 'Can you elaborate on how this change affects query performance, particularly when retrieving large datasets?' What phrasing would be most suitable to add to the PR description to address his concern?The key here is understanding that while GDPR compliance is crucial, it doesn't automatically negate performance implications. Simply stating the change was for GDPR misses the opportunity to proactively address potential issues. Option A incorrectly frames the PR as solely focused on compliance. Option B suggests indexing improvements which might be a *solution*, but not something directly addressed in the description. Option C is the most realistic response, acknowledging that performance isn't the primary driver and therefore doesn't require immediate detail. Option D highlights the need for anticipating potential problems and proactively communicating those concerns – this demonstrates proactive communication, crucial in development.
10 / 25
You're working on a new API endpoint for user profile updates. During code review with your manager, Emily, she asks: 'I noticed this endpoint doesn't explicitly state the expected response time from the database. How could we ensure users aren't experiencing latency when updating their profiles?' Which of the following additions to your PR description would best address her concern?
PR #7890 describes a change: 'Updated the logic for handling user profile updates using a new microservice.'The correct answer is 'informative – adding a note about monitoring database query times and potential bottlenecks.' Emily's concern centers on latency, so providing information about actively monitoring performance metrics (query times) is the most relevant action. Options A focuses on documentation which isn't directly related to the *response time* of the endpoint itself. Option B suggests using benchmarks without demonstrating a real-time understanding of the system – it's premature optimization. Finally, option C is too vague and doesn't offer actionable insight.
11 / 25
Liam: 'Hey team, just submitted PR #1234. It addresses the reported memory leak in the user authentication module. The tests all pass, and I've added a detailed comment explaining the changes.'
Maya (Lead Developer) replies: 'Great job, Liam! Can you include a line about the potential impact on API response times in your PR description?'This scenario focuses on the importance of clear communication within a code review process. 'Clarification' accurately reflects Maya's request for additional information related to the PR – specifically, how the changes might affect API response times. The other options misinterpret Maya's intent; she isn't asking Liam to change his compensation or formally amend the PR, and she isn't escalating a problem without justification.
12 / 25
PR #5678 describes a new feature: 'Implemented the fetchUserPreferences() endpoint for the mobile app. This utilizes GraphQL and returns user settings data in JSON format.' During a code review with Sarah, your team lead asks, 'Could you add some context about the expected API response times for this endpoint?' What phrasing would be most appropriate to include in your PR description to address her concern? The key here is anticipating potential concerns during a code review. Option 2 demonstrates proactive communication by acknowledging the possibility of impact on API response times – a common consideration for developers. Options A and D miss this crucial step; option B overcomplicates the description with unnecessary detail while option C doesn't directly address Sarah's question about performance.
13 / 25
PR #9123 describes a change to the payment processing service. 'Refactored the logic for handling recurring payments using a new asynchronous queue.' During a standup update, David (another developer) asks, 'Can we get some details on how this impacts the latency of our payment confirmations?' What phrasing should you add to your PR description to best address David's concern?The key here is anticipating David's question about latency. Option 1 focuses on error handling, which is important but not directly related to the impact on confirmation times. Option 2 – 'Include an estimate of the expected latency increase' – is precisely what's needed to address his concern. Options 3 and 4 are irrelevant to the question posed. It's crucial in a technical discussion to proactively consider potential performance implications, especially when refactoring payment processing.
14 / 25
PR #3456 describes a database migration: 'Updated the schema for the `users` table to include a new `last_login` timestamp column. This was done as part of GDPR compliance and ensures we can accurately track user activity for reporting purposes.' During a code review with Ben, your senior engineer asks, 'Can you elaborate on how this change affects query performance, particularly when retrieving large datasets?' What phrasing would be most suitable to add to the PR description to address his concern?The key here is understanding that while GDPR compliance is crucial, it doesn't automatically negate performance implications. Simply stating the change was for GDPR misses the opportunity to proactively address potential issues. Option A incorrectly frames the PR as solely focused on compliance. Option B suggests indexing improvements which might be a *solution*, but not something directly addressed in the description. Option C is the most realistic response, acknowledging that performance isn't the primary driver and therefore doesn't require immediate detail. Option D highlights the need for anticipating potential problems and proactively communicating those concerns – this demonstrates proactive communication, crucial in development.
15 / 25
You're working on a new API endpoint for user profile updates. During code review with your manager, Emily, she asks: 'I noticed this endpoint doesn't explicitly state the expected response time from the database. How could we ensure users aren't experiencing latency when updating their profiles?' Which of the following additions to your PR description would best address her concern?
PR #7890 describes a change: 'Updated the logic for handling user profile updates using a new microservice.'The correct answer is 'informative – adding a note about monitoring database query times and potential bottlenecks.' Emily's concern centers on latency, so providing information about actively monitoring performance metrics (query times) is the most relevant action. Options A focuses on documentation which isn't directly related to the *response time* of the endpoint itself. Option B suggests using benchmarks without demonstrating a real-time understanding of the system – it's premature optimization. Finally, option C is too vague and doesn't offer actionable insight.
16 / 25
Liam: 'Hey team, just submitted PR #1234. It addresses the reported memory leak in the user authentication module. The tests all pass, and I've added a detailed comment explaining the changes.'
Maya (Lead Developer) replies: 'Great job, Liam! Can you include a line about the potential impact on API response times in your PR description?'This scenario focuses on the importance of clear communication within a code review process. 'Clarification' accurately reflects Maya's request for additional information related to the PR – specifically, how the changes might affect API response times. The other options misinterpret Maya's intent; she isn't asking Liam to change his compensation or formally amend the PR, and she isn't escalating a problem without justification.
17 / 25
PR #5678 describes a new feature: 'Implemented the fetchUserPreferences() endpoint for the mobile app. This utilizes GraphQL and returns user settings data in JSON format.' During a code review with Sarah, your team lead asks, 'Could you add some context about the expected API response times for this endpoint?' What phrasing would be most appropriate to include in your PR description to address her concern? The key here is anticipating potential concerns during a code review. Option 2 demonstrates proactive communication by acknowledging the possibility of impact on API response times – a common consideration for developers. Options A and D miss this crucial step; option B overcomplicates the description with unnecessary detail while option C doesn't directly address Sarah's question about performance.
18 / 25
PR #9123 describes a change to the payment processing service. 'Refactored the logic for handling recurring payments using a new asynchronous queue.' During a standup update, David (another developer) asks, 'Can we get some details on how this impacts the latency of our payment confirmations?' What phrasing should you add to your PR description to best address David's concern?The key here is anticipating David's question about latency. Option 1 focuses on error handling, which is important but not directly related to the impact on confirmation times. Option 2 – 'Include an estimate of the expected latency increase' – is precisely what's needed to address his concern. Options 3 and 4 are irrelevant to the question posed. It's crucial in a technical discussion to proactively consider potential performance implications, especially when refactoring payment processing.
19 / 25
PR #3456 describes a database migration: 'Updated the schema for the `users` table to include a new `last_login` timestamp column. This was done as part of GDPR compliance and ensures we can accurately track user activity for reporting purposes.' During a code review with Ben, your senior engineer asks, 'Can you elaborate on how this change affects query performance, particularly when retrieving large datasets?' What phrasing would be most suitable to add to the PR description to address his concern?The key here is understanding that while GDPR compliance is crucial, it doesn't automatically negate performance implications. Simply stating the change was for GDPR misses the opportunity to proactively address potential issues. Option A incorrectly frames the PR as solely focused on compliance. Option B suggests indexing improvements which might be a *solution*, but not something directly addressed in the description. Option C is the most realistic response, acknowledging that performance isn't the primary driver and therefore doesn't require immediate detail. Option D highlights the need for anticipating potential problems and proactively communicating those concerns – this demonstrates proactive communication, crucial in development.
20 / 25
You're working on a new API endpoint for user profile updates. During code review with your manager, Emily, she asks: 'I noticed this endpoint doesn't explicitly state the expected response time from the database. How could we ensure users aren't experiencing latency when updating their profiles?' Which of the following additions to your PR description would best address her concern?
PR #7890 describes a change: 'Updated the logic for handling user profile updates using a new microservice.'The correct answer is 'informative – adding a note about monitoring database query times and potential bottlenecks.' Emily's concern centers on latency, so providing information about actively monitoring performance metrics (query times) is the most relevant action. Options A focuses on documentation which isn't directly related to the *response time* of the endpoint itself. Option B suggests using benchmarks without demonstrating a real-time understanding of the system – it's premature optimization. Finally, option C is too vague and doesn't offer actionable insight.
21 / 25
Liam: 'Hey team, just submitted PR #1234. It addresses the reported memory leak in the user authentication module. The tests all pass, and I've added a detailed comment explaining the changes.'
Maya (Lead Developer) replies: 'Great job, Liam! Can you include a line about the potential impact on API response times in your PR description?'This scenario focuses on the importance of clear communication within a code review process. 'Clarification' accurately reflects Maya's request for additional information related to the PR – specifically, how the changes might affect API response times. The other options misinterpret Maya's intent; she isn't asking Liam to change his compensation or formally amend the PR, and she isn't escalating a problem without justification.
22 / 25
PR #5678 describes a new feature: 'Implemented the fetchUserPreferences() endpoint for the mobile app. This utilizes GraphQL and returns user settings data in JSON format.' During a code review with Sarah, your team lead asks, 'Could you add some context about the expected API response times for this endpoint?' What phrasing would be most appropriate to include in your PR description to address her concern? The key here is anticipating potential concerns during a code review. Option 2 demonstrates proactive communication by acknowledging the possibility of impact on API response times – a common consideration for developers. Options A and D miss this crucial step; option B overcomplicates the description with unnecessary detail while option C doesn't directly address Sarah's question about performance.
23 / 25
PR #9123 describes a change to the payment processing service. 'Refactored the logic for handling recurring payments using a new asynchronous queue.' During a standup update, David (another developer) asks, 'Can we get some details on how this impacts the latency of our payment confirmations?' What phrasing should you add to your PR description to best address David's concern?The key here is anticipating David's question about latency. Option 1 focuses on error handling, which is important but not directly related to the impact on confirmation times. Option 2 – 'Include an estimate of the expected latency increase' – is precisely what's needed to address his concern. Options 3 and 4 are irrelevant to the question posed. It's crucial in a technical discussion to proactively consider potential performance implications, especially when refactoring payment processing.
24 / 25
PR #3456 describes a database migration: 'Updated the schema for the `users` table to include a new `last_login` timestamp column. This was done as part of GDPR compliance and ensures we can accurately track user activity for reporting purposes.' During a code review with Ben, your senior engineer asks, 'Can you elaborate on how this change affects query performance, particularly when retrieving large datasets?' What phrasing would be most suitable to add to the PR description to address his concern?The key here is understanding that while GDPR compliance is crucial, it doesn't automatically negate performance implications. Simply stating the change was for GDPR misses the opportunity to proactively address potential issues. Option A incorrectly frames the PR as solely focused on compliance. Option B suggests indexing improvements which might be a *solution*, but not something directly addressed in the description. Option C is the most realistic response, acknowledging that performance isn't the primary driver and therefore doesn't require immediate detail. Option D highlights the need for anticipating potential problems and proactively communicating those concerns – this demonstrates proactive communication, crucial in development.
25 / 25
You're working on a new API endpoint for user profile updates. During code review with your manager, Emily, she asks: 'I noticed this endpoint doesn't explicitly state the expected response time from the database. How could we ensure users aren't experiencing latency when updating their profiles?' Which of the following additions to your PR description would best address her concern?
PR #7890 describes a change: 'Updated the logic for handling user profile updates using a new microservice.'The correct answer is 'informative – adding a note about monitoring database query times and potential bottlenecks.' Emily's concern centers on latency, so providing information about actively monitoring performance metrics (query times) is the most relevant action. Options A focuses on documentation which isn't directly related to the *response time* of the endpoint itself. Option B suggests using benchmarks without demonstrating a real-time understanding of the system – it's premature optimization. Finally, option C is too vague and doesn't offer actionable insight.
Frequently Asked Questions
What does the "Offer Letter Vocabulary" exercise cover?
Practice offer letter vocabulary: base salary, signing bonus, RSU vesting schedule, offer expiry, counter-offer, and formal offer extension 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 "Offer Letter Vocabulary"?
This exercise has 25 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.