Time Zone Overlap for Remote Jobs: How to Play the Game

You see a remote job. The JD says "must overlap with PT for at least 4 hours daily." You live on the other side of the planet.

Apply anyway? Skip it? Lie about your time zone?

Time zone requirements are the most underrated filter in remote hiring. Get them wrong and your application dies in 5 seconds. Play them well and you unlock 10x more jobs than your competitors.

What time zone overlap actually means#

When a company says "must overlap with [time zone] for X hours," they mean: there is at least one team meeting, async cycle, or live working window where you must be available.

For example:

• "Must overlap with PT for 4 hours" usually means 9am to 1pm Pacific must be your working time.
• "Must overlap with EU hours" usually means your day overlaps with 9am to 5pm Central European Time.
• "Must work US business hours" means your full day is on US time.

Different requirements have very different lifestyle implications.

Why companies care#

A few reasons:

1. Synchronous meetings. Even "async" teams have at least one weekly standup or 1:1.
2. Customer support. If you cover customers, you need to be online when they are.
3. Time-sensitive decisions. Engineering and product teams often need 2 to 4 hours of overlap to unblock each other.
4. Cultural cohesion. Some companies just feel uncomfortable with 12-hour gaps between teammates.

The most common requirement in 2026: 3 to 4 hours of overlap with the company's "home time zone."

The reality of common time zones#

Let me map out what overlap actually looks like:

US Pacific Time (PT) team, you in Europe

• Your 6pm to 10pm = their 9am to 1pm
• Doable, but you are working evenings
• Not sustainable long-term for most people

US Eastern Time (ET) team, you in Europe

• Your 3pm to 7pm = their 9am to 1pm
• Much more humane
• This is the sweet spot for many US-Europe arrangements

US team, you in Asia

• Your 10pm to 2am = their 9am to 1pm (Pacific)
• Brutal unless you are a night owl
• Most US companies will not hire you unless they really want to

EU team, you in US

• Your 3am to 7am = their 9am to 1pm
• Almost impossible long-term
• Most EU companies prefer EU-based candidates

Async teams (any location)

• No required overlap, you just need to attend 1 or 2 weekly meetings at flexible times
• The dream

Companies with the loosest time zone requirements#

These companies hire across many time zones without strict overlap requirements:

1. GitLab: 100% async, no hard time zone requirement. Two weekly meetings you can join at any of multiple time slots.
2. Automattic: similar. P2 blogs over real-time chat.
3. Doist: 4-hour overlap with your team only, picked when you join.
4. Plausible: 4-day work week, async, very flexible.
5. Posthog: async with optional weekly meetings.
6. Tailscale: distributed across many time zones, light meeting load.

Companies with strict time zone requirements#

These often require near-full overlap with their home base:

• Most YC-backed early-stage startups (US-hours expected)
• Customer-facing roles at any SaaS company
• Sales teams
• Live support roles
• Most US "remote" jobs at big tech

How to play time zones in your application#

1. State your time zone clearly

In your cover letter and resume, write your time zone explicitly:

"Based in Lisbon, Portugal (UTC+1). I overlap 5+ hours daily with US Eastern Time."

This pre-empts the question and shows you have thought about it.

2. Match yourself to roles you can actually do

If the JD says "overlap with PT 4+ hours," do the math. If your overlap is only 2 hours without working insane hours, skip the job. Do not apply hoping to negotiate later.

3. Address the time zone concern in the cover letter

If you are in a tricky time zone, mention it directly:

"I know my time zone (UTC+8) requires planning to overlap with US teams. In my current role, I overlap 4 hours daily with my US-based teammates by working from 11pm to 8am local time three days a week. I find this arrangement productive and sustainable, but I am open to discussing what works best for your team."

This shows self-awareness and proactiveness.

4. Highlight async work experience

If you can show that you have thrived in async environments before, time zones matter less:

"Led a fully async product team across 6 time zones. We shipped 3 major features in Q4 without any required overlap, using written specs, Loom demos, and weekly async retros."

How to negotiate flexibility#

Once you are in the interview process, you can negotiate. Here is how.

Ask the right questions

In the screening call:

1. "What does a typical day look like in terms of meetings and async work?"
2. "How much overlap is required with [home time zone]?"
3. "Is the overlap a hard requirement or a guideline?"
4. "Are there roles or teams that have looser time zone requirements?"

Listen carefully to the answers. "Hard requirement" is non-negotiable. "We prefer" or "we typically" gives you room to push.

Offer trade-offs

If you cannot meet the standard overlap, propose alternatives:

• "I can do 2 hours overlap daily, plus full overlap one day a week for team meetings."
• "I am happy to work split shifts (morning and evening) to maximize overlap."
• "I would propose a 30-day trial where I work US hours, and we evaluate together."

The point is to come with solutions, not problems.

Lean into your strengths

A candidate willing to work odd hours for the right role is sometimes more attractive than someone in the perfect time zone who is mediocre.

"Yes, I am in Asia and your team is in the US. That said, I run my mornings entirely on async work and own my afternoons for live collaboration with your team. This actually frees me up to do deep work without interruption in my morning."

The "follow the sun" model#

Some teams hire across time zones intentionally so work continues 24 hours a day:

• Asia handoff to Europe
• Europe handoff to US
• US handoff back to Asia

This works for customer support, monitoring/ops, and large engineering teams.

If you are in an "off" time zone for a US-centric team, see if they have a "follow the sun" model. It might be your way in.

How to actually live in a tough time zone arrangement#

If you accept a role with awkward overlap, here is how to survive:

1. Time-block ruthlessly

Mornings = your own deep work. Evenings = overlap and meetings. No mixing.

2. Protect your sleep

If you are working until 1am for overlap, do not start at 7am the next day. Shift your whole day.

3. Use async for everything possible

Push as much communication into Slack, Notion, and Loom as possible. The fewer live meetings, the better.

4. Renegotiate after 6 months

Once you have proven your value, ask to reduce overlap. "I have shown I can deliver. Can we reduce required overlap to 2 hours so I can sustain this long-term?"

Most reasonable managers will agree.

5. Watch for burnout

Working off-hours catches up to people. Track your sleep and energy. If you are getting burned out, raise it with your manager before you crash.

Time zones and pay#

A side note: some companies adjust pay by location, partly tied to time zone.

• US-time-zone-overlap roles often pay full US salaries.
• "Anywhere" roles sometimes pay lower because they assume the candidate is in a cheaper country.
• Some companies (GitLab, Buffer) use transparent pay formulas that adjust by location.

When you negotiate, ask: "Is this salary tied to a specific time zone or location?"

The bottom line#

Time zone overlap decides which remote jobs you can actually win. Be honest about your situation, state your time zone clearly, and target jobs where the overlap math works.

For tough time zones, lean into async-first companies. For sync-heavy roles, be willing to work weird hours or move on.

Ready to apply? Try JobRise's free cover letter generator. Paste any remote job description and get a tailored letter that addresses time zone clearly. Free, no signup.