Most developers are bad at negotiating their salary. Not because they lack the skills — the same analytical thinking that makes someone good at debugging complex systems is exactly what’s needed here. They’re bad at it because they’ve internalized a set of beliefs about negotiation that aren’t true: that asking for more is rude, that a first offer is fair, that their skills will speak for themselves. None of these hold up under scrutiny. And the cost of getting this wrong compounds over an entire career.

The Number That Compounds

---

Salary negotiation matters more than most developers think because compensation doesn’t reset each year. Your current salary is the anchor for your next salary — whether at the same company or a new one. A $10,000 difference at age 28 doesn’t just mean $10,000 less this year. Over a decade of raises, job changes, and vesting schedules, that gap can easily represent $200,000 or more in cumulative difference.

The uncomfortable truth: companies know this and most candidates don’t act like they do.

The First Rule: Never Give a Number First

---

The single most impactful negotiation behavior is refusing to anchor the conversation with your number first. Whoever states a number first anchors the negotiation — and that anchor strongly influences the final outcome.

When asked “what are your salary expectations?”, the goal is to redirect without being evasive:

“I’m more focused on finding the right role and team at this point. I’d love to understand what you’ve budgeted for this position.”

Or, if pressed: “I’m open to the right number based on the full scope of the role and the compensation package. What does your range look like?”

Most recruiters will give you a range at this point. You’ve given nothing away, and you now have their number to negotiate against.

If a company absolutely requires a number before continuing — some applicant tracking systems demand it — research the market first and provide a range with the lower end above your actual target. More on research below.

Research Is Negotiation Preparation

---

You can’t negotiate well without knowing what the market pays for your specific skills, experience level, and location. Guessing is expensive.

Sources worth using:

• Levels.fyi — the most accurate for tech roles, especially at larger companies; includes base, equity, and bonus breakdowns
• Glassdoor — useful for ranges, less accurate for exact figures; treat as a floor estimate
• LinkedIn Salary — requires Premium but gives you filter-by-company data
• Blind — anonymous developer community; real numbers but with selection bias toward frustrated employees
• Talking to peers — the most accurate source if you can get people to share; normalizing this conversation in your professional network pays off for everyone

Build a picture of what the role pays at comparable companies in your area (or remotely, if applicable). Your target number should be at the high end of what you’ve found — you’ll negotiate down, not up.

The Counter-Offer Framework

---

You’ve received an offer. It’s almost certainly not the best number they can do. Here’s the structure that works:

Step 1 — Express genuine interest, not desperation. “Thank you — I’m genuinely excited about this role and the team. I’d like to take a day to review everything before responding.”

Asking for time is not a red flag. It’s professional.

Step 2 — Counter with a specific number, higher than the offer. Not a range — a number. Ranges anchor to the bottom. “Based on my research and experience, I was expecting something closer to $X.”

The counter should be 10–20% above the offer, calibrated to your market research. Going 50% above is bad faith. Going 5% above leaves too much on the table.

Step 3 — Be silent. State the number and stop talking. The silence is uncomfortable. That discomfort is theirs to resolve, not yours.

Step 4 — Negotiate the full package, not just salary. If they can’t move on base salary, ask about signing bonus, equity, remote work days, professional development budget, vacation policy. These all have real value. “If the base is fixed, is there flexibility on the signing bonus?”

Pro-Tip: Get competing offers when you can. A competing offer isn’t a bluff — it’s leverage. “I have another offer at $X and I’d prefer to be here, but I need the numbers to be closer” is one of the most effective things you can say. Even if you wouldn’t take the other offer, having it anchors your counter at a higher, credible number.

When They Say “That’s Our Final Number”

---

It usually isn’t. “Final” is negotiating language for “we’d prefer not to move.” Your response:

“I understand. Can you help me understand the constraints? Is this a band issue, or is there flexibility if we structure it differently?”

Sometimes the band is genuinely fixed — the HR system won’t allow a different base for that role level. In that case, signing bonus or accelerated review timelines often have more flexibility. Asking about the constraint gives you information to work with.

If the number genuinely won’t move and you’ve exhausted the full package negotiation, then you have a real decision to make — not a negotiation one.

For Internal Raises

---

The same principles apply, with one difference: you have more information. You know the company, the team, the budget cycles. Use that.

The right time to ask for a raise is after a visible win, not on an arbitrary calendar schedule. Build the case with specifics: what you delivered, what it was worth, what you’re taking on that’s beyond your current role.

“I’ve taken on X, Y, and Z since my last review, and the scope of my work has grown significantly. I’d like to discuss adjusting my compensation to reflect that.”

Have a number ready. “I’d like to get to $X” is more effective than “I’d like to earn more.” Specificity signals that you’ve thought about it and you mean it.

Conclusion

---

Salary negotiation isn’t adversarial — done well, it’s a professional conversation about alignment between what you bring and what you’re compensated for. The developers who do it well aren’t the most aggressive ones; they’re the most prepared. They know their market, they don’t anchor first, they counter with a specific number, and they negotiate the full package. The preparation takes a few hours. The payoff is real and lasting.

FAQs

---

Q1: Will negotiating make the company rescind my offer?
Vanishingly rare. Companies that rescind offers over a professional counter-offer are companies you don’t want to work for. The actual risk of a well-delivered counter-offer is essentially zero; the risk of not negotiating is real and quantifiable.

Q2: How do I negotiate without lying about competing offers I don’t have?
Don’t fabricate offers — it’s unethical and risks your reputation if discovered. You don’t need a competing offer to negotiate; market research is sufficient. “Based on my research, this role typically pays $X–Y in this market” is honest leverage.

Q3: Is equity negotiable?
Yes, often more so than base salary, which is constrained by compensation bands. Equity cliff schedules, grant sizes, and strike prices are all worth discussing. Make sure you understand what the equity is actually worth before weighing it heavily.

Q4: What if I’m early in my career and feel I have no leverage?
You have more leverage than you think. Demand for developers remains high. Market research still applies. The counter-offer approach still works. The numbers are smaller at entry level, but the percentage gains from negotiating are just as large — and just as compounding.

Q5: Should I negotiate every job offer?
Yes, with very rare exceptions. The only situation where not negotiating makes sense is when you have no leverage whatsoever and the offer is already above market — genuinely uncommon. In essentially every other situation, a professional, specific counter-offer is worth making.