Timezone

INTERVIEWS BOOKED ACROSS ZONES

I joined the interview an hour late and it was not my fault

The invite said 3pm. It did not say whose. You were on the call at 3pm exactly, and it had started an hour before.

You were early, in fact. On the call at 2:55, camera checked, notes open.

At 3:10 you emailed to ask whether the link was right. The reply came back politely: the interview had been at 3pm their time, they had waited fifteen minutes, and could you reschedule for next week.

How the invite failed

The message said "3pm." Somewhere upstream, a human typed a time into a form without a zone, or pasted it into an email, and every system after that rendered it as plain text rather than as an instant.

The failure modes are all mundane:

  • A time written in the email body but not attached to a calendar event, so nothing converted it.
  • A calendar invite created in the recruiter's zone, but the time also restated in the body — where it does not convert — and you read the body.
  • An abbreviation like "3pm EST" in July, which is not a real time and which some tools resolve to UTC−5 while humans read as "New York." An hour of error, right there. See EST vs EDT.
  • A reschedule agreed in a chat thread, in words, that never made it back into the calendar.

None of these are your carelessness. But the cost lands on you regardless, which is the reason to defend against them anyway.

What to do in the first five minutes

If you are the one who is late and you think the invite was ambiguous, say so plainly, once, without arguing:

"I'm so sorry — I had 3pm in my own zone and joined then. That's on the ambiguity in the invite, but I should have confirmed. I'm free now and any time tomorrow if that's easier."

Own the outcome, name the cause in one clause, offer the fix. Most interviewers have watched this happen and will reschedule. Litigating whose fault it was will not help you and will be remembered.

The check that takes ten seconds

Before any interview across zones:

  1. Open the calendar event itself, not the email. A properly created event shows the time in your zone automatically. If the event and the email body disagree, the event is usually right — but ask.
  2. If the time was only ever written in text, reply to confirm. One line: "Confirming 3pm New York — that's 9pm for me here in Prague. See you then." This is not fussy. Recruiters routinely correct it, which tells you how often it is wrong.
  3. Set the reminder against the converted time, not the number you were sent.

The dates when it is most likely to go wrong

Interviews scheduled a week or two out, across the Atlantic, in mid-March or late October, are the highest-risk of all. The US and Europe change their clocks on different weekends, so a time agreed before the transition and held after it can move by an hour on one side only.

If your interview falls near either window, confirming the zone is not paranoia. See Convert EST to GMT.

Related: They said EOD and I don't know whose day · EST vs EDT

Timezone: World Clock Widget

A world clock, converter and live day/night map for iPhone — 325 cities, offline, no account.

What it does

Figures on this page are computed from the IANA time zone database. Last generated 2026-08-18.