All posts
Role Guides7 min read

How to Negotiate Salary as a Software Engineer in 2026

Most engineers leave 10–20% on the table because they don't know what to say. Here's the exact playbook — market data, opening lines, and how to handle every pushback.


A few months ago, a senior engineer named Marcus messaged me after accepting a $155,000 offer at a mid-size fintech. He hadn't negotiated. He'd spent two weeks going back and forth in his head, convincing himself the offer was fair, that they'd rescind it if he pushed back, that asking would make him seem greedy.

Then he got to his first team standup and a colleague mentioned their total comp. It was $178,000 for the same level.

Marcus left $23,000 on the table that year. Compounded over four years with raises and equity refreshes — it was closer to $120,000.

This is the most common story I hear. Not because engineers are bad negotiators. Because they never had a script.

Here's the one they needed.

What the Market Actually Looks Like Right Now

Before you can negotiate, you need a number. And not a vague range from a random salary site — a specific, defensible figure you can say out loud with confidence.

For software engineers in 2026, here's roughly where the market sits:

  • L3/L4, San Francisco or Seattle: $165k–$195k base
  • L4/L5, New York: $155k–$185k base
  • L4, fully remote: $135k–$165k base
  • L3, Austin or Denver: $125k–$150k base

FAANG and top-tier companies sit 20–30% above these figures. Early-stage startups are 10–20% below, ideally offset by meaningful equity.

Your specific number comes from cross-referencing three sources: Levels.fyi (most accurate for TC at large companies), Glassdoor (useful for ballpark by role), and LinkedIn Salary (helpful for newer roles and smaller companies). If all three point in the same direction, you have your anchor.

The Opening: Don't Leave It to Improvisation

Most engineers blow the negotiation in the first 30 seconds. They say something like "yeah, that sounds great, I'm really excited, but maybe there's any flexibility?" — which is the verbal equivalent of walking into a car dealership and saying you really love the car and want to buy it today.

Here's an opening that works. It's direct, it's backed by data, and it doesn't apologise for itself:

"Thank you — I'm genuinely excited about this role and I can see myself doing some of my best work here. That said, based on my research into market rates for this level in [city], and a competing offer I'm also weighing, I was expecting something closer to [$X]. Is there flexibility on the base?"

Three things this line does right:

  1. It confirms genuine interest (you're not playing games)
  2. It anchors to market data, not personal need
  3. It mentions a competing offer without making it a threat

If you don't have a competing offer, drop that clause. The market data alone is enough.

What to Do When They Push Back

They will push back. Every hiring manager does. It's not personal — it's just process. The three most common responses and how to handle them:

"This is the top of our band for this level."

Don't argue with the band. Ask about the band itself:

"I understand — is there flexibility to bring me in at the next level, given my [specific experience/project]? Or is there room to discuss the signing bonus to bridge the gap?"

Bands are often more flexible than recruiters let on. And sign-on bonuses frequently have more room than base salary because they don't affect future raise calculations.

"We can't move on base, but we can look at the equity package."

Engage with this seriously. Get the specifics:

"I'd love to understand the equity better. What's the current strike price, the last 409A valuation, and how has the company grown revenue year-over-year?"

This question signals you know what you're doing. It also shifts the conversation from "do we move the offer" to "how do we make this work."

"The offer expires on Friday."

This is almost always a tactic. A company that wants you badly enough to make an offer wants you badly enough to wait 48 more hours. Respond calmly:

"I appreciate the timeline. I want to make sure I'm making the right decision for both of us — can we find 30 minutes to talk through the full package tomorrow?"

Almost every deadline is softer than it sounds.

The Number to Ask For

Engineers consistently under-ask. They aim for a 5% increase when they should be aiming for 15–20%.

My rule of thumb: if your offer is below the market midpoint, ask for the top of the mid range. If it's at market, ask for 10% above. If it's above market, ask for 5–8% and focus negotiation energy on equity, sign-on, and PTO instead.

For Marcus's situation — $155k offer in a market where the mid was $165k and the high was $185k — the right ask was $172k. That's not greedy. That's what the data says the role is worth.

He should have said it.

Competing Offers: How to Use Them Without It Feeling Gross

If you have a competing offer, mention it. Not as a weapon — as context:

"I want to be transparent with you. I do have another offer at $X. I'm more excited about this role, which is why I wanted to have this conversation rather than just accepting it. Is there anything you can do to make the decision easier?"

This framing is honest and professional. It gives the employer a clear action to take. And in my experience coaching thousands of engineers through this, it works more often than not.

If you don't have a competing offer: don't fabricate one. The tech world is smaller than it looks, and a dishonest negotiation is a bad start to a job relationship. Lead with market data instead — it's almost as effective.

One Thing Most Engineers Get Wrong

They treat negotiation as a single event. It isn't.

The best negotiations are two or three rounds of low-stakes conversation, not one high-pressure ultimatum. When you make your first ask, you're not expecting an immediate yes. You're starting a conversation. The recruiter needs to take it to the hiring manager. The hiring manager might need approval. This takes time, and that's fine.

Don't fill the silence with backpedalling. Make your ask, then wait.

Practice It Until It Feels Normal

I've seen engineers who are brilliant under technical pressure completely freeze when asked "what salary are you expecting?" It's not a skill gap. It's a practice gap. They've never said the words out loud.

If the conversation is happening on Thursday and you haven't rehearsed it — rehearse it tonight. Say the numbers. Say your opening line. Ask someone to play the hiring manager and push back. The first time you say "$172,000" it feels awkward. By the tenth time, it feels like a fact.

Your Move

If you've got an offer in hand right now, you have 48 hours to make a decision you'll live with for years. SalaryAsk will benchmark your offer against real 2026 market data, tell you exactly what to ask for, and let you practice the conversation with a virtual hiring manager until it feels natural.

The first session is free. The average engineer who uses it walks away with $11,000 more per year.

Analyse your offer now →

Negotiating your own offer?

SalaryAsk benchmarks your offer against real 2026 market data, builds your personalised strategy, and lets you practice the conversation with a virtual hiring manager — free.

Analyse my offer free