Hiring Signal Radar — Greenhouse, Lever & Ashby to CRM

Public-job intelligence for recruiting analytics, RevOps research and market monitoring. No API keys required.

Fetch normalized open job postings from up to 12 public company job boards across Greenhouse, Lever and Ashby. Save them as exportable dataset rows, compare them to a prior snapshot you own, and optionally get an evidence-linked CRM research CSV explaining which hiring roles might be relevant to sales operations. No candidate data, private credentials, or auto outreach.

What you get

• Dataset: individual jobs with title, public URL, location, provider, department (where available), compensation (where disclosed), date signal, deterministic ID and fingerprint.
• Storage → Key-value store → SNAPSHOT: all current normalized jobs; copy into previousSnapshot on a subsequent run to identify additions, changes and removals.
• SUMMARY: boards checked, results counted, errors, comparison status and safety caps.
• OPPORTUNITIES: company-board-level research hypotheses, including role evidence and explainable triage scores.
• CRM_EXPORT: ready-to-review CSV; buyer identity, email address, buying intent, company size and pain are not invented.

Copy-paste first run

{
  "sources": [
    {"provider": "ashby", "board": "Ashby"},
    {"provider": "greenhouse", "board": "12twenty"},
    {"provider": "lever", "board": "toptal"}
  ],
  "maxJobsPerSource": 100,
  "previousSnapshot": [],
  "emitUnchanged": false,
  "includeOpportunities": true,
  "includeStableOpportunities": true
}

A board is the slug from its public careers page, not its full URL. Example: from https://jobs.lever.co/toptal, choose provider lever, board toptal; from https://jobs.ashbyhq.com/Ashby, choose ashby, board Ashby. For Lever EU select region: "eu".

The first run is a baseline, never evidence of a freshly opened position. On a later run, paste the JSON from the first run's SNAPSHOT into previousSnapshot to classify new, updated, and removed. There is no automatic cross-run history in this Store edition, by design: your state remains in your own run's storage. You can export that state into a scheduler or another workflow if you want to automate the handoff.

Pay only for relevant postings

You can narrow the returned job rows with optional titleKeywords, locationKeywords, and remoteOnly parameters. By default titleKeywords searches only the job title, avoiding jobs that match merely because their department is Sales. For broader research set titleSearchScope: "title_department_team" explicitly. These filters are case-insensitive and evaluated before rows are written to the paid dataset. A job must match at least one title term and one location term (when both are supplied). For example:

{
  "sources": [
    {"provider": "ashby", "board": "Ashby"},
    {"provider": "greenhouse", "board": "12twenty"}
  ],
  "maxJobsPerSource": 100,
  "titleKeywords": ["sales", "account executive", "revenue operations"],
  "titleSearchScope": "title_only",
  "locationKeywords": ["remote", "united states"],
  "remoteOnly": false,
  "previousSnapshot": [],
  "includeOpportunities": true
}

The default titleSearchScope: "title_only" ignores department and team; choose title_department_team only if you intentionally want to broaden the results. A public test using keywords sales and account executive emitted 31 postings under the broader legacy logic; 6 of those did not match either keyword in the visible title. This stricter default should exclude them when the same postings remain available, but the exact count can change over time.

remoteOnly relies on a remote label in the ATS-provided location or workplace field. It does not invent a remote flag from the job title. Filters are applied after the configured cap per provider, so if a board has more jobs than the cap, matching roles beyond that cap may not be fetched. Increase maxJobsPerSource (maximum 500) when broader coverage is needed; this can increase platform processing. The saved SNAPSHOT keeps all fetched records regardless of filters, preserving comparisons across runs. SUMMARY.changes counts all fetched changes, while SUMMARY.dataset_rows and SUMMARY.filters.items_emitted represent the billable output after filtering. If no jobs match, only the low start-event fee may apply.

What opportunity signals mean

The optional CRM report maps job titles in sales, customer acquisition, sales operations, CRM administration and demand generation into transparent, reviewable research hypotheses. It does not prove an actual problem, purchasing intent, spending ability or a reachable buyer. Existing postings remain RESEARCH; new relevant roles can raise the activity priority only after you provide a prior snapshot. A sales hypothesis is not a verified lead. Outputs include outreach_ready: false and qualification gaps until independently researched.

Limits and reliability

• Up to 12 job boards per run; 1–500 jobs per board, default 100.
• Only fixed Greenhouse, Lever, Ashby public API domains are called (no user-supplied URLs, cookies, proxies or redirects).
• When a board fails or the maximum record cap truncates its list, the Actor does not infer removed postings from missing results.
• Dates differ across providers: Greenhouse updated_at, Lever createdAt and Ashby publishedAt are different concepts and not directly comparable.
• No database subscriptions, outreach, personal-email scraping, company-size verification or warranty of purchase intent.
• The public Store edition rejects autoTrack: true. Never supply other users' prior snapshots.
• Company labels use board slugs, not verified legal entities. Multiple boards for one company can produce separate records.
• Please respect each provider's terms and local data laws. Public postings can change or become unavailable.

Pricing and payment

If a developer configures pay-per-event monetization in the Apify Console, customers are charged according to the clearly displayed Store listing price and events. The standard default-dataset-item event supports per-result pricing without additional code; start events can cover initial compute costs. No monetization is enabled by this README. Billing, event prices and actual costs are managed by Apify Console.

Integration

Use the Apify REST API or schedule an Actor run to get public jobs. To build a recurring diff pipeline, keep and feed back your latest SNAPSHOT as next run's previousSnapshot. Unchanged jobs are omitted by default for a smaller event dataset. For raw research on an existing board, set includeStableOpportunities: true.

Support and source

The source is maintained in a GitHub repository. Issues should contain public board slugs, provider, error summary and sanitized settings, but never credentials or customer data.

API references:

• https://developers.greenhouse.io/job-board.html
• https://github.com/lever/postings-api
• https://developers.ashbyhq.com/docs/public-job-posting-api
• https://docs.apify.com/actors/publishing/monetize

Run checks before deploying this edition: python -m unittest discover -s tests -v.

Disclaimer: This is a data monitoring and research tool, not a recruiting platform, financial forecast or qualified-lead database.