5 Salary Negotiation Patterns I Keep Seeing When Coaching Engineers

5 Salary Negotiation Patterns I Keep Seeing When Coaching Engineers

Salary negotiation coaching is some of the highest-stakes work I do with engineers. It’s also the most revealing. You learn more about how someone handles pressure from one live offer conversation than from months of career planning.

After coaching engineers through dozens of real offer negotiations (early-career through principal, FAANG through series-B startups) certain patterns repeat so consistently that I can predict them now. Not always. But often enough to write this.

These aren’t abstract principles from a negotiation textbook. They’re things I’ve watched go wrong in real time, with real money at stake, across enough engagements that the patterns are hard to miss.

1. The Salary Negotiation Pattern I See Most: Silence After the Number

This is the pattern I see most often. An engineer names their ask, and then, before the recruiter has said a single word, they start walking it back.

“I was thinking around $200K… but I’m flexible, obviously, depending on the full package.”

That second sentence cost them money. The recruiter heard the hedge and stored it. In a real negotiation, that moment gets used.

The instinct behind it is understandable. Silence feels like rejection. Naming a specific number feels exposed. So the engineer softens it in real time.

What I coach instead: say the number, then stop talking. Sit in the silence. Let the recruiter respond. The discomfort of a two-second pause is real. The cost of pre-emptively caving is also real, and it compounds across the whole conversation.

This is almost entirely a preparation problem. You can know intellectually that silence is fine. It’s different to actually sit in it when money is on the table. We rehearse the moment before the call so the engineer has felt the discomfort once already. That makes the second time survivable.

2. Most Engineers Anchor Their Salary Negotiation to the Offer, Not the Market

An engineer gets an offer at $175K base. They’ve done market research. They know the band for this role at this company is probably $175K to $215K. Then they ask for $185K.

When I ask why $185K, the answer is almost always some version of: “It seemed reasonable given what they offered.”

The offer is the company’s anchor. The engineer just accepted it.

The number to start from is the market rate for the role, not the company’s opening position. If the market rate is $210K and the offer was $175K, the ask should be closer to $210K, with reasoning attached. “Based on what I’m seeing for this role and level in this market, I was expecting something closer to $210K. Is there room to move in that direction?”

That framing does two things. It gives the recruiter something to bring back internally (a market comparison, not a personal preference). And it shifts the conversation away from “splitting the difference from the offer” toward a real discussion about comp bands.

For market data, Levels.fyi is the reference I point engineers to before any offer conversation. It breaks down total comp by company, level, and location more granularly than most public sources, and it gives you the external data point your ask needs to land credibly.

I have a longer breakdown of how to frame the total comp ask in Software Engineer Salary Negotiation: How to Get 10-30% More Without Blowing the Offer if you want to go deeper on mechanics.

3. Most Engineers Are Negotiating the Wrong Number

Base salary is the number on the offer letter. It’s not always where the meaningful money is.

Engineer after engineer comes to a coaching session focused on base. RSU grant size, vesting schedule, refresh cadence, signing bonus: these come up as afterthoughts if at all. At some companies and levels, a single RSU refresh negotiation is worth more than two years of base salary delta.

This isn’t always about negotiating harder. Sometimes it’s about knowing which lever to pull. At a company where base bands are genuinely tight, pushing hard on base and ignoring equity leaves money on the table. At a company with flexible signing budgets, a one-time ask for a larger signing bonus can close a comp gap without touching base at all.

The prep question I ask every engineer before they pick up the phone: “If they can’t move on base, what would you ask for instead?” Many people don’t have an answer ready. That’s the gap.

Total comp is a system. Negotiate it like one.

4. They Accept the First “No” as Final

Recruiters are almost never the final decision-maker on comp. Most of the time, they’re carrying a range approved by a compensation team, a hiring manager, or both. When they say “that’s the best we can do,” that’s most likely their current mandate, not a hard ceiling.

A significant number of engineers I coach hear that first pushback and accept it. They either move on to other terms or accept the offer as-is.

What I coach is one more step: “I understand you may not have more flexibility right now. Is it worth checking with the hiring manager to see if there’s any room, given my background in X?” That’s not aggressive. It’s a professional ask that gives the recruiter cover to go back internally.

Sometimes the answer is still no. But in my experience, many recruiter-level declines aren’t actual company-level ceilings. The engineer who accepts the first “no” without a gentle probe is leaving potential comp unexplored.

The related pattern is that engineers often don’t push back when a company moves the level down mid-process. Level determines band. A level downgrade can be worth $50K+ in comp over the offer period. That’s worth addressing directly, before signing. I wrote more about how operating at the right level affects your trajectory in What ‘Operating at the Next Level’ Actually Means (Before You Have the Title).

5. How Emotional Pressure Collapses Salary Negotiation Preparation

This pattern caught me off guard early on. Engineers who came into a coaching session having done solid research (market comps pulled, ask number ready, reasoning prepared) would describe folding the moment a recruiter sounded slightly tired or mildly impatient on the actual call.

Not when the recruiter pushed back substantively. Just when the tone shifted.

The cognitive tell is usually a sudden pivot to non-comp benefits: “Well, the PTO policy and remote flexibility are also important to me…” That’s the engineer retreating to safer ground.

What’s happening is that the emotional read of the room is overriding the preparation. The recruiter sounds like they’re done with this conversation, and the engineer’s brain interprets that as rejection risk. So they back off.

Deepak Malhotra at Harvard Business School, whose research and teaching on negotiation spans decades, makes the case that preparation and execution are two separate skills, and that most people conflate them. You can prepare thoroughly and still fail to execute when the emotional environment shifts unexpectedly. Reading about negotiation doesn’t inoculate you against a recruiter’s impatience.

That’s why preparation has to include rehearsal, not just research. When I coach engineers on negotiation, we don’t stop at building the strategy. We walk through the conversation: what will you say when they counter? What if they sound annoyed? What if they say “this is final” in a flat tone? Feeling the pressure once in a low-stakes environment (a coaching call, not a real offer call) makes it recognizable the second time. The discomfort doesn’t disappear, but it stops being a surprise.

The fix isn’t to become emotionally detached. It’s to have felt the discomfort before it counts.

Coaching engineers through these conversations has made one thing clear to me: the gap for most engineers isn’t knowledge. They know they should negotiate. They often know roughly what number to ask for.

The gap is execution under pressure. That’s a preparation problem, and preparation is available.

If you’re heading into an offer conversation, Engineers Optimize Everything Except Their Careers is worth reading for broader context on why this keeps happening, and what it usually costs over time.