Key takeaway: Offers mostly fall apart on process, not price: compensation surprises late in the funnel, slow responses, and adversarial framing. Run the conversation in the opposite order: benchmark the role first (BLS and SHRM data, plus posted ranges now required by pay-transparency laws in states like Colorado, California, New York, and Washington), surface expectations in the first or second call, share your range proactively, and negotiate total compensation rather than a single base number.
Salary negotiation is where recruiting either compounds trust or destroys it. Candidates read the negotiation as a preview of how the company treats people; companies read it as a test of judgment. The goal is not to "win" a lower number. A candidate who accepts feeling squeezed starts with lower morale, keeps interviewing, and is the first to take a counteroffer six months later.
Why do salary conversations go wrong?
Three recurring failure modes:
- The number appears too late. If compensation first comes up at offer stage, any mismatch has now wasted weeks on both sides and the candidate feels baited. This is the single most preventable cause of declined offers.
- The framing is adversarial. Anchoring games and "what's your current salary?" (now illegal to ask in many US jurisdictions; see the state-by-state salary history ban tracker from HR Dive) put the candidate on the defensive.
- The company negotiates base only. Base salary is one lever; equity, bonus, sign-on, level, review timing, and flexibility often close gaps more cheaply and mean more to the candidate.
Step 1: Know the market before you talk
Never enter a compensation conversation without external data. Useful sources, in rough order of reliability:
| Source | What it gives you |
|---|---|
| BLS Occupational Employment and Wage Statistics | Government wage data by occupation and metro area |
| Posted ranges under pay-transparency laws | Real, current, role-specific ranges from competitors' postings |
| SHRM compensation research | Survey-based salary structures and trends |
| Levels.fyi, Glassdoor, LinkedIn Salary | Crowdsourced, noisier, but fast directional checks |
Location still moves numbers substantially; the same role can pay 20 to 30 percent more in New York or San Francisco than in lower-cost metros. For a concrete example of building a defensible range, see our New York recruiter salary benchmark and AI-era compensation benchmarks.
Step 2: Surface expectations in the first two conversations
Ask early, and ask forward-looking questions rather than salary history:
- "What range would make this move worthwhile for you?"
- "We want to make sure we're aligned before we take your time; the budgeted range for this role is X to Y. Does that work for where you are?"
Sharing your range first costs little (in transparency states it is already public) and immediately filters mismatches. It also signals confidence: companies that hide numbers read as companies with something to hide.
Step 3: Lead with transparency, not tactics
State the range, where the offer sits in it, and why. "You're coming in at the 60th percentile of the band because of X; here's what moving up in the band looks like after your first review" is a stronger close than an unexplained number. Explaining the internal logic also protects pay equity across the team, which matters legally and culturally.
Step 4: Negotiate the whole package
When a candidate's ask exceeds the base band, move sideways before moving up:
- Sign-on bonus: one-time cost, closes one-time gaps (unvested equity, lost bonus).
- Equity or additional grant: aligns long-term and often values higher to the candidate than its cost to you.
- Level or title review timing: a committed 6-month review with defined criteria beats an uncommitted higher base.
- Flexibility: remote days, relocation support, learning budget. Cheap, and frequently decisive.
Ask which dimension matters most before offering anything; candidates optimizing for cash, equity, and flexibility need different packages.
Step 5: Move fast and keep talking
Speed is part of the negotiation. Slow responses after a verbal offer read as ambivalence and invite competing offers. Confirm timelines explicitly, deliver the written offer within a day or two of the verbal one, and keep a single point of contact. If the candidate goes quiet, one direct check-in beats three nudges; our follow-up benchmarks apply to offer-stage communication too.
How does this connect to sourcing?
Compensation mismatches are cheapest to catch before outreach. Noon's Autopilot evaluates candidates against your role requirements before you ever contact them, and strict non-negotiables are never relaxed, so if a seniority bar or location constraint drives your comp band, the pipeline reflects it from the first message. That means fewer late-stage surprises of the kind that kill offers. For the top of that funnel, see how to find qualified candidates.
FAQ
Should recruiters share the salary range first? Yes, in most cases. Pay-transparency laws increasingly require it in postings anyway, and sharing first filters mismatches before either side invests weeks.
Can I ask a candidate their current salary? In many US states and cities, no; salary history bans prohibit it. Ask about expectations for the new role instead, which is legal everywhere and more useful.
What if the candidate's ask is above the band? Say so directly, explain the band, and explore non-base levers (sign-on, equity, review timing). If nothing closes the gap, part ways respectfully; a stretched hire above band creates equity problems that outlast the vacancy.
How do I handle a counteroffer from their current employer? Prepare the candidate for it before resignation: counteroffers are common, and the underlying reasons they wanted to leave rarely change. Do not bid against it more than once.
When should compensation first come up? First or second conversation. Any later and you are gambling weeks of process on an unverified assumption.
