The best async-friendly remote companies

What "async-friendly" actually means

An async-friendly company is one where meaningful work can get done without everyone being online at the same time. Decisions get made in writing. Meetings are the exception, not the rule. A 4-hour response time is normal, and a 30-minute response expectation is considered aggressive.

The opposite is a company where meetings are the main decision venue, Slack is checked compulsively, and "going offline for two hours" causes friction. These companies can technically be remote, but they don't work well across time zones and they burn out employees who can't sustain real-time presence all day.

The distinction matters more than "remote vs. office." A sync-heavy remote company has most of the downsides of office work with none of the social benefits.

How to spot async-friendly in interviews

Three categories of signals.

Structural signals (most reliable):

• Public handbook or employee manual that documents how decisions get made.
• Written decision logs, RFCs, or ADRs.
• Low meeting density — 5 hours/week is common at async-healthy companies.
• "Core hours" defined narrowly (2 to 4 hours) rather than "full working day."
• No expectation of responding to Slack outside core hours.

Cultural signals (softer):

• Team members across 3+ time zones working together.
• Meetings routinely recorded for people who can't attend.
• Public retrospectives, documented outcomes.
• Leaders who publish written updates regularly.

Red flags (sync-heavy):

• "We move fast and we're very responsive on Slack."
• "We have daily standups" plus multiple other standing meetings.
• Calendar invites going out the same day for "urgent" meetings.
• "Core hours" covering 7+ hours.
• No public docs about how the team works.

The gold standard: publicly documented async cultures

A short list of companies that have published how they work async, in enough detail that you can evaluate before applying.

• GitLab. The industry standard for documented async. Public handbook: about.gitlab.com/handbook. Thousands of pages documenting every process. Remote-first from founding.
• Automattic. Fully distributed since 2005. Communication via internal P2 blogs. Strong written culture.
• Doist. Published "Ambitious Async" manifesto. Small (100+ people) and fully distributed across 40+ countries.
• HashiCorp. Remote-first, publicly shares operating principles.
• Basecamp / 37signals. "Shape Up" methodology codifies async work. Publicly documented in their book "It Doesn't Have to Be Crazy at Work."

If you want to see what async done well looks like, read GitLab's handbook or Doist's async posts. Then compare to the role you're interviewing for.

Strong async cultures, lightly documented

Companies where employees consistently report strong async practices, even if the public documentation is lighter.

• Zapier — fully distributed, strong writing culture.
• Canonical (Ubuntu) — globally distributed engineering, decisions by RFC.
• Elastic — long-running remote-first.
• Mozilla — large async culture, long tradition.
• Buffer — small, distributed, public about internal practices.
• Hotjar — distributed, async-friendly.
• Wikimedia Foundation — non-profit, documented async.

Companies that are remote but not async

Some remote companies run in a fundamentally synchronous way. They can still be great places to work — just not async.

• Many early-stage startups (under 30 people). Velocity demands more real-time coordination.
• US-centric companies that expanded remote post-2020 but kept their meeting-heavy culture.
• Sales-heavy organizations where outbound motion requires coordination.
• Companies where the founder runs a lot of the decision-making via personal conversation.

If you value async but the role is at a sync-heavy remote company, expect 15 to 25 hours/week of meetings and compulsive Slack response. Some people are fine with that; some aren't.

Questions to ask in the interview

Ask directly. Their answers are more informative than their public claims.

1. "What does a typical Tuesday look like for someone on this team?" Count the meetings. Count the deep-work blocks.
2. "How are non-trivial decisions made?" If the answer involves a meeting, it's sync. If it involves a doc with a decision-owner and a comment period, it's async.
3. "What's the expectation for Slack response time?" "Within a few hours" or "end of day" = async. "Fast" or "instant" = sync.
4. "How do you document outcomes of important discussions?" Written summaries, decision logs = async. "We just discuss it in standup" = sync.
5. "What are your core hours?" 2 to 4 hours = async-friendly. 7+ hours = sync.
6. "How does the team onboard new hires?" A documented onboarding plan that doesn't require constant pairing = async-healthy. "We mostly pair in real time for the first 4 weeks" = sync.

Good answers match what the public handbook or blog posts have already said. Mismatches are a red flag.

When async matters most

Async is especially important if:

• You work across 4+ time zone offset from the majority of the team.
• You have caregiving responsibilities that require flexibility during the workday.
• You do deep creative or engineering work that needs uninterrupted blocks.
• You live outside the company's primary country/region.
• You've worked at sync-heavy companies before and don't want to repeat the burnout.

Async matters less if:

• The team is in one time zone.
• The work is inherently collaborative (pair programming, brainstorming-heavy product).
• You personally prefer real-time back-and-forth.
• The role is client-facing with external SLAs.

Common misconception

Async ≠ antisocial. Good async companies still have strong team relationships, regular video calls, and offsites. The difference is that the social and relational parts are scheduled deliberately, not scattered throughout the workday.

Async done well often produces more genuine connection, because the team isn't burned out from constant context-switching.

The bottom line

Async-friendly remote is a specific subculture within remote work. Companies like GitLab, Automattic, Doist, and HashiCorp have published how they operate in enough detail that you can evaluate them before applying. Use interview questions to test whether a company's async claim matches its actual practices. The difference between sync-heavy remote and async-friendly remote is larger than the difference between remote and office.