How long do you get to answer a HireVue question?

Where the 30 seconds and 3 minutes come from

One source, repeated everywhere since: HireVue's own step-by-step candidate walkthrough.

That page is dated 7 October 2014 and still tells readers to install Adobe Flash Player. It is the origin of the number, and the number does still describe a lot of real interviews, but treat it as a widely-used default rather than as policy.

What HireVue's current documents say instead

The 2025 Explainability Statement lists the settings an employer configures, along with what HireVue recommends for each. The recommendations are more generous than most candidates ever experience:

Set that beside the reality of a graduate scheme, where one take and a short countdown is normal, and you get the single most useful fact on this page: the constraint you are up against was chosen by the employer, not imposed by the software. A firm that gives you 30 seconds and one take has decided that performing under time pressure is part of what it is screening for. That is a legitimate choice, and it tells you something about what to practise.

Which is exactly why we will not print a per-employer timings table. We cannot see those settings, and neither can anyone else selling you a course. One employer of the eight we cover, BlackRock, publishes its own per-question timings — and even there they differ by region, so blending them would produce a number that is wrong for everybody. Its page is here.

How long the whole thing takes

HireVue's 2025 statement gives an example assessment of 4 to 6 video questions plus 2 to 3 games, typically 15 to 25 minutes of candidate time. Its candidate FAQ says most video assessments run five to eight questions and under 20 to 30 minutes, and suggests setting aside 45 minutes. Block the 45.

Why the timer is what actually catches people

Almost nobody fails a one-way screen because they did not know the answer. They fail on delivery under a clock, and the failure modes are consistent:

• Running out mid-sentence. The recording stops where it stops. An answer that was building to a result and ends on the setup reads as an answer with no result.
• Dead air at the end. Finishing at 1:10 of a 3:00 window and then sitting silently is not penalised by the software, but it usually means an example that never got to its outcome — and if a recruiter watches, twenty seconds of silence is what they watch.
• Wasting the preparation window. Thirty seconds is enough to choose which example and name the outcome you are heading for. It is not enough to script a paragraph. People who try to script arrive at the recording with nothing chosen.
• Front-loading the context. Ninety seconds of background leaves ninety seconds for the part that is being scored.

These are timing failures, not knowledge failures, and they are invisible in every other kind of practice. Answering a question out loud to yourself with no clock running rehearses the wrong thing entirely.

What to check before you start

• Your invitation email. If the employer set anything unusual, this is where it is stated.
• The on-screen text before you record. The interview page shows the preparation and answer limits for that specific question.
• Whether you get a practice question. HireVue's walkthrough describes practice questions you can repeat until you are comfortable, and Target, for example, states publicly that it offers one. Use every one you get.
• Whether retries are on. If they are, an answer you dislike is not the end. If the interface does not offer one, assume one take.