How to Prepare for an Interview with AI

Most interview nerves are a preparation problem

Interviews are stressful for a reason. You have thirty minutes to explain a decade of your working life to a stranger who is also nervous, and you cannot see their notes.

Some of that pressure is unavoidable. A large part of it, though, is simply the fear of being asked something you have never put into words before. That part you can fix in an afternoon, and this is where AI earns its place: it is an infinitely patient practice partner who will never be bored by your fourth attempt at the same answer.

Build the answer bank first

Here is the thing that makes preparation manageable: interviewers ask a lot of questions, but most of them are served by the same six or seven stories from your working life.

A time something went wrong and you sorted it. A time you disagreed with someone. A time you had to learn fast. A time you were under real pressure. Something you are proud of. Something that did not work. That handful covers an enormous proportion of what you will be asked.

Write them out once, properly, and you stop preparing per interview and start adapting.

I am building an interview answer bank. Ask me one question at a time to help me draw out six stories from my work history: a problem I solved, a disagreement I handled, something I learned quickly, a time under pressure, something I am proud of, and something that did not go well.
Ask follow-up questions when my answer is vague, especially about what I actually did and what happened afterwards. Do not write the stories for me and do not invent details. One question at a time, and wait for my reply.

Answer that in plain speech. Do not polish it yet. Getting the raw material out of your head is the hard part.

STAR, explained without the jargon

STAR is just a shape that stops a story from wandering. Four parts:

Situation. Where were you and what was going on. One or two sentences, no more.

Task. What needed doing, and what your bit of it was.

Action. What you personally did. This is the long part, and the word is I, not we. Interviewers cannot hire a team.

Result. What happened afterwards. A number if you have one, plain words if you do not, and honesty if it did not fully work.

Most people ramble through Situation and rush the Action, which is exactly backwards. Situation is scene-setting. Action is the answer.

Here is a rough story from my work history. Reshape it into Situation, Task, Action and Result, using only the facts I gave you. Keep it to about 90 seconds when spoken aloud.
Then tell me two things: where I used we when I should have said I, and which part I have over-explained.
Do not add achievements, numbers or outcomes I did not mention. If the Result is missing, ask me for it rather than inventing one.
MY STORY:
[paste]

Practise out loud with AI as the interviewer

Reading answers silently gives you false confidence. A story that feels fluent in your head can fall apart the moment you hear yourself say it. Practise aloud, even alone in a kitchen, and preferably against something that asks follow-up questions.

Act as the hiring manager for the role below. Interview me properly: ask one question, wait for my answer, then ask a natural follow-up before moving on. Ten questions in total, mixing competency questions with questions about my CV.
Be realistic rather than harsh. If an answer is vague, push on it once the way a real interviewer would. At the very end, and not before, give me feedback on the three answers that were weakest and why.
THE ROLE:
[paste the advert]
MY CV:
[paste]

The questions you are dreading

There is always one. A gap in your CV. Why you left the last job. Why you are changing career at forty-five. Being made redundant. The fact you have not worked for two years.

The dread comes from never having said it out loud in a calm room. Say it to an AI first, ten times, until it is just a sentence.

I am worried about being asked this in an interview: [describe the question you are dreading, and the honest situation behind it].
Help me build a short, calm answer of about 30 seconds. It should be honest, avoid over-explaining, avoid criticising a former employer, and end by moving forward rather than trailing off.
Give me three different versions with different tones. Then ask me the question so I can practise replying, and tell me if my version sounds defensive.

Short is the trick with these. Long answers to uncomfortable questions signal that you think there is something to apologise for. There usually is not. Career breaks, redundancies and career changes are ordinary parts of ordinary working lives.

Have questions for them

When they say do you have any questions, no is the wrong answer. Not because it is rude, but because you are genuinely deciding something too. Ask what a good first six months looks like, why the role is open, or what the team found hard this year. Ask two or three things you actually want to know. Do not interrogate them.