Guides

Working across timezones: what overlap really costs you

A remote job that is open to your country can still ask for hours that do not suit your day, so learn to read the overlap clause and answer it well.

Timezones are the quiet filter in remote hiring. An ad can be open to the whole world and still expect you to be online at a time that sits in the middle of your night. This guide is for people who live far from the team they would join. It covers how to read overlap language, what overlap costs in practice, how asynchronous habits shrink it, and how to talk about it in an interview. For the country side of the question, see Remote, but from where?.

What the clause usually looks like

Overlap language comes in a few common shapes:

• A named zone. "Must work in US Eastern time", "UK hours".
• A range of offsets. "Within three hours of UTC", "UTC-3 to UTC+3".
• A number of shared hours. "At least four hours of overlap with the team".
• A soft preference. "Ideally overlapping with European mornings".
• Silence. Nothing is said, but the interview schedule and meeting times tell the story.

These are different animals. A named zone is a requirement. A preference is an invitation to negotiate. A number of shared hours is the most useful form, because you can work out exactly what it means for your day.

A timezone clause is not the same as a country rule, and on our board a listing can be open to every country while its ad still mentions hours. We quote the ad on each listing, so the clause is there to read. Our about page explains the quote.

Do the arithmetic before you apply

Take the team's working hours, convert them to your clock, and write down what your day would look like. Do it properly, including daylight saving, which does not start and end on the same dates in every country, and which some places do not use at all.

An example, with round numbers so the point is clear. A team works 9:00 to 17:00 in a zone that is nine hours behind yours. Their 9:00 is your 18:00 and their 17:00 is your 02:00. "Four hours of overlap" could mean you work from, say, 18:00 to 22:00, and use the rest of your day however it suits. That is a very different life from a role that needs you awake until 02:00.

Put it in a small table for yourself:

| Their time | Your time | What you would be doing | |---|---|---| | Start of their day | ? | ? | | Their lunch | ? | ? | | End of their day | ? | ? |

Then ask the question that matters: could I do this every week for a year?

What overlap really costs

The cost is rarely the hours on paper. It is what the hours push out.

Sleep and routine. Regular late evenings or early mornings add up. Some people adapt well. Others find a shifted schedule wears them down. Be realistic about which you are.

Family and social time. If the overlap lands at dinner or bedtime, someone else absorbs the cost. Raise it with them before you commit, not after.

Health and exercise. The first things to go when the day is squeezed.

Meetings piling into one block. When overlap is short, every meeting competes for the same slot, and your protected focus time is the part that gets eaten.

Being the one who always adjusts. In a distributed team, the people in the minority zone often carry the inconvenience. Ask whether meeting times rotate or whether the same people always take the awkward slot.

None of this makes a distant timezone a bad choice. Many people do it well. It is simply a cost that belongs in your decision, next to salary.

Core hours, and what they mean

Some teams define core hours: a window when everybody is expected to be reachable, with flexibility outside it. A narrow core, for example a few hours a day, is a good sign for distributed work. A wide one, which stretches to most of a working day, behaves more like a fixed shift.

Ask:

• What are the core hours, in whose timezone, and are they fixed or negotiable?
• Are they every day, or only on some days?
• What happens outside them: is a reply expected in an hour, or by the next working day?

Those last two answers say a lot about the culture.

Habits that shrink the overlap you need

Asynchronous work means doing your job without needing the other person at the same moment. Teams that do it well need less overlap, and people who bring those habits are easier to hire into a distant zone. A few practical ones:

Write things down so they stand alone. A message that says "can we talk about the thing?" costs a day. A message that explains the context, states the decision needed and offers a default lets someone act while you sleep.

Make decisions in writing. A short note of what was decided, why and who owns the next step spares everyone a meeting.

Hand over cleanly. At the end of your day, leave a note: what is done, what is blocked, what you need. At the start of theirs, they pick it up without waiting for you.

Batch your questions. Instead of five small pings, send one organised message. You are more likely to get one complete answer.

Record and summarise. If a meeting happens at an awkward hour, recording it or writing a short summary lets people in other zones catch up without attending live.

State your availability. Put your working hours and timezone in your profile and signature. It lowers friction before anyone has to ask.

Be explicit about urgency. Tell people what really needs a quick reply and what can wait a day.

How to answer the overlap question in interviews

Interviewers often ask: "Are you comfortable with our hours?" Resist the reflex to say "yes, no problem" before you have done the arithmetic. Say what you have worked out.

A reasonable shape for your answer:

1. Show you have looked. "I worked out that your core hours fall between six and ten in my evening."
2. Say what you can do. "I can reliably cover that window, and I can shift when something is urgent."
3. Be clear about limits. "What I can't do is be online past midnight most days. Is that expected?"
4. Offer your async habits. "In my last role I wrote handover notes at the end of each day so the other zone could pick up where I left off."
5. Ask how the team handles it. "How do you share the awkward meeting slots?"

That reads as someone who has thought it through, which is exactly what a team spread over several zones wants. Be honest. If the hours really would not work, saying so early saves everybody time. The wider topic of presenting yourself is in Applying to remote jobs from outside the usual countries.

Questions worth asking

• Where are the team members based, and how many zones does the team span?
• Which meetings are mandatory and which are recorded?
• Is on-call involved, and how is it shared?
• Does the company expect different hours during a launch or an incident?
• Are there any occasions when you would need to travel, such as a planning week, and which time would that fall in? Business travel is part of what we allow on the board, as explained in How to spot a job that is not really remote.

Also ask how hours relate to pay arrangements if you are a contractor: some contracts specify availability windows. That is covered in Employee, contractor or employer of record.

When to walk away

If the required hours would force a schedule you could not keep for a year, say no. A job you quietly resent after three months helps neither of you. If the fit is close, though, a negotiated arrangement often works: a shifted start two days a week, a rotation of meeting times, or a team that agrees to record the awkward ones.

You can browse current roles, and read the quoted words from each ad, on JobsFromAnywhere.