One-Way Video Interview & Online Assessment Tips

You applied to a Wave-1 summer-2027 role, and instead of a recruiter call you got a link with a deadline a couple of days out. That link is the automated first gate, and it's one of three things: a timed coding test, a game-based assessment, or a pre-recorded one-way video interview. By the end of this post you'll know which one you're facing and exactly how to prep it in the 48 to 72 hours you usually get, including the trick to answering a video question when you only have about 30 seconds to think.

The automated first gate: three things "online screen" can mean

This gate comes before any human interview. A real person doesn't talk to you yet; software collects your answers, and a recruiter or hiring manager reviews them later (more on that below). The live round, where someone actually asks you questions and follows up, is a separate stage with separate prep. We cover that in internship interview questions, and it's where most of the classic advice belongs.

The Wave-1 timing is why this lands on you fast. The early recruiters open from July into October, and big employers lean on automated screens to handle the application flood. So sort yourself first. "Online screen" usually means one of three things:

1. A timed coding or online assessment (OA). A set window, a few auto-graded problems. Common for software, data, and some quant roles.
2. A game-based or cognitive assessment. Short timed tasks that measure traits like attention and memory. Common in finance, consulting, and some grad schemes.
3. A one-way (pre-recorded) video interview. You record yourself answering a handful of questions with no live interviewer. Common across business, marketing, and general roles.

Read the section that matches your link. The video section is the longest because it's the one most students get wrong, and the setup checklist near the end applies to all three.

Timed online assessments (OAs) and coding tests

An OA is a coding test on a clock. You get a set window, commonly around one to two hours, with a small number of problems that are graded automatically the moment you submit. Amazon's intern software assessment is a useful public reference point: it runs about 90 minutes and includes a roughly 70-minute coding section plus a short workstyles part. Other employers vary, but the shape is the same: limited time, a few problems, machine-graded.

How to prep in a few days

You can't learn data structures in two days, so don't try. Sharpen what you already know instead.

• Practice under a timer, in the language you'll actually use. Untimed practice hides the real problem, which is that the clock makes you sloppy. Set the same window the OA gives you.
• Partial-but-working beats clever-but-broken. Auto-graders run your code against test cases. A simple solution that passes most cases scores; an elegant one that doesn't compile scores nothing. Get something correct running first, then optimize if time remains.
• Move on when stuck, then come back. Sinking 40 minutes into one problem is how people fail tests they could have passed. Bank the problems you can solve, then return to the hard one.

Then handle the logistics that quietly lose points: a stable internet connection (use ethernet or sit next to the router), and read the rules on allowed resources before you start, since some tools flag tab-switching or restrict what you can look up. Know whether the timer pauses if you close the window. Usually it does not.

Game-based and cognitive assessments

These look like simple browser games: balloons you inflate for points, cards you sort, numbers you remember. They're measuring traits such as attention, working memory, processing speed, and risk tolerance, not whether you're good at the game.

Set your expectations correctly, because this is where students waste energy. There's often no single "right" score to chase. Many of these tools are built to read consistency and how well you follow instructions, not a high score you can grind toward. You can't cram for them the way you cram for a coding test, and trying to outsmart the design tends to make your results look inconsistent, which is the opposite of what you want.

So the honest prep is short. Do the platform's practice round so the format isn't a surprise, read every instruction carefully, and then answer naturally and consistently. Treat it like the cognitive equivalent of a fitness test: you can't fake your way to a different result, so show up rested and just do it cleanly.

One-way (pre-recorded) video interviews

This is the screen most people have never seen before, so here's exactly what happens.

What actually happens

You open a link and answer questions to a camera, alone. There's commonly a small set of questions, often around three to five, and for each one you usually get a short window to prepare (frequently about 30 seconds) and then a capped amount of time to record (commonly up to around two to three minutes). HireVue, one of the common platforms, describes giving candidates 30 seconds to review the question and up to 3 minutes to answer. Your employer sets the exact numbers, so check your link.

The thing that throws people: there's no interviewer. Nobody nods, nobody asks a follow-up, nobody lets you course-correct if you misread the question. You get the prompt, a countdown, and a recording light. That changes how you should answer.

The 30-second prep window

You don't have time to write a script, and you shouldn't. In the prep window, jot three bullets, not sentences:

• the situation (one phrase, like "robotics club budget double-booked")
• your one action (the single most important thing you did)
• the result (what happened)

That's it. Three anchors keep you on track without trapping you into reading. Reading a script is the number one tell on these, because your eyes track sideways and your voice goes flat. Bullets let you sound like a person.

Compress STAR into about 90 seconds

In a live interview you can ramble a little and the interviewer reels you back in. Here, you're alone with a clock, so structure does the steering. Budget your time roughly like this:

• Situation, about 10 seconds. One sentence of context. Where, when, what was at stake.
• Task, about 10 seconds. What you specifically needed to do.
• Action, about 40 to 50 seconds. The heart of it. The concrete steps you took, in order.
• Result, about 20 seconds. What changed, ideally with a number, plus one line on what you learned.

Here's the shape, not a script to memorize:

"Last spring I was treasurer of my robotics club. (situation) Two weeks before our biggest event, I found a chunk of the budget was double-booked. (task) So I listed every commitment, called both vendors, negotiated a smaller package with one of them, and built a shared sheet so commitments get logged the day they're made. (action) We ran the event under budget, and the logging habit stuck for the rest of the year. I learned to surface money problems to the team early instead of quietly fixing them. (result)"

Practice the rhythm out loud a few times with different stories so 90 seconds starts to feel natural. Don't memorize one answer word for word, because a slightly different prompt will break it, and a memorized answer sounds memorized.

Retake strategy: a real decision rule

Some platforms let you re-record an answer, some give you exactly one take. Indeed's guide notes that one-way formats often let you re-record, but also warns you to cap the time you spend on it and move on. Assume you get one take unless the tool tells you otherwise, and use any retake by this rule:

Retake if something actually went wrong: you froze and went blank, you misheard or talked over the question, or you hit a technical glitch (frozen video, dead mic). Those are answers worth redoing.

Don't retake just chasing perfect delivery. A small stumble, an "um," a sentence you'd phrase better: leave it. A calm, complete, slightly imperfect answer beats burning your one shot trying to sound polished, and it massively beats running out of takes and submitting nothing. Done and human wins.

Setup checklist (do this once, before any of them)

These screens are async, so there's no interviewer to say "you're frozen" or "we can reschedule." You own the environment for the full window. Run this list once and it covers the OA, the game test, and the video:

• Book a quiet room you control for the entire window. Not a shared kitchen, not a library you might get kicked out of. No roommate walking in mid-answer.
• Test your camera and mic, and do the platform's practice question. Almost all of these offer one. It's the single highest-value five minutes you'll spend.
• Plain background, light in front of you. Face a window or lamp so your face isn't a silhouette. A blank wall behind you is fine.
• Phone on silent and out of reach. Out of reach, not face-down on the desk, so a buzz can't pull your eyes mid-recording.
• Charger plugged in, other apps closed. A dying battery or a background download tanking your upload speed is an avoidable disaster.
• Water and your three-bullet notes off to the side. Notes, not a full script. A script glued next to the lens is obvious on camera.
• Know your deadline and don't start at hour 47. Give yourself room for a tech problem or a redo. Indeed's advice to finish with a few days to spare exists because plenty of people hit the buzzer with a failed upload.

Frequently asked questions

How long is a one-way video interview?

It varies by employer, but plan for roughly 20 to 30 minutes total, often around three to five questions, with each answer usually capped at about two to three minutes of recording. The exact limits are set in your specific invite, so read the instructions on the link before you start.

Can you retake a one-way video interview answer?

It depends on the employer's settings. Some allow several re-records, some allow exactly one, so assume one unless the tool says otherwise. Use a retake for a real problem (you froze, misheard the question, or hit a glitch), not for nerves or a minor stumble. A complete, calm answer beats a skipped one.

What questions do one-way video interviews ask?

Mostly behavioral and motivational questions, the same families you'd get live: "tell me about yourself," "why this company," "tell me about a time when." So the same prep transfers. For the full set of question types with example answers, see internship interview questions, then practice compressing each one into the 90-second shape above.

Do you have to dress up for a one-way video interview?

Yes. Dress as you would for a live interview, at least from the waist up, because a human very likely reviews your recording later. Match the company's norms and go one step up: a plain collared shirt for most places, more formal for finance. Looking like you took it seriously is part of the answer.

Is a one-way interview like HireVue graded by AI?

Honestly, it depends on the platform, and you shouldn't assume the worst. Some video platforms use natural language processing to analyze the content and structure of your verbal answers against the role. Notably, HireVue publicly dropped its facial-analysis component in 2021 after criticism and an audit, saying language analysis had become the more useful signal. The practical takeaway: prepare as if a human reviews it, because one typically does. Speak clearly, answer the actual question, and structure your response. That's good preparation regardless of what runs behind the scenes, and it's not about gaming any system.

Today, do three things. Confirm which of the three screens you've got and its exact deadline. Run the platform's practice round so the format holds no surprises. And draft three short bullet-stories (a project, a responsibility, a stretch) you can reshape for any behavioral prompt. Those same three stories carry you into the live round too, so once you clear this gate, head to internship interview questions for what comes next. And while you wait to hear back, browse internships and line up a few more Wave-1 applications, because more shots at the gate is the whole game.