How Many Hours of Timezone Overlap Does a Remote Job Actually Need?

"We're flexible on timezone" is one of the least examined sentences in remote hiring. It sounds generous. Nobody asks what it costs until they're three months into a role, waiting until 9pm for a reply that was sent at 2pm somebody else's time. How many hours of timezone overlap for remote work does a role actually need? Almost nobody runs the number before accepting, which is strange, because that number is an important one to know when pursuing geo-flexible work.

The phrase survives because both sides benefit from leaving it vague. A recruiter gets to advertise a wider candidate pool. A candidate gets to believe the arrangement will bend around their life. Neither belief holds up once a sprint deadline lands on a Tuesday and somebody has to be awake at an hour they weren't told about. Answering how many hours of timezone overlap for remote work actually requires means doing the calculations before the offer, not renegotiating it after the first missed standup.

How do you calculate your actual overlap?

Start with the two working windows, not the two timezones. A nine-to-five in Lisbon and a nine-to-five in Austin sound like a six-hour gap. Line up the actual clock hours and the overlap is closer to two, once you account for the fact that nobody is fully present at 9:01am or 4:59pm.

Working across time zones remote job by remote job, the calculation is always the same. You take your end time and subtract their start time, converted to a shared reference. What's left is your true overlap, and it's almost always smaller than the headline gap between the two cities suggests.

Do this before you accept, not after. Ask the hiring manager directly what hours the rest of the team is typically online, rather than asking what timezone they're in. A city name tells you almost nothing about the schedule; the actual working hours tell you everything you need to know.

The 19% rule

Research out of Rice University puts a number on what a single missing hour does. Professor Tommy Fang and colleagues, examining daylight saving transitions as a natural experiment across more than 12,000 employees at a multinational firm, found that losing one hour from the workday produced a 19% loss in the overlap of business hours between colleagues. Communication volume dropped, but by less than the overlap itself shrank, meaning people compressed the same amount of talking into a smaller window rather than simply talking less.

Timezone overlap requirements aren't linear. Losing the second hour of overlap tends to hurt more than losing the first; not only are you trading away conversation time, you're also trading away the buffer that used to absorb a late start or an early wrap.

Is more timezone overlap always better?

A 2025 study in Research Policy, analyzing collaboration patterns across more than 20 million research articles, found that moderate temporal distance was associated with better outcomes than either full alignment or a near-total gap, with the effect strongest in roughly the four-to-six-hour band. Zero overlap loses too much shared time to coordinate. Full overlap loses the handoff advantage, the ability to pass work to someone starting fresh while you sleep.

Follow the sun working depends on that handoff. A support ticket opened in Sydney gets picked up in Lisbon before the customer wakes up again. The model only works for tasks that tolerate a clean pass-off involving support queues, quality assurance, and anything with a defined unit of work. It falls apart for creative or strategic work, where the thread of reasoning doesn't survive a handoff the way a ticket does.

The test is whether the next person needs your intent or just your output. A finished ticket, a passed test suite, and a translated document all carry their own instructions. A half-formed strategy memo doesn't. If the work you'd be handing off requires the receiver to guess what you were thinking, follow the sun working will produce more rework than it saves, no matter how clean the timezone calculations look on paper.

Who pays the cost?

One side of a partnership tends to absorb most of the early mornings or late nights that a partial overlap requires, and it's rarely split down the middle. Before accepting a role with a stated timezone overlap requirement, ask which side has been carrying the inconvenient half, because that answer is a preview into your own calendar six months out.

The pattern usually tracks organizational size rather than geography. A small team hiring its first person abroad tends to expect that person to absorb the gap, since the existing team's hours are already the default. A company built distributed from day one is more likely to rotate the inconvenient block, because nobody's schedule was ever the default in the first place. Ask how the company was built, as well as where the team sits, and you'll get a better read on who actually pays the cost.