Company Hiring Signals: Open Roles & Hiring Velocity
Pricing
from $6.00 / 1,000 company profileds
Company Hiring Signals: Open Roles & Hiring Velocity
Hiring signals for any company domain: ATS, open roles, roles by function, seniority and location, new roles in the last 7 and 30 days, and a hiring velocity score. One row per company from official Greenhouse, Lever, Ashby and Workable job-board APIs.
Pricing
from $6.00 / 1,000 company profileds
Rating
0.0
(0)
Developer
Zac P
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 hours ago
Last modified
Categories
Share
What does Company Hiring Signals do?
Company Hiring Signals turns a company domain into one hiring-signal row. Send ramp.com and you get back which ATS the company uses, how many open roles it has, the mix by function, seniority and location, the remote share, roles added in the last 7 and 30 days, a hiring velocity score, and ready-to-filter signals like hiring_sales.
It's built for sales and growth teams who use hiring as a buying signal ("they're hiring 3 SDRs, they need our tool"), in Clay, n8n and Make, and for AI agents over MCP. No LinkedIn, no scraping of job aggregators, and no job rows to count yourself. Data comes from the official public job-board APIs of Greenhouse, Lever, Ashby and Workable.
1,000 accounts ≈ $6. You pay $0.006 per company only when a job board is found. Companies with no supported board, or that can't be reached, are free.
30-second example
Input:
{ "companies": ["ramp.com"] }
Output (real run, 2026-09-27, trimmed):
{"input": "ramp.com","domain": "ramp.com","status": "ok","ats": "ashby","boardUrl": "https://jobs.ashbyhq.com/ramp","openRoles": 158,"newRoles7d": 19,"newRoles30d": 60,"newestPostedAt": "2026-09-26","byFunction": { "sales": 37, "engineering": 33, "customer_success": 33, "product": 10, "operations": 8 },"bySeniority": { "mid": 103, "senior": 19, "manager": 10, "lead": 8, "director": 7 },"topLocations": [{ "name": "New York, NY", "count": 122 },{ "name": "London", "count": 11 }],"remoteShare": 0.09,"salaryDisclosedShare": 0.96,"medianSalaryUsd": 204000,"techMentioned": ["Python", "Salesforce", "SQL", "LLM", "AWS"],"hiringVelocity": 90,"signals": ["hiring_sales", "hiring_engineering", "hiring_customer_success", "hiring_leadership", "hiring_surge"],"datesSource": "ats","errors": []}
Why use it?
- One row per company, in your order. You get one row per input, in the same order, with your input echoed. It drops straight into a Clay column or a spreadsheet.
- A domain is enough. It finds the company's ATS from its website, or from its careers page or board URL if you have one.
- Right company or nothing. A board is only used when the company's own site links to it, or the board itself points back to the company's domain. A different company that happens to share the name ("acme") is never returned. When nothing checks out you get
no_board_found, free. - Priced per company, not per job. A 150-role company costs $0.23–$0.60 with per-job scrapers; here it's $0.006.
- Watch mode lists the roles opened and closed since your last run. Put it on a weekly schedule for alerts.
Output fields
| Field | What it is |
|---|---|
input, domain | Your input, and the company domain it resolved to |
status | ok (board found, charged), no_board_found (free), unreachable (free) |
ats, boardUrl | greenhouse, lever, ashby or workable, and the public board |
openRoles | Open roles on the board |
newRoles7d, newRoles30d, newestPostedAt | Roles posted in the last 7 and 30 days, from the ATS's own posting dates |
byFunction | Roles per function: engineering, data, product, design, sales, marketing, customer_success, operations, finance, people, legal, other |
bySeniority | Roles per level: intern, junior, mid, senior, lead, manager, director, executive |
topLocations | The 5 most common primary locations |
remoteShare | Share of roles marked remote |
salaryDisclosedShare, medianSalaryUsd | Share of roles with a pay range, and the median annual midpoint in USD (converted at approximate rates) |
techMentioned | Technologies named in two or more postings |
hiringVelocity | 0–100: how many roles opened in 30 days, and what share of the board they are |
signals | hiring_<function> (a function with at least 10% of the board or of recent roles), hiring_leadership, hiring_surge, hiring_slowdown, expanding_new_location:<place>, remote_friendly |
newRoles, closedRoles | Watch mode only: roles opened and closed since the previous run |
detectedAts | For no_board_found: an unsupported ATS we recognised, e.g. workday |
errors | Plain-language notes: why a board wasn't found, or a cap that was hit |
Function and seniority come from deterministic rules on the job title. Seniority is about 92% accurate and function about 83% on titles the rules have never seen, so treat them as a strong guide rather than an audit. The rules are tuned every week.
Input
| Field | Default | Notes |
|---|---|---|
companies | ["gitlab.com"] | Domains, careers URLs or board URLs. Required |
includeJobs | false | Also write one row per job to a second dataset, at $0.001 per job row. No description text |
watchMode | false | Return newRoles and closedRoles since the previous run |
departments | [] | Filter the job rows by department. The summary always covers the whole board |
maxJobsPerCompany | 2000 | Hard cap per board |
maxConcurrency | 25 | Companies in parallel |
How much does it cost?
| Event | Price | When |
|---|---|---|
| Company profiled | $0.006 | status is ok |
| Job row | $0.001 | Each job row, only with includeJobs on |
There's no start fee and no charge per dataset item. no_board_found and unreachable are free, and a duplicate input is charged once.
Use it in Clay, n8n, Make or an AI agent
Clay: add an Apify integration column (or an HTTP column calling the Actor's run-sync endpoint) with {"companies": ["{{Domain}}"]}, one row per account. Then filter on signals contains hiring_sales.
n8n / Make: use the Apify node. Run the Actor with your list, then read the dataset. For weekly alerts, schedule it with watchMode: true and send the rows where newRoles isn't empty.
AI agents (MCP): add the Actor to the Apify MCP server. An agent only needs {"companies": ["ramp.com"]} to answer "Is Ramp hiring engineers in London?"
API:
curl -X POST "https://api.apify.com/v2/acts/vicarious_film~company-hiring-signals/run-sync-get-dataset-items?token=$APIFY_TOKEN" \-H 'Content-Type: application/json' -d '{"companies":["ramp.com","gitlab.com"]}'
FAQ
Is there a 200-job cap? No. Boards are read in full up to maxJobsPerCompany (2,000 by default, up to 10,000), and the counts cover every job read.
Do date filters work? Yes. The new-role counts use each ATS's own publish date (first_published, createdAt, publishedAt, published_on), not the time of the scrape.
Will I get "403 – not subscribed" errors? No. There's no third-party backend to subscribe to: the Actor calls the vendors' public board APIs directly.
Which companies aren't covered? Companies on Workday, iCIMS, SuccessFactors, Taleo and other enterprise ATSs return no_board_found with detectedAts set, and aren't charged. A few companies only show their board through JavaScript on their own site, and some of those can't be found from the domain. Pass the board URL instead.
Is any personal data returned? No. No recruiter, hiring-manager or applicant names are ever output, and job rows carry no description text.
Pairs well with Company Domain Profiler: contacts, tech stack and email infrastructure for the same accounts.