Meeting rooms instead of Notion pages, face-to-face interviews instead of async video, CV screening instead of written case studies — building an async-first team requires you to completely redesign your hiring process. Because traditional recruitment assumes synchronous work. You're looking for someone who "responds immediately," feels comfortable talking in the office," and "can make decisions on the spot." Those criteria filter for the wrong candidate. The right person for async-first: someone whose writing is sharp, can build context alone, and can structure feedback loops independently.
Why removing sync bias is critical
In classic hiring, the first filter is speed: CV screening, phone call, first interview, second interview. Each stage requires live communication. The candidate's async skills are never tested. Result: you're adding someone to your team who "talks well on Zoom but doesn't know how to share written instructions."
In an async-first organization, written communication is a vital competency. You want someone who writes 4000-word PRDs, adds context payloads in Linear issues, keeps decision logs in Notion. You can't measure this through office conversations. To remove bias, you need to adapt your hiring flow to the async world.
Two concrete changes: (1) trial week instead of interviews — real-world testing, (2) written assessment instead of phone calls — giving thinking time to measure decision quality. These two elements are the core of async-first recruitment.
Written assessment: Test the value of thinking time
Your first filter should be a written case, not a CV. Give the candidate a real team scenario: "You're shipping feature X in 3 weeks. There's a priority conflict between engineering, design, and product. How do you proceed?" Give them 48 hours to respond. In that window, you'll see how the candidate thinks, builds context, and communicates in writing.
Evaluation criteria:
- Clarity: Are paragraphs structured, are headers used, is there plain language over jargon?
- Context: Did they see the stakeholder conflicts in the scenario, did they state their own assumptions?
- Decision discipline: Did they quantify the priority matrix ("impact/effort"), or is it intuition-based?
- Async fit: In their writing, do they say "we need to call immediately" or "let's open a Slack thread, gather input in 24 hours"?
Roibase has used this step since 2022. Out of 43 hiring processes over 8 years, 12 candidates who passed the first filter reverted to sync thinking during trial week — when written assessment rigor lapses, that ratio climbs to 40%. Written assessment is the most economical way to filter out candidates misaligned with async culture early.
Example assessment question
Give the candidate this scenario:
"Q4 roadmap has 3 major features: A, B, C. Engineering prefers A (reduces technical debt), design recommends B (solves user complaints), product advocates for C (new revenue stream). The CEO expects a decision this week. Compile your notes in an 800-1200 word Notion doc: (1) data analysis, (2) recommendation, (3) alternative scenarios."
When you read the response, async skill is obvious: did they use tables, support with links, include an "questions for leadership" section?
Trial week: Testing async workflow in the real environment
Invite candidates who pass written assessment to a 1-week paid trial project. Real team environment, async workflow. Here the game changes: you'll see how productive the candidate actually is outside of sync.
Trial week structure:
| Day | Activity | Async metric |
|---|---|---|
| 1 | Onboarding Notion doc + first Linear issue assignment | Quality of questions (in thread or DM?) |
| 2-3 | Feature development / design / analysis | Commit message / Figma comment clarity |
| 4 | Mid-week async check-in (Loom video + written summary) | Self-reporting discipline |
| 5 | Results delivered: PRD or design spec | Documentation quality |
During this period, don't schedule any synchronous meetings. All communication happens via Slack threads, Notion comments, Linear mentions. If the candidate says "we should call for 15 minutes," they're misaligned with async culture.
At Roibase, trial week success rate is 68% — meaning two-thirds of candidates who pass written assessment are also consistent during async process. Failure reasons: (1) response time (48+ hour delays), (2) missing context (every message triggers "what did you mean?" questions), (3) documentation discipline failures (code written but Linear issues not updated).
Feedback loop: Measure async decision discipline
At the end of trial week, offer the candidate an async feedback loop. Write your decision in a Notion doc: (1) strengths, (2) growth areas, (3) final decision. Ask them to respond within 24 hours — written reflection instead of a sync phone call.
This stage tests two things: (1) how the candidate receives feedback, (2) how they use thinking time to respond. If they send an emotional message in 2 hours, they're not aligned with async culture. If a structured response comes back after 24 hours — that person can work in an async-first team.
The feedback loop also mirrors company culture. Branding isn't just logo design; how you communicate during hiring is part of your brand. By giving async feedback, you signal: "we value written transparency."
Decision criteria table
| Dimension | Successful candidate | Misaligned candidate |
|---|---|---|
| Response time | 12-36 hours, consistent | 48+ hours or instant (unthinking) |
| Message structure | Headlines, subheadings, bullet points | Paragraph walls, single sentences |
| Question asking | In-thread with context | Constant DMs, no context |
| Documentation | Leaves trail in Notion/Linear/Figma | Only writes in Slack |
Long-term impact: Scale async-first hiring culture
After your first 3 hires through trial week + written assessment, team DNA starts forming. New people learn from existing members: "we communicate by writing here, sync meetings are exceptions." By the 12th person, the process runs itself — because the team consists of people who internalized async workflow.
To preserve this DNA, template your hiring process. Create a "Standard Hiring Flow" page in Notion: for each role, have written assessment questions, trial week projects, and feedback templates ready. When a new hiring manager joins, they don't start from scratch; they continue with existing async discipline.
Roibase has built teams across 15+ disciplines for 8 years — from SEO to data analytics, UI/UX to first-party data architecture. In every discipline, async-first hiring is critical: the team is spread across Istanbul, London, Berlin — 3 time zones. Sync meetings aren't a luxury; they're efficiency loss. Because of trial week, timezone mismatch isn't the priority; async competence is.
Building an async-first team isn't a technology shift; it's a culture shift. Your hiring process is the first touchpoint with that culture. Written assessment and trial week are as concrete as CV screening and office interviews. The difference: a CV shows you the past; trial week shows you the future. Asynchronous work skill isn't optional anymore — it's mandatory for scaling. The right filter means the right team.