Blog / Reading a Salary Range in 2026 (and Negotiating It)
Job Search Tips

Reading a Salary Range in 2026 (and Negotiating It)

Two people shaking hands across a desk in front of a laptop

Photo by Radission US on Unsplash

Short answer:pay-transparency laws now require a posted range in roughly a dozen states plus D.C., with state-specific effective dates through 2026 and 2027 — but a posted range is a legal minimum, not a promise of where you'll land in it. A wide range is genuinely negotiable, both in where you fall within it and in the total compensation package around it, and the scripts below are for having that conversation directly rather than hoping the number improves on its own.

What pay-transparency laws actually require

The legal landscape shifted substantially through 2025 and into 2026, and it's worth knowing what your state actually requires before you assume a posting is or isn't obligated to show you a number.

StateEffectiveEmployee threshold
CaliforniaJan 1, 202615+
ColoradoCurrent1+
ConnecticutCurrentAll
IllinoisCurrent15+
MarylandOct 1, 2024Covered postings
MassachusettsCurrent25+
MinnesotaJan 202530+
NevadaCurrentAll
New JerseyCurrent10+
New YorkCurrent4+
Rhode IslandCurrent (written-notice req. from Jan 1, 2026)All
VermontCurrent5+
WashingtonCurrent15+
Washington, D.C.June 30, 20241+
DelawareSept 26, 202726+

Most of these apply to remote postings too if the role could be performed from that state, which is why a remote listing from a company headquartered elsewhere often still shows a range — the employer is complying with the strictest law among every state the role could plausibly be filled from, not just its home state.

What these laws generally don't require: a promise that the range reflects one specific, narrow level, or that every candidate within qualifications lands at the same point in it. Most statutes require disclosure of the range the employer "reasonably" or "in good faith" expects to pay — language with real room for a wide, multi-level band to still technically comply.

Why ranges are still artificially wide

A posting showing $70,000–$140,000 for one title usually isn't generosity — it's one of two common patterns. First, the range may cover multiple actual levels (a junior through senior version of the same title) collapsed into a single posted band, either because the company hasn't decided which level it's hiring for yet, or because it wants flexibility to hire at whatever level the strongest applicant turns out to be. Second, the range may have been set early — to satisfy the legal posting requirement before the req was finalized — with the real, narrower budget only confirmed once a specific candidate is further along. Neither pattern is illegal under most current laws, since "reasonably expected" leaves room for a wide band; it does mean the posted number alone tells you less than it looks like it does.

The practical response is to treat a wide range as a question to ask early, not a number to accept at face value. Asking a recruiter directly, in a first conversation, whether the role is being leveled at the bottom, middle, or top of the posted band — and what specifically distinguishes those levels — gets you real information before you've invested in the rest of the process. Most recruiters can answer this reasonably specifically even early on, since the leveling framework typically exists internally even when the posting itself doesn't reflect it. A recruiter who can't or won't answer at all is itself a data point, similar in spirit to the compliance-posting signals covered elsewhere in this series — not disqualifying on its own, but worth noting.

Level-mapping across companies

The same job title means different things at different companies, which is part of why ranges look inconsistent across postings for what seems like the same role. A "Senior" title at one company can map to a mid-level role at another with a more level-inflated naming convention, and the posted range usually reflects the company's actual internal leveling more than the title does. Two practical checks: compare the range against the years-of-experience and scope language in the posting itself, not just the title, and where possible, compare a specific company's range for a title against what current or former employees report for that same internal level — the title alone is a weak signal on its own.

Total compensation, not just the base number

Base salary is the number everyone anchors on, but it's one component of a larger package, and the parts around it are often more negotiable than the base itself. Bonus (individual or company-performance tied, varying frequency), equity (RSUs or options — worth noting the value is genuinely uncertain until it vests, not a guaranteed number), and benefits (health insurance, retirement contributions, and similar) commonly add up to a third or more of total compensation on top of base. A lower base salary with meaningfully better equity or a signing bonus can be a stronger total offer than a marginally higher base with neither — evaluate the whole package, not the headline number in isolation.

ComponentTypical negotiabilityWhat to ask
Base salaryModerate — often the most constrained by internal bandingWhere in the posted range does this offer sit, and why
Signing bonusOften the most flexible lever, one-time budgetIs there room for a signing bonus to bridge a base-salary gap
Annual/performance bonusStructure usually fixed, target % sometimes negotiableWhat's the target bonus percentage, and is it guaranteed in year one
EquityVaries widely by company stageVesting schedule, and current valuation basis if available
Benefits/start date/PTOOften has quiet flexibility even at fixed companiesDirectly, since these are rarely volunteered unprompted

The signing bonus row is worth calling out specifically: it's frequently the fastest lever a company can pull, because it's a one-time budget line rather than a change to an ongoing salary band that has to be justified against internal pay equity for years afterward. If a recruiter says base salary genuinely can't move, asking about a signing bonus before assuming the conversation is over is often worth the extra question.

Three negotiation scripts

Scenario 1: The offer came in below the posted range

"Thanks so much for the offer — I'm genuinely excited about the role. I noticed the posted range was [$X–$Y], and this offer comes in below that. Given [specific relevant experience/skill], I'd love to understand what it would take to get closer to the top of that range."

This is direct without being confrontational — it references the company's own disclosed number rather than an external claim, and asks a specific question rather than a vague request for "more."

Scenario 2: The offer is in-range, but you want more

"This is a strong offer and I'm excited to move forward. Based on [specific market data or competing consideration], I was hoping we could look at [$X] for the base, or discuss the equity/bonus structure if base has less flexibility. Is there room to work with there?"

Naming a specific number, and explicitly offering the alternative of negotiating a different component if base is fixed, keeps the conversation productive instead of a flat yes/no on one number.

Scenario 3: You're comparing multiple offers

"I want to be transparent — I have another offer in process, and I'd genuinely prefer to join this team. Is there flexibility on [specific component] that would make this the clear choice for me?"

Stating a genuine preference, not just leverage, tends to land better than an implied ultimatum — and it's honest, which matters both ethically and practically since overstating a competing offer that doesn't exist is a real credibility risk if it comes up again later in the relationship.

Where this connects to the rest of your search

None of this negotiation matters if you're starting from a role that was never a realistic match in the first place — the same staleness and compliance-posting signals that flag a ghost job are also worth checking before you invest negotiation energy into an offer that was never going to move. And once you do have a real offer in hand, CareerFlint's job searchshows salary information directly alongside each listing where available, so you're walking into that first conversation with a number already in mind, not discovering the range for the first time in the negotiation itself.

Frequently asked questions

Which states require salary ranges in job postings?

As of 2026, roughly a dozen states plus Washington D.C. require a salary range directly in job postings, including California (effective January 1, 2026), Colorado, Connecticut, Illinois, Massachusetts, Minnesota, New Jersey, New York, and Washington, among others — each with its own employee-count threshold and specific requirements. A broader group of states require pay disclosure on request or before an offer rather than in the posting itself.

Why is the salary range on a job posting so wide?

Often because the range covers multiple levels or seniority bands under one posted title, or because it was set to satisfy a legal minimum before final budget and leveling were confirmed — not necessarily because the actual role has that much genuine flexibility. A $60,000 spread usually means you need to find out where in the range your specific experience actually lands.

Should I negotiate salary if the range is already posted?

Yes — a posted range is a starting disclosure, not a final offer. Where you land within a wide range is still genuinely negotiable, and total compensation (bonus, equity, benefits) is negotiable even when base salary has less room to move.

What should I say if a job offer comes in below the posted range?

Ask directly and specifically: reference the posted range, state your understanding of the role's scope, and ask what would move the offer closer to the top of that range — rather than accepting silently or making a vague, unspecific counter-request.