How to predict interview questions from a job description

The interview is written before you ever walk in — inside the job description. Here's how to read it the way the interviewer does.

The JD is the question bank

Hiring managers don't invent interview questions from thin air. They write a job description, then build the interview to test whether you can do what it says. That means nearly every question you'll face traces back to one of four places:

1. The must-have requirements. Each one becomes at least two questions: a proof question ("Tell me about a time you led a team through a difficult delivery") and a depth question ("How would you structure the first 90 days?"). Count the requirements, double it — that's your behavioural core.

2. The responsibilities list. These become situational questions. "Own board reporting" becomes "Walk me through how you'd present a missed quarter to the board."

3. The gap between the JD and your CV. Anything they ask for that your CV doesn't clearly show will be probed — career changes, missing industry experience, short stints, employment gaps. These are the questions that decide interviews, and the ones candidates prepare for least.

4. The company's stage and culture lines. "Fast-paced scale-up" reliably produces "Tell me about a time you delivered with ambiguity/no resources."

The manual method (60–90 minutes)

Print the JD. Highlight every requirement, responsibility and culture signal. For each, write the proof question and the depth question an interviewer would ask. Then put your CV next to it and list every mismatch — each is a likely question. Draft answers in first person with real numbers from your career, and say them out loud at least once.

The 3-minute method

This is exactly the cross-reading InterviewHacks automates. Paste your CV and the job description, and you get back the 50 questions you're most likely to face — grouped by theme, including the uncomfortable gap questions — each with a suggested answer built from your own experience, ready to rehearse.

FAQ