One-way video interview questions, and how to answer them on camera

What a one-way interview is actually testing

In a one-way interview you record answers to a fixed set of questions and submit them. Nobody is on the other end. The reviewer watches later, usually alongside a stack of other candidates, often at speed.

That format changes what a good answer looks like. In a live interview you read the room and adjust; a hesitation gets rescued by a follow-up question. On a recording there is no rescue, no clarifying nudge, and no rapport to carry a vague answer. What survives is the substance you put in the first thirty seconds and how comfortable you look saying it.

Common questions worth preparing

Use these prompts to build a bank of examples. They are preparation suggestions, not a prediction of the questions in your invitation:

• Tell us about yourself. Use it to connect your experience to the role, rather than reciting your whole career. See the worked introduction example for how to choose and cut details.
• Why this role, and why us? Tests whether you read the job description or sent the same video to forty employers.
• Walk us through your relevant experience. The one where specifics decide everything.
• Tell us about a time you handled something difficult. A customer, a deadline, a conflict, a mistake.
• What are you strong at, and what are you working on?
• Anything else we should know? Frequently the last prompt, and frequently skipped. Do not skip it.

Where the job description is unusual, expect one question drawn straight from it — a scenario from the day-to-day, or a tool it names. Read the posting again before you record and you can usually guess that one.

The answer shape that works on camera

Lead with the point. In conversation you can build to a conclusion, because the other person is following along and will wait. A reviewer scrubbing through recordings will not wait, so the first sentence should carry the answer, and everything after it is evidence.

1. The claim — one sentence that answers the question directly.
2. The example — one situation, named. Where you were, what the job was.
3. The evidence — what you actually did, and what changed because of it.
4. The bridge — one line connecting it to this role.

One idea per answer. The instinct on camera is to cover everything in case this is your only chance, and it is the single most common way a good candidate becomes a forgettable recording. Two examples half-told is worse than one told properly.

What separates the answers that get remembered

Almost every candidate says they are hard-working, detail-oriented and a good communicator. Those words do no work, because everyone has them. What gets remembered is the detail that could only belong to you — and that detail is almost never on your resume, because resumes list duties.

The details worth digging for are the ones a resume has no field for:

• Volume — calls, tickets, accounts, patients, orders a day or a week.
• Rank — best month on the team, fastest ramp, most requested shift.
• Before and after — what a number was when you arrived and when you left.
• Promotions, and how quickly they came. Two in eighteen months says something no adjective can.
• The thing colleagues came to you for, even when it was not your job.
• A first job, or a job you left off the resume, that happens to fit this role better than anything on it.

One rule when you use them: never invent a number, and never sharpen an estimate. “About sixty a day” is credible and defensible in a later conversation. “Sixty-two a day” invites a question you cannot answer, and the interview where it falls apart is the one that mattered.

If your resume is short, our guide to video interview answers without work experience shows how projects and other responsibilities can supply honest examples.

Turn an outline into an answer you can say

In Requt, start with the job description and your resume. If the intake step asks for a missing detail, answer from memory or skip it rather than guessing. Review the generated opening, talking points and closing statement for accuracy before rehearsing with the teleprompter.

For the fictional customer-support example above, the rehearsal prompts could be: roughly sixty contacts a day; billing disputes; saved replies; relevance to this support role. Keep the full script while finding your wording, then see whether you can explain those points without reading every sentence. No new achievement or outcome needs to be added.

Before recording, work through the home recording checklist. If your invitation uses HireVue, check the format and retake guidance before choosing how to rehearse.

The mistakes that cost people the interview

• Reading. A script helps you prepare, but an unfamiliar sentence can sound stiff when read aloud. Rewrite it in words you would actually use, and practise looking back toward the lens.
• Running long. A three-minute answer to a one-minute question reads as someone who cannot prioritise.
• Opening with an apology. “Sorry, I am not great on camera” is the first thing they hear about you, and it is not true by the third take anyway.
• Answering the question you prepared instead of the one on screen. It is obvious, and it reads as canned.
• Skipping the last prompt. “Anything else?” is free space to say the one thing the questions did not reach.

Match your practice to the invitation

If the employer names a platform, check its process before choosing your rehearsal conditions. Our guides to Spark Hire practice and HireVue practice explain what to check about preparation time, retakes and submission.

How to rehearse without over-rehearsing

Try saying an answer aloud, recording it, and reviewing it once for delivery and once for substance. Choose one change for the next take. If you start sounding tired or memorized, pause rather than chasing a particular number of attempts.

The one thing worth over-preparing is the opening. If the first fifteen seconds are steady, the rest tends to follow, and a clear opening helps the listener understand your main point.