Hiring as a buying signal works when you read the composition of a company’s job postings, not the fact that postings exist. More than 710,600 companies are hiring at any given moment, so an “is hiring” flag does almost no prioritization work on its own. What separates signal from noise is which functions an account is staffing, at what seniority, in what volume, and against its own prior baseline. This guide covers the five hiring patterns that carry buying intent, a four-tier way to score them, two real postings found today, and how to corroborate before a rep spends a touch.
TLDR:
- Hiring is a buying signal only in its composition. A single posting tells you little; the mix of function, seniority, volume, and timing is what points to a budget decision that already happened.
- Five patterns carry most of the intent: net-new function builds, first-hire roles, leadership hires above an existing team, volume spikes against an account’s own baseline, and tools named in the requirements.
- A “founding member” or “first hire” posting is the strongest single-posting read available, because it describes a function that does not exist yet.
- Corroborate before you act. Pair Job Openings with headcount-increase and office-expansion News Events: 86,676 of those events are on file for US companies.
- PredictLeads Job Openings holds 279.2M+ postings since 2018 across 2.9M+ websites, with 10.2M active at any time, every record carrying an O*NET occupation code, a
seniorityvalue, andfirst_seen_at/last_seen_attimestamps.
Sources: PredictLeads Job Openings and News Events. The 86,676 figure is an all-time total of US increases_headcount_by and office-expansion News Events on file, queried September 11, 2026.
What Hiring as a Buying Signal Actually Means
Hiring as a buying signal is the practice of treating a company’s job postings as public evidence of a budgeted initiative that will need tools, services, or capacity. A requisition is not an intention. It is a committed line of spend that someone already defended internally, and the posting describes the work in detail before the work begins.
That is a different class of information than firmographics. Size, industry, and revenue band tell you an account could buy. A hiring pattern tells you an account just decided to do something new, and the description usually names the stack, the process, and the goal.
Economists read postings the same way at the macro level: the US Bureau of Labor Statistics publishes national openings, hires, and separations every month in the Job Openings and Labor Turnover Survey. A GTM team is applying that logic one account at a time. For how hiring sits alongside funding, news, and technology changes, see our guide to company signals and account prioritization.
PredictLeads Job Openings makes this readable at scale: 279.2M+ postings collected since 2018 from company websites, career subpages, and applicant tracking system integrations, each one categorized and timestamped.
Why an “Is Hiring” Flag Is a Weak Signal
A boolean “is hiring” field fails for four specific reasons, and each one has a fix in the data.
- Volume with no baseline. Two hundred open roles at a 12,000-person company is maintenance. Five at a 40-person company is a strategy change. Absolute counts rank large companies to the top of every list and say nothing about direction.
- Stale and evergreen requisitions. Some postings sit live for months. Without
first_seen_atandlast_seen_at, a six-month-old listing looks identical to one posted this morning. - Non-employers in the data. Staffing firms, recruiting agencies, IT-services shops, and job boards post on behalf of others. This is the single largest source of false positives in raw job-posting data.
- Function blindness. An account hiring 12 warehouse associates and an account hiring its first revenue operations manager both read as “hiring.” Only one is buying what most B2B vendors sell.
Each fix is a field, not a workaround. PredictLeads classifies every posting into one of 26 job categories with an O*NET occupation code, assigns a seniority value from founder and c_level down to junior, and stamps first_seen_at and last_seen_at so you can measure a trend rather than a snapshot.
The Five Hiring Patterns That Carry Buying Intent
Five patterns account for most of the usable intent in job-posting data. Everything else is backfill.
| Pattern | What you see in the data | What it may indicate | Where to open |
|---|---|---|---|
| 1. Net-new function build | Three or more roles in a department with no prior postings there | A new team with its own budget and tooling decisions ahead | The most senior role in the group, before it is filled |
| 2. First hire or founding member | Title or description says “first,” “founding member,” or “build from scratch” | Greenfield. In many cases no incumbent vendor has been chosen | The hiring manager named in the posting |
| 3. Leadership hire above an existing team | A director, head, or vice_president posting where mid_senior roles already exist | A function being professionalized, which often re-opens informal tooling choices | The new leader, in their first 90 days |
| 4. Volume spike against its own baseline | Openings in your buyer’s function at two times the account’s trailing average | Capacity added faster than existing process and tooling were designed for | The function owner, framed around throughput |
| 5. A tool named in the requirements | The description lists a platform as a required or preferred skill | Evidence the company uses or plans to use it, not a live deployment | Integration, migration, or displacement angles, once corroborated |
Pattern 2 is the strongest read available from a single posting and deserves its own filter. Patterns 1 and 4 are stronger in aggregate but need at least two data points, so they arrive later. Pattern 5 needs the most discipline: a platform listed as a required skill is evidence that a company uses or intends to use it, not proof of a live deployment, and it may reflect client work or a migration in progress. That same mechanism is how job descriptions surface enterprise tools that never appear in a website script tag, which we cover in hiring and tech stack signals for technology lead generation.
Two Real Postings, Found September 11, 2026
The same job title can mean two opposite things. Both postings below appeared on September 11, 2026, and both are for a Sales Development Representative.
Snowflake: expansion inside an existing function
Snowflake (NYSE: SNOW) posted a Sales Development Representative (Outbound) role today that states quota expectations of 80 or more meetings and 35 or more qualified opportunities per quarter, and frames the work around what the posting itself calls “the agentic enterprise.”
Read it as pattern 4, not pattern 2. An established outbound function is adding capacity against explicit throughput targets, and those numbers are the useful part. If you sell sales engagement, conversation intelligence, meeting infrastructure, or enrichment data, the posting has told you the volume the team is being built to hit, which is the sizing input for your business case.
Dovetail: a function being created
Dovetail posted a US Remote Sales Development Representative role today, advertised as a “founding member of the SDR team” and explicitly describing the build of a new outbound motion.
Read it as pattern 2. Every decision that function will make is still open: the sequencer, the data source, the dialer, the routing rules, and the reporting. For most vendors selling into a sales organization, that makes it a better account to work this week than the first one, even though the first company is many times larger.
A filter for “companies hiring SDRs” returns both accounts and cannot tell you which is which. The separation comes from the description text, not the title. For the mechanics of pulling a role-specific list, start with finding companies hiring for a specific role with O*NET codes.
A Four-Tier Framework for Scoring Hiring Signals
Patterns are only useful if they map to different actions. Four tiers is enough resolution for most teams, and the tier should drive the service-level agreement, not just the score.
| Tier | Qualifying pattern | Corroboration required | Action and timing |
|---|---|---|---|
| Tier 1 | First-hire or founding-member role in your buyer’s function, or a net-new function build | A headcount, expansion, or financing event in the last 90 days | Route same day to a named rep, personalized to the posting |
| Tier 2 | Leadership hire above an existing team, or a two-times volume spike against the account’s own baseline | One supporting signal, or a posting under 14 days old | Work this week, sequenced around the function being built |
| Tier 3 | Steady hiring with no change in trajectory, or a tool named in the requirements | None. Treat as context, not a trigger | Add to nurture, revisit when tier 1 or 2 fires |
| Tier 4 | Hiring outside your buyer’s function, staffing or job-board domains, or postings past your freshness window | Not applicable | Suppress from hiring-triggered sequences |
One caution on tier 4: it means the absence of a hiring signal, not a negative read on the account. Suppress it from the hiring-triggered play and let a different signal pick it up. Tier assignment is a filter problem rather than a modeling problem, because PredictLeads exposes seniority, 26 job categories, O*NET codes, and posting timestamps as first-class fields. This tiering slots into a wider scoring model, which we walk through in prioritizing accounts with hiring, news, and technology signals.
Corroborate the Hiring Signal With Expansion News Events
A job posting tells you a company intends to hire; a headcount or facilities news event tells you it already did. Those are different confidence levels, and stacking them is what moves an account from tier 2 to tier 1.
Two examples from this week show what that looks like. AEVEX Corp. (NYSE: AVEX) expanded its manufacturing and office space in Florida and Virginia, found September 10, 2026. Options Technology Ltd. increased headcount by 12 in Singapore, found the same day. Neither is a job posting; both confirm that an expansion actually happened, and both carry a location you can route on.
The inverse is under-used. The categories decreases_headcount_by and closes_offices_in are suppression signals: an account posting a few roles while cutting elsewhere is reorganizing, not expanding. Funding is the third leg, and when fresh capital and a hiring spike land in the same quarter the budget question is already answered, which is the pattern behind timing outreach by funding stage.
PredictLeads News Events covers 10M+ signals since 2016 across 37 categories, including increases_headcount_by, expands_facilities, expands_offices_in, expands_offices_to, and opens_new_location. As of September 11, 2026, 86,676 headcount-increase and office-expansion events are on file for US companies alone, each with a found_at timestamp, a confidence score, and a link to the source article.
How to Build This Yourself: A Five-Step Workflow
1. Translate your buying committee into O*NET codes
Job titles are not comparable across companies. A “Growth Engineer” at one account and a “Marketing Technologist” at another may be the same role. The O*NET-SOC occupational taxonomy exists to solve that, and you can look up any code on O*NET OnLine. Write down the three to six codes that describe the people who use or approve your product, then pass them as onet_codes on GET /discover/job_openings.
2. Set a seniority floor
Most hiring-signal noise is junior backfill. Decide the lowest level that implies a decision is being made and filter below it. The values are founder, c_level, partner, president, vice_president, head, director, manager, mid_senior, junior, and not_set. For most B2B plays, manager and above is the right floor, with an exception for pattern 2, where a founding individual contributor role matters regardless of level.
3. Baseline each account against itself
This is the step most teams skip, and it is the one that makes the signal work. Pull each account’s history with the first_seen_at_from and last_seen_at_until filters, compare the trailing 90 days to the prior 90, and score the change rather than the level. A 40-person company going from one opening to four beats a 10,000-person company going from 180 to 200.
4. Filter out non-employers
Remove staffing agencies, recruiting firms, IT-services shops, job boards, and aggregators before you score anything. Add a plausibility check: a 200-person company running 150 concurrent distinct requisitions is almost certainly reposting for clients. Both passes together removed close to half the raw candidate pool in our ranking of the top 20 US tech hiring hubs.
5. Corroborate, then route
Check each surviving account for a headcount, expansion, or financing event in the same window, assign a tier, and push it to the CRM with the posting URL attached. For continuous monitoring, follow your target accounts and subscribe to webhooks on the JobOpeningsDataset and NewsEventsDataset. Job openings refresh approximately every 36 hours, so a daily sync is enough.
One practical warning before you ship it
Count the records you actually receive rather than trusting a headline count on a narrowly filtered query. Aggregate estimates on tightly filtered title-and-date queries can disagree with the result set they describe; in our own testing on September 11, 2026, a narrow title-and-date filter returned an estimated count far smaller than the records it came back with. Page through and count them yourself. Endpoint parameters and pagination behavior are documented at docs.predictleads.com.
How PredictLeads Delivers Hiring Signals
PredictLeads is a company intelligence data provider, not a CRM, a sales-engagement platform, or a contact database. It supplies the signal layer those tools run on, which is the relevant distinction if you are deciding whether to buy this as data or as software.
- Job Openings: 279.2M+ postings since 2018 across 2.9M+ websites, 10.2M active at any time, 710,600+ companies currently hiring, and 6.4M+ new postings detected last month. Every record carries
title,normalized_title,description,onet_data,seniority, one of 26 categories,salary_data,location_data, andfirst_seen_at/last_seen_at. - News Events: 10M+ structured signals since 2016 across 37 categories, covering the headcount and facilities events that corroborate a hiring pattern and the cost-cutting events that should suppress it.
- Financing Events: 210,800+ events since 2016 with normalized types from
pre_angelthroughseries_j, so you can check whether a hiring spike is sitting on fresh capital. - Technology Detections: 1.5B+ detections since 2018 across 95M+ domains and 50,000+ tracked technologies, from five sources: script tags, DNS records, IP ranges, cookies, and job descriptions. The
behind_firewallboolean flags detections found somewhere other than a public website tag, which is how enterprise tools that never appear in page source get surfaced. - Similar Companies: available for 18.9M+ companies with up to 50 lookalikes each and a written
reasonfor the top 20 matches, so a hiring pattern that converts becomes a target list.
Corroboration only works inside one join key. All of these datasets resolve to the same company record across 130.7M+ companies in 195 countries, so checking a posting against a headcount event and a funding round is a lookup, not an entity-resolution project. For criteria on evaluating sources, see our comparison of job openings data providers.
Delivery is by API, flat files, webhooks, and MCP. The REST API suits real-time lookups, flat files suit warehouse ingestion and historical backfills, webhooks suit trigger workflows on followed accounts, and the MCP server at mcp.predictleads.com lets an AI agent query hiring signals in natural language, for example “find 10 companies hiring SDRs in the US.”
On compliance: PredictLeads is SOC 2 Type II certified and GDPR and CCPA compliant, collects only publicly available information, and holds no personally identifiable information in its company intelligence datasets. Job postings are company-level public data, which is what makes this clean to run at scale.
Final Thoughts on Hiring as a Buying Signal
The teams that get value from hiring data are not the ones with the biggest feed. They are the ones that decided in advance which three or four functions matter, set a seniority floor, measured each account against its own history, and agreed on what happens when a tier 1 pattern fires.
Start with the smallest version. Run the first-hire pattern against your existing account list and see how many accounts you are already sitting on that just created a function you sell into. Both postings in this guide were live on a single Thursday in September.
Frequently Asked Questions
Hiring as a buying signal is the practice of treating a company’s job postings as public evidence of a budgeted initiative that will need tools, services, or capacity. A requisition is a committed line of spend that someone already defended internally, and the job description usually names the stack, the process, and the goal before the work begins. It is a different class of information than firmographics, which tell you an account could buy rather than that it just decided to do something new. PredictLeads Job Openings holds 279.2M+ postings since 2018, each classified with an O*NET occupation code and timestamped with first_seen_at and last_seen_at.
Query job-posting data by occupation code, seniority, and date window rather than by company, which is what discovery endpoints are for. Map your buying committee to three to six O*NET codes, set a seniority floor at manager or above, restrict to postings first seen inside your freshness window, and remove staffing firms and job boards from the results. PredictLeads tracks 10.2M active openings at any given time across 710,600+ companies currently hiring, refreshed approximately every 36 hours. The GET /discover/job_openings endpoint accepts onet_codes, location, seniority, and found_at_from parameters.
Five patterns carry most of the usable intent: a net-new function build, a first-hire or founding-member role, a leadership hire placed above an existing team, a volume spike measured against the account’s own baseline, and a specific tool named in the posting requirements. The first-hire pattern is the strongest read available from a single posting, because it describes a function that does not exist yet and in many cases has no incumbent vendor. Everything outside those five patterns is usually backfill. PredictLeads classifies every posting into one of 26 job categories with a seniority value, which is what makes these patterns filterable rather than something you have to read for manually.
Hiring is reliable when it is read as a pattern and unreliable when it is read as a boolean. More than 710,600 companies are hiring at any moment, so an is-hiring flag does almost no prioritization work on its own. The four things that turn it into a real signal are a per-account baseline, a seniority floor, a function filter, and the removal of staffing firms and job boards from the data. Corroborating with a headcount or financing event raises confidence further: 86,676 headcount-increase and office-expansion News Events are on file for US companies alone.
Compare each account to its own trailing window instead of to other companies. A 40-person company going from one opening to four is a much stronger signal than a 10,000-person company going from 180 to 200, even though the second change is larger in absolute terms. Filter by the functions you sell into, because a spike in warehouse roles and a spike in revenue operations roles are not the same event. PredictLeads stamps every posting with first_seen_at and last_seen_at, so a trailing-90-days versus prior-90-days comparison per account is a direct query rather than a reconstruction.
It tells you a function is being created rather than expanded, which is usually the best possible timing for a vendor. A founding-member role means the tooling, process, routing, and reporting decisions for that function are all still open, so in many cases there is no incumbent contract to displace and no internal champion for a rival product. On September 11, 2026, Dovetail posted a US Remote Sales Development Representative role advertised as a founding member of the SDR team, explicitly building a new outbound motion. A generic hiring-SDRs filter would return that account alongside large enterprises simply backfilling an existing team, which is why the description text matters as much as the title.
O*NET codes make job titles comparable across companies that name the same role differently. A Growth Engineer at one account and a Marketing Technologist at another may sit in the same occupation, and a title-keyword search will miss one of them. PredictLeads classifies every job opening with an O*NET occupation code, family, and occupation name, so you can define your buying committee once and query it consistently across employers of any size or industry. You pass the codes as the onet_codes parameter on the Discover Job Openings endpoint, alongside location, seniority, and date filters.
Fresh enough that the requisition is still open when your email lands, which in practice means a detection window measured in days rather than weeks. Stale postings are the second-largest source of false positives after staffing firms, because some employers keep pipeline requisitions live for months. PredictLeads refreshes job openings approximately every 36 hours and records first_seen_at, last_seen_at, and a status field that marks closed postings, so you can enforce your own freshness cutoff. For continuous monitoring, webhooks on the JobOpeningsDataset push found and closed events as they are detected.
It depends on the pattern, which is why a tier model is more useful than a single alert. A first-hire or net-new-function posting corroborated by a recent headcount or financing event justifies same-day routing, because the decisions are open now. A leadership hire above an existing team is usually better worked after the person starts, in their first 90 days, when they have a mandate and a budget. A steady, unchanged hiring pattern is context for a nurture sequence rather than a trigger. PredictLeads exposes seniority, job category, and posting timestamps as fields, so the tier can be assigned by query rather than by manual review.
Use two passes. The first removes known job boards, aggregators, classifieds, and IT-services, staffing, and recruiting companies by domain and industry. The second is a plausibility check on posting volume against claimed company size, which catches the reposting operations that the first pass misses: a 200-person company running 150 concurrent distinct requisitions is almost certainly posting on behalf of clients. In PredictLeads’ own ranking of US tech hiring hubs, those two passes together removed close to half of the raw candidate pool. Skipping this step is the most common reason a hiring-signal list underperforms.
The expansion group is the one to watch: increases_headcount_by, expands_facilities, expands_offices_in, expands_offices_to, and opens_new_location. A job posting says a company intends to hire; these events say it already did, which is a higher confidence level. Recent examples include AEVEX Corp. expanding manufacturing and office space in Florida and Virginia and Options Technology Ltd. increasing headcount by 12 in Singapore, both found on September 10, 2026. The cost-cutting categories decreases_headcount_by and closes_offices_in work in the other direction and should suppress an account from a hiring-triggered play.
Yes, and the combination is stronger than either signal alone because it answers the budget question directly. Fresh capital plus a hiring spike in your buyer’s function in the same quarter means the spend has been raised and is being deployed. PredictLeads Financing Events covers 210,800+ events since 2016 with normalized financing types from pre_angel through series_j, all resolving to the same company record as the Job Openings data. That shared join key is what makes the check a lookup rather than an entity-matching exercise across two vendors.
It is evidence that the company uses or plans to use the technology, not confirmation that it is deployed. A required skill in a posting can reflect a live deployment, a planned adoption, a migration in progress, client work rather than internal use, or simply an aspirational requirement. Treat it as one input and corroborate it before building an outreach angle on it. PredictLeads Technology Detections uses job descriptions as one of five detection sources alongside script tags, DNS records, IP ranges, and cookies, with a behind_firewall boolean that flags detections found somewhere other than a public website tag.
Four delivery methods cover the common setups: the REST API for real-time lookups and enrichment at request time, flat files for warehouse ingestion and historical backfills, webhooks for pushing new signals on followed accounts, and MCP for AI agent workflows. Most GTM teams start with a nightly discovery query that writes tiered accounts and the triggering posting URL into the CRM, then add webhooks once the tiers are tuned. The PredictLeads MCP server at mcp.predictleads.com answers natural-language queries such as finding 10 companies hiring SDRs in the US. A free account includes 100 API requests, which is enough to test the fields against your own account list.
Related Guides
- Company Signals: Hiring, News, Funding, and Technology Changes – where hiring sits in the full signal stack.
- How to Find Companies Hiring for a Specific Role with O*NET Codes – the endpoint-level mechanics behind step 1.
- Sales Trigger Events: An Outbound Outreach Guide – how to time outreach once a trigger fires.
- Best Outbound Buying Signal Tools – how hiring data compares with the other buying signal types.
- Hiring Momentum Tracker: 10 Industries Accelerating Hiring – which sectors are adding roles fastest right now.
Ready to see this in your own data?
Get 100 free API requests when you create an account – no credit card, no sales call.