Tech Salary Negotiation Mistakes Costing You $20K+

Tech Salary Negotiation Mistakes Costing You $20K+

Salary negotiation mistakes cost tech workers tens of thousands of dollars per year. Not because engineers lack skill or experience, but because negotiation is a separate discipline, and most engineers have never practiced it.

I’ve coached dozens of engineers through this exact situation. One client (let’s call her Priya) came to me after accepting a senior role at a large cloud company. She was thrilled with the offer, until she talked to a peer on the same team who’d been hired at the same level, three months earlier, for $35K more in total comp. Same role. Same level. Same team. The difference was how they handled the negotiation.

That gap compounds. Over four years at that company, it’s $140K in lost earnings, not counting the knock-on effect on future offers. Even a conservative average across common mistakes lands well above $20K per year in missed compensation.

Here are five salary negotiation mistakes I see repeatedly, and what to do instead.

Salary Negotiation Mistake #1: Anchoring Too Low by Sharing Your Current Compensation

When a recruiter asks “what are you currently making?”, many candidates answer honestly and immediately. This feels like the right thing to do. It’s not.

Your current salary reflects your current company’s pay bands, your tenure, when you were hired, and how well you negotiated last time. None of that has anything to do with what this new role should pay.

According to research from Harvard’s Program on Negotiation, the first number in any negotiation sets the anchor. If you share a number below the role’s range, the offer will cluster around your anchor, not the top of theirs.

The fix: In many states, it’s now illegal for employers to ask about salary history. But even where it’s legal, you can redirect: “I’d prefer to focus on what this role pays. What’s the range you’ve budgeted for this position?” If pressed, give a range based on market data from Levels.fyi or Glassdoor, not your current paycheck.

Salary Negotiation Mistake #2: Treating Base Salary as the Whole Compensation Package

A senior engineer offer at a major tech company might show $185K base. That looks strong. But total compensation includes RSUs, signing bonus, annual bonus, and sometimes other components like relocation or refresher grants.

I coached an engineer (let’s call him Marcus) who focused exclusively on base salary during his negotiation. He pushed hard and got an extra $10K in base. Good. But he never touched the equity component, which was worth $60K per year. A 10% bump on that equity would have been $6K annually for four years, totaling $24K, and equity negotiations often have more room than base.

The fix: Always negotiate total compensation, not base salary alone. Ask for the full breakdown in writing: base, equity (vesting schedule included), signing bonus, annual bonus target, and any other components. Then negotiate the pieces where the company has the most flexibility. At most large tech companies, that’s equity and signing bonus, not base.

Tech Salary Negotiation Mistake #3: Accepting the First Offer Without a Counter

Companies don’t open with their best number. This is standard practice, not a secret. Recruiters expect a counter. When you don’t counter, you’re leaving money on the table, and the recruiter knows it.

One pattern I see often: an engineer has been job searching for months, gets an offer that’s higher than their current salary, and accepts immediately out of relief. The emotional logic makes sense. But a first offer at a large tech company is typically 10-20% below what they’re willing to pay, especially for strong candidates.

In practice, companies almost never rescind offers for reasonable counteroffers. It’s actually the candidates who don’t negotiate who sometimes raise concerns, because hiring managers wonder if they’re not taking the role seriously enough to engage.

The fix: Never accept on the spot. Say something like: “I’m excited about this opportunity. I’d like to take a few days to review the full package.” Then come back with a specific counter based on market data and your competing signals. Even if you don’t have another offer, expressing enthusiasm while asking for time is standard and expected. I’ve written more about the specific language and tactics in my post on software engineer salary negotiation.

Negotiation Mistake #4: No Bargaining Power From Competing Options

This is the structural mistake behind many weak negotiations. You have one offer and no alternatives. The company knows you need them more than they need you.

A strong negotiating position doesn’t require a competing offer (though that helps enormously). It requires credible alternatives. That might be another company in your pipeline, a strong current role you’re genuinely willing to stay in, or even a counter-offer from your existing employer.

A coaching client once told me he felt guilty about interviewing at multiple companies simultaneously, like he was being dishonest. But running parallel processes is how you create the conditions for a fair negotiation. Companies interview multiple candidates for every role. You’re allowed to evaluate multiple companies.

The fix: Start your job search by building a pipeline, not by falling in love with one opportunity. Even if there’s a clear front-runner, keep two or three processes moving in parallel. When it’s time to negotiate, you don’t have to reveal specific numbers. “I’m in late stages with another company” is often enough to shift the dynamic. For more on structuring a job search that gives you bargaining power, see why your tech job search isn’t working.

Salary Negotiation Mistake #5: Ignoring the Things That Compound

Engineers negotiate salary. The good ones negotiate equity too. But almost nobody negotiates the things that compound over a career: level, title, review timeline, and scope.

Getting hired at L5 instead of L4 doesn’t only mean a higher starting salary. It means your next promotion cycle, your next job’s leveling, and your long-term earnings trajectory all shift upward. According to Levels.fyi compensation data, the median total comp gap between adjacent levels at companies like Google or Meta can be $80K-$150K per year, depending on the company and the specific levels.

One engineer I coached negotiated an accelerated review timeline (six months instead of twelve) as part of his offer. He hit the performance bar, got promoted, and was earning at the next level before most of his cohort had their first annual review. That single negotiation point was worth more than any signing bonus.

The fix: Before you negotiate comp, negotiate level. If the company is down-leveling you (offering L4 when you believe you’re L5), push back with evidence: your scope, your impact, your years of relevant experience. If they won’t budge on level, ask for a written commitment to an early review cycle. These are the decisions that move your career trajectory, not a few thousand dollars in signing bonus.

The Common Thread

All five mistakes share the same root cause: treating negotiation as a one-time event rather than a skill. Engineers who negotiate well aren’t more aggressive or more confrontational. They’re more prepared. They know the market data, they’ve practiced the conversation, and they’ve built their position before the offer arrives.

If you’re preparing for interviews right now and want to make sure the offer stage doesn’t undo all your hard work, I put together the SWE Interview Prep System. It walks you through the full process from behavioral and system design prep through offer evaluation and negotiation tactics, so you’re ready when the numbers hit the table.

Go Deeper

• Software engineer salary negotiation: how to get 10-30% more without blowing the offer
• 5 salary negotiation patterns I keep seeing when coaching engineers
• Why your tech job search isn’t working (and how to fix it)