How to prepare for an AI interview — a checklist from the people who built one

You have been invited to an AI interview, or you are about to take a mock one, and the first question in your head is the right one: what is it actually listening for? This is the answer from the team that builds Alex, SealHire's AI interviewer. It is not a trick. It is a structured conversation with a very patient interviewer, and it rewards exactly the things a good human interviewer rewards — with one difference that changes how you should prepare.

What an AI interview is (and is not)

An AI interview on SealHire is a spoken, two-way conversation. You talk, the interviewer listens, and the next question is built from what you just said. It is not a one-way video where you record answers to a fixed list, and it is not a quiz. There is no question bank you can memorise, because the follow-ups come from your own answers.

The interview is built from a role brief — the work the role involves, what a strong candidate shows, and the skills it will score. For a mock interview you pick the role and the level yourself; for a real one, the employer set them. Either way, the interviewer opens each area with a question about the work, then digs into the details you give: what you did, what happened, what you would change.

At the end you get three things: the recording, a timestamped transcript, and a skill-by-skill assessment where every score links to the moment in the recording that earned it. That last part is the difference we mentioned. A human interviewer forms an impression; an AI interviewer looks for evidence. That is what you are preparing to give it.

Prepare stories, not speeches. The interviewer will go one level deeper on whatever you say, so the answer that scores is the one with something underneath it.

The seven-step checklist

1. Read the role brief like an interviewer would

Open the role page before you do anything else. If you are practising, every SealHire mock interview has a page that shows the brief the interviewer works from — for example the Data Engineer mock interview lists what you will do, what we look for, and the five skills that get scored. Read the "what Alex asks" section. Those are the themes the conversation opens with. If you are taking a real interview, the invitation names the role; find the closest match in the mock interview catalog and read that brief.

For each skill, ask yourself: what is the one story I have that proves this? Write the skill and the story title on a single line. Five skills, five lines. That sheet is your preparation.

2. Pick one real example per skill — and make it specific

The interviewer will ask for a real example and then follow up on the details. Vague answers get vague follow-ups, and vague follow-ups are where interviews stall. Specific answers give the interviewer something to work with.

Specific means: a named system, a real number you actually know, a decision you made and why, a result you can describe. "I improved the pipeline" is not specific. "The nightly job was missing its window twice a week, I moved the two heaviest joins to a pre-aggregated table, and it has hit the window every night since" is.

You do not need a heroic story. You need a true one with details.

3. Structure every answer: situation, action, result, reflection

The classic STAR shape works well in a spoken interview because it keeps you from wandering. Say the situation in one sentence, the task in one, spend most of your time on what you did, and close with the result. Then add the thing most candidates skip: what you would do differently. The interviewer asks that question constantly, so answering it before it is asked reads as self-awareness rather than defensiveness. (There is a longer guide to STAR in a spoken interview if you want the worked examples.)

Keep each answer to roughly a minute or two. If the interviewer wants more, it will ask. Long monologues are not penalised, but they push the interview's time into one story instead of several.

4. Practise out loud, not in your head

This is the step people skip and regret. An AI interview is spoken. Sentences that read fine in your head come out with "um" and "so, basically" and half-finished clauses. That is normal — the interviewer waits for you to finish and does not judge filler words — but it is easier to give a clear answer if you have said it out loud once before.

Take a free mock interview for the role. It is thirty minutes, and the report will show you exactly which answers landed and which did not. Then take it again. Your first attempt is for learning what the format feels like; your second is the one you keep.

5. Set up the room, the microphone, and the window

You will be on camera and on microphone for half an hour. Do the boring things: a quiet room, a door that closes, a lamp in front of you rather than a window behind you, a laptop on a table rather than a bed. Use headphones if you have them — they stop the interviewer's voice feeding back into your microphone.

There is a technical check before the interview starts. Do it properly. A failed microphone check on a mock interview costs you nothing, but on a real one it costs you the calm you walked in with.

6. Know the rules of the room

SealHire tells the employer what it observed during the interview — whether you switched tabs, whether it looked like you were reading from a script, whether someone else seemed to be answering. It never assumes; it notes what it saw with a timestamp, and a human decides what it means. So do not read from notes, do not have a second screen open with answers on it, and do not have someone in the room prompting you. A glance at your one-line sheet from step 1 is fine. Reading a paragraph off it is not, and it shows.

The interview is also recorded and sealed the moment it ends — nobody can edit it, including you. That is a feature: it is what makes the report worth something to the person reading it.

7. Decide what you will do with the result

For a real interview, the result goes to the employer who invited you, and you are done. For a mock interview, the result is yours. You can keep it private, retake it, or share it with a hiring manager instead of a résumé. The public Seal shows that the interview is verified and which skills were assessed — never the video. Anyone who wants to watch it has to verify with a work email and a one-time code, and you see everyone who does.

Knowing that in advance changes how you approach the interview: you are not performing for a machine, you are recording the version of yourself you want a hiring manager to meet.

A worked example: turning the sheet into an answer

Say the brief is for a customer success role and one of the five skills is retention. Your one-line sheet says: "Retention — the renewal we nearly lost at the logistics client." In the interview, the opening question is something like "Walk me through how you manage renewals and expansion conversations."

The answer that scores is not a description of your renewal process in general. It is the story on the line: the account was six weeks from renewal and had stopped opening your emails; you found out from their support tickets that a new ops lead had inherited the contract and did not know what it was for; you booked twenty minutes with her, walked through the three reports her team actually used, and she renewed with a small expansion for a second team. Then the reflection: next time you would watch for a change of contact as an early warning, not wait for silence.

That is one minute, and it gives the interviewer four things to follow up on — the signal you missed, the meeting, the reports, the expansion — each of which produces more evidence for the skill being scored.

What the interviewer is not listening for

A few things candidates worry about that do not matter:

• Accent or pace. The transcript is produced by speech recognition that handles accents well, and the assessment is about what you said, not how fast.
• Filler words. "Um" and "like" are not scored. Thinking pauses are not scored either — the interviewer waits.
• Being interrupted. If you pause mid-thought, the interviewer gives you room. If it does start talking and you were not finished, keep going; it stops and lets you finish.
• Perfect answers. A skill scored as "developing" with an honest example is more useful to a hiring manager than a polished answer with no substance. Hiring managers read the evidence, not just the number.

The night before

Read your five-line sheet once. Say each story out loud once. Charge the laptop. Then stop — the interview rewards clarity, and clarity comes from rest more than from rehearsal.

If you want to see what the report looks like before you take one, there is a sample report you can read now. And if you want to try the format with nothing at stake, pick your role and take a free mock interview. The first three are free, and one only counts when you finish it.