Recruiters Post Already-Filled Jobs for Candidate Hoarding and Pipeline Optics
Yes. Recruiters knowingly post jobs that are already filled or never will be. It's not always incompetence—it's often strategy.
The core reason is candidate pool building. A recruiter fills a role in three weeks but keeps the listing live for another month to accumulate resumes. Those names go into their CRM. When the next similar job opens, they pull from that reserve. It saves sourcing work. It looks like they're always hiring. It justifies their headcount.
A second driver is pipeline optics. Recruiters are measured on open-req velocity and candidate volume. A hiring manager cancels a role mid-search, or the budget freezes—but the recruiter leaves the posting up to hit monthly metrics. They're not lying to you; they're obscuring the truth.
The third reason is contingency search. Some roles are competitive. A recruiter will run the open posting while also conducting passive outreach to known candidates. If the passive outreach succeeds, the posted role stays open anyway—in case the hire doesn't work out or another team needs a similar role. No harm keeping it live.
None of this serves you. You spend time tailoring applications for roles that were filled weeks ago or never existed as real headcount.
How to Spot a Job Posted After the Role Was Already Filled
Watch for these red flags in the posting itself:
- Vague posting date: "Posted 3 months ago" with no refresh timestamp. Real roles get refreshed or closed within 4-6 weeks once filled.
- Generic job description: No specifics about the team, project, or tech stack. Candidate-pool postings are templates—they're designed to cast a wide net, not to attract one person.
- Mismatched seniority or scope: The role description spans junior to senior. "Python developer" but also "system design and people leadership." This signals the recruiter doesn't know what they're hiring for—typical of speculative postings.
- Recruiter, not hiring manager, in the contact field: Legitimate roles list the hiring manager or team lead. If only a third-party recruiter is named, they're building a pool, not filling a specific opening.
- No interview timeline or process info: Real roles mention next steps. Fake postings stay silent so they can respond to every applicant with "we'll get back to you."
The easiest test: reach out directly to the hiring manager (find them on LinkedIn). If they say they're not hiring or the role closed weeks ago, the listing is stale.
Why This Matters for Your Job Search
Applying to ghost jobs burns two resources: time and application quota. If you're job searching, every application counts. Recruiters see volume—first wave of applicants get real feedback; later waves get form rejections or silence. Wasting an application slot on a dead posting is dead weight.
More critically, it trains you to waste energy. After enough rounds of tailoring for roles that don't exist, you stop trusting the posting process. You slow down. You second-guess yourself. The frustration is the point of this broken system.
Learn the full taxonomy of ghost jobs and detection tactics here.
The Recruiter's Incentive Structure Never Changes
Recruiters will keep doing this because the cost to them is zero. They face no penalty for stale postings. Job boards don't auto-close listings after inactivity. Companies don't audit recruiter behavior. And every month, new job seekers arrive who don't know the pattern yet.
The only defense is speed and selectivity. Apply to roles on the day they post, before the filling happens. Verify via direct contact before spending an hour on your application. GiraffyReach detects fresh postings the moment they go live, which cuts the lag between posting and saturation from days to minutes.
Don't fight the system. Outrun it.