Company Hiring Signals Monitor 如何從公司網域彙整職位空缺作銷售訊號
Use open job postings as a sales signal: which companies are hiring for what, from just a domain
Lindenbyte 展示自家 Apify Actor Company Hiring Signals Monitor 如何按公司網域識別 ATS,彙整公開職位空缺及招聘摘要,供銷售團隊判斷招聘方向。
Disclosure: I'm Lindenbyte, the small studio that built the Apify Actor used below, and this post was
drafted with AI assistance. You can read any company's careers page by hand; this is a way to do it for a list of target accounts
at once and get a summary plus "what changed since last week".
If you sell to engineering, sales or security teams, a company's open roles tell you where it is investing. 66 open sales roles at a SaaS company means one thing, 16 engineering roles another.
The catch: companies use different applicant-tracking systems (ATS), so you would need a different scraper per target.
The Company Hiring Signals Monitor takes company domains, detects which ATS each one uses
(Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Personio) and returns one summary row per company plus, optionally, the job rows.
1. Feed it domains
{
"companies": ["notion.so", "bunq.com", "ashbyhq.com"],
"stateKey": "target-accounts",
"includeCompanySummary": true,
"outputJobRows": true
}
In our local test (2026-11-17) it found: Notion on Ashby (165 open roles, detected from a link on its careers page), bunq on Recruitee (24 roles, same way)
and Ashby's own board (77 roles, found by guessing the board name from the domain, marked confidence: low so you know to double-check).
Domains whose ATS is unsupported (e.g. Workday) or that use a custom careers site get a free status row such as no-ats-detected instead of an error.
2. Read the company summary
Each company gets one company-summary row. For Notion it showed, for example, 66 of 165 open roles in Sales, 21 "Outcomes Architect", 16 Engineering and 16 People;
59 roles in San Francisco and 37 in Dublin; and a velocity block with 18 roles posted in the last 7 days and 60 in the last 30. For bunq: 24 roles, 15 in Amsterdam, 2 in Sofia,
14 posted in the last 30 days. That one row is usually enough to decide whether an account is "hiring into your category".
3. Only new jobs, and what closed
Run the same input again later. The Actor keeps a snapshot per stateKey, so with onlyNewJobs it returns only jobs that were not there last time, and the summary
gains newSinceLastRun, closedSinceLastRun, netChange and the list of closed roles. The first run is the baseline (every row is returned once with isBaseline: true; set emitOnBaseline to false to skip them).
Add keywordFilter, departmentFilter, locationFilter or remoteOnly to watch for the roles you care about, e.g. "Head of Security" at accounts in your CRM.
4. Pipe it into your CRM or Slack
from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("lindenbyte/company-hiring-signals-monitor").call(run_input={
"companies": ["notion.so", "bunq.com"],
"stateKey": "target-accounts",
"onlyNewJobs": True,
"keywordFilter": ["security", "data"],
})
for row in client.dataset(run.default_dataset_id).iterate_items():
if row["rowType"] == "company-summary":
print(row["company"], row["openRoles"], "open,", row["newSinceLastRun"], "new")
Schedule it weekly in the Apify Console and send the dataset to a webhook, Google Sheets or your CRM.
Cost and limits
Pay-per-event: a $0.003 start fee, $0.0015 per job row and $0.005 per company summary. Use outputJobRows: false if you only want summaries: a weekly check of 50 target accounts is about $0.25. Status rows (no supported ATS found, site unreachable) are free.
Honest limits: only the seven ATS systems above (not Workday or custom sites); it reads only public job-board data and strips recruiter names and emails; posting dates depend on what each ATS exposes;
a job count is a hint about hiring plans, not proof of a budget.
來源:DEV Community · dev.to