Timezone is the most underestimated filter in remote hiring. It is also the one people most often lie to themselves about.
Decode the overlap language
- "Must overlap 4 hours with PST" — a hard constraint, calculate it before applying
- "EMEA hours" — roughly UTC-1 to UTC+3
- "Async-friendly" — some meetings, but not a rigid schedule
- "Fully async" — rare, and usually means heavy written work
Do the arithmetic honestly
Write down the employer's core hours in your local time. If it means starting at 9pm every day, you will do it for three months and then resent it. Sustainable is more valuable than impressive.
Where your timezone is an advantage
Support and operations teams actively want coverage outside their home hours. If you are in a timezone that fills a gap for them, say so in the first line of your application; it turns your location from an obstacle into a reason to hire you.
Negotiating the overlap
Overlap requirements are sometimes softer than stated, especially for senior roles. Propose a specific window rather than asking for flexibility in the abstract. "I can be online 2pm to 7pm your time" gets a real answer.
Common questions
What is a normal timezone overlap requirement?
Four hours is the most common. Some teams ask for two, and highly collaborative roles sometimes ask for six.
Can I get a fully asynchronous remote job?
They exist but are uncommon. They tend to suit strong written communicators in engineering, writing and design.