How to prepare for an interview without memorising a script

Start with the role, not a list of interview questions

Read the job description and identify a few things the employer needs this person to do. Turn broad requirements into work you can picture. “Stakeholder management” might involve resolving conflicting requests. “Analytical skills” might mean checking information before making a recommendation.

Treat these translations as hypotheses. The interview is also a chance to check what those expectations mean in this particular role.

The National Careers Service recommends reviewing the job description, researching the employer and preparing examples from your experience. ^[1]

Beside each important requirement, name one relevant experience and one question you still have. If you cannot find an example, mark the gap. Do not disguise it by writing a more confident adjective.

Check the interview format too. A conversation about past experience, a technical exercise and a case presentation need different preparation. The story bank below helps with experience questions; it does not replace practising the work an assessment will ask you to do.

Build five story cards

Five is a manageable starting point for this CareerFood exercise, not a rule about how many examples an employer expects. You may need fewer or different ones depending on the role.

The first card is a problem you investigated. Choose an occasion when you worked out what was wrong before proposing a solution. Include how you checked your interpretation. This gives you material for questions about analysis, judgement and uncertainty.

The second is a disagreement you handled. Look for different priorities rather than a story with a villain. What did you need to understand, what did you propose, and what remained unresolved? This can demonstrate collaboration without pretending everyone ended up delighted.

The third is a decision under constraints. Perhaps time, staffing or information was limited. Record which option you chose, which alternative you rejected and the cost of that choice. A decision is easier to discuss when the trade-off is visible.

The fourth is something that did not go as planned. Pick an example you can discuss responsibly. Name your contribution to the problem, how you responded and what you changed afterwards. Avoid turning the answer into a disguised compliment such as caring too much.

The fifth is a skill you learned and used. Show the gap, how you approached learning it and the task you subsequently completed. Attending a course is an activity; explaining how you applied the learning gives the interviewer something more specific to explore.

One experience can support several cards. You do not need five dramatic career milestones. Make sure you have enough range that every answer does not return to the same event.

Give each example a structure, not a script

STAR stands for situation, task, action and result. The National Careers Service describes it as a way to organise examples and recommends conversational delivery with readiness for follow-up questions. ^[2]

For each card, write brief notes under those headings. Add two more prompts of your own: “Why did I choose that action?” and “What would I do differently?” These help you prepare for questions that go beyond recounting events.

Keep the context only as detailed as the listener needs. The names of internal systems and the history of three departments may matter less than the problem you were responsible for solving.

Write the result honestly. If you have a reliable measurement, use it with its context. If you do not, describe the observable outcome. Do not invent a revenue figure or time saving because the example seems insufficiently impressive without one.

A worked answer with a real limit

Here is a fictional example. Daniel, a project assistant, is preparing for a coordination role. His original answer is: “I am a strong communicator. I worked with different teams to make reporting more efficient.”

There is a claim, but little the interviewer can examine. His revised version says:

“Our weekly project update contained conflicting delivery dates. I was responsible for preparing the update, but not for setting those dates. I checked the latest information with the two workstream leads and found that one date was provisional. I proposed separating confirmed dates from estimates and recording an owner for each unresolved item. The project lead approved the format. In the next review, we could identify the decision still needed rather than present two dates as equally certain.”

If asked about the impact, he could add: “I can explain the change to that review, but we did not measure a longer-term time saving.”

The answer shows what Daniel checked, what he proposed and who made the decision. It does not claim he transformed the whole reporting process. It also leaves room for useful follow-up questions about why the discrepancy happened and how he would prevent it recurring.

Practise changing the angle

Take one card and ask yourself three different questions about it. For Daniel's example: “How did you handle incomplete information?” “When did you challenge an assumption?” “What would you improve next time?”

The underlying facts stay the same. The emphasis changes. In the first answer, he might explain verification. In the second, how he raised the discrepancy. In the third, how the format could distinguish estimates earlier.

Do not force the story into a question it cannot answer. Daniel's example does not establish that he has managed a team. Acknowledging that limit is more credible than stretching the meaning of leadership until every task qualifies.

Practise aloud with someone who can interrupt naturally. Ask them to tell you what they understood your personal contribution to be. If their summary differs from yours, clarify the example rather than adding more impressive language.

If you rehearse alone, record one answer privately and listen for where the actual answer begins. Remove the preamble that delays it. Keep any confidential work details out of recordings or external tools.

When your experience is adjacent, not identical

Say where the match ends. “I have not owned that process end to end. The closest example I can offer is…” lets you present relevant experience without claiming the missing part.

You might draw on study, volunteering or responsibilities outside paid work where they genuinely demonstrate the skill. Explain the setting and its limits. Coordinating a volunteer event can show planning; it does not automatically equal managing a commercial budget.

If the requirement is essential and you have no relevant experience, a better story cannot remove that gap. Ask what level of prior experience the role needs and what training, if any, is available. That helps both sides assess fit.

Use the question you are actually asked

During the interview, take a moment to select the example rather than starting with the most rehearsed answer. If you are unsure what the interviewer means, ask a short clarifying question.

Distinguish a request for past experience from a hypothetical scenario. For a scenario, explain your proposed approach and assumptions. Do not present an imagined outcome as something you achieved.

Keep “I” and “we” accurate. Describe your own action, then credit the team's contribution to the result. You can be clear about your value without claiming sole responsibility.

If you need an accessible format or other adjustments, raise the practical need with the recruitment contact. Preparing differently does not make your experience less relevant.

Your next preparation session

Choose one actual role. Write down three important requirements. Find two experiences that help demonstrate them, then create brief story cards with the facts, your contribution, the outcome and one limitation.

Practise one card against two differently worded questions. Finish by preparing a question for the employer about how that responsibility works in their team.

This will not predict every question or guarantee an offer. It will give you something more useful than a paragraph to recite: experience you can explain and a clearer view of the role you are considering.

For help finding the evidence inside ordinary responsibilities, read how to describe your contribution without inventing results. The facts should survive the follow-up question, not just sound good in the first answer.