--- id: A-004 type: artifact title: "Materially similar role reposted shortly after rejection" lang: en registry: 2026.08.2 canonical: https://hoba.work/artifacts/A-004 json: https://hoba.work/api/v1/artifacts/A-004.json --- # 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. ## At a glance - Stage: Sourcing, Screening, Technical - Evidence: supported ## What it looks like Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here. **The two postings, side by side** · rejection on 14 March, repost seen on 2 April — *reconstruction* ``` 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. **Asking the recruiter directly** — *reconstruction* ``` 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. ## 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:** 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. ### ATS vendor - **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. ### Recruiter - **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. ## 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. ## Diagnostic probes - **PROBE-A-004-1** (low) — Check job listing requisition ID or ask recruiter whether the posting is an automated ATS refresh or a distinct headcount opening. → Distinguishes between automated job board bot refreshes and genuine recurring hiring demand. --- hoba — a public, versioned atlas of hiring obstacles. Content CC BY-SA 4.0. This document is generated from the registry; the canonical page is linked above.