What pay transparency laws actually changed in US Life Sciences postings

In recent years, a wave of state-level pay transparency legislation, led by Colorado, New York, California, and Washington, has pushed salary disclosure from a voluntary differentiator into a legal requirement for most employers posting a role in those jurisdictions. The stated goal was straightforward: give candidates enough information to self-screen, reduce wage gaps, and shift negotiating leverage toward applicants. The downstream effects have been more complicated.

To see how that has landed in Life Sciences, the MeridianRoles research desk looked at active US postings in our corpus over the trailing quarter. One caution comes first. Many of the pay figures shown beside a posting on a job site are not the employer's: they are the site's own estimate. So we counted only the postings where our data can tell the two apart. Across 8,416 such postings, 36% of postings carry an employer-advertised salary. Most of the rest show only an estimate.

Why most postings still carry no employer figure

That result deserves unpacking, because it is not evidence that most employers are breaking the law. Our corpus is national, and the mandates are not. A posting for a role in a state with no disclosure rule owes the candidate nothing on pay. The figure also depends on what a job site can read: a range written into the body of a description, rather than into a pay field, may never be picked up as the employer's own.

Where a rule does apply, compliance and usefulness are different things. A range can be so wide that it satisfies the statute while communicating almost nothing actionable. A multistate employer can post one national version of a role without a range and keep the state-specific variants elsewhere. Our data cannot separate these cases, so we do not put a number on any of them. What it does show is the outcome a candidate meets: for most postings, no pay figure that comes from the employer.

The result is that a candidate searching for a Principal Scientist role, a VP of Clinical Operations posting, or a Director of Regulatory Affairs will meet many listings where the compensation field is absent, estimated by someone else, or too wide to use. The legislation moved the floor. It has not made a clear employer figure the norm.

What a disclosed range does and does not tell you

When a usable range does appear, it is worth being precise about what it represents. A posted band is typically the budgeted range for the role as defined at the time the requisition was opened. It is not a ceiling: most employers build headroom above the posted top of band for exceptional candidates. It is not a floor in practice either, because budget revisions, leveling disagreements between hiring manager and HR, and mid-search scope changes are common in Life Sciences, where the difference between a Senior Director and a VP may come down to a single conversation late in the process.

A disclosed range also says nothing about the total compensation architecture. In Life Sciences, the spread between base salary and target total cash, once you layer in annual bonus targets, sign-on provisions, equity participation, and benefits, can be substantial. Two postings showing identical base ranges can represent materially different economic propositions depending on the organization's equity philosophy and the seniority of the role. For any position where variable compensation is a meaningful fraction of total cash, the base range alone is an incomplete proxy.

A posted band is budgeted intent at a point in time, not a ceiling, not a floor, and not the full picture.

Location interacts with ranges in ways that are still settling. Because the transparency mandates are state-specific, a posting that surfaces nationally may have been written to satisfy one state's requirements while the actual hiring location differs. Remote roles complicate this further. Among the 38,115 postings in our corpus that state a work mode, 41% are remote, 26% are hybrid, and 33% are on-site. When a large share of stated-mode postings are not tied to a single geography, the question of which state's law governs the range disclosure becomes genuinely ambiguous.

How to use this as a candidate

The practical implication is that salary ranges, where they exist, are a starting point for calibration rather than a reliable anchor. There are a few ways to build a more grounded picture.

First, check whose number it is. A figure labelled as estimated, or one that appears as a single figure rather than a range, is usually the job site's view of the market, not the employer's budget. Treat it as background, not as an offer.

Second, treat an employer's range as a signal about the role's level, not its precise value. A band that tops out well below your current total compensation is a reasonable filter even if you cannot rely on its precision. A band that overlaps your target range is worth engaging with, but do not assume the number on the posting is the number in the room.

Third, use the presence or absence of a range as soft data about the employer's transparency posture more broadly. Organizations that invest in clear, realistic compensation communication in their postings tend to run more structured and respectful hiring processes overall. This is not a rule, but it is a pattern worth noting.

Fourth, for roles where no range is posted, the most effective move is to state your expectations early and directly, in the first substantive conversation, not the offer stage. In a market where postings have limited disclosure, candidates who surface their range first often find that employers respond in kind. The legislation created a norm even where it did not create universal practice.

For roles requiring physical presence in a high cost-of-labor geography, a posted range may reflect that geography's market. Remote roles drawing on a national candidate pool may post a range calibrated to a lower-cost anchor. Neither is inherently misleading, but they require different interpretive frames.

The transparency laws changed what employers are required to say. They have not yet resolved what that disclosure means for the candidate reading it. Understanding the difference is, at this point, a core research skill for anyone navigating a US Life Sciences job search in 2026.