Overlap Finder: Check Your Team’s Time Zone Overlap
Overlap Finder
Before you move — or before you say yes to that offer — check how much of your actual workday will still line up with your team. Add your city and theirs, and see real, DST-aware overlap, computed live from your browser’s own timezone data.
Check your overlap
Best overlap windows
Does this handle daylight saving time?
Yes — every city above is recalculated live from real IANA timezone data, not a fixed offset. The catch: the US and the EU don’t change their clocks on the same date, so for a week or two each spring and fall, your overlap window can quietly drift by an hour without anything on your calendar changing. This tool always reflects today’s actual local time, DST included.
“What’s the time difference” is the wrong question
A raw time difference doesn’t tell you whether the move — or the job — will actually work day to day. It tells you what time it happens to be somewhere. What actually predicts whether you’ll be able to collaborate with your team in real time isn’t the hour offset, it’s how many usable overlap hours you share.
Research on distributed teams backs this up: each additional hour of timezone difference measurably cuts synchronous communication by roughly 11%, and across globally distributed teams, an estimated 43% of “synchronous” collaboration already happens outside someone’s normal working hours. Below about four hours of overlap, real-time coordination gets meaningfully harder — that’s the point where you should stop asking “what’s the time difference” and start asking “what will my actual day look like.”
What a 3-region spread actually feels like
A common shape when you’re the one relocating: your new home sits between two teammates’ time zones. Here’s what your day would actually look like.
If you’re the one who moves to Lisbon, this is roughly what you’d get: a solid morning-your-time overlap with New York, and a narrow early-morning-Singapore-time sliver in your late afternoon. New York and Singapore barely touch each other — but that’s not your problem. What matters is your window with each of them.
The practical read: your true 3-way overlap is thin, maybe an hour on a good day. That hour is the one you’d want reserved for anything that genuinely needs a live person — everything else should be able to wait. Load this scenario into the tool above ↑
How to make your overlap window work for you
- 1Reserve it for things that need a live human. Decisions, disagreements, unblocking, anything that would take five back-and-forth Slack messages — that’s what your overlap window is for.
- 2Push everything else to async. “Here’s where things stand” doesn’t need real time. If a team can’t work this way, that’s worth knowing before you sign, not after.
- 3Protect it fiercely. If your overlap is under four hours, it’s likely your only shot at live facetime each day — don’t let it get eaten by other people’s meetings.
- 4Re-check it before you commit, and twice a year after. DST shifts move your overlap window even when nobody touches a calendar invite. Re-run this tool after clocks change in March/April and October/November.
What near-zero overlap actually looks like to live
Overlap hours are rarely distributed evenly, and if you’re the newest or most distant remote hire, there’s a good chance you’re the one who ends up absorbing the early calls or late nights — often without anyone deciding that on purpose. Before you accept, ask directly: who currently takes the inconvenient slot, and does it rotate, or does it always fall on whoever’s furthest from headquarters? Surveys of distributed teams have found a large majority of employees feel meeting times favor one office or region over others — worth asking your future team what that actually looks like for them, not just what the offer implies.
Common questions
Does this account for daylight saving time?
Yes. Rather than using a fixed UTC offset, the tool reads each city’s real IANA timezone rules from your browser and recalculates local time for today’s actual date — so if you or your team has shifted onto or off daylight saving, that’s already reflected. Because the US and EU change their clocks on different dates each year, your overlap window can shift by an hour for a week or two each spring and fall. In 2026, the US shifts on March 8 and November 1; the EU shifts on March 29 and October 25 — roughly three weeks each way where the gap is a full hour off from what most people assume. Worth checking before you lock in a start date or a recurring call.
How much overlap do I need to not fall behind at work?
It depends more on your role than on any fixed rule. Roles built around live collaboration — engineering standups, product syncs — often run fine on 2–4 hours; client-facing roles like sales and support typically want 4–6 hours to match business hours where your clients are; some async-first companies (GitLab is a well-documented example) run on zero mandated overlap at all and coordinate through documentation instead of meetings. Use the tool above to see what you’d actually have before deciding whether it’s enough for how you work.
What does near-zero overlap with my team actually look like day to day?
With little to no daily overlap, live meetings stop being your default way to get help or make a decision — you’re working “follow-the-sun” instead, picking up written updates from a team that’s already asleep by the time you’re online, and going a full day between asking a question and getting an answer. It’s manageable for heads-down, well-scoped work; it’s harder if your job depends on quick unblocking or a lot of real-time back-and-forth. Load a scenario above to see roughly how many usable hours you’d actually share with your team.
What should I ask before accepting a remote job in a very different time zone?
What the team’s actual meeting cadence looks like day to day — not just the offer letter’s stated hours. Whether anyone else works from your time zone or nearby. And who currently takes the early or late calls, and whether that rotates. A team that’s never had to answer these questions probably hasn’t thought hard about how a distant hire fits into their day, which is itself useful to know before you sign.
Will working mostly async hurt my visibility on the team?
It can, mostly by default rather than by design — people who are awake and typing during the team’s daytime naturally show up more in decisions and casual context than someone who’s asleep for most of it. It’s not inevitable: teams that write things down well, and treat async contributions as real contributions, tend to close that gap. Worth asking directly how the team handles it, and watching in your first few weeks whether decisions get made in meetings you’re never in.