Hot Jobs Connect bot · €3

Home Blog Remote & relocation

Remote Job Time Zone Requirements: What CET ± 2 and Overlap Mean

· 6 min read

Remote job time zone requirements decide more applications than most people realise. A posting can be open to your country and still not fit, because it quietly expects you online until midnight. This article explains the common phrases (CET ± 2, "overlap with EST", async-first), shows how to work out your actual hours, and gives you a line to put in your applications so recruiters don't have to guess.

Why remote jobs care about time zones at all

A remote team still has meetings, code reviews, incidents and customers. Most companies want people to be reachable during some shared part of the day, and the easiest way to write that down is a time zone rule. It usually sits in one of three places: the location field ("Remote - Europe (CET ± 3)"), a line in the requirements, or a paragraph about how the team works near the end of the posting.

The rule is often more important than the country list. A company that can legally hire you in Georgia may still skip your application if its whole team works on US Pacific time.

Common phrases and what they usually mean

Phrase in the posting What it usually means
CET ± 2 hours Your working day should fall within two hours of Central European Time. Roughly London to Istanbul
EMEA time zones Anywhere from the UK to the Gulf, as long as your day overlaps with Europe
UK hours / GMT Work roughly 9:00–17:30 London time, wherever you are
4 hours overlap with EST At least four of your working hours must match 9:00–17:00 US Eastern
Core hours 10:00–15:00 CET Be online for that block; the rest of the day is flexible
Americas time zones Your day should sit inside North or South American hours
Async-first Most work happens in writing; meetings are few, but check whether any are fixed
Worldwide, any time zone Genuinely flexible hours are possible, but ask about on-call and meetings

Work out your real overlap in five minutes

  1. Convert everything to UTC. Central European Time is UTC+1 in winter and UTC+2 in summer. US Eastern is UTC−5 in winter and UTC−4 in summer. Tbilisi, Yerevan and Dubai are UTC+4 all year.
  2. Check daylight saving. Europe and the US change clocks on different dates, so for a few weeks in spring and about a week in autumn the gap between them is an hour shorter than usual. Georgia, Armenia, Kazakhstan and the UAE don't change clocks at all, so from Tbilisi, Yerevan or Dubai your gap to Berlin is three hours in winter and two in summer (from Almaty, four and three).
  3. Write out the team's day in your time. A 9:00–17:00 US Eastern day is 15:00–23:00 in Berlin or Belgrade, and 18:00–02:00 in Tbilisi in winter.
  4. Mark the hours you can really work. Not the hours you could survive for a month, the ones you could keep for a year alongside your life.
  5. Count the shared hours. If the posting asks for four hours with US Eastern and you're in Belgrade, a working day of 11:00–19:00 gets you there. From Tbilisi, the same requirement means working until about 22:00 in winter.

Some examples to calibrate:

  • Lisbon or London sits one hour behind CET, well inside "CET ± 2".
  • Cyprus is one hour ahead of CET all year, also inside.
  • Istanbul is two hours ahead of CET in winter and one in summer: inside.
  • Tbilisi, Yerevan, Dubai are three hours ahead of CET in winter, just outside a strict "± 2". Many teams won't mind, but ask rather than assume.
  • Almaty is four hours ahead of CET in winter. For "CET ± 2" roles, this needs a conversation.

Is "async" really async?

"Async-first" is a good sign, but it isn't a promise that you'll never have a fixed meeting. Before you plan your life around it, ask:

  • Are there recurring meetings I'd be expected to attend live? At what time, in your time zone?
  • Is there an on-call rotation, and which hours does it cover?
  • How quickly are people expected to answer messages?
  • Where do the people I'd work with most closely sit?

The last question matters most. A company can be spread across the world while your own team sits in one city. What decides your day is the team, not the company's headline policy.

Say your time zone before they ask

Recruiters screening quickly don't want to calculate time differences. Put one plain line near the top of your CV or in your cover note:

Based in Tbilisi (UTC+4). Comfortable working 10:00–19:00 CET, with later calls when needed.

It answers the question before the first call and shows you've read their requirement. If you're outside the stated range but can adjust, say so specifically ("I can shift my day to cover 14:00–18:00 US Eastern three days a week") rather than "flexible". For a broader checklist on reading postings, see how to read a job description.

When to skip, and when to apply anyway

Skip if the requirement means working late every night and you know you won't keep it up. Apply anyway if you're an hour or two outside the range, the rest fits, and you can explain how you'd cover the overlap: time zone lines are often written loosely.

Time zones are one half of the location question; the other is where a company can hire. We cover that in remote IT jobs actually open to Europe and, for region labels, in what EMEA means in a job posting. If you're looking at roles marked worldwide, read which "remote anywhere" jobs are really open as well.

A quick checklist

  1. Find the time zone rule: location field, requirements, or the "how we work" section.
  2. Convert the team's hours into your own, for both summer and winter.
  3. Count the shared hours you can keep long term.
  4. Ask about fixed meetings, on-call and where your immediate team sits.
  5. State your time zone and working hours in one line in your application.

Hot Jobs filters by region rather than by hours: you choose Remote · Europe & EMEA, Remote · Americas, Remote · Anywhere or your own cities, and each alert shows the posting's location string, so the time zone check takes a minute once you open the job. It's €3, paid once. Connect the bot