How to Negotiate Salary as a Tech Professional

$24,479. That’s the annual gap between a tech professional who negotiates and one who takes the first offer. I know because we run the numbers on every placement. The research backs it up too, an 18.83% average increase for people who push back versus those who sign immediately. On a $130,000 base over five years, compounding raises on the higher starting point, the gap blows past $150,000. And still. Fifty-eight percent of Americans just take the number.

I’ve been recruiting software engineers and DevOps specialists and data scientists for fifteen years. Sat on the employer side of maybe two thousand salary conversations. So I’ll tell you something that might be uncomfortable. When a candidate accepts the first offer we send, nobody at the company high-fives about it. Nobody says “wow, what a great team player.” The recruiter marks the req as filled, the hiring manager exhales because the search is over, and the $15K that was budgeted for negotiation just quietly goes back into the department pool. Nobody thinks about it again. Except the candidate who’s now earning $15K less than they could have been. They’ll think about it at every annual review for the next four years.

What follows is specific to engineers, developers, and technical professionals negotiating tech compensation. If you want generic advice about firm handshakes and power poses, there are nine thousand articles about that already. This isn’t one of them.

Why Most Tech Professionals Skip the Conversation

I’ll show you two numbers and then we can talk about why they don’t match.

Number one. A Fidelity survey found 85% of people who countered on salary got at least some of what they asked for. Eighty-seven percent for workers between 25 and 35. Number two. A CareerBuilder study showed 73% of employers fully expect candidates to negotiate.

So the win rate is absurdly high and the other side is literally waiting for you to do it. More than half of candidates still don’t.

Why not?

Confrontation. That’s the word that kills more negotiations than any bad tactic ever could. Engineers especially, and I’m generalizing here but it’s a pattern I’ve seen play out hundreds of times, they treat the “business stuff” like it’s beneath them or at least outside their expertise. They’ll spend three weekends optimizing a database query that saves 40 milliseconds but won’t spend ten minutes on a phone call that’s worth $20,000 a year. I watched a senior developer accept $22K below the approved range last quarter because, and this is a direct quote, “I didn’t want to make it awkward.” Meanwhile a candidate with the exact same qualifications who interviewed the following week asked for more and got it. Same company. Same hiring manager. Same budget. The only variable was willingness to have the conversation.

The other piece is information asymmetry, but that’s collapsing fast. Pay transparency laws now cover 16 states as of 2026. California. New York. Colorado. Washington. If a remote role can be performed from one of those states, the posting usually has to include a range even if corporate HQ is in Texas. Colorado’s law alone pushed posted salaries up 3.6% on average. The information is moving in your direction whether employers like it or not.

Know Your Number Before Anything Else

Hoping is not a compensation strategy. I’ve watched candidates walk into negotiations with nothing but a vague sense that they should be paid more, and every single time it ends with them accepting a number that “felt reasonable” without any data to confirm whether it actually was. You need two numbers before you pick up the phone. A target, which is the specific dollar figure you’re aiming for based on market data and your own assessment of what you bring to this particular role. And a floor, which is the number below which the answer is no regardless of how cool the product is or how much you liked the engineering manager during the onsite.

Here’s where the research gets interesting. Not all salary sites are created equal, and in tech specifically, some of them are dangerously wrong.

Levels.fyi is the one you want. User-submitted data. Verification tiers that go all the way up to W-2 confirmation. Broken down by level, company, and location. If you’re negotiating at any company that has a formal leveling system, start here and don’t leave until you’ve found at least three comparable data points.

The Bureau of Labor Statistics gives you broad occupational baselines. Median annual wage for software developers was $133,080 as of May 2024. Useful as a floor reference, not granular enough to anchor a real negotiation. Glassdoor, ZipRecruiter, and Indeed fill in the gaps for markets and company sizes that Levels.fyi doesn’t cover well.

Payscale and Comparably, though. Be careful. Both handle equity atrociously, and in tech, where RSUs and stock options can represent 30 to 60 percent of total comp at senior levels, that’s not a minor oversight. It’s a fundamental error in what they’re measuring. Using Payscale to benchmark a Staff Engineer offer at a public tech company is like using the Kelley Blue Book to appraise an airplane. Wrong tool. Wrong category. You’ll walk away thinking you’re overpaid when you’re actually $40K below the midpoint.

Pull data from at least two sources. Note where they disagree. That disagreement is content for your negotiation. “I’ve been researching this role at this level in this market, and I’m seeing ranges from $145K to $175K depending on the source” is a factual statement that anchors the conversation without sounding like an ultimatum.

Total Compensation in Tech Is Not Just Base Salary

If you’ve only ever worked in non-tech industries, this section is going to surprise you. If you already work in tech but have only been at startups, it might surprise you too.

A $150,000 base offer at a mid-size public tech company might actually be a $230,000 total compensation package once you add the RSU grant, the target bonus, and the signing bonus. Or it might genuinely be $155,000 total at a company with a thin bonus structure and no equity. The headline number is not the real number. You have to break it apart.

Equity is the biggest lever. Here’s why. Companies hate increasing guaranteed cash because it hits the income statement permanently and creates immediate pay equity conversations with everyone already on the team making less. Stock is cheaper upfront, the accounting treatment is friendlier, and it aligns your incentives with company performance in a way that makes the board happy. When a hiring manager tells you “I really can’t move on base,” believe them. That’s probably the truth. But the RSU grant? The signing bonus? Those budgets are separate and often have significantly more room than the base salary band.

Signing bonuses deserve their own paragraph because they’re so underused. One-time expense. Hits the books in a single quarter and then disappears. Doesn’t set a precedent for anyone’s annual review. Doesn’t create awkwardness with the person sitting next to you who’s been at the company for three years and makes less. We had a candidate last year, a senior backend engineer, who hit a wall at $158K base when she wanted $170K. She asked for a $20K signing bonus instead. Approved in two days. The hiring manager didn’t even escalate it. He had the authority the whole time. Nobody had asked before.

Negotiating a New Job Offer

Timing first. Everything else second. The moment to negotiate is after you have a written offer and before you’ve signed anything. That window, usually 48 to 72 hours, is when your power peaks. The company has decided you’re the one. They told the other finalists no. The hiring manager already told their team to expect a new person. Reopening the search would cost them six to eight weeks and probably $15K to $30K in recruiter fees alone. They know this math even if they don’t say it out loud.

When the offer arrives, say thank you. Mean it. Then ask for a couple days to review. Any company worth joining will give you that without flinching. If someone pressures you to decide by end of day, that’s not efficiency. That’s a red flag, and it just saved you from learning the hard way six months from now that this company treats everything as a fire drill regardless of whether the building is actually burning.

Before you call back, write down every component of the offer on a sheet of paper. Base. Stock. Bonus. Signing bonus. PTO. Remote arrangement. Title. When your first review happens. Half of these are movable and half are locked by policy, and figuring out which is which before the call prevents you from burning a negotiation round on something the recruiter genuinely cannot change no matter how much they want to.

When you do call back, lead with data. “I’ve been researching this role at this level in this market using Levels.fyi and Glassdoor, and based on what I’m seeing, I was expecting total compensation closer to $X.” That gives the recruiter something concrete to take to the compensation committee. Compare it to “I was hoping for a bit more,” which gives them exactly nothing. Recruiters advocate for you internally. Arm them properly and they’ll fight harder.

One more thing on leverage, and I’m slightly uncomfortable saying this because it could be misused, but it’s true. Nothing creates negotiating power like a credible alternative. You’re not holding a gun to anyone’s head. You’re not starting a bidding war. You mention it once, naturally, the way you’d mention it to a friend. “I’m also talking with another company. I genuinely prefer this role. I just need to make sure the numbers work for my family.” If that’s true, say it. If it’s not true, don’t lie. Recruiters talk to each other. Our industry is smaller than you think.

How to Negotiate a Raise at Your Current Company

Different animal entirely.

External offers give you leverage because you can walk. Internal raises require a different kind of argument, one built on institutional knowledge, delivered contributions, and the terrifying cost of replacing you. A Gallup study pegged employee replacement costs at half to two times annual salary. Your engineering manager has seen enough departures to know this is real even if nobody in leadership talks about it that directly.

Start documenting months before you plan to ask. Revenue you influenced. Features you shipped. The production outage you caught at 11pm on a Sunday when nobody else was monitoring the alerts. That Kubernetes migration the team had been kicking down the road for two quarters until you finally picked it up and ran it. Be specific. Specificity is what separates a conversation that produces a raise from one that produces a sympathetic shrug and a promise to “revisit it next quarter.”

Timing matters more than you’d expect. Most companies lock compensation budgets in Q4 for the following year. If you walk into your manager’s office in February asking for a raise, the money might literally not exist until the next planning cycle. October or November is the window. Your manager is building next year’s budget and can advocate for your number while the spreadsheet is still editable. Miss that window and you just donated a year’s worth of underpayment to the company.

I need to say something about counter-offers because I watch this go wrong constantly and the pattern is always identical. Engineer gets frustrated. Engineer interviews elsewhere. Engineer gets an offer. Engineer tells their manager. Manager panics, calls HR, gets a retention counter approved within 48 hours. Engineer stays, feeling validated. And then. Six months later the engineer is passed over for promotion because someone in leadership flagged them as a flight risk during the counter-offer approval process. Eighteen months later they leave anyway, because the underlying frustrations that sent them interviewing were never actually addressed. The counter just bought time. I’m not saying never accept a counter-offer. I’m saying if you’re unhappy enough to interview, you might actually need to go.

What Recruiters Actually See on the Other Side

I’m going to tell you something that might change how you think about this, because it changed how I think about it, and I’ve been doing this for fifteen years.

When a company hires us to fill a senior software engineering role, the hiring manager gives us a range. Let’s say $140K to $175K base. The recruiter is not supposed to share the top. Standard practice across the industry. But here’s what candidates never see. The hiring manager usually wants to hire at the midpoint or a little below. Not because they’re trying to screw anyone. Because landing at $150K leaves room for meaningful raises over the first two years without triggering an out-of-band compensation review, which requires VP approval and nobody wants to deal with that paperwork if they can avoid it.

So when someone accepts $140K, the manager is quietly pleased. When someone counters to $160K with a solid justification, “fair enough, approved.” When someone asks for $175K, the manager calls the references one more time, confirms this person is genuinely senior, and almost always says yes if the references confirm what the interviews suggested.

Same skills. Same role. Same company. The difference between $140K and $175K was one phone call. Ten minutes of discomfort. That gap compounds every single year with every raise calculated as a percentage of the higher base, every bonus tied to that base, every 401k match. Over a five-year tenure that one conversation is worth six figures. I’m not exaggerating.

And here’s the flip side, which is equally instructive. Companies that consistently lowball lose their top candidates. We watch it happen. They extend an offer, wait a week, get the polite rejection. Time-to-fill balloons to 60, 90 days. The hiring manager blames “the market” but the actual problem is that their comp philosophy is broken and the best candidates have options. When a client tells us they want a Staff-level cloud engineer for $130K in Los Angeles, we tell them directly that’s not realistic. Better to have that conversation before the search starts than after three months of rejected offers.

Tech Salary Ranges by Role (2026 Benchmarks)

National ranges pulled from BLS data, Glassdoor, Levels.fyi, and our own placement records at KORE1. Location matters enormously, San Francisco pays 20-30% above these numbers and Omaha pays 15-20% below, so treat this as a starting framework for your own research, not the final word.

The jump from mid-level to senior is $30K to $50K in base. At companies with real equity programs the total comp gap is double that. Which brings up something most people don’t think about during interviews. Leveling. If the company levels you one notch below where you actually belong, that single classification decision costs you $50K or more annually, and nobody on the company side is going to tap you on the shoulder and say “hey, we think you might be under-leveled.” That’s your job to catch. Ask directly what level the role is and how they determined it. If the answer is vague, push.

Mistakes That Actually Cost People Money

Blurting out your current salary. Fourteen states plus a bunch of cities now prohibit employers from asking this question. Even where it’s still legal, you do not have to answer. And here is why answering destroys your negotiation. You’ve just handed the other side an anchor that has nothing to do with the market value of the role you’re interviewing for. If you’re currently making $125K because your last company underpaid the whole engineering team, you just guaranteed yourself an offer in the low $130s when the approved range goes up to $165K. Redirect. “I’d prefer to focus on what the market supports for this role at this level and the value I’d bring.” Practice that sentence until it comes out without hesitation, because they will ask and the first time they ask is the worst possible moment to be making up your answer on the fly.

Hiding behind email. I get it. Email gives you time to craft the perfect response. But salary negotiation is a relationship conversation and email strips out everything that makes relationships work. Tone. Warmth. The ability to hear the recruiter pause and realize “oh, they’re actually flexible on that point.” Call them. Have the real conversation. Send the email afterward to document what you discussed. Not the other way around.

Acting like you’re in a fight. By the time you have an offer, the hiring manager and recruiter are both rooting for you. They chose you. They want you to say yes. The thing you’re actually negotiating against isn’t a person. It’s a compensation policy and a budget. “How can we get closer to $X?” is a fundamentally different conversation than “Give me $X or I’m walking.” One of those gets the recruiter working on your behalf inside the company. The other gets your file flagged and moved to the bottom of the priority list.

Fixating on base and forgetting that four other levers exist. Quick math. A $10K base increase compounds with every future raise and bonus calculated off that number. A $30K RSU bump spread over four years is $7,500 annually but might be dramatically easier to get approved because it doesn’t hit the company’s cash budget the same way. A $15K signing bonus arrives in your first paycheck and the company forgets about it by the end of Q1. If base won’t move, don’t stop. Ask about equity, signing bonus, start date, review cycle timing, PTO, remote arrangement, professional development budget. We’ve seen people pick up $20K in value from components that weren’t even in the original offer because nobody thought to bring them up until the candidate did.

Treating the first counter as the final answer. It almost never is. You ask for $165K, they come back at $155K. That’s movement. The conversation is working. Most candidates stop right there because the first round already felt uncomfortable and they don’t want to push their luck. But one more specific, data-backed round of discussion usually closes another $3K to $5K. That’s $3K to $5K per year for the rest of your tenure. Have the second conversation.

What to Actually Say

I’m not going to give you scripts to memorize. You’ll sound like you’re reading from a card and the recruiter will hear it immediately. Here’s the shape of what works. Put it in your own words.

When you get the offer and need to buy time: Express genuine excitement. Ask for a specific return date. “This looks great, I want to give it a proper look. I’ll call you back Thursday.” Short. Warm. Gives you 48 hours to do your homework.

When you’re ready to counter on base: Lead with data, not with feelings. “I’ve been looking at Levels.fyi and Glassdoor for this level in this market, and based on what I’m seeing plus my experience with [specific relevant thing], I was hoping we could get closer to $[X]. Is there room to move on the base?” Notice it ends with a question. Not a demand.

When base is stuck and you need to pivot: “Totally understand if the base is at the ceiling. Could we look at the equity grant or maybe a signing bonus to close the gap? I’m thinking about total comp over the first couple years.” This works because you’re giving the recruiter a new problem to solve instead of banging on a door they already told you was locked.

When you’re asking your current manager for a raise: Start with your impact, not with your complaint. “Over the past year I shipped [specific thing], saved [specific amount or outcome], and took on [specific responsibility]. Based on what I’m seeing in market data, I think an adjustment to $[X] makes sense. What do you think is realistic?” The last sentence matters. You’re inviting collaboration, not issuing an ultimatum, and that framing makes it dramatically easier for your manager to go to bat for you with whoever controls the budget.

Pay Transparency Is Rewriting the Rules

Sixteen states and counting. California, New York, Colorado, Washington, Massachusetts, and eleven others now require salary ranges in job postings. Massachusetts expanded its law in late 2025. California refined SB 642 in 2026. More bills moving through state legislatures right now.

For job seekers this is a massive shift. If a posting says $140K-$180K, you know $180K exists. You don’t have to guess. You don’t need a friend at the company to slip you the number. It’s in the posting.

But most people misread what the range means. The posted range is the approved band. It is not the typical offer. Most initial offers land somewhere between the 25th and 50th percentile of the range. So $140K-$180K typically means an offer around $148K to $158K. The remaining $20K to $30K above the initial offer is real money that’s theoretically available. It’s just sitting on the other side of a conversation most candidates never start.

There’s a social justice angle here too that matters. Research from the Journal of Applied Psychology found that when objective salary data is publicly available, gender differences in negotiation outcomes essentially disappear. Pay transparency doesn’t just help you personally. It helps fix a systemic problem that has been costing women and underrepresented groups billions in aggregate lost earnings for decades. If you’re an employer still hiding salary ranges, you’re not protecting the company. You’re protecting a system that produces inequitable outcomes. And you’re repelling the candidates who do their homework, which is almost certainly the opposite of the talent filter you want.

Things People Ask About Salary Negotiation

So what happens if they rescind the offer because I negotiated?

In fifteen years I’ve seen it happen maybe three times. Maybe. And in each case the company had other problems that would have surfaced within the first six months anyway. The Fidelity data says 85% of people who negotiate get something. The actual number in my experience is higher than that. If a company pulls an offer because you politely asked a question about compensation, they were going to nickel-and-dime you on every raise, every promotion, every reorg for as long as you stuck around. You didn’t lose an opportunity. You dodged a bad one.

How much more should I actually ask for?

Depends on the gap. 10% to 20% above the initial offer is the comfort zone for most tech counters. Below 10% barely registers after taxes. Above 20% starts to feel unmoored unless you’ve got competing offers or data that specifically shows the initial number is below market. I had a candidate counter at 28% once because she had three other offers and strong Levels.fyi data backing her number. Got it. No drama. But she had the receipts. If you don’t have the receipts, stay in the 10-20% band and bring the research.

Does it work differently at startups versus big tech?

Night and day. Big tech runs on rigid leveling systems with approved compensation bands. The recruiter cannot go above the ceiling for your level. Period. Your lever is arguing for a higher level or pushing hard on equity and signing bonus, where the bands are wider and the approval process is faster. Startups have more flexibility on base and title but less total cash, and the equity is speculative. Could be worth a fortune. Could be worth absolutely nothing. With startup equity, negotiate the vesting schedule, the acceleration clause, and especially the post-departure exercise window. A 90-day exercise window on ISOs at a late-stage startup that hasn’t IPO’d can force you to either write a six-figure check or forfeit years of vesting when you leave. The number of shares matters less than the terms attached to them.

Can I negotiate remote work as part of comp?

Absolutely. More people are doing this than the headlines about return-to-office mandates suggest. Full remote eliminates commute costs, opens up geographic arbitrage on cost of living, and changes the childcare math for parents in ways that are worth real money. If a company is offering a San Francisco salary and you live in Austin, the purchasing power difference alone is worth $20K to $30K annually even though the number on the offer letter is identical. Some companies adjust for location. Others don’t. Find out before you accept, because it changes the math on everything else in the offer.

Should I use a recruiter to handle this for me?

If you’re already working with one, absolutely. Here’s why most candidates don’t realize this: the recruiter has a financial incentive to get you the highest possible salary. Their fee is typically a percentage of your first-year compensation. They negotiate these conversations twenty, thirty times a month, which means they know the hiring managers personally, they know which comp teams are flexible and which aren’t, and they know the exact arguments that work at each company because they’ve made those arguments before for other candidates. Your part is simple. Be honest about what you want, what you’d walk away from, and what matters most to you beyond just the base number. Let the recruiter handle the back-and-forth. That’s literally what they do for a living.

Make the Ask

The math on this is hard to argue with. Ten minutes. 85% success rate. Average 18.83% increase. There is no course, no certification, no conference presentation, no LinkedIn post that delivers anywhere close to that kind of return on time invested. Nothing.

Do the research. Set a number. Practice saying it out loud in your car if you need to, most people find that once they’ve said the words once the second time feels completely different, like the difference between a cold open mic and a rehearsed set. Then pick up the phone. The person on the other end is expecting your call. They budgeted for this conversation. The only person who loses when you stay quiet is you, and unlike most career mistakes, this one is entirely fixable by opening your mouth and asking.

If you’re exploring new tech roles and want someone in your corner who already knows the budget range before the negotiation starts, talk to our team. We do this every week.

For the specific salary data you’ll need to anchor your number, check our guides for AI/ML engineers, DevOps engineers, cloud engineers, data engineers, and cybersecurity engineers. Or plug your info into the Salary Benchmark Assistant and see where you stack up.