Book cross-border interviews without time-zone errors

The scheduler reads the calendars of every panel member, applies each person's own working hours in their own zone, and returns the intersection. What comes back is the set of times when all of them are genuinely available on a working day, which for a three-country panel is often a narrow band and is worth seeing explicitly rather than discovering through four rounds of email.

Where no full-panel slot exists inside everyone's normal hours, the scheduler says so and shows the nearest options with the compromise named: this slot requires the Bengaluru interviewer at seven in the evening, this one requires the Austin manager at seven in the morning. Making the trade-off visible lets a coordinator ask the right person rather than guessing.

Panel members can be marked required or optional, so a slot that misses an optional interviewer is offered rather than suppressed.

There is one rule underneath the whole feature: no person is ever shown a time they have to convert. The candidate sees their zone. The hiring manager sees theirs. The recruiter sees theirs. The same slot appears three different ways and refers to one instant.

Calendar invitations carry the correct zone data rather than a bare time, so the entry lands correctly in whatever calendar application each participant uses and stays correct if they travel. Confirmation and reminder messages restate the time in the recipient's zone, with the zone named in words rather than as an abbreviation, since abbreviations are ambiguous across regions and are a common source of exactly this error.

Daylight-saving is where naive scheduling breaks in ways that look like ghosts. The United States, the European Union, the United Kingdom and Australia change on different dates. India, most of the Gulf and much of Asia do not change at all. An interview booked in early March for late March can shift by an hour relative to a participant in another region, and a system that stored a fixed offset will get it wrong.

Times are held as an instant with a named zone rather than as an offset, and every display is resolved for the actual date of the meeting. A recurring interview series that crosses a transition adjusts, and where a transition changes the relationship between two participants the scheduler flags it during booking rather than letting it surprise everyone on the day.

This also covers the awkward cases: a local time that does not exist because the clocks jumped forward over it, and one that occurs twice because they went back.

A candidate is the participant with the least context, the most at stake and no ability to check the arrangement against a colleague. They receive a booking link showing slots in their own zone, choose one, and get a confirmation and reminders in that zone through the channel they consented to.

If a candidate has moved or is travelling, they can set the zone they will actually be in, and everything they see updates. That is a common case in cross-border hiring and it is one that written invitations handle particularly badly.

Reminders go out on a configurable interval before the slot, computed against the real instant rather than a stored local time, which is the specific bug that sends a reminder an hour after the interview started.

Interview scheduling is a shipping feature: panel availability, held slots, candidate self-selection, reschedule notices and reminders exist in the product today. The time-zone work described on this page is an extension of that scheduler, in build for Wave 1, and it is the cross-border layer rather than a separate product.

That distinction matters when you are evaluating. If your panels and candidates sit in one country, the scheduler already does what you need. If they do not, the parts that make a three-country panel painless are being built now and are not there yet.

It will not decide that an interview at ten at night is acceptable because a model judged the candidate keen. Out-of-hours slots are offered as compromises with the cost named, and a person chooses.

It will not conduct the interview, translate it, or assess anybody. Where a call is recorded and transcribed, that follows the recording rules described in the compliance matrix, including jurisdictions where recording is disabled rather than assumed.

It will not fix a calendar that is not connected. A panel member whose calendar is not integrated appears as unknown availability rather than as free, because treating unknown as free is how double-bookings get created.