What does async-first actually mean?
Async-first means the default way to move work forward is to write something others read later, and meetings are the exception that needs justifying. It does not mean nobody ever meets; it means nothing important depends on two people being awake at once.
The test is simple: if you disappeared for 24 hours, would your team be blocked? On a genuinely async team the answer is no, because your context lives in documents and tickets rather than in your head and your calls.
How do you hand over work across a 10-hour gap?
Write a short end-of-day note in the shared channel or ticket. It costs five minutes and saves a full day of round-trip waiting, because the next person picks up your context while you sleep.
- Done: what actually shipped or moved, with links.
- Next: what you will pick up when you are back online.
- Blocked: precisely what you need, from whom, and by when.
- Decisions: anything you decided alone that others should know about or can overturn.
How many meetings is too many for a distributed role?
Treat meetings as a budget rather than a calendar. A healthy globally distributed role has one or two recurring live commitments per week, plus occasional ad-hoc calls when something genuinely needs a conversation.
| Recurring live meetings | What it usually signals |
|---|---|
| 0–2 per week | Genuinely async; documentation culture likely strong |
| 3–5 per week | Hybrid async; workable if they cluster in your overlap |
| Daily standup at a fixed hour | Office culture running remotely; expect timezone pressure |
| Ad-hoc calls with no notice | Decisions happen live and the written record will be thin |
How do you protect your own hours?
A big timezone gap is only sustainable if it is bounded. The failure mode is quietly shifting your day later and later until you are working two half-days and living inside neither.
- Publish your working hours in your profile and calendar, then hold them.
- Concentrate all live commitments into one window rather than sprinkling calls across the day.
- Turn off notifications outside your hours; being reachable at all times is not a job requirement.
- Ask for meeting rotation so the same people are not always the ones taking a 22:00 call.
- Push for recordings and written summaries of any meeting you are not in.
How do you tell real async from async theatre in an interview?
Ask questions whose answers are hard to fake. The useful ones are about artefacts, not intentions.
- Where is the last significant decision your team made written down? Can you show me the shape of it?
- How many recurring meetings does this role have, and at what hour in my timezone?
- What happens when someone is offline for a day and a decision needs making?
- What is the widest timezone gap currently on this team, and how long has that person stayed?
Frequently asked questions
+How much timezone overlap do remote teams actually need?
Genuinely async teams work fine with two to four protected overlap hours per week, used for the few conversations that benefit from being live. Roles that require four or more overlap hours every day are effectively timezone-locked, even when the advert says worldwide.
+What is a good async handover note?
Four short lines at the end of your day: what you finished, what you will pick up next, exactly what you are blocked on and from whom, and any decision you made that others should know. Post it where the team already reads, not in a private message.
+Does async work mean no meetings at all?
No. It means meetings are the exception rather than the default, and that nothing important is decided only in a call. One or two recurring live commitments a week is normal for a globally distributed role.
+How do I avoid burning out with a 10-hour timezone gap?
Bound your day. Publish fixed working hours, cluster every live commitment into a single window, silence notifications outside it, and insist that meeting times rotate so the same person is not always taking the late call.
+How can I tell if a job is really async-first before applying?
Ask how many recurring meetings the role has and at what hour in your timezone, and ask where the team's last major decision was written down. Strong written records and a low meeting count are the only reliable signals.