Salary Negotiation for Software Engineers: A Step-by-Step Guide
How to negotiate a software engineering offer: handling the salary expectations question, understanding total compensation, researching your market, and the exact words to use when you counter.
LiveHint.ai team · · 4 min read
You passed the interviews and the offer is in. This is the point where many engineers leave the most money on the table, often because negotiating feels awkward or risky. In reality, a polite, well-researched counter is expected at most tech companies, and it rarely costs anyone an offer.
This guide walks through the process from the first recruiter call to the signed offer.
Understand total compensation first
Base salary is only part of the package. Before you compare or negotiate, break every offer down into:
| Component | What to ask |
|---|---|
| Base salary | The fixed annual amount |
| Equity | Type (RSUs, options), total grant value, vesting schedule, any cliff |
| Bonus | Target percentage, and how often it actually pays out at target |
| Sign-on bonus | Amount, and whether you'd have to pay it back if you leave early |
| Level | The title and level, which set your pay band and future raises |
| Benefits | Retirement match, health coverage, learning budget, remote stipend |
Equity needs extra care. Public company RSUs are close to cash. Startup options depend on the company's future, the strike price and how many shares exist in total, so ask for the details rather than relying on a single headline value.
Research your market
You can't negotiate well without knowing what's normal. Good sources include:
- Compensation data sites that collect self-reported offers by company, level and location.
- Your network. Friends at similar companies are often happy to share ranges privately.
- Recruiters. Recruiters at other companies will usually tell you the band for a role if you ask.
- Salary ranges in job postings, which are now required in many places.
Write down a realistic range for the level you're targeting, and decide on your walk-away number before any conversation starts.
Handle the "What are your salary expectations?" question
Recruiters often ask this on the first call. Answering with a number too early can anchor you low. You have a few good options:
- Defer politely. "I'd like to learn more about the role and the level first. I'm sure we can find something fair if it's a good fit."
- Turn it around. "Could you share the range budgeted for this role?"
- Give a researched range, anchored high. If you have to name a number, make the bottom of your range a figure you'd be happy with.
In places where it's legal to ask, you can still decline to share your current salary. "I'd rather focus on the market rate for this role" is a perfectly professional answer.
Get competing offers if you can
Nothing strengthens your position like another offer. If you're interviewing at several companies, try to line up the processes so the offers arrive close together. Tell recruiters about your timeline honestly. Most will speed up their process rather than lose a candidate.
Never invent an offer. Recruiters compare notes more than you'd expect, and some ask for proof.
Make the counter
When the offer arrives, don't accept on the spot. Thank them, say you're excited, and ask for the full details in writing along with a reasonable time to decide.
Then counter with a specific number, backed by a reason. For example:
"Thank you again, I'm really excited about the team and the work. Based on my research for this level in this market, and another offer I'm considering, I was hoping for a base salary closer to [number]. If you can get there, I'm ready to sign."
A few principles make counters work:
- Be specific. "Can you do better?" invites a token bump. A number gives them something to take to the compensation team.
- Give a reason. Market data, a competing offer or the scope of the role all work.
- Show enthusiasm. Recruiters push harder internally for candidates they believe will accept.
- Negotiate the whole package. If base is capped by the band, ask about equity, sign-on bonus or level instead.
- Keep it in writing or on the phone, whichever you're more comfortable with. Many people find email easier to get right.
Negotiate the level, not just the money
Your level often matters more than any single number. It sets your pay band, your scope and your starting point for future promotions. If you were interviewed for a senior role and offered a mid-level one, ask what it would take to be considered at the higher level, and share specific evidence from your experience.
Know when to stop
One or two rounds of negotiation is normal. After that, decide. If they've met your number, accept graciously and don't keep pushing. If they can't move and the offer is still above your walk-away number, it may still be the right job. Salary is important, but so are the team, the manager and the work, which you can learn about by asking the right questions during your interviews.
Common mistakes
- Accepting immediately out of relief or excitement.
- Naming a number first without any research.
- Negotiating by apologizing. "Sorry, I know this is a lot, but..." weakens your request.
- Making ultimatums you won't follow through on.
- Forgetting the details. Confirm the start date, vesting schedule and any repayment terms in writing before you sign.
Negotiating is a skill like any other: a little preparation goes a long way. Write down your numbers, rehearse the counter once out loud, and go in calm. Most of the time, the worst outcome is a polite "this is the best we can do."
Keep reading
5 min read
30 Smart Questions to Ask at the End of a Tech Interview
The best questions to ask your interviewer, grouped by who you're talking to: engineers, hiring managers and leadership. Plus the questions to avoid and how to use the answers.
- #interview-tips
- #questions-to-ask
- #software-engineering
- #career
4 min read
How to Answer "What Is Your Greatest Weakness?" (With Examples for Engineers)
A three-part formula for answering the greatest weakness question honestly, with example answers for software engineers and the clichés that make interviewers cringe.
- #behavioral-interview
- #greatest-weakness
- #interview-tips
- #software-engineering