You found a remote role that fits your skills exactly, you spent an hour on the application, and a recruiter passed because you live nine hours ahead of the team. Nothing in the posting said "location matters," but a single line buried in the requirements did the filtering: "must have at least 4 hours of overlap with PST." That sentence quietly removes more applicants than any skills gap, and most candidates never see it coming because it sits below the salary, the stack, and the perks. This guide shows you how to read those lines, calculate your real overlap before you apply, judge whether a schedule is actually livable, and pitch your zone as a reason to hire you instead of a reason to skip you.

What "4 hours overlap with PST" actually means

Overlap is the number of hours your working day shares with the team's core hours. When a posting says "4 hours overlap with PST," it almost always means the company expects core collaboration hours of roughly 9:00 a.m. to 5:00 p.m. Pacific time, and you need to be awake, online, and reasonably sharp for at least four of those hours. It is not asking you to relocate or to work a full Pacific day. It is asking for a guaranteed window when you can join standups, answer Slack within minutes, and sit in meetings without checking the clock against your bedtime.

Two details trip people up. First, "PST" and "PDT" are often used loosely. From roughly mid-March to early November the US West Coast is on daylight time (PDT, UTC-7) rather than standard time (PST, UTC-8). That one-hour shift can move your overlap in or out of the acceptable range, so the same posting can be a yes in July and a no in January. Second, "overlap" usually means core hours, not the company's full open-to-close span. A team that is technically online from 6:00 a.m. to 8:00 p.m. Pacific may still require your four hours to land inside a narrow 10:00 a.m. to 3:00 p.m. core block, so read whether they define core hours anywhere before you assume the wider window applies.

How to compute your overlap with any target zone

You can do this in under two minutes with a single conversion. The reliable method is to translate both schedules into UTC, find where the windows intersect, then translate the result back to your local clock. UTC does not observe daylight saving, which makes it the one stable reference point when two countries shift their clocks on different dates.

That worked example is deliberately discouraging because it is realistic: a standard Western European day simply does not reach four hours into a Pacific afternoon without someone working late. Tools speed up the check. Meeting Planner on timeanddate.com, the World Clock feature in Google Calendar, and worldtimebuddy.com all let you drag a band across multiple cities and see the shared hours shaded. Use them to sanity-check your manual math, especially across daylight-saving boundaries, which shift roughly twice a year and not on the same dates in every country: the EU changes on the last Sunday of March and October, while the US changes in mid-March and early November, leaving a two-to-three-week window each spring and autumn when the usual offset is off by an hour.

Async-heavy vs sync-heavy roles, and how to tell

Overlap matters far less in async-heavy roles, where work is handed off in writing and judged on output rather than presence. It matters enormously in sync-heavy roles built around live meetings, pairing, on-call rotations, or real-time customer contact. The posting usually signals which one you are looking at, if you know the tells.

Is the schedule actually sustainable?

Meeting the overlap on paper is not the same as living it for two years. The classic strain case is an EMEA applicant covering US hours. To get four hours of overlap with 9:00 a.m. to 5:00 p.m. Pacific, someone in Western Europe is typically online until 9:00, 10:00, or 11:00 p.m. local time, every weekday. That is workable for some people and corrosive for others, especially with school-age kids, a partner on a normal schedule, or a commute-free routine that nonetheless ends after the family has gone to bed.

Be honest before you commit. Ask whether the late hours are every day or only on meeting days, whether deep-focus work can move to your morning, and whether the team rotates meeting times so the burden is shared rather than always landing on the person furthest east. As a rough rule of thumb, a role requiring more than about three hours of routine evening or pre-dawn work, with no flexibility, tends to wear thin within a year, no matter how good the job looks on day one.

Negotiating and clarifying overlap

Overlap requirements are often softer than they read, because they were written for a default candidate the recruiter imagined rather than for you specifically. Clarify early, ideally in a first call, so you do not over-invest in a role that cannot bend. Frame it as logistics, not a complaint.

Turning your zone into an advantage

Some zones are genuinely better matches, and naming that helps you. Latin American applicants from roughly UTC-3 to UTC-6 (think Buenos Aires, Sao Paulo, Bogota, or Mexico City) overlap almost perfectly with US business hours with no late nights, which is one reason US companies increasingly prefer LatAm for sync-heavy roles. If you are far from the team's core hours, pitch the opposite benefit: follow-the-sun coverage. An applicant in Asia-Pacific can own the hours when the US team is asleep, extending support, monitoring, or release watch without anyone working nights. Position it as a deliverable, not an apology: "I close out issues before your day starts, so you wake up to a clear queue."

Quick checklist before you apply

Time-zone rules, daylight-saving dates, and any tax or labor implications of working across borders vary by country and change over time. Treat the examples here as a starting framework as of 2026, confirm the current offsets and core hours with the employer, and for any legal, payroll, or tax questions about cross-border remote work, consult a qualified professional in the relevant jurisdiction.