Async-only, no required meetings — flexible remote jobs

"Async-friendly" is one of the most abused phrases in remote-work job descriptions. Almost every company says it. Very few actually mean it. The difference is observable in five minutes of the right interview questions: a truly async company has a written team handbook, runs decisions through documents rather than meetings, and considers a same-day reply on Slack to be normal rather than urgent. A pseudo-async company says all the right words and then schedules a 9 AM standup, a 2 PM planning sync, and a 4 PM retro every single weekday.

The roles on this page are filtered for the real thing. We look for explicit language in the listing — "no required meetings," "written-first," "fully asynchronous," "we don't do standups" — and for companies whose engineering and operations handbooks are public and confirm that pattern. We exclude listings that say "async-friendly" but list a recurring meeting cadence in the same bullet list.

Why async is different from "remote"

Plenty of remote jobs require you to be online from 9 to 5 in some specific time zone. That's "remote in name, but on someone else's schedule." Async work cuts that cord entirely: you commit to deliverables, not to availability. You can do your morning block at 5 AM, take the middle of the day for a parent-teacher meeting, and finish in the evening, and as long as the work ships on time, nobody notices or cares. For parents and caregivers, this is the structural difference that makes a remote job actually viable. It's also why async roles are disproportionately competitive — every parent on the planet is looking for them.

What async-first cultures look like in practice

The companies that do this well tend to share a few traits. They write everything down, including small decisions, and store the writing somewhere searchable. They use issue trackers and project boards as the source of truth, not Slack threads. They schedule meetings only when an actual decision needs more than two people in real time. They're tolerant of a 12- or 24-hour reply window for non-urgent things. And they hire writers — not literally only writers, but people who can think in writing, because that's the medium the company runs on.

If you're coming from a meeting-heavy culture, the adjustment takes about three weeks. The first week feels strangely quiet. The second week, you realize how much of your previous job was performing busy-ness in real time. The third week, you start producing more, more thoughtfully, in fewer hours. The async parents we've talked to don't go back, even when offered significant salary increases to do so.

How to verify before you accept

Three questions to ask before signing: "How many recurring meetings will be on my calendar in a typical week?" — the right answer is one or two, max. "When was the last time the team made a significant product decision in a meeting versus in a document?" — the right answer references a specific document. "What's your team's policy on Slack response time?" — the right answer is "same day during business hours, no expectation outside of that." If any of these answers come back vague or evasive, the role is probably async in the brochure and synchronous in the daily reality.