Career Growth Foundations · Salary Negotiation & HR
Negotiating the Offer: Tactics and Scripts
Use a simple framework and script to counter an offer
Negotiating the Offer: Tactics and Scripts
Once an offer is on the table, resist responding immediately with a number or a yes. Express genuine enthusiasm, ask for a short amount of time to review the full details, and come back with a specific counter backed by research.
The BATNA Framework
Know your Best Alternative To a Negotiated Agreement before you start — understanding what you'd do if this offer falls through gives you a calmer, more grounded position at the table.
A Simple Script Skeleton
"I'm excited about this opportunity. Based on my research and the value I'd bring, I was hoping for something in the range of $X-$Y — is there flexibility there?" Silence after stating your number is a normal, useful negotiating tool — resist the urge to fill it.
Using Competing Offers as Leverage
If you have a real competing offer or timeline, sharing it honestly can help both sides move faster. Never fabricate one — it's a serious credibility risk if discovered, and rarely necessary.
Practice questions
How do I negotiate an offer politely?
Answer
Summary
I want to say how excited I am about joining the team.
Longer Answer
I want to say how excited I am about joining the team. Based on my research for this role and level, I was hoping for something closer to $X — is there flexibility there?
Key Points
- I want to say how excited I am about joining the team
- Based on my research for this role and level, I was hoping for something closer to $X — is there flexibility there?
- Lead with genuine enthusiasm, then anchor to research rather than a bare demand — naming specific levers (base, bonus, equity) works better than a vague ask for 'more.'
- Use the answer to connect the concept back to a realistic production or interview scenario for 'How do I negotiate an offer politely?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | I want to say how excited I am about joining the team. |
| Practical tradeoff | Lead with genuine enthusiasm, then anchor to research rather than a bare demand — naming specific levers (base, bonus, equity) works better than a vague ask for 'more.' |
Why
Summary
Lead with genuine enthusiasm, then anchor to research rather than a bare demand — naming specific levers (base, bonus, equity) works better than a vague ask for 'more.'
Longer Answer
Lead with genuine enthusiasm, then anchor to research rather than a bare demand — naming specific levers (base, bonus, equity) works better than a vague ask for 'more.' In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview.
Key Points
- Lead with genuine enthusiasm, then anchor to research rather than a bare demand — naming specific levers (base, bonus, equity) works better than a vague ask for 'more.' In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview
- In an interview, relate 'How do I negotiate an offer politely?' to implementation decisions, tradeoffs, and operational impact
- Use the answer to connect the concept back to a realistic production or interview scenario for 'How do I negotiate an offer politely?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | Lead with genuine enthusiasm, then anchor to research rather than a bare demand — naming specific levers (base, bonus, equity) works better than a vague ask for 'more.' |
| Practical tradeoff | In an interview, relate 'How do I negotiate an offer politely?' to implementation decisions, tradeoffs, and operational impact. |
What would it take for you to accept an offer today?
Answer
Summary
I'd rather see the full written offer and take a short time to review it properly before committing to anything today.
Longer Answer
I'd rather see the full written offer and take a short time to review it properly before committing to anything today. This is sometimes a pressure tactic; a calm, professional deferral is a normal and expected response, not a red flag. In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview.
Key Points
- I'd rather see the full written offer and take a short time to review it properly before committing to anything today
- This is sometimes a pressure tactic; a calm, professional deferral is a normal and expected response, not a red flag
- In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview
- Use the answer to connect the concept back to a realistic production or interview scenario for 'What would it take for you to accept an offer today?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | I'd rather see the full written offer and take a short time to review it properly before committing to anything today. |
| Practical tradeoff | This is sometimes a pressure tactic; a calm, professional deferral is a normal and expected response, not a red flag. |
Why
Summary
This is sometimes a pressure tactic; a calm, professional deferral is a normal and expected response, not a red flag.
Longer Answer
This is sometimes a pressure tactic; a calm, professional deferral is a normal and expected response, not a red flag. In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview.
Key Points
- This is sometimes a pressure tactic; a calm, professional deferral is a normal and expected response, not a red flag
- In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview
- In an interview, relate 'What would it take for you to accept an offer today?' to implementation decisions, tradeoffs, and operational impact
- Use the answer to connect the concept back to a realistic production or interview scenario for 'What would it take for you to accept an offer today?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | This is sometimes a pressure tactic; a calm, professional deferral is a normal and expected response, not a red flag. |
| Practical tradeoff | In an interview, relate 'What would it take for you to accept an offer today?' to implementation decisions, tradeoffs, and operational impact. |
Should I negotiate if I like the offer?
Answer
Summary
Yes — liking the offer doesn't mean it can't also be improved; a brief, well-researched counter rarely damages goodwill and often gets at least a partial yes.
Longer Answer
Yes — liking the offer doesn't mean it can't also be improved; a brief, well-researched counter rarely damages goodwill and often gets at least a partial yes. Negotiating and accepting enthusiastically aren't in conflict — you can be genuinely excited about a role while still asking for a fair adjustment. In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview.
Key Points
- Yes — liking the offer doesn't mean it can't also be improved; a brief, well-researched counter rarely damages goodwill and often gets at least a partial yes
- Negotiating and accepting enthusiastically aren't in conflict — you can be genuinely excited about a role while still asking for a fair adjustment
- In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview
- Use the answer to connect the concept back to a realistic production or interview scenario for 'Should I negotiate if I like the offer?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | Yes — liking the offer doesn't mean it can't also be improved; a brief, well-researched counter rarely damages goodwill and often gets at least a partial yes. |
| Practical tradeoff | Negotiating and accepting enthusiastically aren't in conflict — you can be genuinely excited about a role while still asking for a fair adjustment. |
Why
Summary
Negotiating and accepting enthusiastically aren't in conflict — you can be genuinely excited about a role while still asking for a fair adjustment.
Longer Answer
Negotiating and accepting enthusiastically aren't in conflict — you can be genuinely excited about a role while still asking for a fair adjustment. In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview.
Key Points
- Negotiating and accepting enthusiastically aren't in conflict — you can be genuinely excited about a role while still asking for a fair adjustment
- In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview
- In an interview, relate 'Should I negotiate if I like the offer?' to implementation decisions, tradeoffs, and operational impact
- Use the answer to connect the concept back to a realistic production or interview scenario for 'Should I negotiate if I like the offer?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | Negotiating and accepting enthusiastically aren't in conflict — you can be genuinely excited about a role while still asking for a fair adjustment. |
| Practical tradeoff | In an interview, relate 'Should I negotiate if I like the offer?' to implementation decisions, tradeoffs, and operational impact. |
Do you have any competing offers or timelines we should know about?
Answer
Summary
Yes, I have another process moving toward a decision by a specific date — I wanted to flag that in case it's useful for timing on your end.
Longer Answer
Yes, I have another process moving toward a decision by a specific date — I wanted to flag that in case it's useful for timing on your end. Share real timelines honestly — it's useful information that can help both sides move faster. Never fabricate a competing offer; it's easy to get caught and seriously damages trust. In practice, explain where this shows up in production code, what tradeoffs matter, and how you would justify the choice in an interview.
Key Points
- Yes, I have another process moving toward a decision by a specific date — I wanted to flag that in case it's useful for timing on your end
- Share real timelines honestly — it's useful information that can help both sides move faster
- Never fabricate a competing offer; it's easy to get caught and seriously damages trust
- Share real timelines honestly — it's useful information that can help both sides move faster. Never fabricate a competing offer; it's easy to get caught and seriously damages trust
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | Yes, I have another process moving toward a decision by a specific date — I wanted to flag that in case it's useful for timing on your end. |
| Practical tradeoff | Share real timelines honestly — it's useful information that can help both sides move faster. Never fabricate a competing offer; it's easy to get caught and seriously damages trust. |
Why
Summary
Share real timelines honestly — it's useful information that can help both sides move faster.
Longer Answer
Share real timelines honestly — it's useful information that can help both sides move faster. Never fabricate a competing offer; it's easy to get caught and seriously damages trust.
Key Points
- Share real timelines honestly — it's useful information that can help both sides move faster
- Never fabricate a competing offer; it's easy to get caught and seriously damages trust
- In an interview, relate 'Do you have any competing offers or timelines we should know about?' to implementation decisions, tradeoffs, and operational impact
- Use the answer to connect the concept back to a realistic production or interview scenario for 'Do you have any competing offers or timelines we should know about?'
Comparison / Tradeoffs
| Aspect | Notes |
|---|---|
| Core idea | Share real timelines honestly — it's useful information that can help both sides move faster. |
| Practical tradeoff | In an interview, relate 'Do you have any competing offers or timelines we should know about?' to implementation decisions, tradeoffs, and operational impact. |
Open in the app to mark lessons complete, take notes and track your progress.