Notion page instead of conference room, asynchronous video instead of face-to-face interview, written case study instead of CV screening — building an async-first team requires redesigning your hiring process from scratch. Because traditional hiring is built on synchronous work assumptions. You're looking for someone who "responds immediately," "is comfortable talking in the office," "can make decisions on the spot." For async-first teams, these are the wrong filters. The right candidate: someone who writes clearly, builds context independently, structures feedback loops — someone who thinks on paper.
Why removing sync bias is critical
In classical 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 add someone to the team who "talks well on Zoom but doesn't know how to share written instructions"—or worse, ignores them.
In an async-first organization, written communication is a vital competency. You want someone who writes 4,000-word PRDs, adds context payloads in Linear issues, maintains decision logs in Notion. You can't measure this by chatting in an office. To remove bias, you need to adapt your hiring flow to the async world.
Two concrete changes form the core: (1) replace interviews with a trial week—testing in the real environment, (2) replace phone calls with written assessment—giving thinking time to measure decision quality. These two are the backbone of async-first hiring.
Written assessment: Testing the value of thinking time
Your first filter shouldn't be CV—it should be a written case. Give candidates a real team scenario: "You'll ship feature X in 3 weeks. Engineering, design, and product disagree on priorities. How do you proceed?" Give them 48 hours to respond. During that window, you'll see how they think, build context, and communicate in writing.
Evaluation criteria:
- Clarity: Are paragraphs structured? Do they use headings? Plain language over jargon?
- Context: Did they spot the stakeholder conflicts in the scenario? Did they state their own assumptions?
- Decision discipline: Did they quantify priorities (impact/effort matrix), or rely on gut feel?
- Async fit: Does their writing say "we need to call immediately" or "let's open a Slack thread, sync in 24 hours"?
We've used this step at Roibase since 2022. Over 43 hiring processes across 8 years, roughly 12 candidates passed the written filter but reverted to sync behavior during trial week—when we loosen the written assessment, that rate jumps to 40%. Written assessment is the most cost-effective way to filter out async-incompatible profiles early.
Example assessment question
Give candidates this scenario:
"Q4 roadmap has 3 major features: A, B, C. Engineering prefers A (reduces technical debt), design advocates B (solves user pain), product backs C (new revenue stream). The CEO expects a decision this week. Compile your thoughts in an 800–1,200-word Notion doc: (1) data analysis, (2) recommendation, (3) alternative scenarios."
When you read the response, async skills are transparent: Did they use tables? Support with links? Include a "questions for leadership" section?
Trial week: Testing async workflow in a real environment
Candidates who pass the written assessment get a paid one-week trial project. Real team environment, real async workflow. The game changes here: you see how productive they are outside sync.
Trial week structure:
| Day | Activity | Async metric |
|---|---|---|
| 1 | Read onboarding Notion doc + first Linear issue assignment | Question quality (in thread vs. 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 | Deliverable: PRD or design spec | Documentation quality |
During this period, have no synchronous meetings with the candidate. All communication flows through Slack threads, Notion comments, Linear mentions. If they say "we should call for 15 minutes," they're not async-first material.
At Roibase, trial week success rate is 68%—meaning two-thirds of candidates who pass written assessment also succeed in async process. Failures stem from: (1) response lag (delays over 48 hours), (2) missing context (asking "what did you mean?" on every message), (3) documentation indiscipline (writing code but never updating Linear).
Feedback loop: Measuring async decision discipline
At the end of trial week, offer candidates an async feedback cycle. Write your decision in a Notion doc: (1) strengths, (2) growth areas, (3) final decision. Ask them to respond within 24 hours—written reflection, not a sync call.
This tests two things: (1) how they receive criticism, (2) how they use thinking time to respond. If they send an emotional message within 2 hours, they won't fit async culture. If they respond 24 hours later with a structured reply—that person can work async-first.
The feedback loop also reflects company culture. Branding isn't just logo design; it's how you communicate during hiring. By giving async feedback, you're signaling: "we value written transparency."
Decision criteria table
| Dimension | Successful candidate | Misaligned candidate |
|---|---|---|
| Response time | 12–36 hours, consistent | 48+ hours or immediate (unthinking) |
| Message structure | Headings, subheadings, bullet points | Wall of text, single sentences |
| Question asking | In-thread, with context | Frequent DMs, contextless |
| Documentation | Leaves trails in Notion/Linear/Figma | Only writes in Slack |
Long-term impact: Scaling async-first hiring culture
After your first 3 hires using trial week + written assessment, team DNA starts forming. New people learn from existing team: "here, we talk by writing; sync meetings are exceptions." By your 12th hire, the process runs itself—because the team consists of people who've internalized async workflow.
To preserve this DNA, templatize your hiring process. Create a "Standard Hiring Flow" Notion page: ready-made assessment questions for each role, trial week projects, feedback templates. When a new hiring manager joins, they don't start from zero—they continue with existing async discipline.
Roibase has been building teams across 15+ disciplines for 8 years—from SEO to data analytics, UI/UX to first-party data architecture. In each discipline, async-first hiring is critical: because the team spans Istanbul, London, Berlin—3 time zones. Sync meetings aren't a luxury; they're efficiency loss. Trial week made timezone mismatch irrelevant—async competency became the priority.
Building an async-first team isn't a technology shift; it's a culture shift. Hiring is the first touchpoint with that culture. Written assessment and trial week are as concrete as CV screening and office interviews. The difference: CV shows you the past; trial week shows you the future. Asynchronous work competency isn't optional today; it's mandatory for scaling teams. Right filter, right team.