Working across time zones as a digital nomad sounds like a scheduling puzzle. Most days it is a sleep puzzle. You pick a city for the light, the rent, the food — then discover your workday belongs to a city nine hours behind you, and every stand-up lands at the hour you planned to be asleep or on a train somewhere. The fix is rarely a better app. It is deciding, before you book, which hours you are actually selling.
Get it right and the gap becomes the best part: quiet mornings nobody can book, and a handover waiting when your team wakes.
Working across time zones as a digital nomad starts with one decision
Name your anchor. One time zone runs your working week — usually your team’s or your main client’s — and every other choice hangs off it. The Muse’s guide to working across time zones puts knowing your time zones first for a reason: most blow-ups start with someone doing the maths in their head, wrong.
Lisbon on New York hours is an easy anchor: slow mornings to yourself, then an afternoon that lines up with their morning. Northern Thailand on the same anchor is a different life. Talent Pod Asia’s playbook for remote teams works the same maths for Vietnam, which shares Thailand’s UTC+7: 8 p.m. there is 9 a.m. in New York. Workable a few evenings a week. As a permanent address for your sleep, it eats you.
Choose the base for the anchor, not in spite of it. A beautiful city on a brutal offset is a holiday, not a headquarters.
Remote work time zone overlap: how much is enough
Less than you fear. Talent Pod Asia’s rule of thumb scales with the gap: under two hours apart needs no special process, three to six hours apart wants about four hours of overlap, and ten or more hours apart can run on one to two deliberate hours with the rest handled in writing.
Read that as permission. Two good overlap hours beat eight twitchy ones where you are half-present all day. Spend the shared window on what needs a human in real time — a blocked decision, feedback, something delicate — and let the rest move in writing.
The worked example sits in our Chiang Mai for remote workers guide. Chiang Mai is eleven to twelve hours ahead of the US East Coast depending on daylight saving, so a US-hours base there means two or three fixed evening call windows a week and async everything else. On European hours the same city is generous: your afternoon is their morning. Same desk, same city — the overlap decides whether it feels easy or punishing.
One trap hides in that maths: daylight saving. Thailand never shifts; the US and Europe do, on different dates. Your gap changes twice a year without anyone moving house, as Business Anywhere’s guide to time zone challenges for digital nomads warns, and standing calls slide an hour. Note the March and October changes and re-check every recurring meeting.
Async communication for remote workers does the heavy lifting
Async is not a lesser kind of communication. It is the kind that respects the gap. The Muse calls it your best friend on a spread-out team, with one condition: be explicit about deadlines, response times, and what counts as urgent. A message saying what is needed, by when, in whose time zone, lets the other person sleep. One saying “quick question?” at their midnight does the opposite.
Build the habit in both directions. Write updates your team can act on without you: what changed, what is blocked, what happens next. Record the two-minute video walkthrough instead of booking the thirty-minute call. Set a response rule you can keep — same day inside overlap, by the next overlap block outside it — and publish it. Talent Pod Asia uses exactly that split, and calls an undefined overlap, not a small one, the real failure mode.
And rotate the pain: if a call has to land at an awkward hour, The Muse’s advice is to alternate meeting times so the same person is not always setting an alarm for it.
Time zone tools for remote workers worth keeping open
You need three tools, not thirteen. A visual overlap checker — World Time Buddy is the one both The Muse and Business Anywhere point to — so you can see the shared window instead of calculating it. A calendar showing two time zones at once; Google Calendar does this, and it stops the classic error of booking in the wrong zone. And a booking link with your hours locked in your own zone, so clients pick slots that already protect your sleep, shown in their time automatically.
Small settings do quiet work after that. Scheduled send means the update you write at your 6 p.m. arrives at their 9 a.m., not their 11 p.m. Your city and working hours in your chat status save the “sorry, did I wake you?” exchange entirely. None of it is clever. It just removes the arithmetic from days when you are tired or jet-lagged.
Choose the base, then defend the edges
Before your next move, run the test in order. Where is your anchor? How many overlap hours does the new city give you inside a sane day? What will you refuse to do at 3 a.m. — written down before anyone asks?
That last question belongs in job applications too. Remote roles quietly assume a time zone, so read the requirement before the salary line — the Remote Job Postings spell out where each role expects you to be. A role wanting four daily overlap hours is a location decision disguised as a job offer. Take it from a city where those hours fall in daylight, and the map opens up. Take it blind, and you will spend a beautiful place asleep at the wrong end of the day.
Cover photo: the Weltzeituhr (World Time Clock) at Alexanderplatz, Berlin. Photo by Joe Mabel, via Wikimedia Commons (CC BY-SA 4.0).