Skip to content

Jobs / Hiring Signals / Sales Triggers

ATS Hiring Signal Monitor for Greenhouse, Lever, Ashby

Monitor public ATS job boards for new roles, closed roles, team growth, remote hiring, and account-level sales or recruiting signals.

2026-05-30 · 7 min read

What this pipeline does

Hiring pages are one of the clearest public signals that a company is changing. New sales roles can point to go-to-market expansion. New platform roles can point to infrastructure work. Closed roles can show that a team finished a hiring push.

The ATS Hiring Signal Monitor scans public Greenhouse, Lever, and Ashby boards and returns normalized job rows, hiring summaries, change deltas, webhook alerts, and optional hiring briefs.

Best first run

Start with one public ATS board URL, not a huge account list.

{
  "startUrls": [
    "https://boards.greenhouse.io/example"
  ],
  "includeDescriptions": false,
  "enableAiBrief": false,
  "maxItems": 100
}

Check the basic fields first: source_ats, company, title, department, location, and hiring_velocity_label. Add descriptions and AI briefs after the source is working.

Signal row shape

{
  "source_ats": "greenhouse",
  "company": "Example",
  "title": "Senior Platform Engineer",
  "department": "Engineering",
  "location": "Remote - United States",
  "hiring_velocity_label": "expanding"
}

For sales and recruiting workflows, do not send every job to a human. First group by company, department, seniority, and change type. The useful alert is usually "this account added three senior data roles", not "this job exists".

Alerting workflow

Use these alerts first:

  • New executive, director, or head-of role
  • Two or more new roles in the same department
  • First sales or RevOps role at a target account
  • Remote hiring opened in a new region
  • Hiring velocity changed from quiet to expanding

These alerts are easy to explain and map to real follow-up work.

Deployment notes

Run weekly for broad account lists and daily for named accounts that sales, recruiting, or investors already care about. Keep a previous-run dataset so the monitor can separate new, changed, existing, and closed roles.