Why job boards show stale roles - and what to do instead
You opened the daily email about your dream role and the listing has been live for five days. You're not imagining it - here's how the data actually flows from a company's career page to your inbox.
A familiar job-search frustration is opening an alert for a promising role, then discovering that the employer's page has changed, closed or moved. Even when the application still works, the copied timestamp cannot tell you how far review has progressed or how many candidates arrived first.
This isn't a flaw in any one job board. It's a consequence of how the entire aggregation layer is built.
Where roles actually originate
Many employers publish roles through an applicant tracking system (ATS), while others use custom careers sites, agencies or public job boards. Common systems include:
- Greenhouse - dominant in tech and high-growth startups
- Lever - common for mid-stage tech and product companies
- Workday - large enterprise, banks, retail, healthcare
- SmartRecruiters and Workable - widespread in mid-market
- Ashby, Pinpoint, Recruitee - newer, growing fast
- SuccessFactors, Taleo, iCIMS - large enterprise/legacy
When an employer publishes a public vacancy, its careers page is the best place to verify whether the role is still open and what the current requirements are. Other listings may be copied, syndicated or submitted separately, so their timing and status can differ.
The aggregator pipeline
Major job boards build their inventory by ingesting from these ATS systems through one of three mechanisms:
1. Direct API feed
Some employers or hiring platforms provide feeds to selected job boards. This can be quick, but the board may still deduplicate, classify and quality-check the role before showing it in search.
2. Crawl-and-parse
A job board may revisit careers pages on its own schedule and parse the listings it finds. Any gap between checks creates delay, while a later change or closure can leave the copied listing stale until the next update.
3. Manual or semi-automated submission
Smaller employers and recruitment agencies submit roles directly via aggregator forms or feeds. This is fast for the submitter but tends to introduce noise (re-listings, duplicates, sometimes outright fakes).
Layered on top of this: aggregators run their own ranking and freshness signals, so even after a role is indexed it may not appear in your saved-search results immediately. They optimise for "the right role for this user" first and "the newest role" second - and those goals genuinely do trade off against each other.
The compounding lag
Each step can add latency. A role may move through a sequence like this before it reaches a saved-search email:
- Company posts to ATS - T+0
- A feed or scheduled check picks up the role
- The board deduplicates and classifies it
- The role becomes eligible for search and alerts
- The next digest reaches your inbox
Sometimes that chain is fast; sometimes it is not. When a suitable role attracts applicants quickly, finding it at the employer source before a later alert gives you a real visibility advantage because you can apply before the queue grows.
What actually beats this
Three things, in order of effectiveness:
1. Direct careers-page monitoring (this is part of what FirstPost does). Watching the employer's public source removes some of the delay introduced by later indexing and alert schedules. It does not guarantee instant detection or complete coverage, but it can get a suitable vacancy in front of you before the wider queue builds.
2. Niche communities. Some fields have specialist boards or newsletters that surface employers and titles a broad search misses. Their freshness and moderation vary, so confirm the vacancy at the employer source.
3. Direct application alerts on a curated list. If you have a target list of 20-50 employers, an automated daily check of those specific career pages is more useful than a generic saved-search across all of LinkedIn. You're trading breadth for speed and signal quality.
The trade-off you're actually making
Every search strategy trades between breadth, freshness and signal quality. Job boards are useful for discovering employers and roles you did not know about. Direct monitoring is useful when a particular employer or suitable new vacancy matters enough to prioritise timing.
For a targeted search, freshness matters because the employer's process can move while a copied advert remains visible. A suitable application found at the source before the queue and shortlist build has a real visibility advantage, even though no timestamp reveals the exact review state.