The hiring signal
A job posting is committed budget and a stated need, in public. One role can tell you exactly what they are about to buy.
Read the role, not the headcount. Forty open reqs is noise, the right one is a window.
A hiring signal is a job posting read as a buying signal. One role tells you what a company is about to build, the tools it already runs, and the problem it is staffing against. Strong on the right role, noise in bulk.
One posting, five ways to read it
Most teams see a job posting and read one thing: they are growing. A single posting carries five readings, and the difference between them is the difference between a reply and the trash.
The specific need
A role exists because work is piling up that nobody owns. The job they are hiring for is the problem you can help with before the hire even starts.
The first of its kind
A first RevOps manager, a first demand-gen lead, a first security hire. They are standing up a function with no process and no stack, so they will buy to fill the gap.
The seniority of the hire
A VP-level role signals a function getting real budget and a leader to own it. A bigger title for the team you serve means a bigger decision-maker arriving.
The tools named inside
A job description usually lists the stack: "experience with Salesforce, Outreach, ZoomInfo." That is a free technographic read of what they run and what plugs into it.
The freshness of the post
A role posted three days ago is an open question. A role that has been up for two months is a stale list entry, or never real. The date is half the signal.
Read together, these five turn "they are hiring" into "here is the exact need, the exact stack, and the exact week to reach them." That is the whole job.
The closely related read, how fast a company is adding people overall, is its own signal. We cover the raw growth case in the headcount growth signal.
How do you detect a hiring signal?
The data is public and free, which is the good news and the trap. Anyone can see it, so the edge is in the filter, watching the right roles at the right accounts, not scraping everything.
| Source | What it catches | Freshness |
|---|---|---|
| LinkedIn Jobs saved search | New postings filtered to the exact role, seniority, and company profile you sell into. Free for a focused target list. | Days, if you check weekly |
| Careers pages and job boards | Roles a company posts directly on its own site, Indeed, or Glassdoor, often before they hit the aggregators. | Same day, if you watch closely |
| Job-board scrapers and monitors | Automated alerts on new and net-new roles across a list of accounts, with volume and velocity tracked over time. | Near real time |
| Clay job-posting enrichment | Run a target list against a job-posting source, then enrich the role, the named tools, and the right contact in one flow. | On your refresh schedule |
We work across most job-posting and enrichment tools and adapt to your stack. For the trackers worth knowing, see our guide to signal and intent tools, and for the data layer that fills in the right contact, the guide to B2B data tools. The scraper matters less than the role you point it at.
Not sure which roles actually map to what you sell?
Book a Fit CheckThe window: why the first ten days matter
A fresh posting dates itself, which is its best feature. The need is loudest the day it goes live, then it cools as the hire moves through the pipe.
The role is the team's active problem, the manager is in evaluation mode, and the budget is unspent. The warmest moment to reach the hiring manager, not the new hire.
The role is in interviews, attention has moved on, and the urgency has cooled. Still workable, but you need a sharper, more specific reason to land.
The hire has started and is settling in, or the post was never real. Switch to the new joiner as the contact, or drop it. As a fresh trigger, it is gone.
The useful read is that the hiring intent is visible before the company starts shortlisting vendors. You are reaching a need that is real and budgeted, but not yet in a formal buying process, which is exactly where a good first message lands.
The play: how we run outbound off a posting
You are not congratulating them on a hire. You are showing the hiring manager you understand the problem the role exists to solve, before they have even filled it.
-
1
Qualify the role, not the company
Is this the role that maps to what you sell, fresh, and net-new rather than a backfill? If the posting does not point at your problem, it is not this play.
-
2
Reach the hiring manager, not the new hire
The person who opened the req owns the pain right now. The future hire does not start for weeks. Target the manager, or the leader the role reports to.
-
3
Open on the work, name the role
Reference the specific posting and what it implies they are taking on. Then connect it to the gap your product covers in the months before and after the hire ramps.
-
4
Move fast, keep it short
Two channels, a handful of touches, all inside the window. A note that gets the relevance across in three lines beats a seven-email drip that arrives after the role is filled.
This is the signal-specific version. The repeatable motion across any timely trigger, including hiring, lives in the signal stacking play.
The angle that works, and the one that doesn't
Everyone can see the same posting. The difference is whether you noticed the hire or understood the problem behind it.
"Saw you're hiring an SDR, congrats on the growth! We help teams like yours scale outbound. Open to a quick 15 minutes this week?"
- ✕Reads the hire as growth, the laziest reading there is
- ✕Could be sent to any company hiring anyone
- ✕Asks for time before naming a real problem
"Noticed you just opened a first RevOps role. That usually means data and routing are getting messy faster than one person can fix solo. Before they start, want a quick look at how three similar teams set the foundation up so the new hire inherits something clean?"
- ✓Reads the specific role as a specific problem
- ✓Lands before the hire, when the manager owns the pain
- ✓Offers something useful, not a calendar link
Where it is strong, and where it is weak
An honest read, because the people selling you a job-posting scraper will only show you the half that flatters the tool.
- ✓Public and free, no six-figure data contract
- ✓Committed budget, a salary is already allocated
- ✓Self-dating, you know how fresh the need is
- ✓The description hands you the angle and the stack
- !Loud and crowded, everyone sees the same post
- !Noisy in bulk, most roles are not for your thing
- !Ghost and evergreen posts fake a need that is not there
- !Indirect, a hire is not always a buy for your category
When a job posting is just noise
This is the section the scraper vendors leave out. Forty open roles is not in-market for your product. The skill is throwing most postings away. Skip it when:
- ✕It is a backfill. Replacing someone who left keeps the lights on. It does not open a new need or a new budget the way a net-new role does.
- ✕It is evergreen or a ghost post. A req that never closes, or one kept up to look busy, is not a live problem. If it has been open for months, treat it as zero signal.
- ✕It is a recruiter or agency repost. The same role cloned across boards inflates your count. One real opening, not five, so do not act on it five times.
- ✕It is an unrelated function. A great company hiring warehouse staff is not a buying window for your sales tool. Raw headcount without the right role is just activity.
Want the right postings caught and worked for you?
Book a Fit CheckStack it with
A single posting is a maybe. A posting plus a second signal on the same account is a strong yes, and the angle gets sharper when two things point the same way. Gartner found that 99% of B2B purchases happen in the context of at least one organizational change, which is why a hire rarely travels alone.
A hiring wave right after a raise. The budget behind the posting is now confirmed, not assumed.
The tools named in the job description tell you what they run. An integration or adjacency angle writes itself.
A team building out right after a new leader arrives. The mandate and the hires are the same story.
Combining signals on one account is its own motion. We map and score the combinations through signal mapping, so you act on the accounts where two or three signals line up.
An example, start to finish
An illustrative walkthrough of the method, not a specific client result. We report real numbers only when they are real.
-
1Day 0 · Detected
A net-new role posts
A Series A company in the ICP posts its first ever RevOps manager role. The filter flags it as net-new, not a backfill.
-
2Days 1 to 2 · Read it
Mine the description
The post names the CRM and the gaps it wants fixed. That sets the angle and points to the VP of Sales who owns the hire.
-
3Days 3 to 7 · Reach out
Open on the problem
A short note to the VP names the messy-foundation problem a first RevOps hire inherits, with a useful before-they-start offer. No deck.
-
4Day 10 · The ask
Ask for the conversation
A short call to compare how similar teams set the foundation, framed as helping the new hire land well. Then stop, win or not.
Palm.ai
Alcméon
Mindflow
CEF.AI
Boolee
CoachHub
Inrō
Buster.AIPalm.aiAlcméonMindflowCEF.AIBooleeCoachHubInrōBuster.AIQuestions founders ask
What is a hiring signal in outbound sales?
How long is the job posting window?
Is hiring a stronger signal than intent data?
When is a job posting just noise, not a signal?
What is the strongest hiring signal to act on?
Can I run hiring signals at seed stage without expensive tools?
The signals next door
The headcount growth signal
How fast a company adds people, and when the raw growth rate is a real signal versus when it is just churn.
Read the signalThe layoffs signal
The other side of the headcount story: when a company cuts, what it opens, and how to handle it with care.
Read the signalWant us reading the postings and running the window?
Book a fit check. We'll look at which roles map to what you sell, which accounts are posting them now, and whether a hiring-signal motion would put real meetings on your calendar.
Book a Fit CheckNo hard sell. No fake numbers. Real good work speaks for itself.