Negotiating Your Salary With Market Data (Not Vibes)

How to build a defensible salary number from advertised ranges, present it without friction, and handle the counter-offer.

By the TechJobsData Team 9 min read

Most salary negotiation advice is theater direction: sit up straight, pause after numbers, mirror their phrasing. Fine. But posture doesn't move offers; evidence does. The negotiator with better market data walks in with a number they can defend and walks out with more of it. This guide is about building that number from advertised listings — the market's own public statements — and using it without turning the conversation adversarial.

Why advertised ranges are your best raw material

Self-reported salary surveys skew two ways at once: people who feel underpaid respond more, and people round up. Advertised ranges have the opposite virtue — they're what an employer was willing to put a company name next to, in public, this month. They have their own bias (posted ranges lowball the top for negotiation room, and only about a fifth of listings publish numbers at all), but it's a consistent bias, which makes ranges excellent for comparison even when a single one shouldn't be taken literally.

Build your number in an hour

  1. Collect a comparison set. On the job board, search your role and stack, filter to your seniority and work model, and sort by highest salary. You want 10–15 listings with published ranges that a reasonable person would call your job. Discard fantasy outliers in both directions.
  2. Normalize before comparing. Annualize everything, convert to one currency (our listings show a USD equivalent for non-USD ranges), and separate remote-anywhere, remote-regional and on-site listings — those are three different markets, as our remote-work guide explains. Mixing them is how people arrive at numbers that are simultaneously too high for their city and too low for their skills.
  3. Find your band, then your point. The middle of your comparison set's ranges is the market band. Where you sit inside it depends on scarcity: if your particular cluster of skills appears in many listings but few candidates have it deep (the demand-data guide covers reading that), aim upper third. Write the number down with its evidence. A number with receipts survives pressure; a vibe does not.
  4. Check it against the seniority averages on the insights page as a sanity pass — averages blend regions and company sizes, so treat them as guardrails, not gospel.

Deploying the number

Data changes what you say less than it changes how immovably you can say it. A few scripts that work because of the homework behind them:

  • When asked for expectations early: "Based on current advertised ranges for comparable roles — same stack, same level, same remote setup — I'm targeting the band around X." You've reframed the question from personal hope to public market, which is much harder to argue with politely.
  • When the offer lands below your band: don't counter with outrage; counter with the comparison set. "The offers being advertised for this profile are running X to Y — help me understand how you're leveling this role." Sometimes the answer is genuine (smaller company, real equity, lighter on-call) and worth hearing. Sometimes it's anchoring, and naming the band ends it.
  • When they can't move the base: the same data works on the other levers. If the market band says you're conceding €10k of base, that's the size of the signing bonus, extra vacation days, or review-in-six-months clause you're asking to offset it.

The mistakes that undo the homework

  • Quoting one listing. A single range is an anecdote and invites a rebuttal about why that company is different. Bands built from a dozen listings don't have that weakness.
  • Comparing across markets. A remote-anywhere range from a US startup is not evidence in a Munich on-site negotiation. Your comparison set must share the constraint that binds you.
  • Negotiating total comp against base. Advertised ranges are almost always base salary — equity and bonus live elsewhere. Compare like with like or you'll cheerfully accept a pay cut dressed as a raise.
  • Letting the data expire. Ranges from last year's screenshots are last year's market. Rebuild the comparison set the week you negotiate; it costs an hour and it's the hour the entire conversation rests on.

The quiet part

The largest salary increases don't come from negotiating harder; they come from changing which market you're in — the skill cluster, the seniority you can evidence, the geography of the companies you apply to. Negotiation captures the value of a position; the position itself is set by everything upstream. Which is to say: the same hour of market data that wins you a few percent in a negotiation is worth far more when you spend it deciding where to aim in the first place.

The statistics referenced in this guide come from our own continuously updated dataset. See the live numbers on the Market Insights page, or put them to work on the job board.