Negotiation Strategy Vocabulary Quiz
Master negotiation strategy vocabulary: BATNA, counter-offer language, competing offers, total compensation discussion, and anchoring.
0 / 25 completed
1 / 25
What does BATNA stand for, and why is it important in salary negotiations?
BATNA (Best Alternative to a Negotiated Agreement) is your fallback option if negotiations fail. A strong BATNA (a competing offer, a current role you're happy in) gives you genuine leverage — you're negotiating from strength, not desperation.
2 / 25
A candidate says: 'I'd like to counter at $145,000.' What is a counter-offer?
A counter-offer is a response that proposes different terms — typically a higher salary, more equity, or other benefits. It keeps the negotiation open and signals the candidate wants to reach an agreement, just at better terms.
3 / 25
A candidate says: 'I have a competing offer.' How does this affect a negotiation?
A competing offer is the most powerful negotiation lever — it's not just a claim about market value, it's proof. Employers know the candidate will leave if they don't respond, and it shifts the negotiation from abstract to concrete.
4 / 25
What does 'let's discuss the total compensation package' signal in a negotiation?
Shifting to total compensation broadens the negotiation: if base salary is at the cap, there may be room to increase equity, sign-on bonus, PTO, or other benefits. It's a signal to look at the full picture rather than a single number.
5 / 25
What is 'anchoring' in a salary negotiation?
Anchoring is the cognitive bias that the first number stated becomes the reference point for all subsequent negotiation. Stating a specific high number first (e.g. '$155,000 base') tends to shift the final outcome higher than if you wait for the employer to anchor first.
6 / 25
PR #1234 has just been submitted. During the code review, Sarah points out a potential performance bottleneck in the data processing logic. Mark responds with: 'Okay, let's discuss the total compensation package to see if we can accommodate this extra effort.' What is Mark *primarily* trying to do at this stage of the negotiation?
Mark isn't directly addressing the technical issue of the bottleneck. Instead, he's employing a negotiation tactic by broadening the conversation to include 'total compensation,' which is often shorthand for discussing resources like additional time, support staff, or perhaps even budget allocated for optimization efforts. This frames the discussion beyond just the immediate code change and attempts to establish a mutually agreeable framework for addressing the problem – a common strategy when facing pushback on development tasks.
7 / 25
PR #5678 has been submitted for the new user authentication module. During a Slack discussion, Alex says: 'I'm pushing for a 30% bonus on top of the base salary – that reflects the complexity and the impact this feature will have.' Ben replies: 'That's ambitious. Let's explore options to reduce the scope slightly before discussing performance-based bonuses.' What is Ben *most likely* attempting to achieve by suggesting a reduction in scope?Ben is employing 'anchoring,' a common negotiation tactic where the first proposed number significantly influences subsequent offers. By initially demanding a 30% bonus, he's setting a high benchmark; Ben's response signals that this figure is likely too aggressive and proposes a way to adjust the situation before further discussion on bonuses occurs. The incorrect options misinterpret Ben's response as simply accepting a lower bonus or focusing solely on scope reduction without acknowledging the initial anchor.
8 / 25
PR #9012 has been submitted for the new API endpoint. During a standup update, David states: 'I'm aiming for a 5% equity stake in the company alongside my salary – it's crucial to align my incentives with the long-term success of the product.' Maria responds: 'That's a significant ask, David. Could you elaborate on how that aligns with our current vesting schedule and future funding rounds?' What is Maria *primarily* assessing during her response?Maria isn't simply acknowledging David's request; she's probing its practical implications. The question focuses on assessing alignment – a key negotiation concept – by examining how the equity stake interacts with existing structures like vesting schedules and future funding rounds. This demonstrates an understanding that equity is more than just a bonus, and requires careful consideration of long-term company strategy. Option A is incorrect as it's about valuation, not strategic alignment.
9 / 25
PR #3456 has been submitted for a new microservice. During a code review, Emily suggests refactoring the service to use a more efficient data structure. John responds: 'That's a good point about performance. Let's explore options to reduce the scope slightly before discussing potential impact on future feature development.' What is John *most likely* attempting to do in this conversation? John's response highlights the concept of 'scope management' – recognizing that a seemingly beneficial change (optimizing data structures for performance) could have unintended consequences if not considered within the broader context of future development. The phrase 'explore options to reduce the scope' indicates he is advocating for prioritizing immediate tasks and delaying deeper dives into complex issues until they are directly relevant to current deliverables. This demonstrates an understanding of pragmatic negotiation, focusing on achievable outcomes rather than demanding immediate solutions.
10 / 25
PR #7890 has been submitted for a new caching layer. During a Slack message between two developers, Liam says: 'I'm targeting a 15% raise to reflect the added value this caching layer will bring.' Chloe replies: 'While I appreciate the improvement, let's discuss the total compensation package and see if we can factor in potential increased support responsibilities as the system scales.' What is Chloe *primarily* attempting to do with her statement? Chloe isn't simply rejecting Liam's request; she's skillfully redirecting the conversation. Her phrase 'let's discuss the total compensation package' signals an intent to move beyond a purely individual benefit negotiation and consider how Liam's work impacts the larger system and team strategy – a key element of successful development negotiations. This avoids getting locked into a short-sighted discussion about salary alone, which is more beneficial for both parties.
11 / 25
PR #1234 has just been submitted. During the code review, Sarah points out a potential performance bottleneck in the data processing logic. Mark responds with: 'Okay, let's discuss the total compensation package to see if we can accommodate this extra effort.' What is Mark *primarily* trying to do at this stage of the negotiation?
Mark isn't directly addressing the technical issue of the bottleneck. Instead, he's employing a negotiation tactic by broadening the conversation to include 'total compensation,' which is often shorthand for discussing resources like additional time, support staff, or perhaps even budget allocated for optimization efforts. This frames the discussion beyond just the immediate code change and attempts to establish a mutually agreeable framework for addressing the problem – a common strategy when facing pushback on development tasks.
12 / 25
PR #5678 has been submitted for the new user authentication module. During a Slack discussion, Alex says: 'I'm pushing for a 30% bonus on top of the base salary – that reflects the complexity and the impact this feature will have.' Ben replies: 'That's ambitious. Let's explore options to reduce the scope slightly before discussing performance-based bonuses.' What is Ben *most likely* attempting to achieve by suggesting a reduction in scope?Ben is employing 'anchoring,' a common negotiation tactic where the first proposed number significantly influences subsequent offers. By initially demanding a 30% bonus, he's setting a high benchmark; Ben's response signals that this figure is likely too aggressive and proposes a way to adjust the situation before further discussion on bonuses occurs. The incorrect options misinterpret Ben's response as simply accepting a lower bonus or focusing solely on scope reduction without acknowledging the initial anchor.
13 / 25
PR #9012 has been submitted for the new API endpoint. During a standup update, David states: 'I'm aiming for a 5% equity stake in the company alongside my salary – it's crucial to align my incentives with the long-term success of the product.' Maria responds: 'That's a significant ask, David. Could you elaborate on how that aligns with our current vesting schedule and future funding rounds?' What is Maria *primarily* assessing during her response?Maria isn't simply acknowledging David's request; she's probing its practical implications. The question focuses on assessing alignment – a key negotiation concept – by examining how the equity stake interacts with existing structures like vesting schedules and future funding rounds. This demonstrates an understanding that equity is more than just a bonus, and requires careful consideration of long-term company strategy. Option A is incorrect as it's about valuation, not strategic alignment.
14 / 25
PR #3456 has been submitted for a new microservice. During a code review, Emily suggests refactoring the service to use a more efficient data structure. John responds: 'That's a good point about performance. Let's explore options to reduce the scope slightly before discussing potential impact on future feature development.' What is John *most likely* attempting to do in this conversation? John's response highlights the concept of 'scope management' – recognizing that a seemingly beneficial change (optimizing data structures for performance) could have unintended consequences if not considered within the broader context of future development. The phrase 'explore options to reduce the scope' indicates he is advocating for prioritizing immediate tasks and delaying deeper dives into complex issues until they are directly relevant to current deliverables. This demonstrates an understanding of pragmatic negotiation, focusing on achievable outcomes rather than demanding immediate solutions.
15 / 25
PR #7890 has been submitted for a new caching layer. During a Slack message between two developers, Liam says: 'I'm targeting a 15% raise to reflect the added value this caching layer will bring.' Chloe replies: 'While I appreciate the improvement, let's discuss the total compensation package and see if we can factor in potential increased support responsibilities as the system scales.' What is Chloe *primarily* attempting to do with her statement? Chloe isn't simply rejecting Liam's request; she's skillfully redirecting the conversation. Her phrase 'let's discuss the total compensation package' signals an intent to move beyond a purely individual benefit negotiation and consider how Liam's work impacts the larger system and team strategy – a key element of successful development negotiations. This avoids getting locked into a short-sighted discussion about salary alone, which is more beneficial for both parties.
16 / 25
PR #1234 has just been submitted. During the code review, Sarah points out a potential performance bottleneck in the data processing logic. Mark responds with: 'Okay, let's discuss the total compensation package to see if we can accommodate this extra effort.' What is Mark *primarily* trying to do at this stage of the negotiation?
Mark isn't directly addressing the technical issue of the bottleneck. Instead, he's employing a negotiation tactic by broadening the conversation to include 'total compensation,' which is often shorthand for discussing resources like additional time, support staff, or perhaps even budget allocated for optimization efforts. This frames the discussion beyond just the immediate code change and attempts to establish a mutually agreeable framework for addressing the problem – a common strategy when facing pushback on development tasks.
17 / 25
PR #5678 has been submitted for the new user authentication module. During a Slack discussion, Alex says: 'I'm pushing for a 30% bonus on top of the base salary – that reflects the complexity and the impact this feature will have.' Ben replies: 'That's ambitious. Let's explore options to reduce the scope slightly before discussing performance-based bonuses.' What is Ben *most likely* attempting to achieve by suggesting a reduction in scope?Ben is employing 'anchoring,' a common negotiation tactic where the first proposed number significantly influences subsequent offers. By initially demanding a 30% bonus, he's setting a high benchmark; Ben's response signals that this figure is likely too aggressive and proposes a way to adjust the situation before further discussion on bonuses occurs. The incorrect options misinterpret Ben's response as simply accepting a lower bonus or focusing solely on scope reduction without acknowledging the initial anchor.
18 / 25
PR #9012 has been submitted for the new API endpoint. During a standup update, David states: 'I'm aiming for a 5% equity stake in the company alongside my salary – it's crucial to align my incentives with the long-term success of the product.' Maria responds: 'That's a significant ask, David. Could you elaborate on how that aligns with our current vesting schedule and future funding rounds?' What is Maria *primarily* assessing during her response?Maria isn't simply acknowledging David's request; she's probing its practical implications. The question focuses on assessing alignment – a key negotiation concept – by examining how the equity stake interacts with existing structures like vesting schedules and future funding rounds. This demonstrates an understanding that equity is more than just a bonus, and requires careful consideration of long-term company strategy. Option A is incorrect as it's about valuation, not strategic alignment.
19 / 25
PR #3456 has been submitted for a new microservice. During a code review, Emily suggests refactoring the service to use a more efficient data structure. John responds: 'That's a good point about performance. Let's explore options to reduce the scope slightly before discussing potential impact on future feature development.' What is John *most likely* attempting to do in this conversation? John's response highlights the concept of 'scope management' – recognizing that a seemingly beneficial change (optimizing data structures for performance) could have unintended consequences if not considered within the broader context of future development. The phrase 'explore options to reduce the scope' indicates he is advocating for prioritizing immediate tasks and delaying deeper dives into complex issues until they are directly relevant to current deliverables. This demonstrates an understanding of pragmatic negotiation, focusing on achievable outcomes rather than demanding immediate solutions.
20 / 25
PR #7890 has been submitted for a new caching layer. During a Slack message between two developers, Liam says: 'I'm targeting a 15% raise to reflect the added value this caching layer will bring.' Chloe replies: 'While I appreciate the improvement, let's discuss the total compensation package and see if we can factor in potential increased support responsibilities as the system scales.' What is Chloe *primarily* attempting to do with her statement? Chloe isn't simply rejecting Liam's request; she's skillfully redirecting the conversation. Her phrase 'let's discuss the total compensation package' signals an intent to move beyond a purely individual benefit negotiation and consider how Liam's work impacts the larger system and team strategy – a key element of successful development negotiations. This avoids getting locked into a short-sighted discussion about salary alone, which is more beneficial for both parties.
21 / 25
PR #1234 has just been submitted. During the code review, Sarah points out a potential performance bottleneck in the data processing logic. Mark responds with: 'Okay, let's discuss the total compensation package to see if we can accommodate this extra effort.' What is Mark *primarily* trying to do at this stage of the negotiation?
Mark isn't directly addressing the technical issue of the bottleneck. Instead, he's employing a negotiation tactic by broadening the conversation to include 'total compensation,' which is often shorthand for discussing resources like additional time, support staff, or perhaps even budget allocated for optimization efforts. This frames the discussion beyond just the immediate code change and attempts to establish a mutually agreeable framework for addressing the problem – a common strategy when facing pushback on development tasks.
22 / 25
PR #5678 has been submitted for the new user authentication module. During a Slack discussion, Alex says: 'I'm pushing for a 30% bonus on top of the base salary – that reflects the complexity and the impact this feature will have.' Ben replies: 'That's ambitious. Let's explore options to reduce the scope slightly before discussing performance-based bonuses.' What is Ben *most likely* attempting to achieve by suggesting a reduction in scope?Ben is employing 'anchoring,' a common negotiation tactic where the first proposed number significantly influences subsequent offers. By initially demanding a 30% bonus, he's setting a high benchmark; Ben's response signals that this figure is likely too aggressive and proposes a way to adjust the situation before further discussion on bonuses occurs. The incorrect options misinterpret Ben's response as simply accepting a lower bonus or focusing solely on scope reduction without acknowledging the initial anchor.
23 / 25
PR #9012 has been submitted for the new API endpoint. During a standup update, David states: 'I'm aiming for a 5% equity stake in the company alongside my salary – it's crucial to align my incentives with the long-term success of the product.' Maria responds: 'That's a significant ask, David. Could you elaborate on how that aligns with our current vesting schedule and future funding rounds?' What is Maria *primarily* assessing during her response?Maria isn't simply acknowledging David's request; she's probing its practical implications. The question focuses on assessing alignment – a key negotiation concept – by examining how the equity stake interacts with existing structures like vesting schedules and future funding rounds. This demonstrates an understanding that equity is more than just a bonus, and requires careful consideration of long-term company strategy. Option A is incorrect as it's about valuation, not strategic alignment.
24 / 25
PR #3456 has been submitted for a new microservice. During a code review, Emily suggests refactoring the service to use a more efficient data structure. John responds: 'That's a good point about performance. Let's explore options to reduce the scope slightly before discussing potential impact on future feature development.' What is John *most likely* attempting to do in this conversation? John's response highlights the concept of 'scope management' – recognizing that a seemingly beneficial change (optimizing data structures for performance) could have unintended consequences if not considered within the broader context of future development. The phrase 'explore options to reduce the scope' indicates he is advocating for prioritizing immediate tasks and delaying deeper dives into complex issues until they are directly relevant to current deliverables. This demonstrates an understanding of pragmatic negotiation, focusing on achievable outcomes rather than demanding immediate solutions.
25 / 25
PR #7890 has been submitted for a new caching layer. During a Slack message between two developers, Liam says: 'I'm targeting a 15% raise to reflect the added value this caching layer will bring.' Chloe replies: 'While I appreciate the improvement, let's discuss the total compensation package and see if we can factor in potential increased support responsibilities as the system scales.' What is Chloe *primarily* attempting to do with her statement? Chloe isn't simply rejecting Liam's request; she's skillfully redirecting the conversation. Her phrase 'let's discuss the total compensation package' signals an intent to move beyond a purely individual benefit negotiation and consider how Liam's work impacts the larger system and team strategy – a key element of successful development negotiations. This avoids getting locked into a short-sighted discussion about salary alone, which is more beneficial for both parties.
Frequently Asked Questions
What does the "Negotiation Strategy Vocabulary Quiz" exercise practise?
Master negotiation strategy vocabulary: BATNA, counter-offer language, competing offers, total compensation discussion, and anchoring.
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 "Negotiation Strategy Vocabulary Quiz" 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.