The most common reason developers don't negotiate their salary is discomfort. It feels presumptuous, or awkward, or like it might cause the company to rescind the offer. None of these fears are well-founded, and the cost of not negotiating is significant — we're talking about tens of thousands of dollars over the course of a career, not from a single negotiation but from the compounding effect of starting from a higher base.
Here's a practical guide to negotiation that doesn't require you to pretend you're a different kind of person.
I have seen people talk themselves out of negotiating because they assume the recruiter knows the market better than they do. Usually that is not true. Usually the recruiter has a budget and a process, and the candidate has a lot more leverage than they realize as soon as they understand the range and the role. The hard part is not finding the script. It is getting comfortable enough to use it.
At some point in the process — usually early, often in the first screening call — a recruiter will ask what your salary expectations are. This question is a negotiating move, not a neutral information request. The first number sets an anchor, and you want that anchor to be as high as reasonably possible.
There are a few ways to handle this:
Most companies do have a budgeted range and will usually share it if asked. Getting them to anchor first gives you more information and a better negotiating position.
The most important preparation for salary negotiation is knowing what the market actually pays for your role, level, and location. Without this information, you're guessing.
Good sources:
Know the median, the 75th percentile, and the 90th percentile for your target role in your target market. This gives you a sense of what's fair, what's good, and what's exceptional.
When an offer comes in, the absolute worst thing you can do is accept it on the call. Even if you're excited and it's above your target range, say: "Thank you so much, I'm genuinely excited about this. Can I have a few days to review the full offer and get back to you?"
Every company expects this. No legitimate offer will be rescinded because you asked for a few days to consider.
Those days are for:
Negotiation doesn't have to be confrontational. The framing that works best is collaborative — you want to join this company, you're enthusiastic, you just want to make sure the compensation reflects the value you bring.
A script that works:
"I'm really excited about this opportunity and I want to make this work. I've done some research on market rates for this role and my experience level, and I was hoping you could do [X] on the base salary. Is there flexibility there?"
Key elements: enthusiasm is genuine, you've done research (this legitimizes the ask), you state a specific number, and you ask directly.
One thing that often surprises first-time negotiators: the company usually doesn't say no flatly. They either come up to your number, meet you in the middle, or offer something else (more equity, a signing bonus, an earlier review cycle). The conversation is almost never as uncomfortable as the anticipation of it.
A negotiation I always keep in mind is the kind where the company starts below what you expected, but the call itself stays respectful. You do not need to be aggressive to move the number. You need to be calm, specific, and willing to pause before you answer. That pause is doing real work for you.
Base salary is the most important number because it compounds — your future raises and offers will often be pegged to it. But when base salary flexibility is limited, there are other things worth negotiating:
One underrated way to improve your negotiating position is to have other offers or at least to be actively interviewing elsewhere. Not to play companies against each other aggressively, but because having options genuinely changes your psychology in the negotiation. You ask more confidently and with less desperation when you have a real alternative.
If I were reducing this to one sentence, it would be: negotiate like you expect the process to continue, not like you need this exact answer in the next ten seconds. That mindset alone makes people sound more grounded and gets better outcomes.
This is another reason to run your job search with a wide enough net — not just to increase your chances of an offer, but to maintain real alternatives throughout the process.
SWARA Editorial Team writes practical, experience-based job search guides for developers.