What a job description hides — and how to read past it

Every job description is a first move in a negotiation. The hiring organization controls the text, sets the frame, and decides what to reveal. The candidate who reads a posting at face value — matching their credentials to the listed requirements and moving on — is playing by rules that were written to favor the other side. What follows is a field guide to reading US Life Sciences postings more carefully.

Level drift: when the title and the role diverge

Titles in Life Sciences have inflated steadily. A posting labeled 'Senior Scientist' at one organization can correspond to what another calls 'Principal Investigator' or even 'Associate Director.' The title is almost never the most reliable signal of seniority. The more useful signals are buried in the body of the description.

Look first at reporting structure. A role described as reporting to a VP or C-suite officer with no named direct reports is almost certainly individual-contributor territory regardless of what the title says. Conversely, if the description mentions 'leading a team' or 'managing cross-functional stakeholders across regions,' the organization expects someone operating at a higher functional level than the title may suggest. The phrase 'matrixed environment' is common cover for a role that carries accountability without formal authority — worth knowing before you accept an offer framed around a senior title.

Years of experience requirements are a rougher guide than most candidates assume. Requirements like '8+ years' are often aspirational floors set by HR templates rather than real minimum thresholds. The more precise signal is the combination of specific technical demands, the scope of deliverables described, and the budget or program language embedded in the responsibilities section. A posting that mentions 'P&L accountability' or 'IND-enabling studies' or 'BLA submissions' is signaling something about functional depth that a years-of-experience figure cannot capture.

Compensation: what the silence tells you

Across a corpus of 10,000 active US postings, 0% of postings disclose a salary range. That number is not a rounding artifact. It reflects a persistent norm in Life Sciences hiring in which compensation is treated as proprietary information to be revealed, if at all, only after a candidate has invested time in a process. This puts the experienced professional at a structural disadvantage unless they develop independent reference points before engaging.

In the absence of a stated range, the posting itself contains softer signals. The benefit language is one. Descriptions that lead with equity, performance bonus structure, or mention of a long-term incentive plan tend to skew toward mid-to-senior roles where variable compensation is a meaningful share of total package. Descriptions that emphasize health coverage and PTO without equity language tend toward individual-contributor or early-career positions. Neither is a hard rule, but the pattern holds often enough to be useful as a first pass.

Geography is another proxy. A role anchored to the San Francisco Bay Area, San Diego, or the Boston-Cambridge corridor carries different market rates than a nominally equivalent role posted in the Midwest or Southeast, even when titles match. The posting will rarely say this. You have to supply the regional context yourself.

0% of postings disclose a salary range — across 10,000 active US listings. Compensation remains the information asymmetry that favors the employer by design.

Work-mode language is a third signal, and an indirect one. Among postings that state a work mode, 47% of postings that state a work mode are remote, 22% of postings that state a work mode are hybrid, and 31% of postings that state a work mode are on-site — across 1,828 postings with explicit mode language. Roles requiring on-site presence in high-cost markets sometimes carry a modest location premium; remote roles with no geography restriction sometimes compress ranges toward national medians. The posting will almost never make this explicit. But knowing which mode is being offered — and comparing it to what competitors in a given function are offering — helps calibrate the conversation.

Org shape: reading the structure behind the words

Life Sciences organizations post roles at very different stages of internal formation. A Series B biotech posting for a 'Head of Regulatory Affairs' may be describing a department of one. A large pharma posting with identical language may be describing a team of fifteen with two layers of management already in place. Neither posting will say this directly.

The signals are in the verb tense and in what the description treats as already established. If the posting says 'build and lead' rather than 'lead and develop,' it is describing a formative role. If it says 'partner with established commercial and medical affairs functions,' the infrastructure already exists. 'Define strategy' usually means the strategy does not yet exist. 'Execute against established strategy' means it does. These distinctions matter enormously for what the job will actually require in the first twelve months.

Similarly, the list of internal collaborators named in the posting is a map of the org. A description that lists partnerships with Clinical, Regulatory, CMC, and Commercial simultaneously is either describing a very senior generalist role or an organization where those functions are thinly staffed and boundaries are fluid. Either interpretation changes how you would negotiate scope and resources before accepting.

Board composition and investor language occasionally surface in postings from smaller organizations, particularly in the 'about us' section that candidates routinely skip. A company that describes itself as 'backed by' specific top-tier investors, or that names a scientific advisory board in the posting, is providing information about the capital runway and scientific credibility of the program — both of which affect the durability of the role and the resources available to it.

A discipline, not a trick

None of this analysis requires inside information. It requires slowing down, reading the document as a constructed artifact rather than a neutral announcement, and asking what the organization chose to say and what it chose to omit. That discipline does not guarantee better outcomes, but it narrows the information asymmetry that the posting was designed, whether intentionally or not, to create.

The member who arrives at a first conversation already having mapped the likely level, estimated the comp band from external reference points, and identified the org-shape questions worth asking is not at a disadvantage. The posting was the opening move. How you prepare for the conversation is yours.