Unsolicited recruiter outreach followed by ghosting

Recruiter opens direct outreach expressing strong interest, then stops replying once the candidate answers with availability.

entity.artifact obs.unsolicited_recruiter_outreach_followed_by_ghosting SourcingRecruiter Evidence: supported Status: active

📐 On the canonical path

Search closed, and everyone told — A search can legitimately stop: the need changes, the budget goes, someone internal turns out to be right for it. What this path requires is that the posting comes down and every candidate still inside the process is told within days.

This entry is one of the ways that commitment stops being kept.

⏳ What made this ordinary

The record funding years (2020–2021) — Two years in which the policy floor returned and venture funding roughly doubled its previous record. Headcount plans were set against committed capital rather than against bookings, and the terms of entry were set on the candidate's side.

What it looks like

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

Inbound outreach, then silence · the whole thread, eleven days reconstruction

day 0 Recruiter Hi! I came across your profile — your work on payment infrastructure is exactly what our team needs. Would you be open to a chat this week?
day 0 Candidate Thanks for reaching out. Yes, happy to talk. I am free Tuesday or Thursday after 15:00, and here is a short summary of what I have been working on.
day 4 — no reply —
day 4 Candidate Following up in case this got buried. Still interested.
day 11 — no reply —

What to notice: The enthusiasm and the disappearance came from the same side, and the candidate did nothing between them except answer.

What was and was not established reconstruction

Established: an outreach message was sent on day 0; the candidate replied the same day with availability; two follow-ups went unanswered over eleven days.

Not established: whether the role existed, whether it was filled, whether anyone read the reply, or what the recruiter thought of the profile.

What to notice: Writing the two lists separately is the whole method. Most of the pain of this signal comes from filling the second list with guesses.

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-012-1 Cost: low

Action: Send one polite follow-up after five business days, on the original outreach thread.

Expected observation: Recovers a stalled conversation if the recruiter was away or over capacity.

Compatible mechanisms (3)

Open the analysis walkthrough →

What this observation does NOT establish

Does not prove the profile was rejected; often it is what an automated batch sourcing campaign looks like.

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 by2: Intervention2

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: An inbound message naming their specific work, a same-day reply with availability, and then no answer — not to the availability, and not to a follow-up.
What it means from there: The approach and the silence came from the same side. Nothing in the thread separates a search that closed from a message no one opened.
What happens next: Sends one follow-up on the original thread, then treats the role as not live, and keeps the thread as a dated record of who started it.

Recruiter

What reaches them: A reply in an inbox that carries sourcing for several searches at once, beside a screening queue larger than the week's capacity.
What it means from there: A sourced reply is not an application, so it holds no position in the pipeline of record. Time-to-fill is measured; a thread with no requisition attached to it is not.
What happens next: Works the searches that are open now. Nothing in the queue raises the thread again, and no status message exists for a conversation that never became an application.

ATS vendor

What reaches them: A sourcing sequence with a message sent and a reply received. The contact holds no application against any requisition.
What it means from there: A reply is a sequence outcome, not a pipeline stage. Nothing in the record marks the contact as awaiting an answer.
What happens next: Marks the sequence replied and stops sending. The expiry rule and the rejection template both key on an application, so neither fires here.