# Distributed Teams Across Time Zones: An EM Playbook

Source: https://www.techinterview.org/post/3233475184/distributed-teams-across-time-zones/
Updated: 2026-05-05 · techinterview.org

Distributed teams are now standard. Many companies have engineering split across US East/West, EU, and Asia. The interview probes whether you understand the unique challenges of leading across time zones — handoffs, async work, and the dual-class dynamics that ruin distributed teams.

## The categories of distributed

- **Same continent, different cities:** mostly US east + west. Easy — 3-hour overlap.

- **Two continents, one large overlap:** US east + EU. 3–4 hour overlap mid-day.

- **Two continents, small overlap:** US west + EU. 1–2 hour overlap.

- **Three or more continents:** follow-the-sun. No real overlap.

Different patterns require different operating models.

## Standup across time zones

- Async written standup in shared Slack channel — read when you start your day

- Live standup with whoever is awake (rotates burden)

- Skip live; rely entirely on async

Most distributed teams default to async-written standup with optional live.

## Handoffs

For follow-the-sun teams:

- End-of-day status: what shipped, what is blocked

- Pickup-by-next-zone: clear ownership for in-flight work

- Documentation discipline: anyone can pick up where another left off

Without explicit handoffs, work stalls overnight.

## The dual-class trap

Bigger problem than is usually recognized. Symptoms:

- Headquarters team gets the strategic work; remote teams get execution

- Promotion decisions correlate with timezone — HQ wins

- "The decisions happen in person" — remote excluded

- Manager visits HQ but not other locations

Counter:

- Default to remote-friendly meetings (everyone joins by video, even those in same office)

- Strategic work distributed by team strength, not zone

- Calibration explicitly aware of zone effects

- Manager spends time in each zone

## Meeting culture

Distributed teams have less tolerance for bad meetings:

- Async-first by default

- Live meetings only when truly needed

- Recordings posted with summaries

- Schedule with all zones in mind — never always-the-same-zone-takes-the-late-meeting

## 1:1 cadence across zones

- Schedule consistent times

- Rotate which side takes the inconvenient time

- Video on by default

- Async follow-ups for actions decided

## On-call across zones

Follow-the-sun is the dream:

- Each zone owns on-call during their working hours

- Handoff at zone boundaries

- Reduces individual engineer burden dramatically

Caveat: requires team coverage in each zone. Without enough coverage, fallback is one zone covers most of the rotation.

## Hiring

Distributed hiring is harder:

- Time-zone alignment matters for collaboration

- Strong written communicators succeed; live-only thinkers struggle

- Self-management skills more critical than for HQ hires

Some teams require new hires to have at least 4 hours of overlap with existing team. Others go fully async.

## Building culture without offices

Hard but doable:

- Quarterly in-person off-sites

- Watercoolers replaced with Slack channels

- Pair programming via Tuple, Code With Me

- Casual hours (#random, donut bot for 1:1 introductions)

## The "founder mode" tension

Founder mode advice ("be in the work", "talk to engineers daily") works less naturally for distributed teams. Adapt:

- Founder reads team Slack channels

- Founder joins async standup

- Founder visits each location quarterly

## The interview probe

"How would you run a team distributed across 3 time zones?"

Strong answers describe specific operational practices, the dual-class trap, and the cultural investments needed.

## Frequently Asked Questions

### Should I avoid hiring in low-overlap zones?

Sometimes — for tightly collaborative teams. For independent feature teams, low-overlap can work with the right operating model.

### How do I handle a 24-hour incident across zones?

Single incident commander rotates across zones. Documented timeline. Hand off explicitly.

### Are some companies just bad at distributed teams?

Yes. Companies with strong office cultures often fail at distributed even when they say they support it. Diligence carefully if joining.