Prepare for the work in the vacancy, then choose examples that make your own contribution understandable. A polished general introduction cannot answer every employer's question about technical judgment, customer decisions or managing people.
Start with the current job description, your submitted application and the interview invitation. The steps below are a preparation method, not a way to predict the questions or guarantee an offer.
Turn the vacancy into questions you can answer
Highlight the responsibilities and requirements separately. For each important responsibility, write an ordinary-language task, the evidence you can discuss and what you still need to ask. Preserve words such as “required” and “desirable”; do not silently upgrade or remove a condition.
| Vacancy wording | Task to understand | Evidence to prepare | Question still open |
|---|---|---|---|
| Coordinate delivery across teams | Notice a dependency, agree an owner and follow up | A real example of handling an overdue handover | Who decides when priorities conflict? |
| Analyse service information | Check inputs and explain a recommendation |
These are invented vacancy fragments. Your employer may use different tasks and standards. If a requirement is unclear, record a question instead of pretending the title explains it.
Change the practice task to match the work
Job titles are starting points. Use the responsibilities to decide which part of an example needs the most explanation.
| Work being assessed | What to make visible in practice | A useful follow-up question |
|---|---|---|
| Technical or analytical work | Assumptions, method, checks and uncertainty | What would change your conclusion? |
| Customer-facing work | The person's problem, available options and your authority | When would you escalate rather than promise a solution? |
These are editorial prompts, not universal hiring criteria. For a past-experience question, use an actual episode. For a hypothetical exercise, make clear that you are explaining a proposed approach rather than reporting something you have done.
Match preparation to the actual interview format
Ask the recruiter about the format, duration, participants and any task or presentation instructions. Check whether materials, software or advance preparation are expected. Discuss access needs through the employer's process where relevant; local requirements differ.
For a past-experience question, explain the situation, your responsibility, your action, the result and what you learned. For a technical exercise, practise explaining assumptions, checks and an uncertainty rather than memorising only an answer. For a case discussion, clarify the objective and constraints before recommending a solution. For a management conversation, distinguish your decisions from a colleague's work and explain how you supported or corrected the process.
The advertised format takes priority over these examples. Do not assume every technical role uses a coding task or every manager is assessed through the same exercise.
Worked example: one real project, different relevant evidence
This is a fictional teaching example. The project, invitation and feedback are invented; there was no interview or hiring outcome.
Ravi helped organise a community event. Two suppliers had different delivery dates, and the team had not recorded who would confirm them. Ravi made a shared list of dates and owners, checked it with the organiser and contacted the two suppliers with permission. Both confirmations arrived before the event. Ravi did not manage the budget or supervise the volunteers.
Ravi is preparing for an invented project-support vacancy that asks for coordination and accurate records. His first practice answer is: “I led a successful event and improved communication.” It hides the evidence and overstates his role.
A better answer is: “Our event team had two unconfirmed deliveries. I was responsible for tracking them, not the whole event. I listed the dates and contact owners, checked the list with the organiser, and followed up with the suppliers. Both deliveries were confirmed before the event. I kept the confirmation notes, but we did not measure whether my list saved time. Next time I would agree the owner when each supplier is booked.”
For an analytical vacancy, the same story does not establish analysis skills. Ravi would need another genuine example involving checking information and drawing a supported conclusion. For a supervisor vacancy, coordinating suppliers does not establish that he managed employees. He can explain that limit and discuss relevant experience without inventing authority.
Ravi asks a practice partner to identify his responsibility, action and evidence from the answer. The partner asks: “What happened when a supplier did not respond?”
In this invented account, Ravi checks his notes and adds: “One supplier missed the reply date. I checked that I had used the agreed contact, then told the organiser that confirmation was still missing. The organiser approved a phone follow-up. I made the call and recorded the confirmed date. I did not change the order or promise a new delivery arrangement myself.”
That answer makes the escalation and his limits visible. It gives the practice partner something specific to question. In this fictional exercise, the next step is clearer evidence, not a more impressive job title.
Practise questions that expose gaps
Choose one important responsibility and say your answer aloud. Ask yourself or a practice partner:
- What did I personally decide or do?
- What alternatives did I consider, and why did I choose this action?
- What can I verify about the outcome? What remains unknown?
- What would I change if the same problem happened again?
Use confidential work only in a form you are allowed to discuss. Removing names alone may not make restricted material shareable. Use a permitted general account or a clearly labelled hypothetical example when necessary; do not upload employer documents to practise. If you lack an example, say what experience you do have and how you would approach a hypothetical task. Label hypothetical reasoning clearly.
Do not replace task evidence with a personality label or an IQ/EQ score. Those do not demonstrate that you meet this vacancy's requirements.
Prepare questions that help you choose, too
Ask about the first priorities, the standard of an acceptable deliverable, who reviews it and what support is available. Pay, hours and working conditions can also be important decision questions; asking about them is not evidence of poor motivation.
Before the interview, check the location or video link, required materials and a contact for technical problems. If instructions are missing, ask for clarification. If a task requests confidential information or work you cannot safely provide, explain the constraint and ask about an appropriate alternative.
Afterwards, record the actual questions, where your evidence was clear and what you could not answer. A rejection or silence alone does not identify the cause. Use specific feedback where available and revise the relevant example or target requirement.
Your next action is to complete one responsibility-to-evidence row and practise its follow-up questions. If the missing evidence is an artifact, use the career-switch portfolio guide. When an offer arrives, move to the salary negotiation framework, or return to the career planning hub if the target itself remains unclear.
Sources and scope
- National Careers Service: Interview tips, read 22 October 2026. England's public careers service recommends checking the format, researching the employer and preparing relevant experience.
- National Careers Service: The STAR method, read 22 October 2026. A structure for describing experience, not a prediction of interview success.
The table, practice questions and Ravi's example are editorial teaching tools. Employer criteria and local accessibility or employment rules need their own current sources.