A Observation (A-004)
Evidence: supported • Status: active
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.
Funnel Stages: sourcingscreeningtechnical
Diagnostic Epistemic Posture
This observation represents an empirical signal received or experienced by a candidate. In the HOBA framework, an observation is an empirical consequence of underlying system mechanisms, not a causal proof in itself.
Recommended Diagnostic Probes
[PROBE-A-004-1] Diagnostic Probe Cost: low
Action: Check job listing requisition ID or ask recruiter whether the posting is an automated ATS refresh or a distinct headcount opening.
Expected Signal: Distinguishes between automated job board bot refreshes and genuine recurring hiring demand.
Compatible Mechanisms (3)
Run Diagnostic Wizard → M-006 none
Stale or Orphaned Job Requisition
Job posting remains active on careers page and aggregator portals despite the team having ceased active hiring or closed headcount.
M-013 none
Mid-Process Role Requirement Redefinition
Team changes tech stack, seniority requirements, or project scope mid-funnel, invalidating previous interview assessments.
M-024 intermediary
Inflated Requisition Requirements vs Actual Team Needs
Job description demands 10+ niche technologies and Staff-level qualifications for a straightforward feature engineering role.
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.
Participates in Contradiction Patterns:
Machine-readable static endpoint: /api/v1/artifacts/A-004.json