Turn a Job Description Into an Interview Plan

Most interview prep looks like this: you Google "common interview questions," skim a list of thirty, rehearse a few generic answers, and walk in hoping for the best. It feels like preparing, but it's really just worrying with extra steps — because generic questions get generic answers, and generic answers don't get job offers.

There's a much better source of truth sitting right in front of you: the job description. The posting is the closest thing you'll ever get to the interviewer's playbook. It tells you what they care about, what problems they're hiring someone to solve, and — if you read it carefully — what they'll almost certainly ask you about. This article teaches you how to turn any posting into a focused prep plan in about an hour.

Read the posting like the interviewer wrote it (they did)

The hiring manager usually writes or heavily edits the job description. That means the posting isn't corporate boilerplate — it's a list of their anxieties. "Own the onboarding experience for new enterprise clients" means someone is currently not owning it, and it's a problem. "Partner cross-functionally with product and engineering" means the last person struggled with that, or the team structure demands it.

Read the posting with a highlighter and mark three things:

The problems. Every responsibility implies a problem someone needs solved. "Reduce time-to-value for new accounts" = new accounts are slow to see value. Write each problem in plain words.
The must-haves. The requirements that repeat or get their own bullets — same technique as resume tailoring. These are the qualifications the interviewer will probe.
The culture clues. Words like "fast-paced," "scrappy," "collaborative," "self-starter" are telling you what the team values and what gets people fired there. Note them — you'll want stories that demonstrate those traits.

Now flip the page and write the interviewer's probable questions next to each item. "Own the onboarding experience" becomes "Tell me about a time you owned a process end to end." "Partner cross-functionally" becomes "Tell me about a disagreement with another team and how you handled it." You're not guessing wildly — you're translating their words into the questions those words always produce.

Build your scorecard (in plain words)

Hiring teams often use an interview scorecard — a simple list of the 4–6 things the hire must be able to do, scored after each interview. You won't see theirs, but you can build your own from the posting, and it focuses your prep enormously.

Take your highlighted posting and distill it to four to six capabilities. For a hypothetical operations manager posting, the scorecard might be:

Can run a small team day-to-day (scheduling, priorities, accountability)
Has improved a broken process with measurable results
Can work with other departments without escalating every conflict
Comfortable with the tools mentioned (the posting names them — learn the basics of any you don't know)
Brings the steadiness this team seems to need (the culture clues)

Write each one as a plain sentence. Then, for each line, attach one story from your real experience that proves it. One story per line, minimum. If you can't find a story for a line, that's your study priority — either dig deeper into your history (volunteer work, side projects, and previous roles all count) or prepare an honest answer about how you'd approach it as a fast learner.

This is "scorecard thinking" without the jargon: figure out what they're grading, and make sure you have proof for every grade.

Gather your stories: the five-story toolkit

You don't need thirty rehearsed answers. You need five solid stories you can adapt on the fly. Nearly every behavioral interview question — the "tell me about a time when..." questions — can be answered by one of these five:

A time you solved a hard problem. The messier the better. What was broken, what did you try, what worked.
A time you led something. Doesn't require a title — leading a project, a migration, a difficult conversation all count.
A time you failed or got it wrong. Interviewers ask this to test honesty and self-awareness. Pick a real one with a real lesson, not a humblebrag.
A time you dealt with a difficult person or disagreement. Every team has friction; they want to know yours doesn't become drama.
A time you learned something fast. Especially valuable for career changers and returners — it directly answers the unspoken question about whether you can ramp up.

For each story, use a simple three-part shape: the situation in one or two sentences, what you specifically did (this is the part people rush — slow down here, the "you" part is what they're scoring), and the outcome, including numbers if you have them. Practice saying each story out loud once — not memorizing a script, just making sure it comes out in under two minutes without rambling. Stories told out loud sound completely different from stories in your head.

Prepare your questions for them

The "do you have any questions for us" moment matters more than people think. Having no questions reads as disinterest; having sharp ones reads as someone who's already thinking like an employee. Prepare four or five, drawn from your posting analysis:

"You mentioned owning the onboarding experience — what's the biggest pain point there right now?" (Shows you read carefully and think in problems, not tasks.)
"What does success look like in the first 90 days?" (Shows you're already planning to deliver.)
"What's the team's biggest challenge this quarter?" (Gives you real information and shows seriousness.)
"What happened with the person who had this role before?" (Gentle, but revealing — asked warmly, it tells you a lot.)
"What do you enjoy most about working here?" (Human, disarming, and people love answering it.)

Never ask about salary, benefits, or time off in a first interview unless they raise it — not because those things don't matter, but because the first conversation is about whether there's a mutual fit on the work itself.

The logistics most people skip

An hour of unglamorous preparation prevents most interview disasters:

Know the format. Phone screen, video call, or in person? How long? Who are you meeting — get names and look up their roles so you're not surprised.
Test your setup. For video interviews: camera at eye level, light on your face not behind you, test your microphone the day before, and have the interviewer's number handy in case the link fails.
Bring your prep sheet. For phone interviews, have your scorecard and stories printed or open — it's not cheating, it's being prepared. For in-person, bring a notebook with your questions written down. Writing them down means you won't blank when the moment comes.
Plan the stories you'll open with. "Tell me about yourself" isn't an invitation to recite your resume — it's a two-minute highlight reel ending at why this role, why now. Prepare it word for word; it's the only answer worth scripting.

The honest truth about interviews

Here's what nobody tells you: interviews are noisy, subjective, and partly luck. You can prepare perfectly and lose to an internal candidate who was always getting the job. That's not a reason to skip preparation — it's the reason preparation has to be efficient. An hour with the job description, a scorecard, five stories, and good questions puts you ahead of most candidates, and it costs you one focused evening.

And when it doesn't work out, do a five-minute debrief: what did they ask that you weren't ready for, what story landed, what would you change. Write it down. Every interview makes the next one better — but only if you capture what you learned before it fades.

The posting told you what they want. Your experience tells you what you've done. The interview plan is just the bridge between the two — built deliberately, the night before, instead of improvised in the hot seat.