What is time zone overlap and why does it matter for remote teams?
Time zone overlap is the number of hours per day that two people in different time zones are both at work. It is the single best predictor of how a distributed engineering engagement will feel, because it determines whether a blocked task is unblocked in fifteen minutes or the next morning.
Overlap is arithmetic, not opinion, and it is worth calculating rather than accepting a vendor’s adjective. Convert both workdays to UTC and intersect them. A Brazilian engineer working 9 AM to 6 PM local is online 12:00–21:00 UTC; a New York team working 9 to 5 is online 13:00–21:00 UTC in summer. The intersection is eight hours.
Run the same calculation for India and the result is zero on ordinary hours, which is why offshore delivery models are built around night shifts. That is a legitimate arrangement when designed deliberately, and a retention problem when it is treated as free.
Three to four hours of overlap is usually enough for a functioning engagement if the team writes things down. Below two, you need a person whose job is managing the handoff, and that person is more expensive than the hourly savings.
Key points
- Convert both workdays to UTC and intersect — do not compare local clock times.
- Brazil shares 7–8 hours with U.S. Eastern on ordinary hours; India shares zero.
- Below two hours of overlap you need a dedicated handoff manager.
- Extending overlap by shifting someone’s day is a real cost to them, not a free feature.
Frequently asked questions
How much overlap is enough?
Four or more hours works comfortably for most product teams. Two to four works with strong written communication. Below two requires someone managing the handoff full time.
Related
Other definitions
Tell us the role. We come back with candidates.
A 20-minute call to scope the role, then vetted profiles within five business days. No fee to talk, no retainer, no exclusivity.