Habit, Not Hack: Reading The Actual Job Description (Mentor)

The most useful career advice you can give a trainee before an interview isn't about their slides. It's about whether they've actually read the job description.

Dr. Patel had written plenty of job postings.

He knew how they were made — by committees with competing priorities, shaped by HR requirements, refined through rounds of compromise until the final document was a negotiated product rather than a precise specification. He knew their limitations. He also knew something trainees rarely understood: that despite all of that, what ended up in a job description was there deliberately, and what ended up emphasized was what would actually be evaluated.

When trainees came to him for job application advice, they asked about CVs. About slides. About how to talk about a gap in their publication record or what to say when the panel asked about weaknesses. Occasionally they asked about references.

Almost nobody asked about the job description itself.

What He Started Doing

Dr. Patel started every job preparation conversation the same way.

"Read it out loud."

Not silently, not to themselves later — out loud, in the room, while he listened. He had found that reading something aloud produced a different quality of attention than reading it silently. Things that had been invisible in a quick scan became audible. Patterns emerged. The structure of the document became apparent rather than assumed.

What trainees noticed, almost every time, surprised them.

Repetition — the same capability or quality mentioned in multiple sections of the description, sometimes in different language but clearly referring to the same underlying need. Specific verbs that had been skimmed past but carried precise meaning: coordinate, translate, execute, align, communicate, manage — each one a statement about what the role actually did rather than what it was called. Entire sections that had nothing to do with bench science — about stakeholder communication, about cross-functional collaboration, about working within regulatory or commercial constraints — that trainees had registered as background noise and filed away as irrelevant.

They weren't irrelevant. In many cases, they were the point.

What He Taught Them to Look For

Dr. Patel had developed a simple framework for decoding a job description, and he walked trainees through it directly rather than describing it abstractly.

What's listed first? In almost every job description, the most important requirements appear early. Not the legal boilerplate, not the standard qualifications everyone applying will have, but the specific capabilities that distinguish the role from a generic version of itself. The first paragraph of the responsibilities section is rarely accidental.

What's described in detail? Brief mentions are table stakes — the baseline requirements that any qualified candidate will meet. The requirements that receive a sentence or a paragraph of explanation are the ones the hiring team cared enough to elaborate on. That elaboration tells you what they are actually trying to assess.

What's mentioned but not emphasized? Some requirements are present because they have to be — for HR compliance, for institutional consistency, for completeness. They're real requirements but not differentiating ones. Learning to identify these prevents trainees from over-investing in demonstrating things that aren't going to determine the outcome.

What's missing? Sometimes the most informative thing about a job description is what it doesn't mention. A research role that says nothing about publications is telling you something about how the organization measures success. A role that doesn't mention independence is telling you something about how the work is structured. The absences are data.

The Harder Conversation

Dr. Patel also taught trainees to use job descriptions to make a different kind of decision — one that most career preparation advice never reaches.

When a trainee's experience mapped well to a description, the path forward was clear: build the preparation around the alignment, make it explicit in the application and the interview, tell the story that answers the role's actual question.

But sometimes the mapping was poor. The role was emphasizing capabilities the trainee hadn't developed, or prioritizing work the trainee didn't find compelling, or describing a day-to-day reality that didn't match what the trainee was actually looking for. In those cases, Dr. Patel didn't encourage enthusiasm as a substitute for fit.

"If most of this doesn't match your actual strengths or what you want to be doing," he said, "that's not a failure. It's information. Information you now have before the application instead of after the rejection."

This was not advice to apply only to roles that were perfect on paper. It was advice to be honest about the gap between what a role required and what a candidate offered — and to make a deliberate choice about whether to close that gap (through genuine reframing of adjacent experience) or redirect effort toward roles where the alignment was real.

The trainees who learned to make this call early — who developed the habit of reading a description carefully enough to know whether the fit was genuine — sent fewer applications and had more interviews. They also had fewer experiences of getting through a process only to discover, in the debrief, that the role wasn't actually what they had been preparing for.

The Habit: Reading The Job Description As A Preparation Tool

The preparation conversations Dr. Patel had with trainees changed shape after he introduced this practice.

Before, they had been largely about the trainee's story — how to tell it, how to make it compelling, how to handle the gaps and the weaknesses. That conversation still happened. But it happened second, after a different conversation had established the frame: what is this specific role asking for, and which parts of the trainee's story answer that question?

The CV review became a mapping exercise. Not "is this CV strong?" but "does this CV surface the experiences most relevant to this role, in the language the description uses?" The interview preparation became a translation exercise. Not "what are my best stories?" but "which of my stories answer the questions this description predicts?"

Applications became sharper because they were directed at real targets. Interviews became more focused because the preparation had been built around the actual questions rather than generic versions of them. Rejections, when they came, were more interpretable — and less demoralizing — because the trainee could assess with some precision whether the decision had been about fit or about something else.

What This Habit Asks of You

One structural change to how you run job preparation conversations, and two specific practices within them.

Start with the description, not the CV. Before you discuss how to present a trainee's experience, establish what the role is actually asking for. Read through the description together. Ask the trainee what they notice when they read it carefully. Ask them what the role is hired to do — not what it's called, but what problem it solves and how. This conversation takes fifteen minutes and reframes every preparation conversation that follows it.

Walk through the mapping explicitly. Take the three or four most prominent requirements in the description and work through them together: what specific experience does the trainee have that demonstrates this capability? What's the most relevant story? How would they tell it in language that connects to what the description is asking? This exercise both identifies the genuine alignments and surfaces the gaps — which is information the trainee needs before the interview, not during it.

Normalize the decision not to apply. When the mapping reveals that a role is a poor fit — when the gap between what the role requires and what the trainee offers is large enough that no reframing will close it honestly — say so directly. Not as a discouragement from applying broadly, but as a reallocation of effort toward roles where the fit is real. The trainee who applies to fewer roles with genuine alignment will have a better experience than the trainee who applies broadly and encounters the same strong candidate, not the right fit feedback repeatedly without understanding why.

A Note on What This Isn't

This is not a habit about teaching trainees to only apply to roles where every requirement is already met. Job descriptions are aspirational documents — they describe the ideal candidate, and most successful hires meet most but not all of the listed requirements. Gaps are normal and often bridgeable through honest reframing of adjacent experience.

The habit is about reading the description accurately enough to know which gaps are bridgeable and which aren't — and about making that assessment deliberately rather than by optimism. A trainee who reads a description carefully and decides that two requirements can be addressed through reframing and one is a genuine gap is making an informed decision. A trainee who skims the description and applies on the basis of the title and the scientific domain is hoping for the best.

Hope is not a preparation strategy.

Success in a job search isn't about being impressive in general. Every strong candidate is impressive in general. It's about being relevant on purpose — demonstrating, specifically and clearly, that your experience addresses the problem this role is hired to solve.

That starts with reading the document that tells you what the problem is.

That's not a hack. That's a habit.

✨ Explore the Career Navigation & Decision-Making tools that walk candidates through assessing the job description process — from identifying the key requirements to mapping experience to making the alignment explicit before the interview.