Hiring for Async-First: Practical Filters and Interview Structure

Building an async-first team means designing your hiring process async too. The "let's close this in three rounds for speed" approach is a remnant of synchronous culture — ultimately, you're hiring someone who talks well on crowded Zoom calls but can't articulate in writing. Roibase has hired developers, analysts, and strategists from outside Istanbul since 2018. Our process: written assessment, trial week, decision criteria in a document. This article breaks down the mechanics of async-first hiring.

Identify the synchronous interview bias

Classic interview format rewards synchronous communication. The candidate who responds quickly, projects charisma, maintains eye contact scores high. But in async teams, these skills don't matter. What counts is writing a detailed analysis on a Linear issue, responding without context loss three hours later, converting ambiguity into documentation — that's the real competency.

In 2020, Roibase ran an experiment: two developer profiles. The first explained concepts flawlessly on video call; the second showed hesitation verbally but presented solution design clearly in a two-page written assessment. We hired the second. Eight months later, their Linear issue resolution speed was 34% higher — expectation met.

If you allow synchronous filtering in hiring, you're building synchronous dependency into your team. For async-first teams, the screening mechanism must be async too.

Written assessment: show your decision-making process

The first concrete step in async hiring: replace the résumé with a written assessment. Give the candidate 2–3 questions, 48 hours to respond, expect 400–600 words. Example questions: "Have you encountered dependency conflicts in a recent project? Walk me through the resolution process" or "How do you resolve ideological disagreements on a team? Use a real scenario."

Evaluation criteria:

• Structure: are intro, analysis, and conclusion sections clear?
• Detail: did they provide concrete numbers, tool names, time frames?
• Context: can someone else read and understand it?
• Tone: explanatory rather than defensive?

We eliminate 60% at this stage. Candidates who delay submission beyond three days, send single-paragraph answers, or hide behind jargon are out. In async-first culture, writing discipline is a prerequisite — testing this before trial week reduces downstream costs.

Response time: attention isn't the metric, prioritization is

Responding within 48 hours simulates async work. The candidate may work full-time elsewhere, may be in a different time zone. What matters isn't speed but systematic response. We prefer someone who submits detailed analysis after 40 hours over someone who sends half-formed thoughts in 24.

Trial week: paid work, not simulation

Trial week is async hiring's most critical filter. For five days, the candidate has access to your team's actual tools: Linear, Notion, Figma, GitHub. You assign a real task — not a project simulation, but a priority:low issue from your current backlog. At the end, you pay them: daily rate × 5 days.

Trial week evaluation criteria:

• Issue resolution quality (40% weight)
• Context sharing in Linear comments (30%)
• How they ask when stuck — async documentation or Slack panic? (20%)
• Time-to-first-response: when did the first commit land? (10%)

In 2023, a data analyst candidate built a dashboard during trial week. She documented her BigQuery queries in Notion, articulated assumptions, flagged missing data early. First commit arrived 18 hours later (expectation: 24 hours). We hired her. Six months in, project setup costs were 40% lower — because documentation discipline existed from day one.

Unpaid trial weeks create both ethical problems and poor filters. Paid trial weeks make the candidate's time management realistic.

Synchronous call: cultural fit exploration, not decision-making

Async-first hiring doesn't forbid synchronous meetings — but not for deciding. Use a 30-minute video call to introduce team culture, clarify async expectations, and encourage the candidate to keep asking questions.

The only question we ask on the call: "Which part of trial week felt unclear?" We evaluate their async communication style through the answer. If they say "why did you do this?" instead of "I didn't find context in the documentation, so I was uncertain," async fit is low.

Some candidates arrive expecting Zoom to be the main event — this is your moment to convey async philosophy. "Code review can turn in three hours here, but if there's no urgency, expect 24. Does that work for you?" This is a net filter. Early elimination saves time.

Decision: scoring in documents, approval without meetings

After trial week, the decision process is also async. Each team member scores the Linear issue on 1–5 scale. The hiring lead creates a decision document in Notion: scoring table, team comments, final recommendation. The lead closes the document and requests Slack approval. No objections within 48 hours, you hire.

Example scoring table:

This table eliminates the sync call. You're using "what I documented" instead of "what I felt." Decision closes within two days — no sync meeting needed.

Objection mechanism: transparency in documents

The hire decision is visible in Notion (candidate anonymized). If a team member objects, they fill the "counter-argument" section: which criterion they evaluate differently, which data point they base this on. The hiring lead responds within 24 hours. Objections happen ~15% of the time — usually new data changes the conversation.

This mechanism reinforces async culture. The team trusts documentation; decisions are transparent. The founder or lead's "I'll handle it" bypass is blocked. As boutique agencies like Roibase scale, this discipline extends to the branding process itself — "this is how our team operates" becomes external messaging.

Async hiring cost: saves time

At first glance, async hiring looks slower — trial week adds five days, written assessment two. But misplaced hiring costs 3–6 months. Async filtering eliminates mismatched profiles early. Hiring someone who interviewed well synchronously but doesn't fit async culture costs more over two months.

Over the past three years, Roibase hired 12 people through async hiring. First six-month attrition: 8% — industry average is 25%. Why: trial week is real work simulation, filtering happens early. Rushing sync to save time is attractive short-term; it erodes team culture long-term.

If you want to build an async-first team, your hiring process must be async. Trial week, written assessment, documented decisions — these are mechanical steps. Sync calls are fine, but decisions don't happen there. Async hiring discipline sets clear expectations from day one.