You Answered the Recruiter's Salary Question. That Was the Mistake.

The recruiter salary question lands about ten minutes into the call. You've heard about the role, said it sounds interesting, confirmed you're still looking. Things are going great. You feel good. Then:

"Before we go further, I just want to make sure we're aligned on compensation. What are you looking for?"

Most engineers answer. They say a number. Maybe a range. They did the research on Levels.fyi, double-checked against a friend's offer, and feel totally prepared. Mentally rehearsed, even.

And the moment they say it, the negotiation is over. Not ended in a dramatic way. Just quietly decided, in the recruiter's favor.

The Company Already Has Your Number

The salary question is not a question.

The recruiter is not asking because they lack data. They have more data than you do. Big tech companies benchmark compensation using internal surveys, compensation databases, Levels.fyi, and market intelligence tools that aggregate every offer made in their industry. Before you picked up the phone, the company had a salary band for this role. A minimum, a midpoint, a maximum. The band existed before your name reached anyone's inbox.

Asking "what are your compensation expectations?" is a bit like a poker player asking you to show your cards first, then promising to play fair. It's not malicious. It's just a question that only ever benefits the person asking.

If you volunteer a number below their band, they don't correct you. They note it, use it to structure the offer, and thank you internally for making their job easier. If you land at the top of the band, they get useful signal on how hard they'll need to push. Either way, you've handed them information that moves their offer toward your number instead of their ceiling.

There's real research behind this. A 2022 study on US salary history bans found that when employers couldn't use prior compensation as a reference point, newly hired female workers earned salaries 7.8% higher than peers in jurisdictions without the bans. The information itself, when you provide it, costs you money.

So don't provide it.

The Flip

When a recruiter asks what you're looking for, the cleanest response is: "I'd love to make sure we're aligned. Could you share the salary band for this role first?"

You'll feel awkward saying this the first time. That feeling passes. Most recruiters will just tell you the band.

In 18 states plus Washington D.C., this isn't a negotiation tactic. It's the law. California's SB 1162, Colorado's Equal Pay for Equal Work Act, New York's pay transparency rules, and equivalent laws in Illinois, Massachusetts, and Washington require employers to disclose the salary range upon request. If you're interviewing with a company hiring in any of these states, asking for the range is your legal right, and you should exercise it as casually as you'd ask for the meeting invite link.

Even in states without disclosure laws, recruiters share the range more often than candidates expect. They want to close positions. Asking simply and directly gets a real answer most of the time. Try it before assuming it'll create friction.

When they do share the range, anchor to the top end. If the range is $160K to $210K, you're targeting $210K. Not the midpoint, not "somewhere fair." The top.

When They Push Back

Some recruiters push. The system requires a number. They can't proceed without it. Everyone else on the call has told them.

This is pressure, not fact. You don't need to make it a standoff, but you also don't need to fold.

The script that works: "I don't feel equipped to throw out a number because I'd like to find out more about the opportunity first. Right now, I genuinely don't have enough context to say something concrete. If you end up making me an offer, I'd be happy to iterate on it with you."

This is not evasive. It's accurate. You don't know the role scope, the team, the leveling, or the full comp structure. You're not stonewalling. You're committing to good-faith negotiation once you have an actual offer, which is what the recruiter needs to keep the process moving.

If they absolutely need a number for an internal system, Patrick McKenzie's advice from his canonical negotiation essay holds up: "Put in $1 to get the ball rolling. We'll circle back to the actual number." It sounds absurd. It works. The number is a placeholder, not a commitment, and most recruiters understand that implicitly once you say it.

The recruiter will move on. They've had this conversation before. You're not the first.

Base Is Usually the Wrong Number Anyway

Most engineers lose another $20K without realizing it, and it comes from fixating on base salary.

At most tech companies, the package has three components. Base salary. Equity (RSUs). Signing bonus. Candidates spend the entire conversation negotiating base because it's familiar, like an hourly wage, and they have the cleanest intuition about it.

At senior-engineer level and above, equity often exceeds base salary as a percentage of total comp. A $180K base with $200K in annual RSU grants and a $50K signing bonus is a $430K package in year one. A $210K base with $50K in annual RSUs and no signing bonus is $260K. A $30K base difference can flip when you look at the full picture.

Ask explicitly: "Can you walk me through the full comp structure, including equity, the vesting schedule, and signing bonus?" Then evaluate on total comp.

Three things worth knowing that recruiters sometimes understate:

Vesting schedules matter enormously. Amazon's 5/15/40/40 structure means 80% of your equity lands in years three and four. Most other companies vest 25% per year with a one-year cliff, meaning zero equity until month thirteen. (The full mechanics are in vesting schedules and cliffs.) Getting laid off at month eleven at a company with a cliff is a bad day. Get informed before you accept.

RSU grants get quoted four different ways. The same grant might be described as "$400K over four years," "$100K per year," "X,000 shares," or "Y% of annual target equity." Know exactly what you're comparing before you compare anything.

Refresh grants at Google, Meta, and Amazon are often much larger than candidates expect and effectively replace or exceed the initial grant by year two. They're not contractually guaranteed, but they're real and they're included in how total comp should be modeled.

The Lever That Actually Moves Things

No scripting, research, or clever deflection creates as much negotiating power as a competing offer.

When companies see that another employer is willing to pay you $240K total comp, the question stops being "what's in our band?" and becomes "what do we need to do to win this candidate?" Meta's initial offers are often $50K to $100K below what they can actually extend once competing offers surface. The band is not the ceiling. It's the floor of what the recruiter has unilateral authority to approve without escalation.

If you can sequence your processes so that multiple companies are in the offer stage simultaneously, the value of each individual offer multiplies. One offer is a request. Three offers are a market. You don't need to be aggressive about this. You just need to time your processes intentionally.

A phrase that buys you time without burning a relationship: "I'm currently in late-stage conversations with a few other companies and expect to have clarity on their timelines within the next two weeks. I'm very excited about this role and would love to coordinate so we can move to an offer stage together."

Recruiters hear this constantly. They don't resent it. They understand exactly what it means, and they coordinate accordingly.

Things Not to Say Out Loud

A few more things that only hurt you to volunteer before you have an offer:

Where else you're interviewing. Saying you're in process with Google makes a recruiter at Stripe more motivated. Saying you're at a startup no one has heard of does not. Share process status without naming companies until you have competing offers and want to use them.

How far along you are in other processes. "I have an offer expiring in three days" is a real chip. "I had a first round with someone last month" means nothing and deflates your leverage rather than creating it.

Your enthusiasm level. "This is my number one choice" removes your willingness to walk away. That willingness, real or perceived, is the only leverage you have once you're in the final negotiation. You can love the company and still not say that out loud.

Recruiters have their own incentives. External agency recruiters earn 15 to 25% of your first-year salary on placement. Internal recruiters are measured on closed positions. Neither is optimizing for your maximum outcome, and they're not supposed to be. That's your job.

The Number to Know Once You Have an Offer

After you've done the research, asked for the band, and received an offer: the standard counter is 10 to 20% above the initial offer. Not because that's the absolute maximum, but because it's well within the range companies expect and generates very little friction.

The data on this is consistent. Counteroffers within 20% close at high rates. Above 30% starts to create awkward dynamics unless you have a competing offer that justifies it. If you do have a competing offer significantly above theirs, it speaks for itself. You don't need to be clever. You just say the number and explain where it's coming from.

The more important number: around 56 to 60% of candidates accept the first offer without negotiating at all. That's the easiest money left on the table in software engineering. Companies budget for counteroffers. They expect them. The ask itself is almost never the problem.

For the full playbook once an offer lands, see how to counter a job offer.

Practice negotiating the same way you practice coding: in conditions that match the real thing. If you're using mock interviews to sharpen your DSA before the technical rounds, SpaceComplexity gives you a realistic voice-based environment to work through problem-solving under pressure. The principle is the same for comp conversations. You don't want the recruiter call to be the first time you've said any of this out loud.

The Short Version

The recruiter already has your market value estimated. The question tests whether you know it too.
Ask for the band first. In 18+ states you're legally entitled to it. Elsewhere, many recruiters will share it anyway.
When pressed, use the deflection script. Commit to good-faith negotiation after the offer, not a number now.
Think in total comp, not base. RSUs and signing bonuses are often more flexible than base salary.
Competing offers are the real lever. Sequence your processes to create them.
Counter at 10 to 20% above the initial offer. Most companies expect it.