How to Prepare for an Interview Without Memorising Answers

Why memorising answers makes you worse

The instinct before an interview is to find a list of likely questions and write an answer to each. It feels like control, and it produces a worse interview than doing nothing.

Memorised answers are recognisable. They arrive at the wrong speed, they do not quite fit the question that was actually asked, and the candidate visibly stops listening once they have identified which prepared answer to deploy. Interviewers notice all three.

The deeper problem is brittleness. A memorised answer survives the question it was written for and collapses on the follow-up, which is where the interviewer was always going to spend their time.

Prepare material instead. Material adapts. A script does not.

Six to eight stories cover almost everything

Nearly every behavioural question is asking you to describe something you have actually done. There are fewer underlying situations than there are ways of asking about them.

Write down six to eight things from your career, each of which was genuinely difficult. Aim for coverage across these:

• Something you delivered under real pressure or a hard deadline.
• A disagreement with a colleague or a manager, and how it resolved.
• Something that failed, where you were partly responsible.
• A time you changed your mind after new information.
• Something you improved that nobody asked you to improve.
• A time you had to persuade someone who did not report to you.
• The piece of work you are most proud of, and why.

For each, note four things: the situation, what specifically you did, what happened, and what you would do differently. Do not write them as paragraphs to be recited. Write them as notes you could speak from.

Eight stories with real detail will answer thirty different questions, because interviewers are asking about the same handful of qualities from different angles.

Detail is what separates good answers from vague ones

The most common weakness in interview answers is not a lack of relevant experience. It is that the candidate cannot remember it precisely enough to be convincing.

"I improved our reporting process" is a claim. "We were closing three days late every month because two teams were entering dates differently, so I rewrote the template and got the close down to same-day by the second quarter" is a memory. Only the second one sounds like it happened.

So when you prepare your stories, chase the specifics. Numbers, names of systems, how long it took, who else was involved, what went wrong first. This is why writing them down matters. You will find you have forgotten most of the detail, and recovering it is the actual preparation.

One clear takeaway: interviewers cannot tell the difference between something you did not do and something you cannot remember properly.

The research nearly nobody does

Most candidates read the company's homepage and stop. Twenty focused minutes puts you ahead of nearly everyone.

Read the job description again slowly, looking for what the team is worried about rather than what they say they want. The first metric mentioned is what the hiring manager is judged on. The tools named are what the team actually runs. Who the role reports to tells you what the job really is.

Then look up your interviewers. Not to flatter them, but because it changes which of your stories are relevant. An interview with the engineering lead and an interview with the commercial director should not feature the same examples.

Find one recent, concrete thing about the company. A product launch, a funding round, an acquisition, a change of strategy, a public problem. Something specific enough that you could only know it by looking.

If they have customers you can observe, look at what those customers complain about publicly. Arriving with a genuine observation about the product is rare and lands hard.

Preparing questions, which are part of the assessment

The questions you ask are assessed as seriously as the answers you give, and most candidates treat them as a formality.

Weak questions have answers on the careers page. Questions about culture invite a rehearsed reply and tell you nothing.

Strong questions are specific, and they usually come from having read carefully. What does success look like for this role in six months. What is the biggest thing slowing the team down right now. Why is this position open. What has been tried already for the problem you mentioned.

That last one is the most useful question in interviewing, and hardly anyone asks it.

Prepare six, because three will get answered during the conversation. Our guide on questions to ask an interviewer goes deeper into this.

Practising out loud, which feels absurd and works

Reading your notes silently creates a false sense of readiness. You will discover in the interview that saying a thing is much harder than knowing it.

Say your stories out loud, once each, and time them. Two minutes is about right. Most people run to five on the first attempt, which is far too long, and the fix is cutting setup rather than talking faster.

If you can, get someone to ask you questions you have not seen. The discomfort of an unexpected question is exactly what you are training for. Our interview prep tool generates role-specific questions if nobody is available.

Record yourself once. It is unpleasant and it is the fastest way to notice that you say "kind of" nine times a minute or take forty seconds to reach the point.

The logistics that quietly ruin interviews

Preparation fails for boring reasons more often than for substantive ones.

For a video interview, test the link, the camera and the microphone on the actual platform the day before. Sit where the light is in front of you rather than behind. Close everything that makes a noise. Have the job description and your notes visible on a second screen or on paper, not in a window you have to hunt for.

For an in-person interview, know the journey, the building, and who to ask for. Arrive early enough to be unhurried, which is worth more than the extra twenty minutes of revision.

Have the job description, your resume as they received it, and your notes in front of you either way. Being asked about a bullet you cannot see is an avoidable disadvantage.

The day before, and the hour before

The day before is for reading your notes once and stopping. New preparation the night before adds anxiety without adding recall.

The hour before is not for revision at all. Reread the job description, look at your six questions, and then leave it. Candidates who cram immediately beforehand arrive with a head full of half-formed sentences and listen badly for the first ten minutes, which is where a lot of interviews are decided.

Preparing differently for each round

A screening call, a hiring manager interview and a final round are asking different things, and preparing for them identically wastes effort.

The screening call is checking whether you are broadly plausible and whether the basics line up. Be concise, be clear about what you want, and have your salary expectation ready in a form you can say without hesitating.

The hiring manager interview is where your stories matter. This is the conversation to prepare hardest for.

The final round, particularly with someone more senior, is usually assessing judgment and whether you will be easy to work with. Expect broader questions with fewer right answers, and expect your own questions to carry more weight than they did earlier.

Our career guides set out what each role's interview process typically looks like, which is worth reading before you plan your time.

Questions people ask

How long should I spend preparing for an interview?

Two to three hours for a role you want, most of it spent writing out stories in detail rather than reading about the company. Beyond about four hours the returns fall away sharply.

Should I memorise answers to common questions?

No. Memorised answers are recognisable, fit the question badly, and collapse on the follow-up. Prepare reusable stories with real detail and adapt them live.

What should I research about the company?

The job description read slowly, your interviewers' backgrounds, and one recent specific thing the company has done. That is roughly twenty minutes and puts you ahead of most candidates.

How many questions should I prepare to ask?

Six, because several will be answered during the conversation. Ask what success looks like in six months and what has already been tried for the problem they described.

Does practising out loud actually help?

Considerably. Knowing a story and being able to tell it in two minutes are different skills, and only one of them is tested in the interview.

Related reading

• Answering the Interview Questions Everyone Gets Wrong
• Behavioural Interviews: Using STAR Without Sounding Like a Robot