Async Interviews and Video Screens: How Remote Hiring Really Filters

Why remote companies use these formats

Three reasons: volume, time zones and fairness. An international opening attracts far more applicants than a local one, candidates cannot all be scheduled into overlapping hours, and structured formats let different reviewers assess the same answers rather than different conversations.

There is also a practical signal being tested. In a distributed team, most of your communication will be written or recorded rather than live. A process that assesses those skills is assessing the actual job, not a proxy for it.

Where automated scoring is involved, EU rules on automated decision-making give you the right to information about it and, in significant decisions, to human review. Asking how your submission is assessed is a legitimate question.

In shortThese formats test the medium you will actually work in. Treat them as the job, not as an obstacle.

The recorded video screen

You get a set of questions, a time limit per answer and usually one or two takes. It tests whether you can be clear and structured without the interviewer's help, which is exactly what an async team needs. Rambling is the failure mode, not nervousness.

1. 01
   Prepare a structure, not a script

   Situation, what you did, result, in about sixty seconds. Memorised scripts sound memorised and collapse when the question shifts.

2. 02
   Fix the technical basics once

   Camera at eye level, light in front of you rather than behind, and the microphone closer than the laptop's. This costs ten minutes and is visible in every answer.

3. 03
   Answer the question first

   Lead with the answer, then the context. The reviewer may be watching at double speed and skipping the preamble.

4. 04
   Practise out loud, timed

   The gap between thinking an answer and saying it in sixty seconds is larger than anyone expects until they try.

Do not aim for polish. Reviewers are not comparing you to a presenter; they are comparing you to other candidates who mostly ramble. Clear and structured beats smooth.

In shortAnswer first, context second, sixty seconds. Structure beats polish every time.

The written round

Some companies replace the first call entirely with written questions. It is the most predictive stage for async roles and the one candidates most often underestimate, treating it as a form to fill rather than as a work sample being assessed on its own merits.

• Write as you would to a colleague: context first, then the point, then the detail.
• Answer what was asked. Long answers that drift signal exactly the problem async teams fear.
• Use structure, headings and short paragraphs. How you organise a written answer is part of what is being read.
• Do not pad. A precise three-paragraph answer beats a thorough page every time.

If you use AI to help, use it to check structure rather than to generate the substance. Written rounds are where generated text is most visible, because the reviewer is reading closely and comparing several answers side by side.

In shortThe written round is a work sample. Being organised counts as much as being right.

The take-home assignment

A scoped exercise, usually with a stated time budget, testing how you approach a realistic problem. What is being assessed is rarely the answer alone: it is your assumptions, your prioritisation under a constraint, and how clearly you explain what you did and did not do.

1. Respect the stated time budget and say what you would have done with more. Overdelivering signals poor prioritisation, not enthusiasm.
2. Write down your assumptions explicitly. Real briefs are ambiguous and how you handle ambiguity is the point.
3. Include a short note explaining your reasoning and your trade-offs. Many candidates submit only the artefact.
4. Say what you deliberately left out and why. It reads as judgement, not as gaps.

If the exercise looks like unpaid production work rather than an assessment, it is reasonable to ask. A scoped exercise of a few hours is normal; a full deliverable for their real client is not.

In shortThe reasoning note matters more than the artefact. Most candidates omit it entirely.

What actually sinks candidates

Not nerves and not technical glitches. It is answering a different question than the one asked, exceeding the stated constraints, submitting without explaining any reasoning, and treating async stages as paperwork before the real interview rather than as the assessment itself.

In shortThe async stage is the assessment. Candidates who treat it as a formality are the ones filtered out.