A job posting is one of the few things a company publishes voluntarily about its own gaps.
To hire, someone wrote a business case, got a budget approved and committed to solving a problem within a quarter. All of that happened before the post went live, and the post tells you most of it if you read it properly.
What a job post actually tells you
Budget was approved. A salary is a larger and harder commitment than most software purchases. If a company can fund a $90,000 role to solve a problem, it can fund a tool that reduces the problem.
Someone owns the problem now. Before the hire there was a gap nobody was accountable for. The requisition creates an owner.
There is a deadline. Roles get posted because something needs to happen this quarter, not eventually.
The pain is specified. Job descriptions list responsibilities, which are problems written as duties. “Own outbound pipeline generation” means they do not have enough pipeline.
The tools are listed. Requirements sections name the stack. That tells you what they use, what they are moving to, and occasionally what they are replacing.
Three patterns worth watching
A single senior role. A first VP of Sales, a first Head of RevOps. This is the strongest version, a function being built from nothing, with budget and a mandate. Whoever takes the role will buy tooling in their first 90 days.
A hiring surge in one function. Three SDRs at once means the outbound motion is scaling, which means the supporting stack is about to be stretched. Surges are a better signal than single junior roles because they imply a strategic decision rather than backfill.
Repeated reposting. The same role posted three times over six months means they cannot fill it. That is the moment a “hire someone” solution becomes a “buy something” conversation, and almost nobody works it.
What to largely ignore: single junior backfills, and roles at companies outside your ICP. A hiring signal at a company you cannot sell to is noise.
Reading the posting
Five things to extract before writing anything:
- Seniority. Does this person buy, influence or use?
- Responsibilities. Which of them map to what you solve?
- Named tools. Current stack, and whether a competitor appears.
- Team context. “Join a growing team of 8” versus “first hire in this function.”
- Posting age. Fresh, or reposted?
That last one changes the message. A role posted yesterday means the problem is being addressed by hiring. A role posted for the fourth time means hiring is not working.
Who to contact
Not the role being advertised. That person does not exist yet.
For a senior role: the hiring manager’s manager, or whoever owns the function today. A VP of Sales requisition means the CEO or COO is carrying that problem right now.
For a hiring surge: the function head. Three new SDRs means the VP of Sales is about to have a scaling problem.
For a repeated repost: the hiring manager directly. They are frustrated, and the frustration is the opening.
Writing the message
The thing to avoid is making the job post the subject. It is why you are writing, not what you are writing about.
Weak: “I saw you’re hiring a Head of RevOps.”
Everyone sends this. It announces an alert fired.
Better, for a first senior hire:
Hi [name], [company] is building out RevOps, which usually means the reporting has outgrown spreadsheets and somebody is stitching tools together by hand.
Most teams at that point are deciding between hiring for it and buying something that removes half the work. Happy to show you what the second route looks like, if it’s useful before the hire lands.
Better, for a repeated repost:
Hi [name], you’ve been looking for an SDR for a while. The market for them is grim right now.
A few teams in your position have covered the gap with tooling rather than headcount while the search runs. Worth twenty minutes on what that actually covers and what it doesn’t?
Both reference the situation rather than the alert. The second works because it acknowledges something true and slightly uncomfortable, which is rarer than it should be in cold outreach.
Timing
Job-post signals decay more slowly than job changes but faster than people assume.
Week 1–2: the strongest window. The problem is acute, nobody has solved it, and the hiring process has not yet created a sense that it is handled.
Week 3–6: still good. Candidates are being interviewed, and the gap between posting and starting is where “could we solve this differently” lands best.
After the hire starts: the signal converts into a job-change signal for the new person, which is a different and also strong play. Job change signals covers that.
So a hiring signal has roughly a six-week useful life, then becomes something else.
Running it
Watch companies rather than keywords. A watch on 25 target accounts checking job posts daily and headcount weekly gives you the signal with the ICP already applied, which is the difference between a usable queue and a job-board firehose.
Set a seniority floor. Director and above for most B2B; include the function head for surges.
Route reposts separately. They need a different message and they convert better, so do not let them sit in the same sequence as fresh postings.
And suppress the account afterwards. A company that just posted three roles will generate several signals in a fortnight. Contacting them four times because four requisitions fired is how a good signal becomes a complaint.
The short version
A job posting is a company publishing a problem it has already funded. The budget exists, someone owns it, and there is a deadline.
The strongest versions are a first senior hire in a function, a surge of three or more in one team, and a role reposted repeatedly, that last one being the most under-worked signal in B2B.
Contact the person who owns the problem today, not the role being advertised. Write about the situation rather than the posting. And work it inside six weeks, because after the hire starts it becomes a different signal entirely.
Next: job change signals and the 90-day window, or how long each signal stays actionable.
Frequently asked questions
Is hiring a buying signal?
Yes, and a strong one. A job posting means budget was approved, someone now owns the problem, and there is a deadline, all of which happened before the post went live.
Which job postings are worth acting on?
A first senior hire in a function, a surge of three or more roles in one team, and roles reposted repeatedly. Single junior backfills and roles outside your ICP are noise.
Who should you contact on a hiring signal?
Whoever owns the problem today, usually the hiring manager’s manager for a senior requisition, or the function head for a surge. Not the role being advertised, since that person does not exist yet.
How long is a hiring signal useful?
About six weeks. Weeks one and two are strongest; after the hire starts it converts into a job-change signal for the new person, which is a separate play.