A pod that spans Pacific to JST sounds, on paper, like a recipe for 2am stand-ups. In practice we run a 24-hour engineering loop where nobody works outside their daylight hours. It is not magic. It is a discipline, and most of it sits in three places: the handoff, the artefact, and the on-call rotation.
The handoff is the product
The most-watched ritual in the pod is the daily handoff. The engineer wrapping up in their evening writes a short note: what they shipped, what is blocked, what the next person should pick up. The next time zone picks it up at the top of their morning. Nothing slips because nothing waits.
Async-first artefacts
- Every decision is captured in a Loom or a doc, never lost in a Slack thread.
- Pull requests carry context, not just diffs. Reviewers in another time zone can pick up the why without needing a meeting.
- On-call is followed by the sun. The pager moves with the working day.
What we do not compromise on
Two things. First, one weekly 30-minute live sync that everyone joins. It is usually painful for one time zone, but the cost of a fully-async team is loss of cohesion. Second, two in-person weeks a year. Cameras are not the same as a whiteboard and a coffee. Budget for it.
“You can be async without being absent. The teams that get this wrong drift apart inside a quarter.”
Zowork is a healthcare and behavioral health AI engineering team. For a decade we’ve shipped clinical platforms. Now we’re building the AI that runs underneath them.