How to prepare for a job interview out loud

The night before an interview, almost everyone does the same thing. They look up the fifty most common questions, read the list, decide they would know what to say, and go to bed.

The next morning they stumble on tell me about yourself. Not because they do not know the answer, but because they have never said it out loud. Between knowing and saying there is a gap that reading does not close.

Here is the method I use, in the order that matters.

1. To prepare for a job interview, start with the posting

You know your CV. The posting you read once, diagonally, three weeks ago, just before applying.

Go back through it line by line and split it into three columns: what is required, what is preferred, and what is mentioned only once. The requirements are your guaranteed questions. The preferences are your likely ones. The rest is filler written by someone who had a template to fill.

A posting read properly gives you between five and eight subjects. That is your revision plan, and it is far shorter than a list of fifty generic questions.

2. Find the three things they will press on

Put your CV next to the posting and look for the gaps. The gaps are what trigger the real questions.

A six-month hole. A career change. A junior role applied for with twelve years of experience somewhere else. A required skill that appears nowhere on your side. An impressive project on the CV where your exact contribution stays vague.

Write down the three most visible. A competent interviewer will go there, and will go early. If you have spotted them, those are three questions you see coming. If not, they are three moments where you will improvise.

For each one, prepare a three-part answer: the fact, the explanation in one sentence, and what it gave you. No apology, no speech.

3. Prepare six stories, not twenty answers

This is the change of method that makes the most difference.

Nobody can memorise twenty answers. Six well-chosen stories, on the other hand, cover most behavioural questions: a measurable success, a failure, a conflict you resolved, a decision made without full information, a moment where you learned something fast, and a project you carried end to end.

Each story holds in four beats: the situation, what you were responsible for, what you personally did, and the result. The last beat is the one everybody forgets, and it is the only one your interviewer cares about. A result with no number is an opinion.

One story serves several questions. That is the point: you have six, not twenty.

4. Say them out loud, with a timer running

A written answer always reads well. It has subordinate clauses, transitions, and vocabulary nobody uses in speech.

Say it. Standing up, out loud, with a timer. You will discover three things: that your fine sentence does not survive being spoken, that you take forty seconds where you aimed for twenty, and that the ending falls apart because you never worked out how to land it.

Aim for a minute and a half for a full story, two minutes for your opening pitch. Beyond that, the person opposite has stopped listening.

Record yourself and play it back. It is unpleasant the first two times, and it is by far the highest return exercise on this list.

5. Count your filler words

While playing yourself back, count the ums, the sort ofs, the you knows, the rights. Turn the total into a rate per hundred words.

That number is brutal and useful. Nobody hears their own fillers, everybody hears other people’s. Above roughly ten per hundred words it becomes obvious, and it projects a hesitancy that has nothing to do with your actual level.

The fix is not talking faster to fill the gaps. It is the opposite: accept silence. A one-second pause before answering reads as thinking. A two-second um reads as discomfort.

6. Prepare your closing questions

Do you have any questions is not a courtesy, it is the last thing anyone remembers.

Prepare three, and not ones whose answer sits on the company website. Ask how the team you would join is put together, what the priority projects of the next six months are, or what a successful first year in the role would look like.

Three, because two of them may well get answered during the interview itself.

7. The night before, and the morning of

The night before, stop revising. Read your six stories once, check the place, the time and the name of the person you are meeting, then close everything. Cramming at midnight wins no points and costs a night.

On the day, say one answer out loud before you leave. Any of them, two minutes. A voice needs a warm-up like everything else, and you do not want your first attempt of the day to be the real first question.

Practising under real conditions

Everything above can be done alone, and it is enough to make a difference. What is missing is the unexpected: the follow-up you did not see coming, the pushback, the silence you have to fill.

That is exactly why I am building Nelo, an interview simulator that calls you, runs the conversation from your CV and the posting you are chasing, then hands back a report on what you actually said, filler words included.

But start with the seven steps. No app replaces a posting read line by line and six stories ready to go.