Use the Prep Method in an Interview: Honest Talking Points

If you want to use the Prep Method in an interview, the short version is this: gather real material from your own history, reduce it to a few honest talking points, say them out loud until they are natural, then choose and sequence them live as the conversation actually unfolds. If you freeze mid-answer because you have notes but no way to order them in real time, the problem is usually not your content. It is that you never practised moving between points while someone was waiting for an answer. This article walks through the whole routine, step by step, and shows how to apply it without sounding like a recording.

What the Prep Method Actually Is (and What It Is Not)

The method has three moves. Before the interview you gather raw material. You choose a small number of honest talking points from it. You rehearse saying those points out loud in an order that sounds like a person thinking, not a document being read.

It is not a script. A script collapses the moment the interviewer asks the question slightly differently, because your memory is holding sentences rather than ideas. It is not a set of canned answers either, and it is not a way to disguise a thin background. The method only organises what is genuinely true about your work. If the material is not there, no amount of structure will create it, and pretending otherwise is a bad trade: you will be asked a follow-up.

It helps to separate preparation from performance. Preparation gives you options: several stories, several angles on your experience, several ways to open an answer. Performance is the live act of choosing among them, in the second or two after the question lands. You cannot prepare the choice itself, because you do not yet know what was asked. You can only prepare the pool you are choosing from.

Set your expectations honestly. This routine reduces blank moments and rambling. It will not stop you from needing to listen carefully to the actual question, and it will not make an unfamiliar question familiar. Those two things stay your job.

Step 1: Gather Your Raw Material Before You Write Anything

Start with evidence, not adjectives. Concrete sources to mine:

Projects you delivered, and the specific part you owned.
Decisions you made when the information was incomplete.
Conflicts you handled, including the ones you handled badly at first.
Failures and what changed in your approach afterwards.
Results you can describe plainly, without inflating them.
Feedback you received, especially the uncomfortable kind.

Use the job description as a filter, not as a source of stories. The description tells you which parts of your real history are relevant to this role. It does not tell you what to claim. If the posting mentions stakeholder management and you have one genuine example of it, that example moves to the front of the queue. If you have none, that is information about fit, not a gap to paper over with invented detail.

Write one line per story, in four parts: the situation, what you did, what changed, and what you learned. Four short clauses per story is enough. For example: "Checkout migration slipped two weeks; I split the release into three stages; we shipped the first stage on the original date; I learned to sequence risk before scope."

Keep all of this in a single document that you add to over time. The night before an interview is the worst possible time to reconstruct your own career from memory. A living document means preparation for any given interview is editing, not archaeology.

Step 2: Turn Raw Material Into Three to Five Talking Points

A talking point is a short, honest claim plus the evidence that supports it. The claim is the sentence you would say first. The evidence is the story you already wrote in Step 1.

For instance, a claim about handling ambiguity: "I'm comfortable starting work before the requirements are fully settled." The evidence is the checkout migration story. Together they form one point you can deliver in thirty or ninety seconds depending on how much room you get.

Keep the number small. Three to five points per answer is a practical ceiling, because you have to hold them in working memory while you are also listening, breathing and watching the interviewer's face. More than that and you will start reading from a mental list instead of talking.

Order the points by what the interviewer most needs to hear first, not chronologically. If the question is about leading without authority, lead with the point that shows it most directly, even if it happened later than the others. Chronology is a comfortable default for the speaker and a slow one for the listener.

Finally, write each point as a phrase you would actually say out loud. "Stakeholder alignment across two teams" is an essay heading. "I got two teams who disagreed about the launch date into one plan" is something a person says. If you cannot imagine saying it to a colleague over coffee, rewrite it.

Step 3: Practise Out Loud, Not in Your Head

Silent rehearsal is where gaps hide. Reading your points and nodding feels like preparation, but it never tests the part that fails under pressure: producing sentences in real time, in the right order, while nervous.

Say the answer out loud. Record it once. Then listen for three things: filler words, repeated phrases, and buried openings. The buried opening is the most common problem. You have the right claim, but you say it third, after two sentences of context. Move it to the front.

Practise the same story at two lengths. Thirty seconds is your compressed version: claim, one line of situation, one line of action, one line of result. Ninety seconds is the full version with the learning at the end. Knowing both means you can expand or contract depending on how much the interviewer seems to want.

Notice where you naturally pause. A pause before a key sentence is not a failure; it reads as thought. A pause in the middle of a sentence is usually a sign that you are trying to recall a written phrase instead of an idea, which means the point needs rewriting in your own words. Deliberate pausing is a skill in its own right, and it is worth a few minutes of attention.

Step 4: How to Use the Prep Method in an Interview Without Sounding Rehearsed

Live, the method becomes a loop: listen, select, sequence, speak.

Listen to the whole question before you start choosing. The most common way prepared candidates go wrong is answering the question they hoped for. If the question is about a disagreement with a manager and your best story is about a disagreement with a peer, you can still use it, but say so: "The closest example I have is with a colleague rather than a manager." That single sentence keeps you honest and keeps the answer relevant.

Open with a one-sentence direct answer. Then support it with your points. The opening sentence is what the interviewer writes down; everything after it is evidence.

Use signposting phrases to keep the structure audible: what the situation was, what I decided, what happened, what I took from it. These phrases are not decoration. They tell the listener where you are, which buys you the freedom to take a moment to think.

If you lose your place, return to the last point you made and continue from there. Do not restart the answer. Restarting is what makes an answer sound memorised, because you are replaying from the top rather than continuing a thought.

Handling Follow-Ups, Interruptions and Curveballs

Treat a follow-up as a signal that the interviewer wants depth, not that your first answer was wrong. "Can you say more about the trade-off you made?" means the story landed and they want the interesting part. Go one level deeper into the same example rather than switching to a new one.

When you are interrupted, finish the sentence you are in, then answer the new question. Do not try to hold both threads at once; you will lose both. If the interruption came with a new question, the old one is finished for now.

For a question you did not prepare, fall back to the structure rather than the content. Situation, action, result, learning. You can run that shape over material you have never rehearsed, and it will still come out coherent, because the structure is doing the work the preparation would otherwise do.

It is acceptable to say you have not faced that exact situation. Then describe the closest honest example and say how you would approach the unfamiliar version. Interviewers generally recognise the difference between a candidate who has not done a thing and a candidate who is bluffing about it, and the second is much more damaging.

Common Mistakes When People Use the Prep Method

Memorising full paragraphs. The answer sounds recited and shatters the moment the wording changes. Memorise the points, not the sentences.
Preparing content but never practising transitions. The joins between points are where most rambling happens, and they are the part nobody rehearses.
Overloading the answer. Every detail that is relevant is not the same as every detail that is useful. Choose the strongest evidence and leave the rest.
Using the method to cover a genuine gap. If the experience is not there, acknowledge it and describe how you would approach the problem. That is a stronger answer than a vague claim that invites a follow-up you cannot survive.
Preparing one perfect story for every question. Rotate your material so you are not forcing the same example into questions it does not fit.

A Short Practice Routine You Can Repeat Weekly

Twenty minutes a week is enough to keep the method sharp.

Pick three questions, ideally from the role you are targeting.
Write or revise the talking points for each, using material already in your document.
Answer each one out loud, once, without stopping to correct yourself.
Review what you actually said: did you open with the claim, did you land the result, did you learn anything from the recording.
Rotate the questions next week so you are not rehearsing the same three answers indefinitely.

Over a month, notice which structures you default to and which you avoid. If you always reach for a conflict story but never a failure story, that avoidance is worth examining before an interviewer examines it for you.

A practice tool is useful for one thing here: rehearsing and reviewing your own answers honestly. It is not a substitute for someone else's words during a real interview. If you want to see how practice sessions are described, our documentation is the place to look, and the authorized use policy sets out the boundaries for using the product.

The takeaway: build the raw material once, reduce it to a handful of honest points, and rehearse them out loud until you can rearrange them mid-sentence. That is what makes the method survive contact with a real interview, and it is the whole point of learning to use the Prep Method in an interview.

Frequently asked questions

How many talking points should one interview answer have?

Three to five is a practical ceiling. You need to hold them in working memory while you are also listening and speaking, and a longer list tends to turn into a recital. If your material is richer than that, keep the extra points in your document and pick the most relevant ones for each question.

Does using the Prep Method make my answers sound scripted?

Not if you rehearse points rather than sentences. Scripted answers come from memorising full paragraphs, which breaks when the wording changes or the question shifts. Practising a short claim plus its evidence, and saying it aloud in different orders, keeps the delivery flexible.

What do I do if the interviewer asks something I did not prepare for?

Fall back to the structure rather than the content: situation, action, result, learning. That shape works over material you have never rehearsed. If you genuinely have not faced the situation, say so and describe the closest honest example, plus how you would approach the unfamiliar version.

Can I use the Prep Method for behavioural and technical questions at the same time?

Yes, with different emphasis. Behavioural questions lean on the story structure and the learning at the end. Technical questions lean on the decision and the trade-off you accepted. The same underlying example can often serve both, with a different opening sentence and a different level of detail.

How long should I practise before an interview?

A short weekly routine is more effective than one long session the night before. Twenty minutes a week, rotating the questions and answering out loud, keeps the material current. In the final days before an interview, spend the time on transitions between points rather than on new content.

Is it dishonest to prepare structured answers in advance?

No. Preparing how you will organise true information is different from inventing information. The line is straightforward: the stories, results and lessons should be real, and the structure should simply make them easier to follow. If the method is being used to disguise a gap rather than present your actual experience, that is the problem, not the preparation.

Read how practice sessions are described in our documentation.