A job description is not a wish list. It is the document the interviewers wrote their questions from, and the hiring manager will probably score you against it. Reading it well is the cheapest preparation you can do, and most candidates skim it once and move on.
Separate the must-haves from the nice-to-haves
Look at the wording. Phrases such as "required", "essential", "must have", "minimum" and "proven experience of" usually mark a must-have. Phrases such as "desirable", "preferred", "ideally" and "a plus" usually mark a nice-to-have. A minimum number of years, a named qualification or a named tool in the first list tends to be a hard requirement.
There is also a clue in the order and the repetition. A skill that appears in the summary, the responsibilities and the requirements is the heart of the job. Something mentioned once, at the end, is probably not.
Read the responsibilities as questions
Each responsibility is a question in disguise. "Manage relationships with key suppliers" will produce "tell me about a time you handled a difficult supplier". "Produce monthly reports for senior management" will produce "how do you make sure a report is accurate when the deadline is close". Go through the list and, for each one, write the question you would ask if you were the interviewer.
Build an evidence table
For each must-have, find an example from your own experience. A simple table keeps you honest:
| Requirement | My example | Proof |
|---|---|---|
| Managing a budget | Ran the events budget for a student society | Kept spending within the limit, with a monthly report |
| Stakeholder communication | Weekly updates for a client project | Client asked for me on the next one |
| Data analysis in a spreadsheet | Cleaned and analysed survey data for a final-year project | Findings used in the dissertation |
The proof column is the one people forget. A claim with no proof sounds like a claim; a claim with a result sounds like experience.
What to do about a gap
Almost everyone meets a job description with at least one requirement they cannot fully meet. Do not hide it, and do not bluff. There are three honest moves:
- Find the nearest example. A smaller version of the same thing is still evidence. "I have not managed a team of ten, but I led a group of four on a project for a term."
- Show that you learn quickly. Describe a time you picked something up in weeks, and what you did to get there.
- Say what you are doing about it. A course you have started, a project you are building, a person you have asked for advice.
Panels notice when an obvious must-have is skipped and nobody mentions it. Naming the gap and showing a plan reads as honesty, which is itself a quality they are looking for.
How a practice interview treats the same document
This is also how the practice interview here works. Before the interview starts, the job description is turned into the list of skills the role needs, and the questions are built from that list and from your resume. Afterwards, each skill is scored from 1 to 10 on what you actually said about it, and the must-haves are marked. A must-have that never came up is visible as a gap, and missing one caps the recommendation. You can see exactly how in how your interview is scored, or look at the sample report to see the skills laid out.
A short checklist
- Highlight every requirement, and mark each must-have.
- Write one question for each responsibility.
- Fill in the evidence table, with proof for every must-have.
- Prepare an honest answer for the biggest gap.
- Practise saying your examples out loud, in under two minutes each.
When you are ready, start a practice interview with your resume and the job description, and see which skills come through and which do not. The ones that do not are the ones to prepare next.



