Interview loops that respect a candidate in another time zone
Three stages, two of them asynchronous.
five-stage interview loop is an inconvenience when everyone shares a working day. Across a twelve-hour gap it is something else: five evenings, each one negotiated around a current employer, each one confirming to a strong candidate that this process does not value their time. The loops we see succeed are three stages, and only one of them is live.
Stage one: a written screen
Not a form. Four or five questions that only someone who has done the work could answer well, sent as a document, answered in the candidate's own hours.
Ask about decisions rather than facts. "Describe a system you worked on where the original design stopped fitting the problem — what was the signal, and what did you change?" A question like that cannot be answered from a job description, it takes a competent person twenty minutes, and it filters harder than an hour of live screening ever has for us.
The side benefit is that you are reading their writing, which for a distributed role is a thing you will be relying on daily and would otherwise discover after they start.
Stage two: a scoped exercise
A small, real, time-boxed piece of work — in the region of three hours — with the time box stated and respected, and with a clear brief that includes what you are not assessing.
Two rules we hold to. The work must be representative of the actual job rather than a puzzle, and nobody should be asked to produce something you could ship. A candidate's unpaid time is not a free sample.
Then review it asynchronously and write down what you found before anyone speaks to them. Written-first assessment is harder to drift, and it gives the final stage something concrete to start from.
Stage three: the one live hour
This is the only round that needs shared hours, so spend it on the only thing shared hours buy: watching someone think.
Open their exercise. Change the requirements. Ask what they would do if the data were ten times larger, or if the constraint they assumed turned out to be false. You are not checking whether they produce the right answer under pressure; you are checking how they reason when the ground shifts, what they ask about before committing, and whether disagreeing with you is something they are able to do.
Include the person who will actually work with them. For a distributed hire, "can I ask this person a question at the edge of my understanding" is close to the whole job, and it is answered in that hour or not at all.
Why the count of live rounds matters
The CHI 2023 analysis of cross-time-zone collaboration at Microsoft found that meetings spanning time boundaries concentrate into early mornings and late evenings, and that the burden falls unevenly on the people in particular geographies rather than being shared.
That finding is about employees, but a hiring process is the first experience a candidate has of how your organisation distributes that cost. A loop with five live stages has already told them where the asymmetry will sit once they join. A loop with one has told them something different.
There is also a plain commercial argument. Our shortlists move in days, and strong Philippine engineers are usually in two or three processes at once. The loop that respects their evenings is frequently the one that still has them at offer stage.
The same study finds the burden of meeting across time boundaries falls asymmetrically on workers in particular geographies — the argument for keeping stages asynchronous.