Make talent quality your leading analytic with skills-based hiring solution.
Ghost jobs, postings for roles a company has no real, immediate intent to fill, get discussed almost entirely from the candidate side: wasted applications, wasted interview time, eroded trust in a company’s listings. Our companion piece on why companies post ghost jobs and what the practice costs employer brand covers that ground in full, including how common the practice actually is and what the current legal landscape looks like.
What gets discussed far less is what a stale or fake requisition does to the numbers a recruiting team actually runs on. If a meaningful share of open requisitions are not genuinely active, every metric built on top of them, time to fill, time to hire, funnel conversion rate, cost per hire, is measuring a blend of real and fake activity with no way to separate the two.
Time to fill and time to hire both use “requisition opened” as their starting clock. A requisition that has been effectively dead for weeks, frozen budget, internal candidate already selected, forgotten after the hiring manager moved on, keeps that clock running anyway, which means every dashboard reporting these metrics is quietly averaging in postings that were never on a real path to a hire in the first place.
Funnel conversion rate suffers the same distortion from the other direction. A ghost job can show plenty of top of funnel activity, applications, even some early screens, before it stalls with zero real conversions, dragging down the conversion percentage for every genuinely active requisition it gets averaged against.
Cost per hire calculations get skewed too, since sourcing and screening spend against a ghost requisition gets attributed to a hire that will never happen, inflating the true cost of the hires that do close.
Pull every requisition currently marked open and sort by days since last candidate stage change, not days since posting. A requisition with recent candidate movement is active by definition. One with zero stage changes in 30 or more days is either genuinely stalled or a ghost job, and it needs a human decision, not a default assumption that it is still hiring.
Cross reference open requisition count against actual approved headcount for the same period. A gap between the two, more open reqs than approved headcount can explain, is the clearest early signal that some requisitions are not being closed when they should be.
Set a mandatory review trigger, 45 to 60 days is a reasonable default, that forces a hiring manager to confirm a requisition is still active or close it. Without a forcing function, stale requisitions default to staying open indefinitely, since closing one requires someone to notice and act, while leaving it open requires nothing at all.
If leadership is reviewing a time to fill number, a conversion rate, or an open requisition count without this audit having been run recently, they are looking at a number that includes some amount of ghost job noise, and they likely do not know how much. Flagging that caveat explicitly, and running the audit above on a regular cadence, is a small operational habit with an outsized effect on whether hiring metrics actually reflect what is happening versus what the requisition list claims is happening.
This is the same discipline behind good quality of hire tracking generally: know precisely what a metric is actually measuring before using it to make a decision.
Ghost jobs are usually framed as a candidate experience problem, and they are one. They are also a data integrity problem for the recruiting team running them, one that quietly inflates or deflates every metric downstream of an open requisition count.
Auditing requisitions against real candidate activity, not just posting age, is the fix, and it is worth doing regardless of how the broader ghost job conversation resolves. For the fuller picture on why ghost jobs happen and what they cost employer brand, see our companion guide to ghost jobs in 2026.
Both. Beyond the candidate experience cost, a stale or fake requisition keeps running against time to fill and time to hire clocks, dilutes funnel conversion rate averages, and can inflate true cost per hire, since every metric built on requisition data inherits whatever share of that data is not genuinely active.
Sort open requisitions by days since the last candidate stage change rather than days since posting. Little or no candidate movement in 30 or more days is the clearest signal that a requisition needs a human review rather than continuing to run by default.
Many recruiting operations teams use a 45 to 60 day trigger that forces a hiring manager to confirm a requisition is still active or close it, since without a forcing function, stale requisitions tend to stay open indefinitely by default.
Yes. Sourcing and screening spend against a requisition that never produces a hire still gets counted, which inflates the calculated cost of the hires that do close, since the denominator of “hires made” does not include the spend attributed to requisitions that were never truly active.
No, that is a related but separate question about employer motive and candidate impact, covered fully in our companion guide to ghost jobs in 2026. This page focuses specifically on what a ghost job does to a recruiting team’s own reporting once it exists, regardless of why it was posted.
On at least a monthly cadence for most organizations, and more frequently for high volume hiring programs, since a growing gap between open requisition count and approved headcount is one of the earliest and clearest signals that ghost or stale postings are accumulating.
Global hiring fraud hotspots are the countries and regions where documented candidate fraud and identity verification risk run highest, based on named industry indices rather than assumption. In 2026, that data points consistently in one direction: fraud vulnerability is concentrated in markets with weaker centralized identity infrastructure and fast growing digital hiring volume, led by […]
A synthetic candidate is a job applicant who does not exist as a single real person at all. The persona is assembled, usually by combining stolen or purchased personally identifiable information (PII) with an AI generated resume, an AI generated or composite photo, and an invented work history, into a package that looks, on paper […]
Hiring overqualified candidates is not automatically a mistake, but it is a decision that carries real, well documented risk if the role and the offer are not restructured around it. Recent survey data shows most employers already do this regularly: 70 percent of hiring managers say they typically consider candidates who are overqualified for the […]
