TL;DR — Time-zone overlap is how many of your working hours coincide with the team's. Most remote roles that look location-free carry an overlap requirement — commonly "4 hours overlap with US Eastern" or "must be within ±3 of CET" — and it disqualifies more remote applicants than any skills gap.
Time-zone overlap is the number of hours in a day when you and your colleagues are both online. A role advertised as "remote — anywhere" that asks for four hours of overlap with US Pacific is not, in practice, anywhere: from Central Europe that means working until 8pm, and from India it is not workable at all.
This is the requirement that catches people out, because it is rarely in the title, often buried in the middle of a posting, and sometimes only surfaced in the first screening call.
How employers phrase it
Of the remote roles we track, 668 state an overlap requirement explicitly — "4+ hours of overlap", "core hours 10am–2pm ET", "must be within ±3 hours of CET". A further 1,373 describe themselves as asynchronous or async-first, which is the opposite promise: little or no overlap needed.
Together that is under 5% of listings. The rest say nothing at all — and silence usually means the team's own time zone by default, not freedom.
Common formulations, and what each really asks:
| Phrasing | What it means |
| "4 hours overlap with EST" | Your day must include 9am–1pm New York time |
| "Core hours 10–2 CET" | Fixed meeting window; the rest is yours |
| "US time zones only" | A hard location filter, stated as a schedule |
| "Async-first" | Overlap is genuinely optional |
| "EMEA-friendly hours" | Usually ±2–3 hours of CET |
Why it exists
Overlap is not arbitrary. Teams need it for the parts of work that are genuinely synchronous: incident response, live pairing, standups where decisions get made, and onboarding — which is far harder with no shared hours. The honest version of the requirement is "here is the part of our work we have not made asynchronous yet".
Which is why the number varies so much. A support team may need eight hours of coverage; a mature async engineering team may need two, or none.
How to work with it
- Search for the phrase, not just the location. "Overlap", "core hours" and "async" are the words that decide whether a role is open to you.
- Read the whole posting before applying. Overlap requirements appear in the middle far more often than at the top.
- Ask in the first call if it is unstated. "What hours does the team actually need me online?" is a normal question and saves both sides a round.
- Treat "async-first" as a claim to verify. Ask how many recurring meetings there are and when they sit. A genuinely async team can answer immediately.
- Count the cost honestly. A four-hour overlap that puts you online 2pm–10pm every day is a real lifestyle change, not a detail.
Frequently Asked Questions
How many hours of overlap do remote jobs usually require?
Where it is stated, four hours is the most common ask, with two to three hours typical for async-leaning teams and full-day coverage for support and operations roles. Most listings state nothing, which usually means the team's own hours.
What does "async-first" actually mean?
That the team's default is written, non-blocking communication — decisions recorded in documents rather than made in meetings — so shared hours are not required to do the work. About 1,373 of the remote roles we track describe themselves this way.
Can I negotiate the overlap requirement?
Sometimes, especially if the number was set for a meeting cadence rather than for coverage. Come with a specific proposal — which hours you would cover and how you would handle what falls outside them — rather than asking for less.
Why do "remote anywhere" jobs still ask for time zones?
Because "anywhere" is usually about not requiring an office, not about being time-zone free. Employment law and payroll add a second constraint: a company can often only employ people in countries where it has a legal entity or an employer-of-record arrangement.
RemoteHunt reads the full posting, not just the title, and scores each role against your profile — including the requirements that only appear halfway down. Start for free.