How to Use Hiring Signals to Book Meetings
How to Use Hiring Signals to Book Meetings
Use hiring signals to book meetings: find companies hiring your buyer's team, rank postings by recency and seniority, and write from the posting.
No credit card required
Free 200 credits every month
A job posting is one of the few documents a company publishes after the budget is approved. A first RevOps hire, three SDR openings in the same week, a posting that asks for "Salesforce admin experience": each one says what the company is about to spend on, and roughly when. Hiring signals are easy to find. Turning them into meetings is the part most playbooks skip, because they stop at an export and a template that opens "I saw you're hiring".
This guide walks one hiring search to a booked meeting: search, rank, read each posting, find the person who owns the problem, and send on email and LinkedIn from the same list. Hiring is one timing input to a lead score. The guide to lead scoring covers how fit and timing combine, and buying signals explained covers the other kinds.
Which hiring signals mean a company is about to buy
Search for hiring signals sales triggers and most of what comes back is a list of "high-intent roles" somebody else picked. Start from your own wins instead. Pull the customers you closed in the last year and look at what each one was hiring for in the quarter before they signed.
You will probably find two or three patterns, and those are your signal list. If you have no history yet, these are the postings we would start with for most B2B products:
Posting | What it usually means | Who to write to |
|---|---|---|
First hire in a function (first RevOps, first data engineer) | Someone is about to own the tooling | The person they will report to |
Three or more openings for the same team | The team is outgrowing its current process | The head of that team |
A role that names a tool you replace or plug into | You know the stack, and maybe a switch | The hiring manager |
A new VP or Head of | A stack review in their first 90 days | The new leader, once they start |
"Implementation" or "migration" in the title | A project with a deadline | The project owner |
One backfill for an individual role | Attrition, rarely a purchase | Usually nobody |
The last line matters as much as the first five. Most of what sits on a job board is replacement hiring, and a list that treats every posting as intent buries the good ones.
Hiring intent data, a vendor's account score built from postings and headcount, is a reasonable shortcut. Reading the postings yourself is slower and far more specific, and specificity is what a first line runs on.
Find companies that are hiring for your use case
In Oneprofile this is Find companies hiring, one of the searches under Find leads.
Type the job titles. Add up to ten. Each is matched as a whole phrase, in order, so "Revenue Operations" finds "Senior Revenue Operations Manager". To match what the posting says rather than its title, use Keywords: "HubSpot" finds every opening that mentions it.
Narrow the role. Set seniority, department and job function, then the posting date and the countries, states or cities the roles are based in.
Narrow the employer. Industry, company size, the technologies on its website, and its last funding round and date.
Read the count. It counts open job postings that match, costs nothing, and updates as you type. If it reads in the tens of thousands, you have described a labor market, not a buyer.
Save to a new table. The price of what you are adding shows before anything is added.
Each company arrives once, carrying its matching postings (up to 25 listed): titles, seniority, locations, a link to each, and when the newest went up. That is why you end up with fewer companies than the count promised.
Rank hiring signals by recency, seniority and volume
Three things decide the order, and none of them needs a model.
Factor | Work it first | Push it down |
|---|---|---|
Recency | Newest matching posting under 14 days old | Newest posting over 8 weeks old |
Seniority | Head of, VP, or the first hire in a function | A single junior or individual role |
Volume | Three or more distinct matching titles | One posting |
Sort by the newest posting date first, then read down. Volume here means matching postings in your window, nothing cleverer. You do not need a baseline model to spot a hiring surge when one company has six open SDR roles and its peers have one.
To weigh fit alongside timing, sort within each recency band by an ICP score. Scoring every account against your ICP covers the setup.
Two traps that inflate job posting signals
The first one hides at the top of the list. The company with the most postings can turn out, on a closer read, to have one role.
One role, cross-posted. The same title on the same day in four countries is one hiring decision, posted regionally. Count distinct titles, not postings, before you call anything a surge.
Postings that never close. A role that has been up for more than about eight weeks is usually filled, frozen, or left open to collect resumes. Treat it as background, not as a reason to write today.
Find the hiring manager behind your hiring signals
Write to the person who owns the problem the hire is meant to solve. For three SDR openings that is the head of sales, or the founder at a 30-person company. The future hire does not exist yet.
Start a people search from the hiring list: set Start from to A table of companies and pick the list you just built.
Filter to the titles that would own each role. Keep it tight, two or three titles rather than a whole department.
Fill work emails from the provider waterfall. The cheapest likely provider runs first, deeper ones only for the contacts it missed, and a miss costs nothing.
Verify every address. Send the valid ones and hold catch-all and risky addresses for a smaller batch. The bulk email finder guide covers each verdict.
The people search follows the hiring list, which pays off in the last section.
Write outreach from the job posting signals, not a template
"I saw Acme is hiring three SDRs" is the opener every vendor reading the same job board sends that week. It proves you saw the posting. It says nothing about the person reading it.
The posting itself has better material, and two research steps pull it out for each company:
Enrich job reads one posting link you pick and returns the title, team, seniority, location, the salary range exactly as published, and one sentence on what the role is for.
Hiring signal finder reads the company's careers page and public job boards, counts the roles open right now, and lists the departments they are hiring into. It also writes a hook that names one role and what it implies, and it will not build that hook on an undated posting nothing else backs up.
Then send the list to a sequence on the Hiring signal campaign, or let Best fit choose, which it usually does for a list built from a hiring search. The agent writes each contact's message from those facts and ties the opening to what the hire means for the reader: ramp time, who trains the new people, what the empty seat costs.
From a template: "I saw you're hiring SDRs and wanted to reach out."
From the posting: "Your SDR posting says new reps will build their own lists in Salesforce. That is usually most of their first month."
The second line could not go to anyone else. The campaign starts as three emails. Add LinkedIn steps (profile views, connection requests, messages) in the sequence builder and they run from the same list, sent from the rep's own browser. Replies land in one inbox and stop the cadence for that contact.
One opinion that has nothing to do with us: pay transparency laws have made job postings much better reading. A published salary band tells you the seniority they actually mean and the budget behind the seat, and it is probably the most honest number a company puts on the internet.
Re-run hiring signals weekly without paying twice
Postings go stale within weeks, so the search has to run again. Open the list's Lead search panel, click Edit inputs, switch Run this search to On a schedule, and pick weekly.
Each run estimates how many new companies it could add and prices them. Nothing is added and nothing is spent until you click Approve, so you pay for the new companies and not for the ones you already have. Only open postings are searched, which keeps closed roles out of new results.
Remember the people search from earlier? When the hiring list gains companies, it offers the people at the new companies only, priced and waiting for approval the same way. A weekly routine becomes two approvals, new companies and then their people.
Once a month, check which signal types actually produced meetings and keep only those. In our experience that list gets shorter every time you look.
Pick one role your best customers were hiring for when they bought, and run the count on it today. Counting is free, and the free plan renews 200 credits a month, which is enough to take a short list from posting to first message. Get started free.
What are hiring signals in sales?
How old can a job posting be and still count as a signal?
Should I contact the hiring manager or the new hire?
Are hiring signals better than intent data?
Why does one company show several postings for the same role?
What does it cost to run hiring signals in Oneprofile?