In a one-way interview there's no live interviewer. Candidates open a link, answer a few questions by video, voice or text, and submit before the cutoff. A Friday cutoff in one time zone can fall on Saturday in another.

For the hiring side, give candidates about a week, say which time zone the cutoff is in, and review submissions together once it has passed. Jobicy has a longer piece on how to keep async video screening fair across time zones, and The Super Lede explains how one-way video interviews work if the format is new to you. This post is about the backend side, from building AnswerReel, where an automatic retry can leave the invite email showing one cutoff and the link enforcing another.

Store an instant, and start the clock when the email goes out

Each candidate row has an expires_at timestamptz. The job sets invite_validity_days to anywhere from 3 to 14 days, with 7 as the default.

"Sent" is doing some work there. An invite can sit in pending_send while the email provider is slow, or land in send_failed. If the clock started when the recruiter clicked Invite, those candidates would lose days they never had.

The first attempt sets the cutoff printed in the email. Retries reuse the same body so the provider accepts the same idempotency key. Once the provider accepts the email, we look up the job's current validity window and add it to the time the successful attempt started:

update app.candidates set first_sent_at = coalesce(first_sent_at, p_now), expires_at = case when first_sent_at is null then p_now + make_interval(days => v_days) else expires_at end where id = p_candidate_id; 

If the job's validity setting stays the same, a retry moves the link's cutoff later by the time between the first and the successful attempt. If the recruiter shortens the window in between, the link can close earlier than the email says. We count days from the send rather than computing "end of Friday in the candidate's local time", because when the invite goes out we don't know where the candidate is, and guessing from an email domain or the recruiter's office would be wrong often enough to matter.

Show it in a time zone the reader can check

The invite and reminder emails give the cutoff in UTC. In English it looks like "5:00 PM UTC on Friday, November 27".

// Candidate emails: we don't know their zone, so say UTC const day = date.toLocaleDateString("en-US", { weekday: "long", month: "long", day: "numeric", timeZone: "UTC" }); const time = date.toLocaleTimeString("en-US", { hour: "numeric", minute: "2-digit", timeZone: "UTC" }); return `${time} UTC on ${day}`; 

The recruiter's invite panel also uses UTC, for a different reason. It's rendered on the server and then hydrated in the browser. If the server formats in UTC and the browser in local time, the text doesn't match and hydration fails, so it's pinned to UTC and labelled.

The one place we use the browser's time zone is the makeup page. If a recording fails while we're processing a submission, the candidate has 24 hours from the failure to record that answer again. That page runs in their browser, so we format it with Intl.DateTimeFormat and no timeZone option, and the zone name is printed next to the time.

Don't cut off an upload that started in time

Say a candidate starts uploading a two-minute video at 16:58 UTC. On a slow connection, it can still be uploading at the 17:00 cutoff, and rejecting it would punish their bandwidth rather than their timing.

An interview still in progress can enter a grace state that lasts until one hour after the cutoff. That applies if an upload started before the cutoff and was still uploading or processing at the cutoff, or if a follow-up question created before the cutoff was still unanswered:

select exists ( select 1 from app.attempts a where a.candidate_id = v.id and a.upload_started_at < v.expires_at and (a.finished_at is null or a.finished_at >= v.expires_at) ) -- or a follow-up created before the cutoff that isn't answered yet 

During grace, candidates can finish uploads already under way, answer follow-ups created before the cutoff, record failed answers again, and submit.

The check runs both when the candidate does something on the page and in a sweep every minute. Because it compares timestamps rather than looking at the clock when the sweep runs, a recording that was uploading at 17:00 and finished processing at 17:00:30 still qualifies when the sweep gets to it at 17:00:50.

Remind relative to both ends of the window

Either reminder can land at 3 a.m. local time. For candidates who haven't submitted, we queue up to two reminders, one 48 hours after the invite and one 24 hours before the cutoff.

On a three-day invite those two times coincide. We skip the first reminder whenever the two scheduled times are less than 12 hours apart:

and c.first_sent_at + interval '48 hours' <= p_now and (c.expires_at - interval '24 hours') - (c.first_sent_at + interval '48 hours') >= interval '12 hours' and p_now < c.expires_at - interval '24 hours' 

The minute sweep locks candidate rows with for update ... skip locked and records each reminder on the row as it queues it, so a second sweep won't queue it again. Reminders are on by default, and recruiters can turn them off per job.

Extensions and closing a job early

A local public holiday can take a working day out of the window. While the job is open, a recruiter can reopen an expired invite if the candidate hasn't submitted. They pick a new cutoff 3 to 14 days from now, up to twice per candidate. The cutoff is capped at 42 days after the first send, so the actual window can be shorter than what they picked. The candidate gets an email with the new cutoff that says the link is the same and anything they already saved is still there.

Closing a job works the other way. Invites expire immediately for candidates who haven't started the interview, even if they've opened the link, and queued or failed sends are revoked. For interviews in progress, the cutoff moves to 24 hours after the job closed if it was later than that. A cutoff two hours away stays two hours away. The one-hour grace rule still applies at the new cutoff, and anyone already in grace keeps their grace end time.

The timestamps don't decide who gets reviewed first

Every submission has a submitted_at, and it's tempting to sort the review queue by it. We'd rather recruiters didn't. Someone who gets the invite over breakfast may see it hours before someone whose invite arrives overnight. That alone is a good reason to wait for the cutoff and score everyone against the same written criteria. If several people are scoring, the interview scorecard template for LibreOffice has a printable card for up to six criteria, scored from 1 to 5. Its Calc sheet gives each candidate a column, skips blanks and shows how many criteria were scored.

I work on AnswerReel. The candidate statuses mentioned here, including grace, are listed in the AnswerReel API and webhook docs if you're integrating with it.

I used AI to help draft this post.