Timezone app icon Timezone

HIRING AND ONBOARDING SOMEONE FAR AWAY

We hired someone eight zones away and nobody checked the overlap

Great candidate, signed the offer, started Monday. The shared working window turns out to be about ninety minutes.

The short answer

An 8-hour UTC offset gap reduces a standard 09:00–17:00 workday overlap to 0 hours (or 1–2 hours if one side extends to 18:00), requiring asynchronous written handoffs and a protected 60–90 minute synchronous window.

The hiring process went well. Strong interviews, good references, the offer was accepted inside a week. Everyone was pleased.

Nobody, at any point, opened a clock and asked how many hours a day this person would actually be able to talk to the rest of the team.

The answer turned out to be about ninety minutes.

How Many Shared Work Hours Exist Eight Time Zones Apart?

It takes a minute. Take the new hire's normal working day, take the team's, and look at where they intersect.

An eight-hour gap between two nine-to-five days leaves one hour of overlap. Nine hours leaves none at all. That is not a communication style problem or an onboarding problem — it is arithmetic, and it was knowable before the offer went out.

Some real shapes, with an ordinary waking window on both sides:

  • New York ↔ London — a genuinely comfortable overlap; most of the London afternoon meets most of the New York morning.
  • Berlin ↔ Singapore — workable, concentrated in the European morning.
  • New York ↔ Bengaluru — roughly four and a half hours, and both ends of it are unsociable: early US morning, late Indian evening.
  • London ↔ Sydney — the hard one. Whatever you find sits at the very edge of somebody's day.

Can a One- or Two-Hour Overlap Work With Strong Async Habits?

Plenty of teams work like this successfully. But it only works if it is designed for, deliberately, before the person starts — not discovered in week three when they have been sitting on a blocked task for two days waiting for an answer.

What actually makes it work:

Write things down by default. If the overlap is ninety minutes, anything that requires a synchronous conversation to unblock will cost a day. Decisions, context and rationale have to exist in text, or the remote hire spends most of their week waiting.

Spend the overlap on the things only humans-in-real-time can do. Unblocking, judgement calls, relationship. Not status updates — those belong in writing, and using the shared hour for them is the most common way teams waste it.

Give them a real decision boundary. Someone eight zones out who has to ask permission is idle for half of every day. The scope of what they can decide alone matters more than it would for a colleague down the hall.

Name who covers the gap. One person on the main team who is genuinely responsible for answering during the overlap, so questions do not evaporate.

What Time-Zone Expectations Should Be Agreed Before Onboarding?

The honest version helps both sides:

"Our overlap will be about two hours a day, roughly 8–10am your time. Most coordination happens in writing. Does that work for how you like to operate?"

Some candidates want exactly that. Others will tell you it would make them miserable, which is far cheaper to learn in an interview than in month two.

How Much Does an Eight-Hour Gap Shift When Clocks Change?

The overlap is not fixed. If one country observes daylight saving and the other does not — India does not, most of the US does — the shared window moves by an hour twice a year, and it can move in the direction that shortens it. See IST to EST.

Related: Somebody on this team is always taking the call at 6am · The handoff window nobody can agree on

Timezone & World Clock Widget app icon

Timezone & World Clock Widget

A world clock, converter and live day/night map for iPhone — 325 cities, offline, no account.

What it does

Figures on this page are computed from the IANA time zone database. Last generated 2026-11-18.