How to Run a HireVue Mock Interview

You have probably rehearsed answers in your head and still frozen the moment a red dot appeared. That is the gap this section closes. A HireVue mock has to be recorded, because almost everything that goes wrong in a one-way interview goes wrong for reasons you cannot notice from the inside.

In a live interview you get feedback continuously: the interviewer nods, interrupts, or asks you to go deeper, and you adjust. A recorded one-way interview removes all of that. You speak to a lens, a timer runs, and there is often no second take. The failures that follow are format failures rather than knowledge failures: trailing off because you cannot tell whether the point landed, filling silence with restarts, or finishing in a fraction of the time allowed and mistaking that for efficiency.

Rehearsing without a camera trains the content and none of that. Rehearsing with one trains both.

The setup is deliberately plain, and the constraints matter more than the tools:

• Pick questions you did not write today. Pull common prompts from a question bank rather than inventing ones you already have answers for.
• Start recording before you read the question. Reading time is part of the real thing.
• No restarts. If you stumble, keep going. Recovering out loud is a skill, and you cannot practise it if you always start over.
• Use the camera you will actually use, in the room you will actually sit in.
• Do three prompts back to back, so you rehearse the fatigue as well as the answers.

A junior product manager preparing for a retail company’s screening round recorded five prompts this way on a Tuesday evening. Watching them back, she found her first sentence was a variation of “yeah, so, I guess” in four of the five. She rewrote nothing about her stories, practised only her openings, and re-recorded the set two days later.

If you would rather have questions delivered to you and spoken aloud, the practice mode on the /mock-interview page runs an AI interviewer that asks and listens.

Watch each recording twice: once with the sound off, once with your eyes closed.

Sound off shows what a reviewer sees before processing a single word. Are you lit from the front or backlit into a silhouette? Does the camera sit at eye level or below your chin? Are you looking at the lens or at your own thumbnail? Eyes closed shows the answer itself: how long before you make your first concrete point, whether you name a result, and how often a filler word buys you thinking time.

Write down one fix per pass and re-record the same question. Two or three cycles on one prompt teach more than one cycle on ten.

An AI mock solves the supply problem. You get questions you did not choose, spoken at conversational pace, and a transcript afterwards showing what you actually said rather than what you remember saying. That is the hardest part of a HireVue rehearsal to reproduce alone.

Be clear about what it cannot do. No mock predicts which prompts a specific employer loaded into its HireVue set. Nothing transfers into the recording session either: the format is one-way and captured, so live answer suggestions are out of scope by design, and anything on your screen is part of what gets recorded. What travels with you is your own rehearsed structure.

More on how practice transfers to the real conversation sits under /answers/topic/mock-interviews, and what hiring platforms actually test, stage by stage, is under /answers/topic/platform-vetting.