LuckPicker

Randomising Interview Question Order

Consistency across candidates is the legal defence. Randomising it costs you that.

Interviews are the case on this site where randomising is usually the wrong move: a structured interview's defensibility rests on every candidate getting the same sequence, so the randomness belongs in question selection before the process, not during it.

This is the one page on this site that mostly advises against randomising. A structured interview's value comes from every candidate getting the same questions in the same order, and randomising the order gives that up.

There is a place for randomness in hiring, and it is before the process rather than during it.

Why consistency is the point

A structured interview is one where every candidate is asked the same questions, in the same order, and scored against the same criteria. That structure is what makes the comparison between candidates meaningful, and it is what makes the process defensible if it is ever questioned.

Randomising the order breaks the comparison in a specific way. If candidate A got the technical question first and candidate B got it fourth, they were assessed under different conditions — different warm-up, different fatigue, different context from the preceding answers.

The order effects that make randomisation valuable in judging work against you here, because you are comparing people rather than entries and the comparison requires the conditions to match.

Where randomness does belong

Choosing which questions to use, before the process starts, is a legitimate place for a draw. If you have a bank of twelve behavioural questions and time for four, drawing four at random and then using those same four for every candidate preserves the structure while removing the interviewer's selection.

That matters because interviewer question selection is a documented route for unconscious preference. Choosing questions that suit a candidate you already like, without noticing, is easy; drawing them before you have seen any candidates is not.

Selecting who reviews an application, or the order applications are reviewed in, is also a reasonable use. Reviewing order effects are real, and unlike interview order, review order does not need to be consistent across applications to make the comparison valid.

  • Draw the question set once, before any candidate is seen. Then use it unchanged.
  • Randomise the order applications are reviewed in — that does not need consistency.
  • Randomise assignment of reviewers to applications where you have more than one reviewer.
  • Do not randomise the question order within an interview.

The defensibility question

Hiring processes get challenged, and the strength of a challenge depends heavily on whether you can demonstrate that candidates were treated the same. A structured process with a documented question set and consistent scoring is a strong position.

A process where the questions varied by candidate — even for a reason as neutral as randomisation — is a considerably weaker one, because it requires explaining why the variation did not disadvantage anyone rather than simply showing that there was none.

This is a practical point about defensibility rather than legal advice, and the specific requirements vary by jurisdiction and employer. The general principle that consistency is easier to defend than justified variation holds broadly.

The order that does need randomising

One thing is worth randomising and is usually not: the order in which candidates are interviewed. Later candidates in a day are assessed against an established comparison set, and interviewer fatigue is real.

Scheduling is usually driven by availability rather than by anything intentional, which means the order is effectively arbitrary already. Making it deliberately random costs nothing and removes the possibility that scheduling correlated with something you would rather it did not.

Where you have several candidates and a choice of slots, the order randomizer will produce a defensible sequence in one press, and recording that you did it is worth more than it costs.

Frequently asked questions

Should I randomise the question order within an interview?

No. A structured interview's comparison depends on every candidate getting the same questions in the same order under the same conditions.

Why is this different from randomising judging order?

Because you are comparing people rather than entries, and the comparison requires the conditions to match. In judging, per-judge variation cancels the effect; here it introduces one.

Where is randomness useful in hiring?

Choosing the question set before any candidate is seen, randomising the order applications are reviewed, and assigning reviewers to applications.

Why draw the question set in advance?

Because selecting questions that suit a candidate you already like is easy to do without noticing. Drawing them before seeing anyone removes that route.

Should candidate interview order be randomised?

It is worth doing. Later candidates are assessed against an established comparison set, and scheduling order is usually arbitrary anyway.

Is inconsistency a legal problem?

This is a practical point about defensibility rather than legal advice, and requirements vary. Consistency is generally easier to defend than justified variation.

Can I skip a question if it does not apply?

That is a deviation from the structure and should be recorded as one. Doing it for some candidates and not others is the pattern that causes trouble.

What about randomising within a question bank per interview round?

If the rounds are being compared with each other, no. If each round is scored independently, drawing a fresh set per round is defensible.

Tools for this job

Background reading

← All use cases