Negotiating Your Offer: It Starts Before the Offer
You don't get what you deserve. You get what you negotiate.
Most engineers are terrible at negotiation. They think it's rude. They think the company will rescind the offer.
Fact: A company will almost never rescind an offer just because you asked for more money (politely).
Fact: If you don't negotiate, you are leaving $10k-$50k on the table. Every year.
That gap compounds. Over a ten-year career, the difference between an engineer who negotiates and one who does not can easily exceed $500,000 in total compensation. And the irony is that negotiation is a skill that takes a few hours to learn and a few minutes to execute.
The Research Phase: Before You Negotiate
Negotiation does not start when you receive the offer. It starts weeks before, when you gather the data that gives you confidence and credibility.
Know the market rate for your role. Use Levels.fyi, Glassdoor, Blind, and Comprehensive.io to find real compensation data. Filter by company, location, years of experience, and level. The more specific your data, the stronger your position.
Understand total compensation. Base salary is only one component. For senior roles at tech companies, equity often represents 30-60% of total comp. Do not compare a $180k base at a startup with a $180k base at a FAANG company. The total packages are wildly different.
Know your own number. Before you enter any negotiation, decide on three numbers:
- Your target: What you actually want.
- Your floor: The minimum you will accept.
- Your ask: 10-15% above your target. This gives you room to "meet in the middle" and still hit your target.
Write these numbers down. Do not negotiate without them. Emotional decisions in the moment almost always leave money on the table.
The Golden Rule: Don't Give a Number First
Recruiter: "What are your salary expectations?"
You: "I'm focusing on finding the right fit first. I'm sure if we find a match, we can agree on a competitive number."
If they push: "I'm currently interviewing for roles in the $180k-$220k range." (Give a range, and make the bottom of the range your actual target).
Why this works: Whoever names a number first sets the anchor. If you say $160k and they were prepared to offer $185k, you just cost yourself $25k. If they name $185k first, you can negotiate up from there. Anchoring is one of the most well-documented effects in negotiation psychology. Use it to your advantage.
If you are in a state that has salary transparency laws (Colorado, New York, California, Washington), the job posting may already include a range. Use the top of that range as your anchor.
Leverage is Everything
You cannot negotiate effectively if you have no leverage.
Leverage = Other offers.
Or at least, the possibility of other offers.
"I'm currently in final rounds with Company X and Company Y."
This signals: "I am in demand. You need to move fast."
You do not need to have actual competing offers to use this tactic. Being "in final rounds" is enough to create urgency. But if you do have competing offers, you have the strongest possible negotiating position.
How to create leverage if you have none:
- Apply broadly and interview at multiple companies simultaneously. Stagger your timelines so that offer deadlines overlap.
- If you only have one offer, you can still reference "market data" and "other conversations" without lying about having competing offers.
- An internal promotion offer from your current company counts as a competing offer.
Competing Offers as Leverage
When you have multiple offers, use them strategically:
Be transparent, not aggressive. "I have an offer from Company X for $195k total comp. I would prefer to join your team, but I want to make sure the compensation is competitive. Can you match or improve on that?"
Never bluff. If you claim to have an offer you do not have and the company asks for proof (some do), you will lose all credibility. Only reference offers that are real.
Time your deadlines. If Company A gives you a deadline of Friday, ask Company B to accelerate their process. Most companies will move faster if they know they are competing for you. "I have an offer deadline this Friday. Is there any way to expedite the final decision on your end?"
Do not play companies against each other in a bidding war unless you are genuinely willing to walk away. Repeated back-and-forth ("Company A just raised to $200k, can you beat it?") burns goodwill and can backfire.
The "Counter-Offer" Script
They offer $150k. You want $170k.
Don't say: "Can you do $170k?"
Say: "I'm really excited about the team and the mission. However, looking at the market rate and the other conversations I'm having, I was expecting something closer to $175k. If you can match that, I would be ready to sign today."
Why this works:
- "Excited": You are not being hostile.
- "Market rate": It's objective, not greedy.
- "Ready to sign": You are giving them a clear way to close the deal. Recruiters want to close deals.
Notice the ask is $175k, not $170k. You are leaving room for the recruiter to negotiate you down to your actual target of $170k and feel like they "won" something. This is intentional.
Equity and RSU Negotiation
For mid-level and senior engineers at tech companies, equity is often the most negotiable component of the offer. Here is what you need to know:
RSUs (Restricted Stock Units): These are shares of the company's stock that vest over time, typically on a four-year schedule. When you negotiate RSUs, you are negotiating the total grant value, not the number of shares. The number of shares is calculated based on the stock price at the time of the grant.
Stock options (more common at startups): These give you the right to buy shares at a fixed price (the strike price). They are only valuable if the company's valuation increases. Ask about the latest 409A valuation, the total number of outstanding shares, and the company's funding stage to assess their potential value.
What to negotiate:
- Total grant value: Ask for 20-30% more RSUs. Companies have more flexibility on equity than base salary because equity does not impact salary band compliance.
- Vesting schedule: Some companies offer one-year cliffs with four-year vesting. Ask if they can accelerate the vesting (e.g., monthly vesting instead of annual).
- Refresh grants: Ask about the company's policy on annual equity refreshers. A lower initial grant with strong annual refreshers can be worth more over time.
Script: "I appreciate the equity component. Based on my research and the current market for [level] engineers, I was expecting a total equity package closer to $X over four years. Is there flexibility to increase the grant?"
Negotiate Equity and Sign-On
If they can't move on Base Salary (due to salary bands), ask for:
- Sign-On Bonus: Easy for them. One-time cash. Companies love sign-on bonuses because they do not create ongoing salary obligations.
- RSUs / Stock Options: Often more flexible than base salary.
- PTO / Remote Days: Harder at big corps, easier at startups.
The sign-on bonus is your best friend when salary bands are rigid. A $20k sign-on bonus costs the company less than a $20k salary increase (which compounds annually), so they are more likely to approve it.
When NOT to Negotiate
There are situations where negotiation is not the right move:
The offer is already above market. If the company offers $200k for a role where market rate is $170k, pushing for more can signal poor judgment. Express enthusiasm and accept.
You have zero leverage and the offer is fair. If this is your only offer, the pay is at market rate, and you genuinely want the job, a small negotiation attempt is fine but do not push hard. A 5% bump request is reasonable. A 25% bump request with no competing offers is unrealistic.
The company explicitly states the offer is non-negotiable. Some companies (especially certain government contractors and early-stage startups with standardized comp) have fixed compensation frameworks. Pushing against a genuinely non-negotiable offer wastes everyone's time.
You are negotiating with a small startup where the founders are paying themselves $80k. Read the room. If the company is pre-revenue and stretching to make you an offer, aggressive negotiation can sour the relationship before it starts.
Scripts and Templates for Common Scenarios
Scenario: They ask for salary expectations early in the process.
"I'd prefer to learn more about the role and the team before discussing compensation specifics. What's the budgeted range for this position?"
Scenario: The offer is below your floor.
"Thank you for the offer. I'm genuinely excited about the opportunity. However, the base compensation is below what I'm seeing in the current market for this level of role. Based on my research and other conversations, I was targeting a total compensation package in the range of $X-$Y. Is there room to revisit the numbers?"
Scenario: They say they can not move on salary.
"I understand that salary bands can be rigid. Would it be possible to bridge the gap with a sign-on bonus, additional equity, or a guaranteed review at the six-month mark with an adjustment target?"
Scenario: You want to negotiate remote work.
"One thing that would make this opportunity significantly more attractive is flexibility on remote work. Would the team be open to a hybrid arrangement, say three days in-office and two remote? I've found that I do my deepest technical work from home, and I want to set myself up for maximum impact."
Remote Work and Benefits Negotiation
Compensation is not only about money. Benefits and flexibility have real financial value:
- Remote work: Saving $200-400/month on commuting, meals, and wardrobe. Over a year, that is $2,400-$4,800 in after-tax value.
- Professional development budget: $2,000-$5,000/year for conferences, courses, and certifications. Ask for it if it is not included.
- Equipment stipend: A $1,500-$3,000 home office setup allowance.
- Relocation assistance: If the role requires moving, negotiate relocation packages separately from compensation. These are typically handled by a different budget.
These items are often easier to negotiate than salary because they come from different budget lines and do not set precedents for other employees.
Conclusion
Negotiation is a business transaction. It is not personal. The recruiter expects you to negotiate. Don't disappoint them.
The key principles are simple: do your research, know your numbers, never give a number first, and always be enthusiastic while being firm. Practice the scripts until they feel natural. And remember that the worst thing they can say is "no," at which point you are exactly where you started.
Confidence comes from preparation.
The best leverage is knowing you can pass any interview. When you are confident in your skills, you walk into the negotiation room differently. Build that confidence with our Interview Simulator.
Ready to practice for your next interview? Interview Simulator gives you AI-powered feedback on your responses — behavioral, technical, and system design. Start with 3 free practice interviews today.
Try Interview Simulator free →
Master the most common coding interview patterns to ace your technical rounds.
For technical interview preparation, our system design guide is essential reading.
Don't neglect behavioral preparation — see our behavioral interview guide.
Your resume is the first impression — get it right with our resume guide.
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Negotiating Your Offer: The Engineer's Complete Playbook",
"description": "Salary negotiation scripts, equity strategies, and leverage tactics for software engineers. Stop leaving money on the table.",
"datePublished": "2026-02-28",
"author": {
"@type": "Organization",
"name": "CodeSwiftr Team"
},
"url": "https://codeswiftr.com/blog/negotiating-your-offer"
}
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How should I structure my technical interview preparation?",
"acceptedAnswer": {
"@type": "Answer",
"text": "A structured 8–12 week preparation plan is most effective. Week 1–4: data structures and algorithms fundamentals using LeetCode easy-to-medium problems. Week 5–7: system design patterns using resources like the System Design Primer. Week 8–10: behavioral interview preparation with the STAR method. Week 11–12: company-specific mock interviews and review. Consistency matters more than intensity — 1–2 hours per day beats irregular all-day sessions."
}
},
{
"@type": "Question",
"name": "What is the STAR method and how should I use it in interviews?",
"acceptedAnswer": {
"@type": "Answer",
"text": "STAR stands for Situation, Task, Action, Result. It is the standard framework for answering behavioral interview questions. Situation: briefly describe the context (1–2 sentences). Task: explain your specific responsibility. Action: detail the steps you personally took — use 'I' not 'we'. Result: quantify the outcome wherever possible (e.g., 'reduced latency by 40%', 'increased conversion rate by 12%'). Keep each answer to 2–3 minutes."
}
},
{
"@type": "Question",
"name": "What LeetCode difficulty level should I focus on?",
"acceptedAnswer": {
"@type": "Answer",
"text": "For FAANG interviews, focus 20% on easy, 60% on medium, and 20% on hard problems. Easy problems build speed and confidence. Medium problems represent the most common interview difficulty at top companies. Hard problems appear mostly at Google, Meta, and specialised algorithmic roles. Do not skip easy problems — many candidates fail by overthinking genuinely simple questions that require clean, efficient solutions."
}
},
{
"@type": "Question",
"name": "How important is system design compared to coding in tech interviews?",
"acceptedAnswer": {
"@type": "Answer",
"text": "At mid-level and senior positions, system design carries equal or greater weight than coding. Entry-level and new-grad interviews are predominantly coding-focused. Senior and staff-level interviews dedicate one or two full rounds to system design. Master the core components: load balancers, databases (SQL vs NoSQL trade-offs), caches (Redis, Memcached), message queues (Kafka, SQS), CDNs, and API design. Practice designing real systems you use daily — the interviewer values practical reasoning over textbook answers."
}
}
]
}
Related Reading
- Job Negotiation Guide for Engineers
- Tech Salary Negotiation: How to Negotiate a $20-50K Higher Offer (2026 Guide)
Explore Related Topics
- LeetCode Burnout: Silent Epidemic in Tech Interviews...
- Life After the Offer: Your Complete Onboarding Success Guide
- Mock Interviews vs. Real Interviews: Closing the...
Related Guides
- Negotiating Job Offers: How to Get 20-40% More Compensation
- How to Compare and Evaluate Software Engineering Job Offers
- Software Engineer Salary Negotiation Guide
Ready to practice? Start a mock interview →