About half of job-seekers never say the first salary number—and quietly lose thousands. A recruiter asks: “So, what were you hoping for?” Your pulse jumps. You stall, toss the question back, and think you’re being smart. In reality, you just handed them control of your entire range.
Most candidates think staying vague keeps options open: “I’m flexible,” “I’m sure you’ll be fair,” “I’m more interested in the role than the money.” On paper, that sounds cooperative. In practice, it strips you of one of the only levers you fully control: the first concrete number tied to your value.
The data is blunt. In one experiment, every extra $1,000 in the initial ask pulled the final salary up by about $500. For a role with a realistic spread—say $135,000 to $185,000—that difference in anchoring can mean walking away with $150,000… or $175,000… for doing the same job.
And recruiters know this. Most arrive with a prepared range and a ceiling they won’t volunteer. When you avoid giving a number, you’re not being strategic; you’re silently agreeing to negotiate inside *their* frame instead of deliberately setting your own.
Here’s the part most people miss: the first number only works in your favor if it’s *both* bold and justified. “I was thinking $200K” with no backup sounds random; “Based on market data for Senior PMs in SF, I’m targeting $195K–$210K base” sounds prepared. That difference is everything. Your target should rest on three pillars: current market ranges for your exact role and location, a clear view of your measurable impact (revenue, savings, growth), and a BATNA you’d actually accept—whether that’s your current job at $140K or another offer at $150K.
Here’s how to actually build that first number so it does real work for you instead of sounding wishful or random.
Start with a precise role+location snapshot, not generic titles. “Software Engineer II, NYC, product-focused, 4–6 YOE” is different from “Software Engineer, remote, infra, 2–3 YOE.” Pull data from at least three sources—say LinkedIn Salary, Levels.fyi, and one crowd-sourced site. If you see $145K at the 25th percentile and $195K at the 75th percentile for your band, treat that $50K spread as your playing field, not the company’s posted mid-point.
Next, translate your history into numbers that justify the upper part of that field. If you grew MRR by $600K, improved retention by 4 percentage points, or automated a workflow that saves 120 engineer-hours per quarter, write that down. You’re not just “experienced”; you’re attached to concrete business results. When those results align with what this new team cares about (revenue, cost, risk, speed), you’ve earned the right to sit near the top of their budget.
Now, connect that to a structured ask. One simple formula:
1. Identify the realistic top of market for your band (e.g., $200K). 2. Add 5–10% to create room (e.g., 8% → $216K). 3. Round to a confident, specific figure ($215K instead of $213,720).
Specific numbers signal research. “Given what I’ve seen—similar roles at $185K–$205K—I’m targeting $210K base” sounds intentional. You’re not lobbing $250K just to “see what happens”; you’re steering toward a defendable high end with built-in negotiating space.
Then stress-test that figure against your alternatives. If your current role pays $160K and another pipeline opportunity looks likely at $170K–$175K, anchoring at $210K–$215K for this role sets you up to land somewhere around $195K–$205K. If they come back with $180K and won’t move, you can walk away knowing you’re not leaving obvious money on the table elsewhere.
Finally, pre-plan a concession path. For instance:
- Anchor: $215K - First move down: $207K–$210K with stronger bonus/equity - Floor: $195K total comp, below which you exit
When the recruiter asks, “What range are you targeting?” you’re ready with a number that is high, specific, and already battle-tested against the rest of your market reality.
Here’s where a lot of candidates quietly lose money: their examples don’t match their anchor.
Say you’re targeting $210,000. You’ll sound much stronger if your stories line up with that level of responsibility and impact. For instance, instead of “I led a project migration,” you say: “I led a cross-team migration that cut infra spend by $38,000 per month and reduced incident volume by 27% over two quarters.” Now your ask isn’t just a number; it’s tethered to clear business wins.
Concrete, recent, and comparable is the trio you’re aiming for:
- Concrete: “Improved signup conversion from 22% to 29%, adding ~9,400 users per quarter.” - Recent: Focus on the last 18–24 months, not a win from five years ago. - Comparable: If you’re going for a $210,000 role, highlight work done in similarly complex environments—say, coordinating 5–7 engineers, partnering with product and design, or handling systems that touch $3M+ in annual revenue.
Used this way, each example quietly answers: “Why your high anchor makes sense *here*.”
Expect tools to price you before you speak. Internal comp algorithms already cluster candidates into “bands” based on skills, location and experience; a model might peg you at $168,400 because you clicked “mid-level” and “NYC metro.” As laws like NYC’s pay-transparency rules spread, those internal ranges get tighter—and harder to move after the fact. Your edge will be running your own numbers first, then using them to challenge any auto-generated bracket you’re dropped into.
Treat your anchor as a reusable asset, not a one-off line. Save a version you can adapt for recruiters, hiring managers, and written forms: one tight sentence with your number, one with proof. Example: “For Staff roles in SF, I’m targeting $260K base given my $1.2M ARR impact and current offers at $235K–$245K.” Refine it after every interview.
To go deeper, here are 3 next steps: (1) Open a free valuation calculator like **MicroAcquire’s Startup Valuation Calculator** or **EquityNet’s Business Valuation Tool** and plug in your current annual revenue, growth rate, and margins to generate a concrete “first number” you can use as an anchor in negotiations. (2) Spend 20 minutes with **Chapter 2 (“Valuation: The Outer Limits of the Deal”) of _Venture Deals_ by Brad Feld** or **Chapter 9 (“How Much Is Your Company Worth?”) of _Angel_ by Jason Calacanis** to see how experienced investors think about first numbers, then adjust your number based on those frameworks. (3) Open a shared Google Doc or Notion page and paste in your chosen number, your valuation assumptions (revenue, growth, comparable multiples from **BVP Nasdaq Emerging Cloud Index** or **YCharts industry P/E data**), and two backup numbers (an “ideal” and a “walk-away” valuation) so you have a ready script for the next investor or acquirer conversation.
