Salary Negotiation for Tech Roles: Scripts That Actually Work in 2026

Most people in tech under-negotiate not because they lack leverage, but because they lack words. The moment the recruiter asks "what are your salary expectations?", the silence gets uncomfortable and they blurt out a number that anchors the whole negotiation low. This guide gives you the actual sentences to say at each stage — no bluffing required.

Before anything: know your number

Negotiation without data is just hoping. Before your first call, establish three numbers:

• Market rate — check salary ranges on job boards for your role, level, and region. Look at ranges in actual job posts, not just survey averages.
• Your walk-away number — the figure below which you decline regardless of how nice everyone was.
• Your target — typically 10–20% above what you'd accept, sitting inside the market range.

Script 1: Deflecting the early salary question

When asked for expectations in a first screen, don't name a number if you can avoid it — you have the least information and the least leverage at this point.

"At this stage I'm focused on whether the role is a strong fit. Could you share the budgeted range for the position? If it's in the right neighborhood, I'm happy to move forward."

Most recruiters will share it — they don't want to waste cycles either. If they insist you go first, give a range whose bottom is your target: "Based on the market for senior backend roles in this region, I'm looking at 120–140." Companies negotiate toward the bottom of your range, so your bottom must be a number you'd be happy with.

Script 2: Responding to the offer

Never accept on the call, even a great offer. Say:

"Thank you — I'm genuinely excited about this. I'd like a couple of days to review the full package. Can you send everything in writing?"

Then, when negotiating, be specific and collaborative, not adversarial:

"I'm ready to say yes. One gap: the base is at 115, and given my experience with [specific relevant skill] and the market range I'm seeing of 125–140, I was targeting 130. If you can get there, I'll sign this week."

That structure — enthusiasm, a specific number, a specific justification, and a commitment to close — is the highest-converting negotiation format there is. It gives the recruiter exactly what they need to argue your case internally.

Script 3: When they can't move on base

Base salary is often the stiffest lever. If they hold firm, move to the rest of the package:

• "If base is fixed, could we look at a signing bonus to bridge the gap?"
• "Would a six-month review with a defined raise criteria be possible?"
• "Is there flexibility on equity, learning budget, or additional vacation days?"

A signing bonus is usually the easiest yes — it's a one-time cost that doesn't reset their salary bands.

Script 4: Handling competing offers honestly

If you have another offer, say so plainly — no games, no invented numbers:

"I want to be transparent: I have another offer at 135 with a decision deadline on Friday. Your role is my first choice because of [genuine reason]. Is there anything you can do on timeline or numbers?"

Never fabricate an offer. Tech circles are small, verification happens, and a caught bluff ends the negotiation permanently.

What not to worry about

A reasonable, well-justified counter has essentially never caused a genuine offer to be revoked — companies that pull offers over polite negotiation were going to be bad employers anyway. The real risk isn't asking for too much; it's the compounding cost of not asking. A 10% higher starting salary follows you through every future raise, bonus calculation, and next-job anchor. Ten minutes of scripted conversation is the best-paid work you'll do all year.