Hiring Velocity Signals — Greenhouse, Lever, Ashby + 4 more ATS avatar

Hiring Velocity Signals — Greenhouse, Lever, Ashby + 4 more ATS

Pricing

from $25.00 / 1,000 company hiring signals

Go to Apify Store
Hiring Velocity Signals — Greenhouse, Lever, Ashby + 4 more ATS

Hiring Velocity Signals — Greenhouse, Lever, Ashby + 4 more ATS

Track any company's public job board over time: new vs closed roles, growth %, 30-day trend, median days-to-fill, department mix and per-role opened/closed events. Schedule it daily and the history builds up in your own account.

Pricing

from $25.00 / 1,000 company hiring signals

Rating

0.0

(0)

Developer

Agilityy Research

Agilityy Research

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

15 minutes ago

Last modified

Features

Full permissions

Share

Hiring Velocity Signals — know when any company speeds up or slows down hiring

You give it the companies you care about. Every run you get one row per company that tells you whether that company is hiring faster or slower than last time: open roles, roles opened and closed, growth %, 30-day trend, median days-to-fill, what functions and seniority levels are being hired, AI/ML share, remote share, and the exact titles that appeared or disappeared. Optionally, one row per role that opened or closed, for alerts and for your own history of postings.

Put your 200 target accounts in, schedule it daily, and each morning you know which of them just opened five sales roles, which froze hiring, and how long their engineering roles take to fill. The history accumulates in your own Apify account from your first run.

The data is read from each company's public job board on Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee or Personio, through the vendors' own public JSON/XML feeds (the same data a visitor to the careers page sees). No login, no HTML scraping, no personal data.

Who it is for

  • Sales and revenue operations — growth in open roles is one of the strongest buying signals; a hiring freeze is a churn risk. Feed the rows into your CRM and route accounts by signal.
  • Recruiters and staffing agencies — see which clients are ramping, which roles stay open longest, where to pitch.
  • Investors and analysts — track portfolio and competitor headcount momentum weekly, from primary data.
  • Talent-intelligence and people-analytics teams — days-to-fill and posting lifecycle for the companies you benchmark against, measured the same way for every company.

If you want this for thousands of companies you did not pick yourself, with history that already exists, use Hiring Signals Feed (daily archive of 21,000+ companies, pay per row) instead.

What you get

Company signal row (one per company per run)

FieldWhat it tells you
company, provider, slug, careersUrlThe company and its public job board
snapshotAt, previousSnapshotAt, daysSincePrevious, snapshotsRecordedWhen this and the previous reading were taken
signalACCELERATING (3+ new roles and +20 %), STEADY, FLAT, CONTRACTING (board shrank 30 %+ with nothing new), BOARD_EMPTY (all roles gone); BASELINE on a company's first run
openRoles, previousOpenRoles, newRoles, closedRoles, netChange, growthPctChange since the previous run
trend30dPct, rolesOpened30d, rolesClosed30dRolling 30-day momentum
medianDaysToFillHow long the roles that closed had been open, counted from the posting date (first sighting when the vendor gives none)
functionsOpen roles by function: Engineering, Data & AI, Product, Design, Sales, Marketing, Customer, Operations, Finance, People, Legal, Clinical, Other
seniorityMixEntry, Mid, Senior, Staff/Principal, Manager, Director, Executive
aiRoles, aiRoleSharePctAI / ML / LLM roles and their share of the board
remoteSharePct, topDepartments, topLocationsWhere and what the company hires for
newRoleTitles, closedRoleTitlesThe titles that moved (up to 15 each)

Example:

{ "company": "Notion", "provider": "ashby", "signal": "ACCELERATING", "openRoles": 143, "previousOpenRoles": 131,
"newRoles": 14, "closedRoles": 2, "netChange": 12, "growthPct": 9.2, "trend30dPct": 18.4, "medianDaysToFill": 27,
"functions": [{"name": "Engineering", "roles": 61}, {"name": "Sales", "roles": 24}], "aiRoleSharePct": 11.2,
"remoteSharePct": 34.3, "newRoleTitles": ["Enterprise Account Executive", "Staff Software Engineer, AI"] }

Functions and seniority are derived from job titles and departments with explainable keyword rules, so they are comparable across companies whose department names differ.

Job event row (one per role that opened or closed, emitJobs on)

FieldWhat it tells you
eventTypeopened or closed
company, provider, slug, jobId, urlThe company and the role's public page
title, department, location, remoteAs published on the board
firstSeen, closedAt, daysOpenPosting lifecycle; daysOpen is set on closed events

Input

  • companies (required) — one entry per company: a board slug (stripe, auto-detected across all seven vendors) or a careers URL (https://boards.greenhouse.io/figma, https://jobs.lever.co/<slug>, https://jobs.ashbyhq.com/notion, https://apply.workable.com/<slug>, SmartRecruiters, Recruitee and Personio board URLs). 50–500 companies per run is typical.
  • emitJobs (true) — also write one row per role that opened or closed.
  • emitBaselineJobs (false) — on a company's first run every role would count as newly opened; leave off so the first run bills signals only.
  • stateStoreName (hiring-velocity-state) — the key-value store in your account that keeps snapshots between runs. Use different names for different watch-lists. Snapshots are stored as 128 shard records, so a run costs about 128 store writes however many companies it covers.
  • archiveDatasetName (optional) — a named dataset in your account that keeps every signal and job event beyond run-dataset retention. Recommended for scheduled runs.
  • maxConcurrency (5) — boards fetched in parallel.
  • qualityStoreName (hiring-quality) — a named key-value store with one RUN_QUALITY record per day: boards fetched vs not found, HTTP errors per vendor, open roles per vendor, day-over-day change, and two accuracy spot checks (25 boards re-counted on the vendor's public careers page, 10 closed roles re-fetched to confirm they are gone). The same record is in every run's key-value store; set the name empty to skip the named copy.
{ "companies": ["stripe", "https://jobs.ashbyhq.com/notion", "https://boards.greenhouse.io/figma"], "emitJobs": true }

How to run it

  1. Console — paste your list, click Run. The first run writes BASELINE rows; the second run gives you signals.
  2. Schedule — Apify → Schedules → daily (for example 0 6 * * * UTC). Signals need two runs; the 30-day trend and days-to-fill mature over a few weeks.
  3. Deliver — connect the dataset to Slack, Google Sheets, your CRM, Make, Zapier or a webhook with Apify Integrations, or read it with the API:
POST https://api.apify.com/v2/acts/agilityy~hiring-velocity-signals/runs?token=<your token>
body: the input JSON above
GET https://api.apify.com/v2/acts/agilityy~hiring-velocity-signals/runs/last/dataset/items?token=<your token>&format=csv
  1. AI agents (MCP) — Apify's MCP server (https://mcp.apify.com) exposes this product as a tool; add agilityy/hiring-velocity-signals to the tools your agent may call and it receives the same rows.

Pricing (pay per row)

EventPrice
company-signal — one row per company per run$0.025 launch price until 2027-01-21 (list price $0.05)
job-event — one row per role that opened or closed$0.004

Plus Apify compute for the run, a few cents. Examples at the launch price:

  • 200 companies, daily: 200 × $0.025 × 30 ≈ $150 per month in signals (≈ $300 at list price), plus about $0.004 per role that opens or closes.
  • 50 companies, weekly: 50 × $0.025 × 4 ≈ $5 per month.
  • Set emitJobs: false to pay for signals only.

Limits and good to know

  • Companies whose board cannot be found or whose board has no public feed produce no row and are not billed; the run's quality record counts them.
  • A company's first run is a BASELINE: there is nothing to compare against yet. Growth and trend need at least two runs; trend30dPct needs 30 days of your own history.
  • Workable, Personio and Recruitee rate-limit per IP; requests to them are paced automatically, so very large lists on those vendors take longer rather than fail.
  • Only official, public job-board feeds are read. No login, no HTML scraping, no personal data.

FAQ

Can I backfill history from before my first run? No. Snapshots start on your first run; the 30-day trend and days-to-fill fill in as your history grows. For 21,000+ companies with history that already exists, use Hiring Signals Feed.

Why does medianDaysToFill stay empty at first? It is computed from roles that closed while you were tracking them. It appears after your first closures and becomes stable after 30–60 days.

Can I get benchmarks from this history? Yes. Hiring Pulse Benchmarks reads the same state store and gives you benchmarks by industry, company size and job-board vendor, leaderboards and a weekly Markdown report.

Is there a free market-wide view? The weekly Hiring Pulse report across 21,000+ companies is free at https://hiring.agilityy.com/ ; bulk access (monthly CSV, Snowflake share) is described at https://hiring.agilityy.com/for-data-teams/ .

Hiring Signals Feed — the same rows for 21,000+ companies, read every day, pay per row. Company Hiring Lookup — one profile per company, right now, no history. Greenhouse / Lever / Ashby / Workable Jobs Scraper — one row per open role. YC Companies Hiring Tracker — this product with the 650+ Y Combinator job boards built in.