Tech Salary Negotiation: Tactics, Scripts & Costly Mistakes

Tech salary negotiation is the part of hiring that most candidates skip, usually for the wrong reason. The fear is that asking will make the company pull the offer. In practice, a company that has taken you through four or five interview rounds has invested heavily in you, and a reasoned, professional request is an expected part of the process, not an insult.

This guide follows the process in order: how to build a range without guessing, what to say when a recruiter asks for your expectations, what to do when the offer lands, what else you can negotiate, and which mistakes cost the most.

When should you talk about salary?

The first question usually comes in the recruiter screen, but real negotiation only starts once there is an offer. Until then, the goal is to stay in the process without anchoring yourself too low.

Early on you don't yet know the scope of the role, the team or the level of responsibility, so any number you give is a guess, and the company will treat it as an anchor. On the other hand, many recruiters have to confirm early that you fit the budget, so refusing to answer entirely rarely works. The answer is a reasoned range now and a precise number later.

How do you build a salary range without guessing?

Combine three sources: published salary surveys, people doing similar work, and recruiters who see the market daily. Each source alone misleads; together they give you a range you can defend.

• Published surveys: recruiting agencies and professional sites publish salary data by role, seniority and sector. They show the order of magnitude, but they update slowly and rarely separate an early-stage startup from a public company.
• Peers in similar roles: a direct conversation with two or three people at a similar level beats any survey. Don't ask "what do you earn"; ask "what's a reasonable range for this role at a company this size?"
• Recruiters: agency recruiters see many offers a month. When one reaches out about a different role, ask what the market is paying right now.
• Your own offers: if you're in several processes at once, the first real offer is the most reliable data point you have.

From those sources, set your three numbers: a target (what you actually want), an opening figure (slightly above target, so there's room to meet in the middle) and a floor (below this, keep looking). Never say the floor out loud.

What do you say to "What are your salary expectations?"

Early in the process, give a wide, reasoned range and turn the question back to the role's budget. Once you understand the role, you can give a single number.

A line that works in a screening call: "Based on what I see in the market for similar roles, the range is X to Y, depending a lot on scope and the full package. What range have you set for this position?" Start the range around your target, not your floor, because companies almost always aim for the bottom of whatever range you give.

If they push for one number: "I'd rather give an exact figure once I understand the role better in the next stage. For now I can say the range I mentioned reflects the market." Most recruiters accept this, because it's what they hear from experienced candidates too. Practise this answer like any other interview question - the HR interview guide covers how to prepare.

What do you do when the offer arrives?

Thank them, ask for the offer and every component in writing, and take a day or two. Don't accept or reject on the same call.

• Get everything in writing: base salary, equity (amount, strike price, vesting schedule), bonus, pension and benefits, vacation, remote days and start date.
• Compare the package to your target, not your current salary. Your current pay is not the new company's reference point.
• Pick two or three things to ask for, not ten. A focused request lands better than a list.

A counter-offer line: "I really want to join, and the role is exactly what I'm looking for. Based on the market and what I'll bring to the team, I was expecting a base of X. If we can get there, I'm ready to sign this week." Three things do the work: a clear wish to join, one reasoned number, and a commitment to close quickly.

If you have another offer, you can mention it gently and without threats: "I have another offer in a higher range, but you're my first choice." Never invent one; tech hiring communities are small and it tends to surface.

What can you negotiate besides base salary?

When base is stuck at the top of the budget, the package is still flexible. Many components cost the company less than they're worth to you.

• Equity: amount, strike price and vesting. At startups a four-year vesting schedule with a one-year cliff is common; make sure you understand what happens to your options if you leave or the company is sold.
• Signing bonus: a common way to bridge a one-off gap, such as a bonus you forfeit by leaving.
• Pension and benefits: in Israel, check whether the company offers a study fund (keren hishtalmut) and on which part of your salary.
• Title: Senior instead of Mid, or Lead, shapes your next role as much as the pay does.
• Start date: a month off between jobs is a perfectly normal request.
• Remote days, a learning or conference budget, equipment.
• An early salary review: a written commitment to revisit pay after six months instead of a year.

Which negotiation mistakes cost the most?

The most expensive mistake is not negotiating at all. After that: revealing your current salary, naming a low number too early, and haggling item by item.

• Accepting on the spot: even a great offer won't disappear because you asked for a day.
• Revealing your current salary: it anchors the offer downward. Talk about expectations and the market instead.
• Arguing from personal needs: "I have a mortgage" doesn't persuade; "this is the market range for the role" does.
• Asking in drips: one request on base, then another on equity, then vacation - it erodes trust. Ask for everything at once.
• Bluffing: "or I walk" only works if you will.
• Forgetting you'll work with these people: a professional, pleasant negotiation is part of your first impression.

What if you have no experience or are changing careers?

You still negotiate, just on fewer components. In a first role there's usually more flexibility on terms - start date, learning budget, an early salary review - than on base.

In a first job, your leverage is motivation and potential rather than track record. A reasoned request for a salary review after six months, tied to clear goals, is almost always accepted and is often worth more than a small raise now. If you're switching into tech, you can also point to experience from your previous field - managing people, working with clients - that adds value from day one. And the case for a higher number starts with a resume that shows results; the ATS-friendly resume guide covers how to make yours readable.