Working across Time Zones Engineering Team

An engineering team works well across time zones when the answers people need most already exist in writing, so nobody has to ping a sleeping colleague or wait a full day for a reply. The goal is not more overlap hours, it is fewer questions that only one awake person can answer.

The 8 PM ping and the all-day wait are two faces of the same problem: the waiting. Someone needs an answer, and the answer lives only in a head that is off the clock. You can solve that by making people stay online across zones, which burns them out, or by making the work answer for them when they are off. The second is the only one that lasts. When you write down the state of your work, your day keeps helping the team after it ends.

Why the 8 PM ping happens

The late-night ping is not a discipline problem. It happens because a colleague across the world hit a wall, and the only known source of the answer is you. From their side, pinging you is the rational move: the alternative is to guess or to lose the day. So they message, and you either answer on your own time or feel the pull to be always reachable.

Every ping like this points at a gap in the written record. If the answer had been written where the other person could find it, the ping would never have been sent. That is why the fix is upstream of the ping, in how work gets captured, not in setting a boundary and hoping people respect it. The failure modes here overlap heavily with engineering handoffs: what breaks and why.

Habits that remove the ping

A few small habits, done consistently, remove most cross-zone pings before they start.

• Write the why, not just the what: when you make a call, note the reason next to it. Most late-night questions are "why did you do it this way", and the answer is cheap to write once.
• End each day with a handoff: the 90-second end-of-day handoff template catches the state that goes stale overnight.
• Answer in the open: when someone asks you something in a direct message, move the answer somewhere the next person can find it too.
• Make the process async by default: treat live time as the exception, following an async handoff process nobody has to be awake for.

None of these are heavy. Together they shrink the pile of questions that only a single awake person can answer, which is the pile that generates the pings.

Protect the overlap you do have

Most distributed teams have some window where zones overlap, even if it is short. The mistake is spending it on status updates that could have been written. Guard that window for the things that genuinely need two people awake at once: a design disagreement, a tricky pairing session, a decision with real trade-offs.

How much overlap you need is smaller than most teams assume, and we argue that qualitatively in how many overlap hours a distributed team actually needs. The cost of getting it wrong, in nights lost to waiting, is the subject of the timezone tax, measured in whole nights. Sarah in Tokyo and Alex in Amsterdam might share only an hour or two; the trick is to make that hour count and to make sure the other twenty-two do not depend on it.

When you are the one who is off

Habits help, but you cannot pre-write every answer. The question you did not anticipate still arrives while you sleep. This is what your StandIn is for. It answers for you when you are off, on your behalf, using only your brief and your team's record. When a colleague asks something the record covers, your StandIn gives them your written answer in your words. When the record does not have it, it says so, rather than guessing, so nobody builds on a made-up answer overnight.

That is the difference between being unreachable and being unavailable but still useful. Your boundary holds, your evening is yours, and the team is not stuck waiting on you. New hires benefit from the same thing, which is why onboarding a remote engineer when nobody is free to explain works on identical principles.

Common Questions

How do we handle urgent questions across time zones?

Keep a clear escalation path for true emergencies, and route everything else through the written record. Most "urgent" questions turn out to be routine ones that felt urgent because the asker was blocked.

Do we need everyone to shift their hours to overlap more?

Usually not. Shifting hours trades one person's wait for another person's burnout. It is better to reduce the number of answers that require live time than to force more people awake at once.

Is async slower than being in the same time zone?

Only when the record is thin. A well-kept record can be faster than co-location, because the answer is already written and does not depend on catching a person at their desk.

How do we stop important context from living only in direct messages?

Make a habit of moving any answer that others might need out of the private thread and into a shared place. If a question was worth asking once, it will be asked again.

Working across time zones stops hurting when being off no longer means being a bottleneck. Write down the state of your work, protect the overlap for what truly needs it, and let your StandIn answer the rest from what you wrote. See the full approach on working across time zones.