What pay transparency laws actually changed in US Life Sciences postings
More states now mandate salary disclosure, yet a posted range tells a candidate less than it appears to. Here is what the data show — and what to do with an imperfect signal.
Over the past three 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 any employer 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 understand how the mandate has landed in Life Sciences specifically, the MeridianRoles research desk examined active US postings in our corpus over a recent trailing period — 6,852 postings in total. The finding was stark: 0% of postings disclose a usable salary range. Not a rounding anomaly. Across nearly seven thousand live US Life Sciences postings, a clean, machine-readable compensation band that a candidate could meaningfully act on was absent in every single case.
Why the number is zero
That result deserves unpacking, because it is not evidence that employers are uniformly breaking the law. It reflects something more structural: the gap between legal compliance and candidate utility.
Employers have found several routes to technical compliance that fall short of genuine transparency. A common pattern is the placeholder band — a range so wide it collapses into noise. A posting that lists a band spanning more than half the potential market rate for a role satisfies most statutory definitions while communicating almost nothing actionable. Other postings bury a range in unstructured text in ways that are difficult to extract systematically. Some multistate employers post a single national version of a role that omits the range, then rely on state-specific variants that never propagate to aggregator feeds. A smaller share simply omit the range and accept the compliance risk, particularly for roles that are hard to fill and where they believe the candidate will engage regardless.
The result is that a candidate searching for a Principal Scientist role, a VP of Clinical Operations posting, or a Director of Regulatory Affairs may encounter dozens of listings where the compensation field is either absent, a token gesture, or genuinely uninformative. The legislation moved the floor; it did not yet move the ceiling of transparency.
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 489 postings in our corpus that state a work mode, 61% describe the role as remote and 27% as hybrid. When the majority of stated-mode postings are untethered from a single geography, the question of which state's law governs the range disclosure becomes genuinely ambiguous, and employers are handling it inconsistently.
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, treat the disclosed 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.
Second, 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.
Third, 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.
The on-site share among postings that state a work mode is 12%, with hybrid at 27%. 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.