Offer Letter — Reading and Vocabulary
Learn vocabulary for reading and understanding technology offer letters.
0 / 25 completed
1 / 25
What is 'base salary' in a tech offer letter?
Base salary is the fixed annual cash compensation paid in regular instalments (bi-weekly, monthly). It is distinct from equity grants, signing bonuses, annual performance bonuses, and benefits.
2 / 25
What is a 'signing bonus' in an offer letter?
A signing bonus is a one-time payment made when the offer is accepted. It often offsets unvested equity left at a previous employer. Signing bonuses are typically subject to clawback if the employee leaves within 1–2 years.
3 / 25
What does 'cliff' mean in equity vesting vocabulary?
A 1-year cliff means no equity vests during the first year. On the 1-year anniversary, 25% of the grant typically vests at once (the cliff), then monthly or quarterly vesting continues.
4 / 25
What does 'vesting schedule' mean in an offer letter?
Vesting schedule defines when equity becomes the employee's property. Standard tech: 4-year schedule, 1-year cliff, then 1/48th vesting monthly. Unvested equity is forfeited if the employee leaves.
5 / 25
What is 'OTE' (On-Target Earnings) in an offer letter?
OTE is the total cash compensation (base + target variable) when the employee meets 100% of their performance targets. Common in sales roles. E.g., £80k base + £20k target bonus = £100k OTE.
6 / 25
Alex posted this comment on a pull request to the `authentication-service` repo:
"I've implemented rate limiting using Redis. The key is constructed as `user:{userId}:requests`. This should prevent abuse, but I'm concerned about potential false positives hitting users with high API call volumes. Should we consider adding an exponential backoff strategy for these cases?"This question assesses your ability to interpret developer communication within a code review context. The phrase 'potential false positives' is crucial vocabulary; it indicates a concern about the rate limiter incorrectly blocking legitimate users due to high API usage – this is a common problem in rate limiting design. Option A misinterprets Alex's comment, implying sole responsibility without acknowledging the potential issue. Option C is incorrect because exponential backoff isn't *always* the best solution; it depends on the specific scenario and should be discussed.
7 / 25
Sarah posted the following PR description for a new feature in the payment-gateway service:
"Implemented support for ACH transactions. The API endpoint now accepts `ACH_TRANSACTION_ID` as a required parameter. This allows us to integrate with major banks directly, reducing latency and improving reliability. We're targeting a 99.9% uptime."This question tests understanding of how developers communicate technical changes in a PR. The correct answer focuses on recognizing the value of stating KPIs and highlighting important design decisions like required parameters – this demonstrates an awareness of operational impact. Incorrect options reflect common misconceptions about PR descriptions; overly verbose language isn't helpful, and focusing solely on implementation details ignores broader considerations like monitoring. It's crucial to articulate *why* a change matters beyond just *what* was changed.
8 / 25
Daniel sent this Slack message after receiving his offer letter from NovaTech Solutions:
"Just wanted to clarify a couple of things before I accept. The offer letter mentions 'stock options' and 'phantom stock'. Could you explain the difference between these, and what happens if I leave NovaTech within four years? Also, is there a standard non-compete agreement included?"This question tests understanding of common offer letter terminology related to equity compensation. It's crucial to differentiate between *stock options* (the right to buy) and *phantom stock* (a contractual agreement for cash value). The non-compete clause is also a standard element; the misconception here is that all these terms are simply synonymous, when they represent distinct financial arrangements. NovaTech likely uses these terms to describe different aspects of their equity program.
9 / 25
Liam sent this Slack message after reviewing the draft PR description from a new team member:
"Okay, I've read through the PR for the new user profile API. The description mentions 'SLAs' (Service Level Agreements). Can someone clarify what those are in this context? Specifically, what uptime percentage does it guarantee, and how is that measured? Also, should we include a statement about rollback procedures?"This question tests understanding of a common term in DevOps – SLAs. The key misconception is that SLAs are purely internal documentation. In reality, SLAs (Service Level Agreements) formally define the *guaranteed* level of service a product or system provides to users, usually expressed as an uptime percentage (like 99.9%) and how performance is monitored. Including details about rollback procedures in the PR description demonstrates best practice for communication and accountability – it's crucial for setting expectations and managing user experience.
10 / 25
Mark received an offer letter from Stellar Dynamics. It included a clause stating: 'A relocation bonus of up to $15,000 will be paid upon successful transfer to the company's headquarters in San Francisco.' Mark is currently living in Seattle. Which of the following best describes the *purpose* of this relocation bonus?
The relocation bonus is specifically tied to a *change* in location – moving from Seattle to San Francisco. It's designed to offset the costs and potential difficulties associated with this transition, which is a common practice when an employee moves for a job. Option A is incorrect because bonuses aren't typically used for salary decreases; options C and D are too broad and don't relate to the specific trigger (relocation).
11 / 25
Alex posted this comment on a pull request to the `authentication-service` repo:
"I've implemented rate limiting using Redis. The key is constructed as `user:{userId}:requests`. This should prevent abuse, but I'm concerned about potential false positives hitting users with high API call volumes. Should we consider adding an exponential backoff strategy for these cases?"This question assesses your ability to interpret developer communication within a code review context. The phrase 'potential false positives' is crucial vocabulary; it indicates a concern about the rate limiter incorrectly blocking legitimate users due to high API usage – this is a common problem in rate limiting design. Option A misinterprets Alex's comment, implying sole responsibility without acknowledging the potential issue. Option C is incorrect because exponential backoff isn't *always* the best solution; it depends on the specific scenario and should be discussed.
12 / 25
Sarah posted the following PR description for a new feature in the payment-gateway service:
"Implemented support for ACH transactions. The API endpoint now accepts `ACH_TRANSACTION_ID` as a required parameter. This allows us to integrate with major banks directly, reducing latency and improving reliability. We're targeting a 99.9% uptime."This question tests understanding of how developers communicate technical changes in a PR. The correct answer focuses on recognizing the value of stating KPIs and highlighting important design decisions like required parameters – this demonstrates an awareness of operational impact. Incorrect options reflect common misconceptions about PR descriptions; overly verbose language isn't helpful, and focusing solely on implementation details ignores broader considerations like monitoring. It's crucial to articulate *why* a change matters beyond just *what* was changed.
13 / 25
Daniel sent this Slack message after receiving his offer letter from NovaTech Solutions:
"Just wanted to clarify a couple of things before I accept. The offer letter mentions 'stock options' and 'phantom stock'. Could you explain the difference between these, and what happens if I leave NovaTech within four years? Also, is there a standard non-compete agreement included?"This question tests understanding of common offer letter terminology related to equity compensation. It's crucial to differentiate between *stock options* (the right to buy) and *phantom stock* (a contractual agreement for cash value). The non-compete clause is also a standard element; the misconception here is that all these terms are simply synonymous, when they represent distinct financial arrangements. NovaTech likely uses these terms to describe different aspects of their equity program.
14 / 25
Liam sent this Slack message after reviewing the draft PR description from a new team member:
"Okay, I've read through the PR for the new user profile API. The description mentions 'SLAs' (Service Level Agreements). Can someone clarify what those are in this context? Specifically, what uptime percentage does it guarantee, and how is that measured? Also, should we include a statement about rollback procedures?"This question tests understanding of a common term in DevOps – SLAs. The key misconception is that SLAs are purely internal documentation. In reality, SLAs (Service Level Agreements) formally define the *guaranteed* level of service a product or system provides to users, usually expressed as an uptime percentage (like 99.9%) and how performance is monitored. Including details about rollback procedures in the PR description demonstrates best practice for communication and accountability – it's crucial for setting expectations and managing user experience.
15 / 25
Mark received an offer letter from Stellar Dynamics. It included a clause stating: 'A relocation bonus of up to $15,000 will be paid upon successful transfer to the company's headquarters in San Francisco.' Mark is currently living in Seattle. Which of the following best describes the *purpose* of this relocation bonus?
The relocation bonus is specifically tied to a *change* in location – moving from Seattle to San Francisco. It's designed to offset the costs and potential difficulties associated with this transition, which is a common practice when an employee moves for a job. Option A is incorrect because bonuses aren't typically used for salary decreases; options C and D are too broad and don't relate to the specific trigger (relocation).
16 / 25
Alex posted this comment on a pull request to the `authentication-service` repo:
"I've implemented rate limiting using Redis. The key is constructed as `user:{userId}:requests`. This should prevent abuse, but I'm concerned about potential false positives hitting users with high API call volumes. Should we consider adding an exponential backoff strategy for these cases?"This question assesses your ability to interpret developer communication within a code review context. The phrase 'potential false positives' is crucial vocabulary; it indicates a concern about the rate limiter incorrectly blocking legitimate users due to high API usage – this is a common problem in rate limiting design. Option A misinterprets Alex's comment, implying sole responsibility without acknowledging the potential issue. Option C is incorrect because exponential backoff isn't *always* the best solution; it depends on the specific scenario and should be discussed.
17 / 25
Sarah posted the following PR description for a new feature in the payment-gateway service:
"Implemented support for ACH transactions. The API endpoint now accepts `ACH_TRANSACTION_ID` as a required parameter. This allows us to integrate with major banks directly, reducing latency and improving reliability. We're targeting a 99.9% uptime."This question tests understanding of how developers communicate technical changes in a PR. The correct answer focuses on recognizing the value of stating KPIs and highlighting important design decisions like required parameters – this demonstrates an awareness of operational impact. Incorrect options reflect common misconceptions about PR descriptions; overly verbose language isn't helpful, and focusing solely on implementation details ignores broader considerations like monitoring. It's crucial to articulate *why* a change matters beyond just *what* was changed.
18 / 25
Daniel sent this Slack message after receiving his offer letter from NovaTech Solutions:
"Just wanted to clarify a couple of things before I accept. The offer letter mentions 'stock options' and 'phantom stock'. Could you explain the difference between these, and what happens if I leave NovaTech within four years? Also, is there a standard non-compete agreement included?"This question tests understanding of common offer letter terminology related to equity compensation. It's crucial to differentiate between *stock options* (the right to buy) and *phantom stock* (a contractual agreement for cash value). The non-compete clause is also a standard element; the misconception here is that all these terms are simply synonymous, when they represent distinct financial arrangements. NovaTech likely uses these terms to describe different aspects of their equity program.
19 / 25
Liam sent this Slack message after reviewing the draft PR description from a new team member:
"Okay, I've read through the PR for the new user profile API. The description mentions 'SLAs' (Service Level Agreements). Can someone clarify what those are in this context? Specifically, what uptime percentage does it guarantee, and how is that measured? Also, should we include a statement about rollback procedures?"This question tests understanding of a common term in DevOps – SLAs. The key misconception is that SLAs are purely internal documentation. In reality, SLAs (Service Level Agreements) formally define the *guaranteed* level of service a product or system provides to users, usually expressed as an uptime percentage (like 99.9%) and how performance is monitored. Including details about rollback procedures in the PR description demonstrates best practice for communication and accountability – it's crucial for setting expectations and managing user experience.
20 / 25
Mark received an offer letter from Stellar Dynamics. It included a clause stating: 'A relocation bonus of up to $15,000 will be paid upon successful transfer to the company's headquarters in San Francisco.' Mark is currently living in Seattle. Which of the following best describes the *purpose* of this relocation bonus?
The relocation bonus is specifically tied to a *change* in location – moving from Seattle to San Francisco. It's designed to offset the costs and potential difficulties associated with this transition, which is a common practice when an employee moves for a job. Option A is incorrect because bonuses aren't typically used for salary decreases; options C and D are too broad and don't relate to the specific trigger (relocation).
21 / 25
Alex posted this comment on a pull request to the `authentication-service` repo:
"I've implemented rate limiting using Redis. The key is constructed as `user:{userId}:requests`. This should prevent abuse, but I'm concerned about potential false positives hitting users with high API call volumes. Should we consider adding an exponential backoff strategy for these cases?"This question assesses your ability to interpret developer communication within a code review context. The phrase 'potential false positives' is crucial vocabulary; it indicates a concern about the rate limiter incorrectly blocking legitimate users due to high API usage – this is a common problem in rate limiting design. Option A misinterprets Alex's comment, implying sole responsibility without acknowledging the potential issue. Option C is incorrect because exponential backoff isn't *always* the best solution; it depends on the specific scenario and should be discussed.
22 / 25
Sarah posted the following PR description for a new feature in the payment-gateway service:
"Implemented support for ACH transactions. The API endpoint now accepts `ACH_TRANSACTION_ID` as a required parameter. This allows us to integrate with major banks directly, reducing latency and improving reliability. We're targeting a 99.9% uptime."This question tests understanding of how developers communicate technical changes in a PR. The correct answer focuses on recognizing the value of stating KPIs and highlighting important design decisions like required parameters – this demonstrates an awareness of operational impact. Incorrect options reflect common misconceptions about PR descriptions; overly verbose language isn't helpful, and focusing solely on implementation details ignores broader considerations like monitoring. It's crucial to articulate *why* a change matters beyond just *what* was changed.
23 / 25
Daniel sent this Slack message after receiving his offer letter from NovaTech Solutions:
"Just wanted to clarify a couple of things before I accept. The offer letter mentions 'stock options' and 'phantom stock'. Could you explain the difference between these, and what happens if I leave NovaTech within four years? Also, is there a standard non-compete agreement included?"This question tests understanding of common offer letter terminology related to equity compensation. It's crucial to differentiate between *stock options* (the right to buy) and *phantom stock* (a contractual agreement for cash value). The non-compete clause is also a standard element; the misconception here is that all these terms are simply synonymous, when they represent distinct financial arrangements. NovaTech likely uses these terms to describe different aspects of their equity program.
24 / 25
Liam sent this Slack message after reviewing the draft PR description from a new team member:
"Okay, I've read through the PR for the new user profile API. The description mentions 'SLAs' (Service Level Agreements). Can someone clarify what those are in this context? Specifically, what uptime percentage does it guarantee, and how is that measured? Also, should we include a statement about rollback procedures?"This question tests understanding of a common term in DevOps – SLAs. The key misconception is that SLAs are purely internal documentation. In reality, SLAs (Service Level Agreements) formally define the *guaranteed* level of service a product or system provides to users, usually expressed as an uptime percentage (like 99.9%) and how performance is monitored. Including details about rollback procedures in the PR description demonstrates best practice for communication and accountability – it's crucial for setting expectations and managing user experience.
25 / 25
Mark received an offer letter from Stellar Dynamics. It included a clause stating: 'A relocation bonus of up to $15,000 will be paid upon successful transfer to the company's headquarters in San Francisco.' Mark is currently living in Seattle. Which of the following best describes the *purpose* of this relocation bonus?
The relocation bonus is specifically tied to a *change* in location – moving from Seattle to San Francisco. It's designed to offset the costs and potential difficulties associated with this transition, which is a common practice when an employee moves for a job. Option A is incorrect because bonuses aren't typically used for salary decreases; options C and D are too broad and don't relate to the specific trigger (relocation).
Frequently Asked Questions
What does the "Offer Letter — Reading and Vocabulary" exercise practise?
Learn vocabulary for reading and understanding technology offer letters.
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 "Offer Letter — Reading and 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.