Focused preparation
How to turn a job description into an interview preparation plan
A long list of interview questions can keep you busy without helping you decide what matters. The job description offers a more specific starting point: the work this employer wants someone to do.
You cannot know every question in advance. You can prepare evidence for the main responsibilities, identify the gaps you need to discuss honestly and decide what you want to learn from the interview.
1. Pull out the work
Read the vacancy once for context, then mark the responsibilities and essential requirements. Separate those from benefits, company descriptions and desirable extras.
Rewrite the main responsibilities in plain language. “Cross-functional stakeholder management” might mean agreeing priorities with teams that want different things. “Service reliability” might mean recognising incidents, restoring service and preventing repeat problems. Keep your interpretation tentative when the wording is unclear.
Choose three to five themes for your first practice session. This is a way to focus your time, not a prediction of the interview's scoring criteria.
2. Match each theme to evidence
For every theme, note an experience you can discuss, your personal contribution and the outcome. Use work, study, volunteering or another relevant setting. Mark whether your experience is direct or transferable.
Here is a fictional example for an operations role:
- Responsibility: improve handovers
- Evidence: I helped introduce a short shift-handover template. Prepare: what was missing, who I consulted and what changed.
- Responsibility: handle competing priorities
- Evidence: I agreed an order of work when two urgent requests arrived together. Prepare: the trade-off, who made the final decision and how I communicated it.
- Requirement: a reporting tool I have not used
- Gap: no direct experience. Prepare: related reporting work, what I understand about the tool and a realistic learning plan.
Do not turn a gap into a made-up project. A clear account of related experience and what you still need to learn is more useful than a claim that will unravel under follow-up questions.
3. Create a few practice questions
Convert each responsibility into a prompt that invites evidence. These are preparation questions, not a claim about what the employer will ask.
- For prioritisation: “Tell me about a time you had to choose between competing requests.”
- For collaboration: “Describe a disagreement about how to approach a piece of work.”
- For quality: “How did you know the work was ready, and what did you check?”
- For learning: “Tell me about a task that required you to learn something unfamiliar.”
Practise answering one prompt before adding more. Use STAR to structure a specific experience, and prepare to explain your reasoning beyond the initial answer.
4. Check the employer context
Read the organisation's own website and the information supplied with the interview invitation. Look for its products, customers and the team's stated purpose. Distinguish confirmed facts from your assumptions.
Use that context to improve your questions. “The description mentions supporting several teams. How are conflicting priorities resolved?” is more useful than assuming how their process works.
Check the interview format too. A technical exercise, presentation and conversational interview need different preparation. If essential details are missing, ask the recruiter for the format and any materials you should bring.
5. Make a small plan you can finish
For your next practice session, try this order:
- Choose the most relevant responsibility and one real example.
- Answer a question aloud, then check whether your contribution and result were clear.
- Repeat the answer once, changing only the part that needed work.
- Prepare a short professional introduction that connects your experience to the role.
- Write two questions about the actual work and the team's expectations.
Keep your notes brief enough to review. Before using any practice tool, remove confidential client names, private contact details and internal information you do not have permission to share.
Use the plan to decide what comes next
After practice, record one thing to improve: a missing example, an unclear decision or a technical topic to revisit. That gives the next session a purpose.
Our free interview practice questions are a place to start. For engineering roles, you can also explore the software engineering and DevOps resources.
Further reading: Oxford University's interview preparation guidance covers researching the organisation and preparing relevant experience. The worksheet and practice plan above are MockReps guidance.