- What reaches them
- The same requisition number, team and band on a listing whose posted date has moved, with the body text otherwise unchanged.
- What it means from there
- A refreshed listing and a second opening look the same on the board. The requisition number is what separates them, and one question resolved which it was.
- What happens next
- Records both dates and the requisition number, and asks the recruiter directly, which costs one message.
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.
entity.artifact obs.materially_similar_role_reposted_shortly_after_rejection SourcingScreeningTechnical 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.
14 Mar — Senior Backend Engineer · Payments · Remote (EU) · 5+ years · Go, PostgreSQL, Kafka · req #4471
2 Apr — Senior Backend Engineer · Payments · Remote (EU) · 5+ years · Go, PostgreSQL, Kafka · req #4471
Body text identical except for the posted date. Same requisition number, same team, same band.
What to notice: The requisition number is the thing to record. A refreshed listing and a genuinely new headcount look identical on the board and are different facts underneath.
- 2 Apr Candidate I saw req #4471 posted again this week. Is this a second opening on the team, or the same one refreshed?
- 3 Apr Recruiter Good catch — the board auto-refreshes listings after 30 days so they stay visible. Same requisition, still open.
What to notice: One question separated an automated refresh from a real second opening. This is the cheapest probe in the whole registry.
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-004-1 Cost: low
Action: Check the requisition ID on the listing, or ask the recruiter whether the posting is an automated ATS refresh or a separate headcount opening.
Expected observation: Distinguishes an automated refresh on the job board from a genuinely recurring hiring need.
Compatible mechanisms (3)
Open the analysis walkthrough →- mech.inflated_requisition_requirements_vs_actual_team_needs Inflated Requisition Requirements vs Actual Team Needs intermediary The posting lists 10+ named technologies and a Staff-level bar for a role whose actual work is feature delivery.
- 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.
What this observation does NOT establish
- Does not establish that the role was a "fake" or "ghost" posting.
- Does not establish that the prior interview feedback was fraudulent.
Appears in these contradiction patterns
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.
- 25
- Mechanism9Pattern3Loop2Intervention11
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
- One requisition record and a syndication schedule that re-posts a listing when it passes the configured interval.
- What it means from there
- Whether a listing stays in the visible window on a board is a distribution setting. Nothing about who was rejected enters that path.
- What happens next
- Refreshes the posted date on the interval the customer's configuration sets, and the board shows the listing as new.
- What reaches them
- The same requisition open on their own board with an unchanged number, and a question about it in the inbox.
- What it means from there
- The repost is the board's refresh cycle rather than a decision anyone took after the rejection.
- What happens next
- Answers it, since the requisition number and the refresh interval are facts that cannot be quoted back as a commitment.
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.
Hiring managerNot 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.
