# Hiring Signal Radar — ATS Job Board Monitor + AI Tagging (`congism/hiring-signal-radar`) Actor

Track company job boards (Greenhouse, Lever, Ashby) for new postings, and get Claude-tagged buying-intent insights the moment a target account starts hiring for a role that matters to your pitch.

- **URL**: https://apify.com/congism/hiring-signal-radar.md
- **Developed by:** [Cong](https://apify.com/congism) (community)
- **Categories:** Lead generation, AI, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 new posting founds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Hiring Signal Radar — ATS Job Board Monitor + AI Tagging

**Know the moment a target account starts hiring for a role that matters to your pitch.**

Hiring Signal Radar tracks company job boards on Greenhouse, Lever, and Ashby — the three ATS platforms that expose public job APIs — and reports newly-opened postings since the last run. With an Anthropic API key set, each new posting gets a Claude-generated role category, seniority estimate, and a one-sentence buying-signal insight (e.g. "first DevOps hire suggests they're scaling infra now").

***

### Why ATS APIs instead of scraping LinkedIn

Most hiring-signal tools scrape LinkedIn or Indeed, which means constant breakage against anti-bot defenses. Greenhouse, Lever, and Ashby all expose **public, unauthenticated JSON APIs** for their customers' job boards — no login wall, no bot detection, no proxy required. That makes this Actor cheap to run and low-maintenance, at the cost of only covering companies that use one of those three ATS platforms (a large and growing share of tech/startup hiring).

The output is clean structured JSON per posting — plug it straight into an AI agent, a CRM enrichment pipeline, or Zapier.

***

### Quickstart

#### 1. List companies to track

```json
[
  { "name": "Notion" },
  { "name": "Ramp" },
  { "name": "Ro", "leverSlug": "ro" }
]
```

If you know the exact board slug, set `greenhouseSlug` / `leverSlug` / `ashbySlug` for a guaranteed match. Otherwise the Actor auto-detects the board by trying name-derived slug guesses against all three ATS platforms and caches whichever one resolves.

#### 2. (Optional) Add keywords to watch

`watchKeywords`: e.g. `["DevOps", "Enterprise Sales", "Data Platform"]` — matching postings get flagged with 🎯 in Slack. Leave empty to track everything.

#### 3. (Optional) Add your Anthropic API key

Get one at [console.anthropic.com](https://console.anthropic.com). Without it, you still get every new posting — just without the AI role/seniority/buying-signal tags.

#### 4. Run it once to capture a baseline

The first run per company just records the current open-jobs list — no "new posting" output yet, since there's nothing to diff against.

#### 5. Set up a schedule

Apify **Schedules** tab → daily or every few hours. From then on, new postings are detected automatically.

***

### Output

One dataset record per new posting:

```json
{
  "company": "Ramp",
  "ats": "ashby",
  "boardSlug": "ramp",
  "job": {
    "externalId": "34413f8d-26bf-4bbc-8ade-eb309a...",
    "title": "Security Engineer, Cloud",
    "department": "Engineering",
    "location": "New York, NY (HQ)",
    "url": "https://jobs.ashbyhq.com/ramp/...",
    "postedAt": "2026-07-30T00:00:00.000Z"
  },
  "tag": {
    "roleCategory": "DevOps/Infra",
    "seniority": "Senior",
    "buyingSignalInsight": "A senior cloud security hire signals Ramp is investing in infra hardening — good timing for security tooling or compliance pitches."
  },
  "matchedKeywords": ["Security"],
  "detectedAt": "2026-07-31T14:00:00.000Z"
}
```

***

### Pricing guidance

Billed per company tracked per run (pay-per-event recommended). Each company costs one or two lightweight JSON API calls plus, if AI tagging is enabled, one Claude Haiku call per run covering all that company's new postings in a single batch — not one call per job.

***

### Known limitations

- **Only covers Greenhouse, Lever, and Ashby.** Companies on Workday, LinkedIn-only, or a custom careers page won't resolve — the Actor reports an error for that company rather than guessing.
- **Auto-detect is name-based guessing.** It tries the company name as a slug across all three platforms; if the company's actual slug is different (rebrand, abbreviation), set the explicit `*Slug` field.
- **A company changing ATS platforms** will look like every job is "new" on the next run relative to the old snapshot — this is a one-time false signal, not an ongoing issue.

***

### Architecture

```
Greenhouse / Lever / Ashby public JSON APIs → normalized job list
  → Apify KV Store (previous job-ID snapshot per company)
  → Diff engine (new postings since last run)
  → Claude Haiku (batched role/seniority/buying-signal tagging)
  → Slack Block Kit digest
  → Apify Dataset (full run archive)
```

# Actor input Schema

## `companies` (type: `array`):

List of companies to monitor. Each item needs a 'name'. If you know the exact ATS board slug, set 'greenhouseSlug', 'leverSlug', or 'ashbySlug' for a reliable match — otherwise the Actor will try to auto-detect the board from the company name.

## `watchKeywords` (type: `array`):

Job title/department keywords to highlight, e.g. 'DevOps', 'Data Platform', 'Enterprise Sales'. Leave empty to track all new postings.

## `onlyNotifyMatchingKeywords` (type: `boolean`):

When enabled and watchKeywords is set, Slack notifications and dataset output only include postings that match at least one keyword. All new postings are still detected either way.

## `anthropicApiKey` (type: `string`):

Your Anthropic API key. When set, each new posting gets a Claude-generated role category, seniority estimate, and a one-line buying-signal insight. Get a key at console.anthropic.com. Leave empty to skip AI tagging and just get raw new-posting data.

## `slackWebhookUrl` (type: `string`):

Slack Incoming Webhook URL for a digest of new postings. Leave empty to skip Slack notifications. Create one at api.slack.com/apps.

## Actor input object example

```json
{
  "companies": [
    {
      "name": "Notion",
      "greenhouseSlug": "notion"
    },
    {
      "name": "Linear"
    },
    {
      "name": "Vercel"
    }
  ],
  "watchKeywords": [],
  "onlyNotifyMatchingKeywords": false
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        {
            "name": "Notion",
            "greenhouseSlug": "notion"
        },
        {
            "name": "Linear"
        },
        {
            "name": "Vercel"
        }
    ],
    "watchKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("congism/hiring-signal-radar").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "companies": [
        {
            "name": "Notion",
            "greenhouseSlug": "notion",
        },
        { "name": "Linear" },
        { "name": "Vercel" },
    ],
    "watchKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("congism/hiring-signal-radar").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companies": [
    {
      "name": "Notion",
      "greenhouseSlug": "notion"
    },
    {
      "name": "Linear"
    },
    {
      "name": "Vercel"
    }
  ],
  "watchKeywords": []
}' |
apify call congism/hiring-signal-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=congism/hiring-signal-radar",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/2wn4VIiLccizs9BY9/builds/RWG0veqwkV40FHpUW/openapi.json