← Back to all posts
Watercolor: East Asian woman pointing at a compensation chart with a confident half-smile in golden afternoon sun
·6 min read·By George Brewer

Salary Bands Explained: Negotiating With Comp Data

Employers build salary bands with real room inside them. Here's how to read that structure, find public comp benchmarks, and anchor your ask where the band actually flexes.

Employers rarely post the top of a band, which means the number you see in a job posting is almost never the ceiling.

Employers build salary bands before they post a job. Those bands have a floor, a midpoint, and a ceiling, and each of those numbers means something different depending on where you are in the hiring process. Knowing the structure doesn't guarantee a higher offer, but it tells you where to push and where you're wasting breath.

How Salary Bands Actually Work

A salary band is an internal range tied to a job level, sometimes called a grade or a pay grade. HR teams set it annually using market survey data from compensation consultancies. The midpoint is typically what the company considers "fully performing" for that level.

New hires almost always land between the floor and the midpoint. That gap between where you'd start and the midpoint is called "compa-ratio headroom," and it's real negotiating space. The upper half of a band is generally reserved for internal promotions and long-tenure employees, though exceptions happen.

Bands also overlap between levels. A Senior Engineer band might start below where a Staff Engineer band ends. That overlap is why two people with the same title can have meaningfully different salaries without either being wrong.

Where to Find Real Comp Data

Public comp data has improved substantially. A few sources are genuinely useful, and a few are noise dressed up as data.

  • Levels.fyi: best for software engineering, product, and design at larger tech companies. Self-reported but high volume and reasonably clean.
  • Glassdoor salary data: broader coverage across industries, but take individual data points with skepticism. Aggregated ranges are more reliable than single entries.
  • LinkedIn Salary Insights: useful for cross-industry benchmarks, especially at the mid-career level. Requires some reciprocal disclosure.
  • H-1B salary disclosure data: publicly filed with the Department of Labor. Covers actual offered salaries at specific employers for specific job titles. Searchable and underused.
  • State pay transparency filings: Colorado, California, New York, and Washington now require salary ranges on postings. Even if you're not applying in those states, the same employer's posting there tells you their band for that role.
  • JobClarity salary intelligence: current distributions by role and location, updated from live posting data rather than annual BLS aggregates.

Cross-reference at least two sources before you anchor on a number. One data point is a guess. Two overlapping data points are a position.

Reading the Posted Range (When There Is One)

Pay transparency laws have pushed more employers to post ranges, but most posted ranges are wide on purpose. A range of $90,000 to $140,000 tells you the band exists. It doesn't tell you where they expect to hire.

A useful rule of thumb: the bottom third of a posted range is for candidates who meet minimum qualifications. The middle third is the target for a solid, experienced hire. The top third is for someone who could have reasonably been leveled up. Figure out which third describes your candidacy before you walk into the conversation.

The posted range is the band's public face. The number they're actually planning to offer is usually somewhere in the lower half of it, unless you give them a reason to move.

George Brewer, JobClarity

Anchoring: Where Candidates Leave Money

Range anchoring is the single most concrete lever in a salary negotiation. Whoever names a number first sets the reference point for everything that follows. If the employer anchors low, every counter feels like a win for them even when it isn't for you.

When you're asked for your salary expectations, give a range with your target at the bottom, not the middle. If you want $130,000, say $130,000 to $145,000. This is not a trick. It reflects the reality that you'd accept anywhere in that range, and it keeps the negotiation from collapsing toward a number you'd find disappointing.

Cite your sources when you anchor. "Based on H-1B filings for this role at companies of similar size and the ranges I'm seeing in current postings, I'm targeting $130,000 to $145,000" is harder to push back on than a number with no backing. It signals you've done the work.

Where Bands Are Fixed and Where They Flex

Some parts of a comp package have genuine flexibility. Base salary within a band, signing bonus, equity refresh grants, remote work stipends, and start date are all commonly negotiable. Others are much harder to move: benefits tiers, 401(k) match percentages, and PTO accrual schedules are usually set at the company level, not the hiring manager level.

The band ceiling is also real. If a company has a strict leveling structure, they often can't pay you above the band for the posted level without re-leveling the role, which requires additional approvals. When a recruiter says "that's the top of our range for this level," they may be telling the truth. The right response is to ask whether the role could be evaluated at the next level up, not to push harder on the same number.

  1. Confirm the level the role is posted at before you negotiate base salary.
  2. Ask directly whether there's flexibility on signing bonus if base is capped.
  3. Get the full offer in writing before you evaluate it. Verbal offers omit things.
  4. Counter once with your anchored range and specific data. A second counter is fine if the gap is meaningful. A third starts to cost you goodwill.
  5. If the offer is below your floor, say so plainly and ask what it would take to bridge it. That's a cleaner move than a series of small counters.

Using JobClarity's Salary Intelligence

JobClarity's Market feature pulls salary distributions by role and location from live posting data, updated continuously rather than on an annual BLS cycle. You can see what employers are actually posting for a specific O*NET-aligned role in your metro area right now, not what they were posting fourteen months ago.

Pair that with the MyCareer suite to see where your current skills place you relative to the full distribution for a role. If you're at the 75th percentile of skills for a posting, you have a defensible argument for targeting the upper portion of the band. The data gives you something concrete to point to in the room.

Comments