- 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 P-002 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
Candidate observes role closure/rejection followed by public reopening of materially similar role listing 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 requisition requirements or target profile were not satisfied by the interviewed pool, or 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 candidate was intentionally misled.
Observations this pattern requires
- A-003 Position closed after final interview without hire Candidate completes all interview rounds, but is informed that the requisition has been cancelled, frozen, or closed.
- A-004 Materially similar role reposted shortly after rejection Candidate observes the same or near-identical job listing reposted or refreshed on job boards within 1–8 weeks of rejection.
Compatible mechanisms in this pattern
- M-002 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.
- M-006 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.
- M-010 Hidden Evaluation Rubric or Undisclosed Priority intermediary The interview team grades candidate against specific undisclosed architectural dogmas, internal frameworks, or unwritten biases.
- M-013 Mid-Process Role Requirement Redefinition none Team changes tech stack, seniority requirements, or project scope mid-funnel, invalidating previous interview assessments.
Interventions that mitigate this pattern
- I-001 Auto-Close Stale Job Requisitions Implement automated ATS policy to expire public listings when headcount authorization lapses or no interview activity occurs within 60 days.
- I-003 Standardized Late-Stage Rejection Feedback Taxonomy Provide candidates reaching technical or panel stages with structured, rubric-based feedback categories rather than generic templates.
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.
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.
