Multiple interview reschedulings or interviewer no-show

Interviews are postponed repeatedly or moved at short notice, or the interviewer does not join the call at the scheduled time.

entity.artifact obs.multiple_interview_reschedulings_or_interviewer_no_show RecruiterTechnicalTeam Evidence: supported Status: active

What it looks like

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

Scheduling thread · same interview, four dates reconstruction

week 2 Recruiter Tuesday 14:00 works for the panel — sending the invite now.
week 2 Recruiter Apologies, the interviewer has a conflict. Can we move to Thursday same time?
week 3 Recruiter Sorry to do this again — Thursday is out. Would Monday work?
week 4 Recruiter Something urgent came up on the team. I will come back to you with new slots.

What to notice: Four moves, no interview. Record the dates: a pattern of postponement is evidence about the process, not about the candidate.

Calendar record reconstruction

week 2, Tue Invite sent — Technical panel
week 2, Tue Cancelled by organiser
week 3, Mon Invite sent — Technical panel
week 4 Cancelled by organiser · no replacement issued

What to notice: Every cancellation came from the same side. That asymmetry is the observable part.

How to read this observation

An observation is something a candidate received or lived through. It is a consequence of the mechanisms underneath, not proof that any one of them was at work.

Diagnostic probes

Probe PROBE-A-007-1 Cost: low

Action: Offer a set of concrete times you are free, and confirm the contact details 2 hours before the call.

Expected observation: Minimises scheduling friction and shows how quickly the recruiter answers.

Compatible mechanisms (1)

Open the analysis walkthrough →

mech.interview_resource_scheduling_saturation Interview Resource & Scheduling Saturation intermediary Engineering interviewers carry sprint commitments alongside the panels they sit on, and rounds are moved, read cold, or dropped.

What this observation does NOT establish

Does not imply candidate rejection; frequently reflects interviewer calendar congestion or emergency incidents.

Reached without being linked

The relations above are one step. This is what the entry reaches only by walking through them — the shape of it, since the list runs long in a registry this cross-referenced.

Borne on by9: Mechanism3Loop1Intervention5

Walk it in the graph →

From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

Candidate

What reaches them: Four dates for one interview, invitations withdrawn by the organiser each time, and a fourth message with no replacement slot in it.
What it means from there: Something on the other side is moving, and which thing it is — a calendar, a panel, a requisition — is not in any message received.
What happens next: Records the dates and the wording, keeps other processes open, and asks for a date rather than for a reason.

Recruiter

What reaches them: Declines coming back from the panel's calendar, and no instruction about whether the search itself has changed.
What it means from there: A slot to reissue. Whether the requisition is still funded is not visible from the scheduling view.
What happens next: Sends new times and keeps the candidate in the pipeline; no cause arrives with the decline, so none travels onward.

Hiring manager

What reaches them: One conflict on one morning, resolved by moving one invitation. The series exists in the candidate's inbox, not in the panel's calendar.
What it means from there: A week in which delivery and the loop need the same hours, and the loop is the part that can be moved.
What happens next: Releases the slot to the work the role exists to absorb and asks for a new time, each move decided on its own.