---

Stage 3: The Loom Interview or Async Video Response

Some remote-first companies replace the first-round live interview with an async video response — you receive a set of questions and record yourself answering them via Loom or a similar tool.

This format terrifies candidates who’ve only ever done live interviews. It shouldn’t. It’s actually easier — you can do multiple takes, you can prepare, and you’re not trying to think in real time while managing someone else’s facial expressions.

What remote-first companies are screening for in Loom responses:

• Clarity under async conditions: Can you communicate a complete thought without being prompted? In a live interview, interviewers ask follow-up questions that guide you toward a complete answer. In a Loom response, you have to provide both the answer and the follow-up yourself.
• Tone and communication style: Does this person communicate the way our team communicates? Overly formal, over-rehearsed, or monotone responses feel misaligned with async-first cultures that skew conversational and written-first.
• Technical competence with async tools: Using Loom well — appropriate length, clear screen share if relevant, no 10-minute rambles — is itself a signal. It tells the team you’ve actually used async video before.

Practical tips for Loom responses:

• Keep each response to 90 seconds to 3 minutes maximum. If you’re running longer, you haven’t figured out what you actually want to say.
• Record in a clean, well-lit space. Background and audio quality are evaluated — they tell the hiring team about your home office setup, which is where you’ll be working.
• Don’t read from a script word for word. Write bullet points and speak to them. Scripted responses sound scripted.
• State the question at the start of your answer: “You asked about how I handle conflicting priorities across projects — here’s how I think about that.” This makes the response self-contained and easy to share internally.
• Re-record if you ramble significantly. You have that option in an async format. Use it.

---

Stage 4: The Paid Work Trial

The gold standard of async hiring at remote-first companies is the paid work trial: you do a small piece of actual work for the company over 1–2 weeks and get paid for it. GitLab, Automattic, and Doist all use versions of this format.[1]

A paid trial is the highest-signal format for both sides. For the company, it’s a real preview of your work. For you, it’s a real preview of their culture, tools, and management style.

How to succeed in a paid trial:

Communicate more than you think you need to. In a live work environment, your manager can see you’re working. In an async trial, your output is invisible until you surface it. Send a brief end-of-day update every day: what you worked on, what you completed, what’s blocked, what you’re doing tomorrow. This is not micromanagement — it’s the async equivalent of existing in the same office.

Document your work as you go. Don’t wait until the end of the trial to write up what you did. Keep a running log in Notion or a Google Doc. This gives the hiring team visibility into your process, not just your output, and it’s exactly how effective remote workers operate on the job.

Ask questions in writing, batched. Don’t send individual Slack messages every time a question comes up. Collect questions, determine which ones you can answer yourself with reasonable assumptions, and send a batch. This signals that you understand async communication norms — you don’t interrupt people for every small thing.

Deliver before the deadline. In an async environment, delivering early creates positive signal. It tells the team you managed your time without reminders, which is exactly what remote work requires.

If the trial goes well and you get the offer — before you sign, make sure the remote arrangement is permanent and in writing. The full framework for that is in the article on how to negotiate a remote arrangement at your current job — the same principles apply when negotiating terms at a new employer.

---

The Meta-Skill: Treating Every Async Touchpoint as a Work Sample

The single most important mindset shift for async hiring processes is this: every touchpoint is a work sample, not a performance.

A live interview is a performance. You’re managing impressions in real time, reading social cues, filling silence. An async hiring process is a work sample. The hiring team is asking: is this how this person actually works?

That reframe changes how you approach everything:

• A written application response is a sample of how you write async updates
• A take-home assignment is a sample of how you manage independent work
• A Loom response is a sample of how you communicate async video
• A paid trial is a sample of your first two weeks on the job

In each case, the question isn’t “did I impress them?” It’s “did I show them exactly how I work?” If you work well remotely, that showing is the impression.

The companies worth working for are the ones where your actual work is what gets you hired. If you want to find those companies — and target the ones that also offer the best geographic arbitrage opportunities — the ArbJobs framework at GalaxyBuilt maps out exactly where to look.

---

Summary

Passing async hiring processes means understanding that every format — written applications, take-home assignments, Loom responses, paid trials — is a direct sample of how you’ll work on the job. Remote-first hiring teams aren’t evaluating charm or confidence. They’re evaluating specificity, communication clarity, async tool proficiency, and your ability to produce documented output without real-time supervision. Answer written questions in under 200 words with specific tools and outcomes. Submit take-home assignments with a written process summary attached. Keep Loom responses under 3 minutes and speak to bullet points, not scripts. In paid trials, over-communicate your progress in writing and deliver early. The candidate who treats async hiring as a live interview will lose to the candidate who treats it as a work sample. Be the second candidate.

---

Get the weekly intel — join the free newsletter

---

References

[1] GitLab — “Hiring Process: Work Trials” — handbook.gitlab.com — 2024
[2] Automattic — “How We Hire” — automattic.com/work-with-us — 2024
[3] Doist — “How Doist Hires Remotely” — blog.doist.com — 2023
[4] Loom — “How Teams Use Loom for Hiring” — loom.com/use-cases — 2024