ATS Hiring Signal Radar

Pricing

Rating

Developer

Actor stats

Categories

Share

Monitor public ATS career pages and turn job posting changes into company-level hiring intent signals — so you know who is hiring, what they're building, and why it matters to you.

Why This Actor?

Job scrapers give you rows. This actor gives you answers.

Zero proxies. Zero login. Zero maintenance. All data comes from official public ATS APIs — no anti-bot issues, no cookie management, no breakage.

Who Is It For

• SDRs / Sales Teams — Find accounts showing buying intent before your competitors do
• Recruiters / Talent Intelligence — Track which companies are ramping specific teams
• Investors / Analysts — Monitor portfolio company growth and hiring velocity
• Market Researchers — Detect industry trends from hiring patterns at scale

Supported ATS Platforms

V2 roadmap: Workday, Rippling, BambooHR, JazzHR.

Key Features

10 Intent Triggers Across 3 Packs

Pre-built detection patterns that convert raw job deltas into named, explainable events:

GTM Pack — Sales, Marketing, RevOps signals

Engineering Pack — Dev, Security, Data, AI signals

Expansion Pack — Geo, Leadership, New Functions

Snapshot Diffing

Automatically stores and compares job snapshots between runs:

• New roles added since last scan
• Roles removed (filled or closed)
• Net headcount change
• Function distribution shifts (engineering vs. sales vs. marketing...)

Signal Scoring

Each company receives a 0-100 signal score:

• high (70+) — Strong hiring momentum with clear intent triggers
• medium (40-69) — Notable changes worth monitoring
• low (15-39) — Minor activity detected
• none (0-14) — Stable or no meaningful changes

First Scan Behavior

On the first scan of a new company, the actor captures a baseline snapshot without emitting signals (to avoid false positives). Signals start firing from the second run onward. You can override this with emitSignalsOnFirstScan: true.

Input

Full Input Reference

Company Object

Input Example

{
"companies":[
{
"name":"Stripe",
"domain":"stripe.com",
"boardUrl":"https://boards.greenhouse.io/stripe",
"tags":["fintech","competitor"]
},
{
"name":"Figma",
"boardUrl":"https://jobs.lever.co/figma",
"tags":["design-tools","prospect"]
},
{
"name":"Linear",
"boardUrl":"https://jobs.ashbyhq.com/linear",
"tags":["dev-tools"]
}
],
"changesOnly":true,
"triggerPack":"all",
"minConfidence":0.3,
"maxCompaniesPerRun":100,
"emitSignalsOnFirstScan":false
}

Output

Each company produces one record in the dataset with the following fields:

Output Fields Reference

Output Example

{
"company":"Acme Corp",
"domain":"acme.com",
"tags":["prospect","series-b"],
"provider":"greenhouse",
"slug":"acmecorp",
"boardUrl":"https://boards.greenhouse.io/acmecorp",
"intentEvent":"first_revops_buildout",
"intentLabel":"First RevOps / Sales Ops Buildout",
"signalScore":72,
"signalStrength":"high",
"confidence":0.86,
"whyNow":[
"Sales Ops Manager posted",
"Salesforce Admin posted",
"BI Analyst posted"
],
"recommendedAngle":"CRM, pipeline visibility, forecasting, territory planning",
"allSignals":[
{
"triggerId":"first_revops_buildout",
"label":"First RevOps / Sales Ops Buildout",
"pack":"gtm",
"confidence":0.86,
"evidence":["Sales Ops Manager posted","Salesforce Admin posted","BI Analyst posted"],
"recommendedAngle":"CRM, pipeline visibility, forecasting, territory planning"
}
],
"newRoles":5,
"removedRoles":1,
"netChange":4,
"totalOpenRoles":23,
"previousOpenRoles":19,
"isFirstScan":false,
"functionDistribution":{
"engineering":8,
"sales":5,
"revops":3,
"marketing":4,
"other":3
},
"scannedAt":"2026-03-23T12:00:00.000Z",
"snapshotAge":"2026-03-22T12:00:00.000Z"
}

The run summary is stored separately in the Key-Value Store under the key RUN_SUMMARY:

{
"totalCompanies":50,
"processed":48,
"skipped":1,
"signalsDetected":12,
"errors":1,
"triggerPack":"all",
"changesOnly":true,
"completedAt":"2026-03-23T12:05:00.000Z"
}

Scheduling for Monitoring

This actor is built for recurring scheduled runs:

1. Set up a schedule — daily or weekly in Apify Console
2. Enable changesOnly: true — only companies with new activity appear in output
3. Connect webhooks — pipe results to Slack, email, HubSpot, or Salesforce via Make/Zapier
4. Tune minConfidence — raise to 0.5+ if you want fewer, higher-quality alerts

Pricing

This actor uses pay-per-event (PPE) pricing with a single event: company-scanned.

You are charged once per company successfully processed. Companies that are skipped or fail are never charged.

Cost Examples ($0.02 per company-scanned)

Changelog

v1.0.0

• Initial release
• Greenhouse, Lever (US + EU), Ashby support
• 10 intent triggers across GTM, Engineering, Expansion packs
• Snapshot diffing with signal scoring
• First-scan baseline capture (false positive prevention)
• Retry/timeout handling with exponential backoff
• Namespaced snapshot storage for multi-context monitoring