How to Read a Job Description Before Your Interview

In this chapter

Most interviews are not invented in the room.

They are a live check of a document someone already wrote: the posting. The hiring manager used it to get headcount. The recruiter used it to screen. The panel skimmed it the morning of. When they ask a question, they are usually pressing a line they already committed to — a skill, a responsibility, a level of ownership — not a surprise topic from a textbook.
That is why “I studied interview questions for this title” still fails.

Titles are marketing. Bullets are the work. If you prepare the title, you prepare a different job. If you prepare the bullets, you prepare this interview.
Reading a job description well is not highlighting every noun.

It is building a map of what will be tested, in this employer’s language, before you memorize anything.

A posting is two documents glued together.

One is a hiring spec: what the team needs done, at what seniority, under which constraints. The other is a recruiting ad: mission, perks, “fast-paced environment,” stacked tools, a salary band if you are lucky. Your job is to split them.
Keep: verbs that describe owned work (“own,” “run,” “decide,” “ship,” “close,” “diagnose”).

Skills that appear more than once. Constraints (on-call, travel, shift, licensed practice, quota, stakeholder level). Signals of round type (take-home, case, board presentation, live problem, panel).
Park for later: culture slogans, benefit lists, “nice to have” tools listed once at the bottom, and any paragraph that could sit on any company’s careers page without changing a word.

Those lines rarely become questions. The repeated, specific work does.
Salary range and level belong to a later chapter.

Here, use them only as a seniority clue: intern, individual contributor, manager, director. Seniority changes how they will ask, not only what.

You do not need a spreadsheet.

You need one pass you can finish before you start drilling answers.
Pass 1 — Frame.

Title, team, location or remote rules, and anything that limits the work (license, language, shift, travel, security clearance). Write one sentence: “This role exists to ___ for ___.” If you cannot finish that sentence from the posting, the posting is vague — and the interview will be too, which means they will fall back on generic probes. You still need a sentence. Infer it from the first five bullets.
Pass 2 — Verbs.

Circle every verb that implies you will be asked to do this in the room. “Experience with Python” is a noun pile. “Build and operate data pipelines that…” is a verb. Verbs become walk-throughs: “Walk me through how you would…”
Pass 3 — Seniority.

Who do you talk to? What do you own vs support? How much ambiguity is named (“define the roadmap,” “follow the playbook”)? A senior posting that still lists every tool is often a junior spec with a senior title. Believe the owned outcomes more than the title.
Pass 4 — Round hypothesis.

Guess the likely shape: screen (can you talk about the work), craft (can you do a slice of it), judgment (can you choose under constraint). Mark it as a hypothesis, not a fact. You will confirm from the calendar invite. Do not prep a coding round for a posting that never mentions implementation.

Once is a maybe.

Three times is the exam. If “stakeholder,” “forecast,” or “incident” shows up in the title, the summary, and two bullets, that is not flavor text. That is what they will press until they believe you.
Separate required from familiar with.

Required skills become “show me.” Familiar-with skills become “have you seen.” Interviewers still ask both - they weight them differently. Do not spend equal hours on a tool mentioned once under “plus.”
Then read for implied work that never got its own bullet.

Who gets the 2 a.m. call. Which vendor you will fight. Which executive will sit in the room. “Cross-functional” often means you will be asked about conflict. “Highly regulated” often means a process or evidence question. Write those implications down in the employer’s nouns, not yours.
Your output from this chapter is not a highlighted PDF.

It is a short list: eight to twelve atoms — one skill, one responsibility, or one constraint each — in the posting’s words. That list is the syllabus. Everything else is optional until those atoms are speakable.

A responsibility becomes a walk-through: “Take me through how you would run X here.” A skill becomes a tradeoff: “When would you not use Y?” A soft-skill line (“influence without authority,” “patient communication”) becomes a behavioral: they will ask for a time you had to do that work, not a definition of the phrase.
A constraint becomes a judgment question.

On-call, quota, board pack, infection control, code review SLA — whatever the posting named as a limit is a gift. Limits make questions specific. Specific questions are easier to answer than “tell me about yourself.”
You do not need a bank of sample questions yet.

You need to hear the posting as a set of asks. If you cannot turn a bullet into a plausible question in one sentence, you have not understood the bullet. Rewrite the atom until you can.

Prepping the brand instead of the bullets.

Famous companies still interview the posting in front of them. Prestige does not replace the spec.
Studying every tool equally.

A stack list is a menu, not a weighting. The work verbs tell you the weight.
Treating “nice to have” as the exam because it looks harder.

Difficulty is not the same as likelihood. Likelihood lives in repetition and ownership.
Pasting the JD into a chatbot and accepting the first twenty questions.

That can be a draft. It is not a reading. If you skip the annotation, you cannot tell a good generated question from a paraphrase of the about-the-company paragraph.
Waiting to “feel ready” before you mark the atoms.

Readiness is the list, then practice. Not the reverse.

You are done with this chapter when you can hold one page — paper or notes — that a stranger could use to quiz you.

Eight to twelve atoms. Each in the employer’s language. Each tagged roughly as craft, judgment, or story. No paragraphs. No tool dump.
That page is what you practice from.

If you do not have a posting at all — referral, internal move, a screen with no brief — the next chapter is how to build a proxy spec. If you do have a posting, skip ahead to the opener: “tell me about yourself,” then the stories that have to fit this syllabus.
When you later generate questions from this same posting, you will recognize them.

Recognition is the point of reading first. If a question does not map to an atom you marked, either you missed a bullet — or the question is generic. Either way, you now have a way to tell.

Generate questions from that job description — free preview, $2 for the full kit. No account. Paste a job description.