How to Prepare for a Job Interview Using the Job Description

Most interview advice tells you to prepare for generic questions. "Tell me about yourself." "What are your strengths?" "Where do you see yourself in five years?" Every candidate practises these. The problem is that the interviews that actually decide whether you get the job are not about generic questions — they are about specific competencies, specific experience, and your fit for this specific role.

This guide covers how to prepare for a job interview using the actual job description — the approach that gets results.

Why generic interview prep fails

Generic preparation gives you generic answers. And generic answers, no matter how polished, signal to the interviewer that you have not thought deeply about this particular role. The candidates who get hired are usually the ones who demonstrate, through specific and relevant answers, that they understand what this job requires and have done exactly that kind of work before.

The vast majority of interview questions for any role are predictable from the job description. A job description tells you:

• The key competencies the role requires
• The technical skills they will test
• The seniority and leadership expectations
• The potential gaps between your background and what they want
• The culture signals that will inform "culture fit" questions

If you know what to look for, you can predict 80% of the questions you will be asked — and prepare for them specifically.

Step 1 — Extract the competencies from the job description

Read the job description and identify the core competencies it is testing for. Look for:

• Technical skills — specific tools, languages, methodologies
• Behavioural competencies — "stakeholder management," "cross-functional collaboration," "leadership under pressure"
• Experience requirements — "proven track record of X," "experience managing teams of Y size"
• Problem types — what kind of problems will this person solve day to day?

Each of these competencies maps to likely interview questions. "Stakeholder management" becomes "Tell me about a time you managed a difficult stakeholder." "Leading cross-functional teams" becomes "Describe a situation where you had to align multiple teams with competing priorities."

Step 2 — Identify your likely gap areas

Compare the job description's requirements to your resume honestly. The areas where your background is weakest relative to the job description are where the interviewer is most likely to probe. Prepare specifically for those questions.

If the job requires five years of experience and you have three, expect a question about that gap. Prepare a confident, honest answer that acknowledges it while emphasising the quality and pace of your experience.

If the job requires a specific technical skill you have limited experience with, prepare to demonstrate your adjacent competence and your ability to learn quickly — with a specific example of how you have done this in the past.

Step 3 — Prepare STAR answers for each competency

The STAR framework (Situation, Task, Action, Result) is the most reliable structure for answering competency-based and behavioural interview questions. It gives your answers a clear narrative structure that is easy for the interviewer to follow and assess.

• Situation — Briefly describe the context. One or two sentences. Set the scene without over-explaining.
• Task — What was your specific responsibility in this situation? What problem were you solving?
• Action — What did you specifically do? This is the most important part. Be specific about your role and decisions. Use "I" not "we."
• Result — What was the outcome? Quantify where possible. What changed as a result of your actions?

The questions most candidates get wrong

Competency-based questions

These are the most common format for structured interviews and the questions most candidates underperform on. They follow the pattern: "Tell me about a time when..." or "Give me an example of a situation where..."

The mistake most candidates make is answering in vague generalities. "I generally approach conflicts by trying to find common ground" is not an answer to a competency question. "Tell me about a time you managed a conflict" requires a specific, real example structured as a STAR answer.

Technical questions

For technical roles, expect questions that test your actual ability with the tools and methods in the job description. Prepare by reviewing the specific technical skills listed in the job description and being ready to discuss specific projects where you applied them.

Motivation questions

"Why do you want this role?" and "Why this company?" are among the most important questions in any interview — and most candidates give weak answers. Strong answers are specific, honest, and connected to something real about the role or company.

How long before the interview should you start preparing?

Start as soon as you receive the interview invitation. Ideal preparation time is 3–5 days — enough to prepare your STAR stories, practise them out loud, and refine your answers based on what sounds compelling versus what sounds rehearsed.

Practising out loud is essential. Answers that sound logical when you think through them often sound awkward when spoken. Record yourself or practise with someone else. The goal is confident delivery, not memorised scripts.