Leading Distributed Teams from UTC+8: Overlap Is Negotiated, Not Endured

Sydney and Zurich are nine hours apart. Serving both doesn't mean someone takes the bad call — it means synchronous time is scheduled where it's civil for everyone, and the rest of the work doesn't need it.

Sydney and Zurich are about nine hours apart. The usual assumption is that if one person serves both, somebody is taking a call at an uncivil hour — and that somebody is the contractor.

That has not been my experience, and the reason is not that I work heroic hours. It is that the question is framed wrong. Synchronous time is not a constraint you endure, it is a slot you negotiate — and how much of it you actually need depends on what your role is.

I'm a full stack and lead developer working from the Philippines (UTC+8) — hands-on in the code, but also on the oversight side: leading teams, setting direction, and owning delivery for clients in Australia, Switzerland, the UAE, and the United States. This is how that actually works.

The map, honestly

First, the raw material. Working from UTC+8, here is what the other end sees at various points in my day:

| My time (UTC+8) | Sydney (UTC+10/11) | Zurich (UTC+1/2) | Dubai (UTC+4) | New York (UTC-4/5) | |---|---|---|---|---| | 09:00 | 11:00 — mid-morning | 02:00 — asleep | 05:00 — asleep | 21:00 — previous evening | | 12:00 | 14:00 — early afternoon | 05:00 — asleep | 08:00 — starting | 00:00 — asleep | | 15:00 | 17:00 — end of day | 08:00 — starting | 11:00 — mid-morning | 03:00 — asleep | | 17:00 | 19:00 — after hours | 10:00 — mid-morning | 13:00 — afternoon | 05:00 — asleep | | 21:00 | 23:00 — asleep | 14:00 — afternoon | 17:00 — end of day | 09:00 — starting |

(Offsets shift an hour with Australian and European daylight saving; the shape holds.)

Read that as a negotiation space, not a schedule. It tells you which slots are civil for which pairs. Mid-afternoon my time reaches an Australian late-afternoon and a Swiss morning simultaneously — that band exists, and it is where a call involving both naturally lands. Nobody is being asked to do anything unusual.

The point is not that UTC+8 has a magic overlap with everyone. It is that for any given client there is a slot that costs neither side their evening, and finding it is a five-minute conversation rather than a standing sacrifice.

Why the overlap doesn't need to be large

Here is the part that actually makes a nine-hour spread workable, and it has nothing to do with timezones.

Most of the work does not need synchronous time at all. Writing code, reviewing a PR, designing a schema, diagnosing a failing pipeline — none of that requires the other person to be awake. If your collaboration model depends on tapping someone on the shoulder, then yes, a nine-hour gap is fatal. But that dependency is a choice, and usually a bad one even when everyone shares a room.

What genuinely needs a live conversation is a much shorter list:

• Ambiguity — the requirement is unclear, and a written round-trip would cost a day
• Disagreement — two reasonable positions need resolving
• Direction — what the team is doing next, and why

Everything else is better written down anyway. Writing forces precision and leaves a record.

What being on the oversight side changes

This is the piece I think people miss when they think about distributed work.

If your role is purely hands-on IC, the timezone conversation is about your availability — when can you be reached, can you make standup. Overlap is a cost you pay.

If part of your role is leading — setting direction, unblocking a team, owning whether the thing ships — the conversation inverts. Synchronous time stops being about presence and starts being about decisions. And decisions schedule well: they can be batched, prepared for, and resolved in a deliberate call rather than an ambient one.

So the working model is: business and direction calls happen at a specified, mutually agreed time. Around them, my hands-on work and the team's work proceed without anyone needing to be simultaneously online. The call is where ambiguity gets killed. The rest of the week is where things get built.

That is why the overlap can be narrow without the relationship being strained. I am not trying to be present for eight hours of someone else's day. I am trying to be decisive for one of them.

Boundaries, stated plainly

Flexibility is not the same as permanent availability, and I would be suspicious of anyone who claimed otherwise.

I will move to meet a client — an early call for Europe, a late one for the US East Coast — when the thing warrants it. What I will not do is pretend a nine-hour gap can be papered over with constant availability. That model produces a contractor who is tired, slow, and eventually unreliable, which serves nobody.

The honest version: agreed slots, held reliably, with a written trail around them. A client who knows exactly when they have my attention, and can read what happened in between, is better served than one who could theoretically reach me at any hour and receives progressively worse work for it.

What this means if you're hiring

If you are running a team across Australia, Europe, or the Gulf, the timezone question to ask is not "how many hours do we overlap?"

It is: what do we actually need synchronous time for, and can this person operate without it the rest of the week? A developer who needs constant contact will struggle at any distance. One who can take a direction, run with it, lead the people around them, and report back clearly will work fine across nine hours — and the scheduled call becomes a real decision point rather than a status ritual.

That is the model I run, and it is why serving Sydney and Zurich at the same time is unremarkable rather than heroic.

I'm Ehnand Azucena — full stack and lead developer. I've led delivery on multi-tenant SaaS platforms, AI document-intelligence pipelines, and government enterprise systems across Australia, Switzerland, the UAE, and the US. Available for remote contract and lead engagements — get in touch, contact@ehnand.com.