On-Call Time Zones

Distributed rotation.

Overview

On-call time-zone design decides whether global engineering is a fair workplace or a midnight hazard. The discipline matters more than the number of rotations.

• Distributed rotation. Per-time-zone primary on-call; the rotation matches the team's actual geography.
• Follow-the-sun. Each region covers its own daytime; nights belong to the next region; nobody is paged at 3am.
• Per-region escalation. Secondary on-call lives in the same region; escalation is local, not transcontinental.
• Handoff rituals. Standardised end-of-shift handoff; the next region knows what is open before the first page.

The approach

The practical approach combines follow-the-sun rotation with per-region escalation and explicit handoff rituals. Each piece is small; together they produce sustainable global on-call.

• Follow-the-sun. Daytime on-call per time zone; the work day is the on-call shift.
• Per-region escalation. Local secondary; escalation paths stay within the region.
• Handoff rituals. Same template across regions; written, not verbal; the doc is the contract.
• Documented topology. Rotation written down per team; supports operational reviews and onboarding.

Why this compounds

Time-zone discipline pays off over years. The first region is investment; each subsequent region builds on the same playbook and the team's institutional knowledge grows.

• Retention. Less overnight on-call preserves teams; engineers in non-headquarters time zones get a fair life.
• Global coverage. Daytime response in every region; incidents do not wait for the headquarters office to wake up.
• Cultural signal. Fair rotation distribution; the team sees that leadership values their schedules.
• Compounding knowledge. Each region teaches global ops patterns; year 2+ is habit, not investment.