Remote works here because async is engineered, not assumed. This page is the protocol, including the parts that cost us something.
[ 01 ]How it works
Async is the protocol, not a perk
Work moves through written threads and documents that anyone can read tomorrow. A decision that happened in a call gets written down within the day or it did not happen.
Overlap hours, narrowly defined
We ask for a few hours of overlap with IST afternoons for the conversations that genuinely need to be live. Outside that window your calendar is yours, and nobody schedules into it without asking.
Writing is the remote skill
The honest cost of async: you will write more here than at most companies — specs, updates, postmortems, thread replies that hold up without your tone of voice. We screen for it and we coach it.
What sync is reserved for
Hard trade-offs, bad news, design jams that need a whiteboard, and the quarterly week together in Bengaluru. Status is never a meeting; status is a document that takes two minutes to read.
The failure modes, named
Async drifts into silence, and remote drifts into isolation — we know. Every person has a weekly written check-in with their lead and a standing invitation to turn any thread into a call. Using it is normal, not an escalation.
[ 02 ]Work from where you think best