The 3-7 day gap: how a company's careers page leaks hiring intent before LinkedIn does.
A role goes live on the company's own ATS-fed careers page days before it shows up on LinkedIn. For a recruiter, those days are the difference between a warm intro and a cold inbound.
Every recruiter has had this conversation. You see a role pop up on LinkedIn for a target account you've been working for months. You send the email, you send the InMail, you call the hiring manager. So have eleven other recruiters and one in-house team. By the time anyone replies, the role has been mentally claimed, the front-runner candidates are already in the funnel, and you're competing on speed against people who started before you knew the job existed.
The frustrating bit is that the role was actually live several days earlier. Not on LinkedIn. On the company's own careers page — the one fed straight from their applicant tracking system. By the time the LinkedIn post drops, the company has already had the requisition open, the JD finalised, the hiring manager briefed, and in many cases the first applications in.
That window — usually somewhere between three and seven days, occasionally as long as two weeks — is one of the cleanest signals available in the recruitment market. And almost nobody works it systematically, because watching twenty-five careers pages by hand every morning is no one's idea of a job.
Why the gap exists in the first place
The gap isn't a bug. It's a feature of how modern hiring infrastructure is wired together.
When a hiring manager opens a requisition in Greenhouse, Workable, Lever, Teamtailor, Ashby, or any other ATS, the role typically becomes live on the company's public careers page within minutes. That careers page is just an automatically-rendered list of open requisitions in the ATS — it costs the company nothing to publish there, and there's no approval process beyond the requisition itself being approved internally.
LinkedIn is a different beast. LinkedIn job posts cost money (either per-slot, per-click, or via a recruiter seat), they're a separate workflow, and they usually go through whoever owns the employer brand or talent marketing budget. That person batches them, often weekly. They might also wait until the hiring manager has signed off on the long-form copy, the team's leadership has reviewed the title, and someone has decided whether to splash for a Promoted slot.
Result: the role exists in the wild — public, indexable, accepting applications — for three to seven days before LinkedIn announces it. In some larger companies, where the LinkedIn workflow is owned by a TA ops team running a weekly cycle, the gap can stretch to ten or twelve days.
Indeed, Glassdoor, and the rest of the job aggregators are even slower than LinkedIn for a different reason: most of them scrape ATS feeds on a delay, then re-publish. The careers page is the source of truth. Everything else is a mirror, refreshed at someone else's cadence.
What you can actually do with the gap
The point of knowing about the gap isn't to feel clever. It's to translate it into specific recruiter moves that pay off.
1. Reach the hiring manager before they're being asked twelve times a day. Day one of a role going live, the hiring manager's inbox is calm. Day five, it's a war zone. The same email lands very differently in those two contexts. Catching the role on day one means the conversation starts with "thanks for the heads up, we just put this out" instead of "we already have a vendor on this."
2. Pre-build the shortlist before competing recruiters know to start. Most agency recruiters work reactively — see role, search database, send CVs. If you have three to seven days of head start, you can run a proper search, qualify two or three candidates, and send a curated shortlist on the same day the LinkedIn post goes live. The hiring manager sees CVs the moment they open the LinkedIn workflow, and you look magic.
3. Catch entire team build-outs early. A single role on a careers page is a data point. Four roles in the same function appearing across a week is a strategy. Watch the page, not the role: when a target account suddenly opens a head of sales, two account executives, and a sales engineer in five days, that's a quarterly plan executing, and there's an exclusive engagement worth pitching.
4. Notice when a role gets pulled. A role that appears and then quietly disappears within a week — without a hire announcement — usually means an internal candidate was found, the spec was wrong and is being rewritten, or the budget got pulled. All three are useful. The first means the hiring manager is still in market for a similar profile next quarter. The second means there's a chance to influence the rewrite. The third tells you something about the company you should know before placing any other candidates there.
5. Read pattern, not noise. Hiring patterns telegraph strategy faster than any earnings call. A company that quietly pauses engineering hiring for a quarter is signalling something. A company that opens its first US-East-Coast role after years of UK-only hiring is announcing a market expansion. Watching the careers page gives you the same signal an analyst gets from a press release, weeks earlier.
Why "just check it manually" doesn't work
The honest answer most recruiters give if you ask them do you watch your target accounts' careers pages? is "yes, I should, but in practice I check them when I remember." Which is roughly never, after the first two weeks of a new tracking spreadsheet.
The structural reasons are exactly the same as competitor monitoring of any other type:
- You see what you saw last time. Same five roles for three weeks, your eyes glide over them. On the day a sixth quietly appears, you skim past.
- You don't check on the right day. Tuesday's new role gets read on Friday — if at all — and by then the gap has already closed.
- You won't actually do it for six months. Daily manual cadence collapses within two weeks. The discipline isn't the problem; the routine is the problem.
The pattern that solves all three, again, is the same as for any monitoring problem: have something else watch on a fixed cadence, classify what it sees, and only interrupt you when something matters.
The setup, in four steps
- List your target accounts — the twenty-five companies whose hiring you'd genuinely act on, not a wishlist of two hundred.
- Find each one's careers page (almost always /careers, /jobs, /join-us, /work-with-us, or a Greenhouse / Workable / Lever subdomain).
- Configure something to fetch each page daily and parse the role list — title, level, location, salary band where visible — and compare against yesterday's snapshot.
- When something changes, route a plain-English summary — "Acme just opened a Senior Backend Engineer, London, £90-110k, plus a second AE role — third hire in their sales function this month" — into your inbox before your first coffee.
The first step is judgment. The other three are mechanical, and they're roughly the same engineering problem as competitor pricing monitoring with a different parser on the front and a different classifier on the back.
What this changes about the job
The recruiters who consistently outperform aren't necessarily faster on email or better on LinkedIn. They're earlier. They're talking to the hiring manager before there's a vendor on the role. They're sending shortlists the day the requisition goes public, because they had three days to find the candidates. They notice when a target account starts a team build-out before the build-out shows up in any market report.
None of that requires a different skillset. It requires being told, automatically, the moment a role you care about goes live somewhere — and quietly told, with no noise, no false positives, no daily ritual to maintain.
The 3-7 day gap is the cleanest unfair advantage in recruitment that nobody is working systematically. The reason nobody is working it isn't strategic. It's tooling.
Watch 25 target accounts' careers pages. Free for 14 days.
Daily ATS scan. AI-classified new / pulled / pattern signals. Morning brief in your inbox only when something actually happens. Concierge setup.