The most expensive eleven seconds of a developer's career happen before an offer exists.
Recruiter: "So, what are you looking for, compensation-wise?"
Candidate: "Uh, around 140?"
I was the hiring manager on that call. The approved band for the level we were about to slot them into topped out around 175. They got 143 and said yes the same day. Everybody on my side was thrilled. I felt slightly sick.
That call is the whole game. Developer salary negotiation is not a haggling contest that starts when the offer email lands. It is a sequence of internal decisions that mostly finish before anyone says a number out loud, and almost nobody tells candidates how it works.
TL;DR
- The recruiter asks for your number first because your answer can only pull the offer down. It can never raise the ceiling.
- Your number is mostly decided before comp comes up: the interview loop assigns a level, the level maps to a band, and the band sets the floor and ceiling.
- Negotiate the level, not the digits. One level bump beats every clever line you can say about base salary.
- "I'll have to check with the team" is a workflow, not a rejection. Exception requests are routine and usually approved when you hand over a reason.
- Offers get pulled for being rude or dishonest. Asking once, politely, with a justification, does not blow up offers.
Why does the recruiter ask for your salary expectation first?
Because it is a free option with no downside for them. If your number is below the band, they save budget and look good. If your number is above the band, they learn early and screen you out. There is no version of that question where answering first helps you.
Here is the part that stings: the range already exists. It was approved before the job was posted. Somebody filled in a requisition with a level and a budget, and a comp partner signed off. When a recruiter asks what you are looking for, they are not gathering information to build your offer. They are checking whether they need to use their whole budget.
I have sat in the meeting where we said, out loud, "they asked for 140, let's do 143 so it feels like a win." Nobody was being evil. Everybody was doing their job. The number was just sitting there unclaimed.
How does developer salary negotiation actually work from the inside?
Three steps, in this order:
1. The debrief assigns you a level. After your loop, the interviewers argue about scope, not likeability. Did this person drive a project or execute a ticket? Do they need a design handed to them, or do they produce the design? That argument outputs "senior" or "mid," and that word is worth more than anything you will say later.
2. The level maps to a band. Every company past ~50 people has a table. Level 4 is 130 to 175. Level 5 is 165 to 215. The bands overlap on purpose. Where you land inside the band is the recruiter's discretion, up to a point.
3. The recruiter picks a spot in the band. Their default is somewhere below the midpoint, because that leaves room for a counter and for your next two raises. Your entire negotiation happens inside those last twenty percent unless you change step one.
That is why "I got them up 5k" feels good and mostly is not the story. The story is whether you got scored at level 4 or level 5.
Why is negotiating your level worth more than negotiating base salary?
A level bump moves the whole band, the equity grant, the bonus target, and every future raise, which is compounding money. Squeezing base salary moves one number, once.
Levels are also more negotiable than people think, because leveling is a judgment call made by tired humans in a 30-minute debrief. It is genuinely fuzzy at the boundaries.
You influence it during the interview, not after. Practical version: every time you describe work, describe the decision you made and who else it affected. "I rewrote the ingestion job" is level 4. "Ingestion was failing weekly and blocking two other teams, so I proposed a queue-backed rewrite, got the on-call team to sign off, and shipped it in three weeks with a rollback path" is level 5. Same project. Different scoring.
If the offer arrives and the level feels low, you can still say so: "The scope you described in the interviews matches what I have been doing for two years. Can we talk about whether this is the right level?" That is a real conversation, not a rude one. I have had it and changed my answer.
What should I say when asked about salary expectations?
Deflect once, then anchor with a reason. Two lines you can steal:
When they ask early:
"I want to make sure this is the right fit first. It would help more if you told me the band you have approved for this level. I can tell you right away whether we are in the same neighborhood."
Nine times out of ten they say the band. Ranges are increasingly posted anyway, and recruiters are usually happy to skip the dance.
When they push and you have to name something:
"For this scope in this market, I am targeting the upper half of the band."
Then stop talking. The silence after your number is the highest-paid silence in your career. Most people fill it by softening: "...but I'm flexible." That sentence has cost more engineers more money than every whiteboard question ever asked.
When the offer is on the table:
"I'm genuinely excited about this. Base at 168 and I'm an immediate yes."
One number, one reason, one commitment. Recruiters are measured on acceptance rate and time-to-close far more than on how cheaply they close you. "Immediate yes" is the phrase that gets your exception request approved, because it converts their risk into a done deal.
What can you negotiate besides base salary?
Base is often the stiffest lever, because it sets precedent for the whole team. The flexible ones:
- Sign-on bonus. Usually a separate budget with a shorter approval chain. The easiest yes in the building.
- Equity. Often has a wider band than base, and refresh timing is negotiable at some companies.
- Level and title. See above. The compounding one.
- Start date. Three extra weeks of unpaid rest is worth real money and costs them nothing.
- Remote days, on-call exemption for the first quarter, conference budget, a hardware allowance. Small, but they are approved by your manager, not by finance.
If base is frozen, ask directly: "Which of these has the most room?" A good recruiter will tell you, because they want the deal closed too.
What mistakes do engineers make in salary negotiation?
- Naming a number before knowing the band. Discussed. It is the whole article.
- Negotiating against themselves. Naming a number, then discounting it before the other side has responded. Say it, then wait.
- Asking for "more." A recruiter cannot take "more" into an approval form. Give them a number and a sentence they can paste in verbatim.
- Bluffing a competing offer. Some companies ask to see it. Now the conversation is about your honesty instead of your comp.
- Treating comp as one number. Base, bonus, equity, and sign-on have different approvers and different flexibility. Push on the loosest one.
Can an offer be rescinded if you negotiate?
Practically never for one polite, reasoned counter. I have seen offers pulled twice: once for a candidate who negotiated for three weeks and moved the goalposts every time we agreed to something, and once for someone who lied about a competing offer that the recruiter happened to be able to check. Both were behavior problems, not negotiation problems.
The company spent weeks of engineering time interviewing you. Withdrawing over one counter means restarting the whole loop. Their pain is much larger than yours, and you should price that in.
So, does the recruiter already have a number? Yes. The band was approved before the job was posted, and the interview debrief picked your level inside it before comp ever came up. Which means developer salary negotiation is mostly won earlier than you think: by describing your work in terms of scope and decisions so you get leveled correctly, by refusing to name the first number, and by making one specific ask with a reason and an "immediate yes" attached. The last twenty percent is haggling. The first eighty is scoring, and you are allowed to influence it.
What is the worst salary question you have been asked on a first call? I want to hear it.
