- What reaches them
- A generic rejection after a final round, and the same requisition number back on the careers page weeks later with the text unchanged.
- What it means from there
- Either the profile was revised, or the platform refreshed the listing, or the headcount is new — and the sequence on its own does not separate them.
- What happens next
- Asks whether the listing is the same requisition, and records the dates and the answer before deciding whether to reapply.
Closed-Then-Reposted Requisition Motif
A candidate completes multiple late-stage interviews, is rejected with a generic message, and sees the identical role reposted weeks later.
Pattern pat.closed_then_reposted_requisition_motif Evidence: supported
⏳ What made this ordinary
Rates up, payroll repriced (2022–2023) — The policy rate reached its cycle peak, technology equities repriced, every stage of the private funding chain contracted at once, and software payroll became something to amortise rather than deduct. The correction ran through announced reductions rather than through attrition.
Trigger rule
The role is closed and the candidate rejected, and a materially similar listing is publicly reopened within 60 days.
What it looks like
Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.
- week 0 Applied — req #4471
- week 2 Recruiter screen — passed
- week 4 Technical panel — passed
- week 5 Final round with hiring manager — completed
- week 6 Rejected — generic template, no specifics given
- week 11 req #4471 visible on the careers page again, text unchanged
What to notice: Late-stage progress, a contentless rejection, and the same requisition number back on the board. The sequence is the observation; its cause is not in the sequence.
- week 11 Candidate I saw req #4471 listed again. Is this a new opening on the team, or the same one?
- week 12 Recruiter Same requisition. We restarted the search with a revised profile after the first round of interviews.
What to notice: A revised profile, an automated refresh and a genuinely new headcount are three different mechanisms with one appearance. This is the question that tells them apart.
What this pattern establishes
- The interviewed pool did not meet the requisition's requirements or target profile, or the search criteria changed mid-process.
What this does NOT establish
- Does not establish that the original job listing was fake or a ghost job.
- Does not establish that the candidate was intentionally misled.
Observations this pattern requires
- obs.materially_similar_role_reposted_shortly_after_rejection Materially similar role reposted shortly after rejection The same listing, or a near-identical one, is reposted or refreshed on the job boards within 1–8 weeks of the rejection.
- obs.position_closed_after_final_interview_without_hire Position closed after final interview without hire The candidate completes every interview round and then learns that the requisition has been cancelled, frozen, or closed.
Compatible mechanisms in this pattern
- mech.hidden_evaluation_rubric_or_undisclosed_priority Hidden Evaluation Rubric or Undisclosed Priority intermediary The panel grades the candidate against architectural preferences, internal frameworks and house conventions that were not stated in the posting or in the round.
- mech.mid_process_role_requirement_redefinition Mid-Process Role Requirement Redefinition none The team changes the stack, the seniority level or the project scope while candidates are mid-process, and the assessments already taken no longer apply.
- mech.stale_or_orphaned_job_requisition Stale or Orphaned Job Requisition none Job posting remains active on careers page and aggregator portals despite the team having ceased active hiring or closed headcount.
- mech.stronger_competing_candidate_in_final_cohort Stronger Competing Candidate in Final Cohort none Candidate cleared all passing bars, but another applicant in the same pipeline demonstrated superior domain overlap or lower onboarding overhead.
Interventions that mitigate this pattern
- int.auto_close_stale_job_requisitions Auto-Close Stale Job Requisitions Implement automated ATS policy to expire public listings when headcount authorisation lapses or no interview activity occurs within 60 days.
- int.recorded_finalist_standing_with_a_dated_re_entry_route Recorded Finalist Standing With a Dated Re-Entry Route Record, for every finalist who cleared the bar and received no offer, the cohort size, the class of reason and a dated stage the record re-enters at when a requisition at the same level opens.
- int.standardized_late_stage_rejection_feedback_taxonomy Standardized Late-Stage Rejection Feedback Taxonomy Provide candidates reaching technical or panel stages with structured, rubric-based feedback categories rather than generic templates.
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.
- 29
- entity.artifact8Barrier14Mechanism7
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.
- What reaches them
- The requisition record moving from closed back to open with a revised profile, and a rejection template that is the same for every candidate at that stage.
- What it means from there
- This is one continuous search that changed shape, not two openings.
- What happens next
- Sends the standard wording, since a specific reason given at the close of one round can be quoted back at the next, and states the restart when a candidate asks directly.
- What reaches them
- Two finalists at the end of a loop, and the work the role exists to absorb still uncovered.
- What it means from there
- A loop that ended without a hire is information about the profile, and the profile is the part of this the manager controls.
- What happens next
- Rewrites the requirements and restarts the search on the same requisition, because a new requisition would go back through funding.
- What reaches them
- A requisition whose status returned to open, and a scheduled refresh that pushes open listings back out to aggregators with a current date.
- What it means from there
- An open requisition is a listing to distribute; the refresh reads the status field and not the history behind it.
- What happens next
- Republishes under the original identifier and stamps the posting with today's date, which is the default behaviour for any open requisition.
ClientNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Employer policyNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Public policy and industry standardsNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
