How to pass a one-way video interview

A one-way video interview is a recorded screen with no live interviewer. You read a question, record your answer on camera, and a hiring team reviews it later. To pass one, answer to the lens, lead with your point, back it with one specific example, and avoid reading a script. The format rewards structure and specifics, not polish.

That last part is the whole game. There is no interviewer to react to you, ask a follow-up, or pull you back on track. The structure has to do all of that work itself. Most people who bomb a one-way interview do not lack the answer. They lose to the format. Below is how to beat the format.

Answer to the lens, not to your face

This is the single biggest tell, and almost no one gets it right on the first try.

When you record, your screen shows your own face, and the instinct is to look at it. But the camera is the little dot at the top of your screen, and that is where the reviewer’s eyes will be. If you look at your face, you appear to be looking down and away. If you look at the lens, you appear to be making eye contact.

Put a small arrow or a sticky note right next to the lens that says “LOOK HERE.” Shrink the recording window and drag it as close to the top of the screen as it will go, so your face and the lens are nearly in the same place. It feels unnatural and it looks great.

The “we can tell when you’re reading” problem

Recruiters say reading off a script is obvious, and they are blunt about it. One recruiter who screens video interviews put it plainly on Reddit: “Watch for eye contact for reading interview responses from the screen. You can literally tell if someone is reading an answer to you.”

Two things give it away. Your eyes track left to right across the text, and your delivery goes flat because you are reading instead of talking. A reviewer watching twenty of these in a row spots it in seconds.

That does not mean you cannot have notes. It means notes have to be keywords, not sentences. Write three or four bullet words for each answer, the kind you can glance at without reading: a name, a number, a result. Tape them right next to the lens at eye level so your eyes barely move. Then know your answers well enough that the bullets are only a safety net. The goal is to sound like you are talking to a person, because someone is going to watch it as if you were. For more on what is allowed and how to do it cleanly, see can you use notes in a one-way video interview.

Plan for the thirty-second prep window

Here is the async-only reality that trips people up. On many tools, the clock is short. You may get around thirty seconds to read a question before recording starts, and on some you start recording the moment the question appears. One candidate described it exactly: “I had 30 seconds to prepare for a two minute answer.”

You cannot fix that in the moment, but you can prepare for it. Two things help:

• Use the practice question for real. Almost every tool gives you a practice or test recording. Do not skip it. Use it to learn the exact flow: how long the prep window is, whether recording starts automatically, and whether there is a countdown. Knowing the mechanics removes most of the panic.
• Have a thirty-second skeleton ready. You will not know the questions, but you know the shape of a good answer. The moment a question appears, mentally drop it into: point, one example, result. That structure is your scaffold so you are never starting from a blank page.

There is a separate, common disaster worth naming: not noticing the timer or the retake setting. One candidate panicked on the first question of a sales screen and wrote, “I didn’t notice the time limit, and there were no retake options.” Read the intro screen before you start. It tells you the time limit per question and whether retakes are on. Thirty seconds of reading the rules saves the whole interview. See one-way video interview time limit and how many retakes you get.

STAR, but under a timer

The STAR method (situation, task, action, result) is the standard frame for behavioral answers, and it works here. But the live-interview version is too long for a recorded answer with a hard cap. Tighten it:

1. Point first. One sentence that answers the question directly. Not a windup.
2. Situation, fast. One sentence of context. Where, what, why it mattered.
3. Action. What you did, specifically. This is the heart of the answer. Spend your time here.
4. Result. How it turned out, with a number or a concrete outcome if you have one.

The trap is spending forty seconds setting up the situation and running out of time before the result. Front-load the point and the action. If the clock cuts you off, you still landed the part that mattered. Candidates already prep this way. One on Reddit described running the job description and their resume through ChatGPT to get the five likely questions “with answers in STAR format.” That is a fine way to find your examples. Just do not memorize them word for word, or you are back to reading. The full breakdown lives at the STAR method in a one-way video interview.

The recruiter’s basics, from someone who watched hundreds

Before any of the clever stuff, get the obvious things right, because reviewers notice the obvious things first. A recruiter who has watched hundreds of these listed the recurring problems:

• Background. “I get a lot of bizarre backgrounds including two garages and one bathroom.” Sit in front of a plain wall. Close the door.
• Camera angle. “Now is not the time to hold it like a selfie.” Prop the laptop or phone at eye level on a stack of books. Looking down at the camera flatters no one.
• Attire. “PJ’s, stained t-shirt, or shirtless have all happened.” Dress the way you would for a live interview for that role. See what to wear for a one-way video interview.

Add the rest of the checklist: light coming from in front of you, never a bright window behind you, a tested mic, a silenced phone, and a charged device on stable internet. None of this wins the interview on its own. All of it loses the interview if you get it wrong. The full setup walkthrough is in how to prepare for an asynchronous interview.

Make the first ten seconds count

A reviewer often watches many answers in a row, frequently at speed and alongside an automatic transcript. They decide fast whether an answer is worth their full attention. That means the opening of each answer carries more weight than the middle.

So do not warm up on camera. Skip “that’s a great question” and “let me think.” Open with something real and specific in the first sentence. The candidates who get remembered say something concrete before the ten-second mark. If you are worried whether anyone is really watching, the honest answer is yes, a person reviews these, just not always at full length. See do employers actually watch one-way interviews.

What good answers sound like, by role

The questions are not random. Most one-way screens ask role-specific behavioral and scenario questions. Here are the real ones common roles get, with model answers and the trap to avoid. For a full bank per role, follow the links.

Sales

A common opener: “Walk me through a deal you closed from first contact to signature.” Reviewers are listening for a real process, not a war story. A strong answer names the prospect type, the discovery questions you asked, the objection you hit, how you handled it, and then your own real outcome, such as the deal size or how much you shortened the sales cycle. Another frequent one: “How do you handle a prospect who says your price is too high?” A good answer does not cave or argue. It reframes to value and asks a question back.

Trap: talking about the team’s number instead of yours. Reviewers want your actions and your result. Say “I” more than “we.” More at one-way interview questions for sales.

Customer service and support

A common one: “Tell me about a time you dealt with an angry customer.” The model answer shows you let them finish, acknowledged the problem in plain language, took a specific action, and confirmed it was resolved. A second frequent prompt is a live scenario: “A customer is upset that a refund hasn’t arrived. What do you say?” Answer it as if you are actually talking to them, in real words, not a description of what you would do.

Trap: describing the policy instead of demonstrating empathy and a fix. Support screens are testing tone and judgment, which is exactly what video shows. More at one-way interview questions for customer service.

Software engineer

These lean less behavioral and more practical. A common prompt: “Describe a bug that was hard to track down and how you found it.” Reviewers want your debugging process: how you reproduced it, how you narrowed it, what the root cause was. Another: “Tell me about a technical tradeoff you made and why.” A strong answer names the two options, the constraint that decided it, and what you would revisit.

Trap: jargon without a story. Saying you “leveraged a microservices architecture” tells a reviewer nothing. Name the actual problem and the actual decision. More at one-way interview questions for software engineers.

Before you submit

Watch one answer back if the tool allows it. Check three things: your face is lit and at eye level, your audio is clear, and you got to your point inside the time. If retakes are allowed and one answer is genuinely weak, take a single extra pass. Do not re-record a decent answer five times hunting for perfect. Reviewers want a real person who made their point, not a flawless performance.

Then submit and let it go. You did the work. The format is just a different room, and now you know how it is wired.

If your nerves are the real obstacle, not the tactics, read one-way video interview anxiety.