Salary Negotiation Conversation Tactics

Research consistently shows that most employers build wiggle room into their initial offers precisely because they expect candidates to counter — except many don't, and those people are leaving real money sitting on the table. A UCLA Anderson field study tracking tech job seekers over a recent two-year stretch found that candidates who countered walked away with a meaningful bump over the initial offer, often in the tens of thousands annually. That's a car payment, or a kid's daycare, or a real dent in a mortgage.

It compounds, too, and not in your favor if you skip this step. Every raise you get from this job gets calculated as a percentage of your base, so a higher starting number doesn't just pad year one, it pads every single year after it. Run that out over a decade and the gap between the person who negotiated and the person who didn't stops looking like pocket change. It starts looking like a down payment on a house.

Here's the part that should actually bother you: the fear driving the silence doesn't match the real risk. Most employers say they've never once pulled an offer because a candidate asked for more, and negotiated offers stay intact at rates far higher than most candidates assume going in. The catastrophic outcome everyone's quietly dreading basically doesn't happen, while the cost of saying nothing compounds for ten years straight. Calling that a bad trade is underselling it.

How the first number said out loud controls everything that follows

Anchoring is one of the oldest, most replicated findings in behavioral economics: the first number introduced into any negotiation shapes every judgment that follows it, even when everyone in the room knows the number is arbitrary. It holds up especially well in single-issue negotiations like salary talks, where there's no second variable to distract from the anchor. Whoever speaks first sets the frame, full stop.

Once that anchor lands, it's stubborn. Even trained, professional negotiators tend to move their final number only a modest distance from wherever the anchor first sat. Set it high, and the ceiling moves with it. Say nothing, and someone else sets it for you, usually lower than you'd like, and usually without telling you that's what just happened.

This is exactly why salary history questions turned into a legal fight in half the country. A large share of hiring managers admit a candidate's previous salary swayed the offer more than the market rate for the role itself, which is a polite way of saying your old paycheck was doing the negotiating for you without asking permission. A growing list of U.S. states and cities have banned employers from asking the question outright. The law caught up to what the anchoring research already knew: whoever states the first number wins the frame, so don't hand it over for free.

What to say when they ask your number before you're ready

Two questions show up in nearly every interview, and both are traps dressed up as small talk. "What are you currently making?" chains your new offer to your old one. "What are your salary expectations?" forces you to anchor before you know enough about the role to anchor well. Neither gets asked out of curiosity; both get asked to lock in the frame before you've built one of your own.

Josh Doody, who wrote Fearless Salary Negotiation, has a deflection for the first question worth memorizing word for word: "I'd prefer to focus on the value I can add here rather than what I'm paid now." For the expectations question, something like "I want this move to be a big step forward in both responsibility and compensation" does the same job. Both move the conversation off your past paycheck and onto your future contribution, which is the frame that actually helps you.

If the interviewer presses after the deflection, resist the urge to invent a number just to end the discomfort. Ask for information instead: "Can you share the range budgeted for this role? That would help me give you a more useful answer." That question keeps you from negotiating blind.

None of this works if it comes out sounding like a hostage note read off an index card. It has to sound like something you'd say normally on a Tuesday, which means saying it out loud, alone in your car, twenty separate times before the interview. Reading it once and hoping muscle memory shows up on command is how you end up stammering through it live, in front of the one person you were trying to impress.

How to deliver your counter-offer so it lands with authority

The counter itself has three moves, and skipping any one weakens the whole thing. First, acknowledge the offer like you mean it: "Thank you, I'm genuinely excited about this role and the team." Second, state your number, specifically: "Based on my research and the scope of this position, I was expecting something closer to $X." Third, stop talking, completely.

That third move trips up more people than the first two combined. Silence after a number feels unbearable to most candidates, so they fill it, apologizing, softening, over-explaining their way right out of the number they just stated. Every word that follows the number chips away at it. The discomfort of silence is doing the actual work; let it.

Use a specific figure, never a range. A range just tells the employer which end to aim for, and it's always the low one. A precise number signals you did your homework, and citing where it came from adds weight: a named market benchmark or industry salary data source. Professionals who cite market data in these conversations tend to out-earn the ones arguing from gut feeling alone, sometimes by a wide margin. "Glassdoor puts this role at $X to $Y in this market" carries more weight than quiet confidence in your own worth on its own.

How you say it matters almost as much as what you say. Confident delivery leans toward lower pitch, steady volume, and a pace that stays controlled. A rising tone at the end of a sentence reads as a question even when it's phrased as a statement, and it undercuts the ask instantly, like ending a demand with a shrug. Cutting the apology reflex matters too: "I'm sorry to ask" and "I know this might be too much" tell the other side you don't believe your own number, and why should they, if you don't?

The odds favor asking regardless. Among workers who ask for more pay, roughly a quarter get exactly what they requested, and another sizable share get more than the original offer even without the full ask. Add those groups together and most people who simply asked walked away better off than the ones who stayed quiet and took whatever landed on the table first.

What to say when they push back or say no

Employers rarely say no outright. What you'll usually get is soft resistance: "That's above our range," or "We're pretty firm on this." Treat that as an opening, not a locked door. The single best response is short, but it does real work: "Is there flexibility here?" Five words, and the conversation doesn't get to die on the sentence before it.

If the pushback hardens, don't just repeat your ask louder. Ask a diagnostic question instead: "Can you help me understand how you arrived at this number? I want to make sure I'm clear on how my experience and skills map to this level." That question tends to surface the real constraint, usually an internal pay band the recruiter genuinely can't move on their own authority. Pay bands, unlike recruiters, sometimes have flexibility built in elsewhere.

That's your pivot to total compensation. If base salary is genuinely locked, name something specific instead of vaguely asking for "more": "If adjusting the base salary isn't possible, I'd value discussing flexible work arrangements. In my previous role, working remotely two days a week made a real difference in my output." A signing bonus works the same way, since it's a one-time payment that never touches the pay band at all. Accelerated review timelines, extra PTO, a development budget are all fair game. The goal is widening the table until something on it actually moves.

Persistence pays off here more often than people assume; the large majority of full-time employees who ask for a raise get one. One caveat, though, and it's worth stating plainly: leave personal expenses out of the conversation entirely. "My rent went up" or "I've got student loans" reframes the ask as need instead of value, and need loses to value every time at this particular table.

Why these words only work if you've said them out loud before

The best negotiators rehearsed the exact words beforehand, over and over, until the phrasing stopped sounding like a script and started sounding like them, just talking. Practicing the conversation with a spouse or a friend the night before — not the morning of — gives the words time to feel awkward and then get less awkward before it counts.

Repetition is the whole mechanism. Say a sentence enough times and your mouth stops treating it like a threat. Anyone who's ever rehearsed a hard conversation in the shower knows this firsthand: the words don't change, but your relationship to saying them out loud does.

That matters because fluency itself is a signal, separate from content. Delivery that doesn't halt or hedge reads as sharper and more authoritative, regardless of whether the number behind it is any good, while a stumbled or over-apologized ask undercuts even excellent research. There's a mirroring effect too: people in a negotiation tend to match the confidence level of whoever's sitting across from them. Walk in projecting certainty, and the other side's posture shifts to meet it. Walk in hedging, and you've just handed them the upper hand, free of charge.

So rehearse like it's the actual job, treating it with the same seriousness as the interview itself. Say the deflection lines until they stop sounding stiff. Record yourself running the counter-offer and listen for where your pitch climbs or your pace stutters, because you will hear it, and it's uncomfortable in a genuinely useful way. Sit in the silence after the number instead of rushing to fill it. Then find someone willing to actually push back, not just nod along politely, and run the resistance scenario until the diagnostic question comes out clean and unbothered.

Reading this once is homework. Saying these sentences out loud ten times, badly, alone in a room where nobody's watching, until they stop sounding borrowed, is the part that actually works.