What "async-first" actually means in practice
A field guide to evaluating whether a company's async-first claims are real or performative.
Every company hiring remote workers in the last five years has put "async-first" or "remote-friendly" or "asynchronous communication" somewhere in its job listing. Some of them mean it. Most don't. Telling the difference is a survival skill for caregivers, because async-first is the single biggest cultural lever for whether a remote job is actually compatible with your life.
The four tests
Before you take an async-first claim seriously, look for four concrete artifacts. Each one is hard to fake, because each one represents a real organizational investment.
1. A written communication culture
Real async companies write things down obsessively. Look for: a public engineering blog with multiple authors, internal RFCs or design docs as the default decision-making mechanism, weekly written updates instead of weekly meetings, recorded demos instead of live ones. If the company has nothing to point to here, the async claim is decorative.
2. Bounded core hours
True async-first companies still have some synchronous overlap, but they bound it explicitly. "Core hours: 11am-1pm Eastern, three days a week" is async-first. "We're flexible but expect availability during business hours" is not — that's a 9-to-5 with extra steps.
3. Decisions documented after they're made
The single biggest failure mode of fake-async cultures is that decisions still happen in real-time conversations and are never written down. Six months in, you're either in every meeting or you're missing context. Real async cultures write a one-paragraph summary of every meaningful decision and post it where everyone can find it later. Ask in your interview: "How do you document decisions that get made in meetings?" The quality of the answer is the quality of the async culture.
4. A response time SLA, not a response time expectation
Async companies set a service-level agreement for response times — typically "respond within one business day." Synchronous companies set expectations — "be responsive on Slack." The difference is enormous. SLAs let you batch your day; expectations require you to keep checking.
The interview probe
In a first interview, ask: "Walk me through a typical Wednesday for someone in this role. What meetings are on the calendar, what async work is happening, and how does information move?" The answer is diagnostic. A real async-first manager can describe a Wednesday with two short meetings and significant deep-work blocks. A fake async-first manager will describe a Wednesday with five meetings, "and then we squeeze in the actual work between them."
The first-month test
If you take a job that claims to be async-first, the first month tells you the truth. Watch for: how many meetings appear on your calendar in week two, whether your first project lands as a written brief or a verbal one, whether there's a writeup after every important conversation, and whether "quick syncs" multiply faster than they get written down. If the trajectory is bad in month one, it almost never recovers in month six.
What to do if it's not what you were promised
If you discover the async-first promise was overstated, you have leverage you didn't have at offer stage: you took the job under a specific representation. Raise it explicitly with your manager — not as a complaint but as a calibration: "When I joined I was told this was an async-first culture; I'm seeing X meetings per week. Can we revisit?" Most decent managers will own the gap and adjust. The ones who don't are showing you what the next year will look like.
Why this matters more for caregivers
Synchronous work has a fixed cost regardless of who you are: you have to be at your desk during certain hours. For caregivers, those hours overlap with the hours you can't predict — sick kids, school early dismissals, doctor visits. Async cultures absorb that unpredictability invisibly; sync cultures expose it constantly. The difference between an async and a sync culture is the difference between a job that works for the next ten years and a job that breaks the first time the school nurse calls.