Mock Interview Checklist: Set Up Before You Start

Before a mock interview, have four things ready: one real job description for the role you are targeting, a quiet space with working audio, a chosen way to record yourself, and a short list of the questions you most fear. Set a timer for the real interview length, answer out loud in full sentences, then review the recording against the marked job description. This mock interview checklist covers that setup in about fifteen minutes, because the setup is what decides whether the practice is worth doing.

Pick one job description and mark it up

Choose a single posting for the role you actually want. Two postings pull the session in two directions: you end up answering a blend of both and can judge neither answer properly.

Read the posting once, then highlight two things:

• the five or six responsibilities you would be hired to carry out;
• the named skills, tools and qualities it asks for.

Turn each highlighted line into one question you expect to hear. This is the step most people skip, and it is the one that makes the review concrete later.

Worked example: a support-team lead posting

Suppose the posting lists "handle escalations" and "report on trends". Those two lines become two questions:

For the first question, write three keywords you will speak from: for example, customer, timeline, handover. Three words give you a spine without turning the answer into a script.

A common mistake is practising from a long generic question list. A generic list can feel productive, but it gives you nothing to score an answer against for this posting. Keep the marked posting open while you review, and score each answer against the line it was built from.

To go further on that mapping, see turn a job description into answers.

Set the room, the timer and the audio

Book a slot when the space is quiet. Close the door, and put your phone on silent, face down, out of reach. The point is not ceremony: a session interrupted twice is a session you cannot review honestly.

Set a timer for the real length of the interview you are preparing for. Assume a screening call runs about 30 minutes and a panel 45 to 60; set the timer to whatever your invitation says, and use these only if it does not say. Practising for ten minutes trains you for a format that does not exist.

Then test the audio before you start. The ten-second playback test:

1. Start your recording method (voice memo, video call with yourself, or screen recorder).
2. Say one sentence at the volume and distance you will use in the session: "This is a test of the microphone for my practice interview."
3. Stop, save, and play it back through the speakers or headphones you will use.
4. Listen for three things: is it audible, is it clear rather than muffled, and is there background noise you had stopped noticing?

If the recording is silent, the input device is wrong: check which microphone is selected before anything else. If it is muffled, move the microphone closer or switch to a headset, then repeat the ten-second test. Repeat it again any time you change headsets or rooms. Discovering a dead microphone halfway through an answer wastes the session; ten seconds prevents it.

For a fuller pass over the room and the software, the calm remote interview setup checklist covers the rest.

Choose how you will record and review

Pick one method and write down where the file will be saved:

• a phone voice memo, if you only want to hear structure and filler;
• a video call with yourself, if you want to see posture and eye contact;
• a screen recorder, if you are practising with notes or a shared document on screen.

Each has a cost. Audio is quick and easy to delete but hides your face. Video shows everything and tempts you to judge your appearance. Choose the one you will actually review, not the most thorough one.

Before you record anything involving another person or a platform, ask and follow their rules. If a partner or a friend is playing the interviewer, get their agreement on the recording first. If you are using a service, read its policy on recording. Ask first: a recording made without agreement is one you should not keep, use or share.

Keep recordings local and delete them after review unless you have a reason to keep them. Then schedule the review immediately after the session, fifteen minutes in the calendar, so the file does not sit unwatched.

Write the five questions you least want asked

List the questions that make you pause: an employment gap, a layoff, a project that failed, a skill the posting asks for and you lack, a role you left quickly. Five is enough.

For each one, write two lines:

• one true sentence of context;
• one concrete action you took.

No invented results. If the honest outcome was that the project was cancelled, say that and say what you learned to check earlier next time. A plain true sentence is stronger than a polished fiction you have to remember.

Decide in advance what you will not disclose, and prepare one neutral sentence for it: "That period is personal, and I would rather focus on what I did next." Holding a boundary is reasonable; inventing a reason is not. Keep the sentence true and short.

Do not script answers word for word. A script collapses the moment the question arrives in a different shape. Note three keywords per question and speak from them. Here is what that sounds like for the escalation question above:

"A customer's export had been failing for two days when it reached me. I owned it from that point: I confirmed the timeline with them in writing, pulled the two failed runs, and found the job was timing out on a large file. I split the export, sent them a working file the same afternoon, and handed the fix to the engineering team with the logs. Before, exports over a certain size failed every time; after the split and the new run limit, the customer's export completed in one attempt and the same failure stopped recurring. When the customer pushed for a date, I gave them the one I had confirmed in writing rather than a guess, and the engineering team decided the new limit from the logs I passed on."

That is about 120 words. Assume a speaking pace of about 130 to 140 words a minute; at that pace 120 words is roughly 50 to 55 seconds, comfortably inside the 60 to 90 second target for a behavioural answer. It works because every step is an action you could be asked to defend, and the result is stated as a change rather than a boast. Expect follow-ups: "What did you do when the customer pushed for a date?" and "Who decided the new limit?" Those are good signs; they mean the answer gave the interviewer something to pull on.

Run the mock interview checklist in real time, out loud

Sit or stand as you would in the real call. Answer in full sentences, out loud, without stopping to edit.

Let the timer run. If you freeze, note the question on a sheet and move to the next one rather than restarting. Restarting teaches you to begin well and finish badly, which is the opposite of what a real interview asks.

Keep a one-line log as you go: "Q3, lost the thread on the failed project", "Q5, too long on the gap". That log gives the review its targets, and it takes seconds to write.

The temptation is to pause and perfect an answer. Resist it: treat the first run as a draft, and save every fix for the review. You are collecting evidence, not performing.

Review the recording with a four-line rubric

Watch or listen once without scoring, then score each answer on three lines, 0 to 2 each, and note delivery separately:

Below the table, add one observation line: filler and pace, noted once. Do not score it. Note it once per answer and do not correct mid-session: fixing delivery while you speak splits your attention.

The maximum on the scored lines is 6. A total of 5 or 6 means the answer is working; 3 or 4 means one line is dragging it down; below 3 means rebuild the answer rather than polish it.

The mistake here is reviewing for personality, asking whether you seemed confident or likeable. That is not scoreable and not fixable in a week. Score only these three lines, keep the delivery note, and pick one to improve next time.

The one rule: one change per session

After the review, choose a single fix for the next mock: add a result to every example, or cut each answer to 90 seconds, or replace filler with a pause. One fix, written down.

Pick a cadence you can keep, such as one session a week while you are actively applying, and carry one fix into each.

If you use an AI tool to generate practice questions or feedback, treat its output as a draft. It can be wrong, so check it against the posting and answer in your own words.

The printable one-page version

• Job description: one posting, five or six responsibilities highlighted, five questions written from them.
• Room and timer: quiet slot booked, door closed, phone silent, timer set to the real length.
• Recording and consent: method chosen, file location noted, ten-second playback test passed, anyone else involved asked first.
• Feared questions: five listed, one true context line and one action each, three keywords per answer.

Start with the posting, not the questions

If you only do one thing before your next session, mark up a single job description and write five questions from it. Everything else on this mock interview checklist serves that list: the audio test protects it, the recording preserves it, and the rubric scores your answers against it. Fifteen minutes of setup turns an hour of talking into evidence you can act on. For the wider routine around it, see the day-before interview checklist.

Frequently asked questions

How long should a mock interview session last?

If time is tight, run three questions in fifteen minutes and review only those. Skip the full set, keep the timer honest for each answer, and score the three against the rubric. A short, reviewed session teaches more than a long one you never watch, and you can cover the remaining questions next time.

Can I run a mock interview alone without a partner?

Yes, and it works well if you record it. Speaking your answers out loud to a camera or a voice memo exposes gaps that silent reading hides. Write your questions from the posting first, then answer them in order under a timer. A partner adds pressure and unexpected follow-ups, so alternate between solo sessions and a person when you can.

Should I record video or just audio?

Choose video if you want to check posture, eye contact and pacing, and audio if hearing your structure and filler is enough. Video shows more but invites you to judge your appearance instead of your answers. Pick the format you will genuinely review, and delete the file once you have scored it.

What if I don't have a job description yet?

Find one posting for a role close to what you want and use it as a stand-in. The marked responsibilities give your practice a target, and a real posting is better than a generic question list. When you settle on a specific role, repeat the setup with that posting, since the questions and the review will change with it.

How often should I repeat the mock interview?

Aim for a rhythm you can sustain rather than a burst you cannot. One reviewed session a week while you are applying keeps the habit alive, and each session should test the single fix you chose last time. If an interview is close, run one session two or three days before, leaving time to act on what the rubric shows.

Preparing for interviews? See how AI Interview assistant works.