# B2B Hiring Signal Tracker — Who's Hiring & Why (AI) (`noniner/b2b-hiring-signal-tracker`) Actor

Track which companies are hiring, for what, and what it means. Pulls open roles from company career sites, then AI reads the signal: which teams are growing and whether it's a buying or expansion signal for your sales or recruiting.

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

## Pricing

from $150.00 / 1,000 company trackeds

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## B2B Hiring Signal Tracker — Who's Hiring & Why (AI)

**Hiring is the loudest public signal a company sends.** When a company opens ten sales roles, it's about to scale revenue. When it posts its first security engineer, it just crossed a compliance line. When a whole team appears, a new product is coming. This Actor reads that signal for you: give it **company domains**, it pulls their **open roles** straight from the company career site, and then AI tells you **which teams are growing and whether it's a buying or expansion signal** for your sales or recruiting.

You bring the companies. It hands back a hiring-intent read.

***

### The flow

```
1. Give company domains        2. Pull open roles                3. AI reads the signal
   stripe.com              →       (noniner/career-site-jobs-api:  →    growth level · depts growing ·
   notion.so                       Greenhouse/Lever/Ashby/...)       buying signal · recruiting angle
                                            │
                                            ▼
                                    aggregate deterministically
                                    (roles · departments · locations · remote)
```

1. **Give company domains** (or website URLs / emails). The tracker derives each company's career-board handle from the domain name.
2. **It pulls the open roles** from each company's public applicant-tracking system via the [`noniner/career-site-jobs-api`](https://apify.com/noniner/career-site-jobs-api) organ — Greenhouse, Lever, Ashby, Recruitee and Workable. No login, no proxies.
3. **It aggregates the roles deterministically** (count, department mix, locations, remote), then an OpenAI layer **reads the signal** and returns a growth level, the departments growing, and a one-line buying and recruiting interpretation.

***

### What you get per company

For every company, the Actor returns:

1. **`isHiring` + `openRolesCount`** — whether the company has open roles right now, and how many.
2. **`roleCategories`** — open roles bucketed by function: Engineering, Sales, Marketing, Product, Ops, Security, Finance, HR, Other.
3. **`matchedRoles`** — job titles matching the roles/skills you chose to watch (e.g. `security`, `RevOps`, `sales`).
4. **`topLocations` + `remoteCount`** — where they're hiring and how many roles are remote-friendly.

Then the **AI layer** (OpenAI `gpt-4o-mini`, fast and low-cost) adds, grounded only in the roles above:

- **`growthSignal`** — `none` · `low` · `medium` · `high`, from the volume and breadth of hiring.
- **`departmentsGrowing`** — the functions with the most openings.
- **`hiringSummary`** — one sentence on what they're hiring for.
- **`buyingSignalInterpretation`** — one sentence on what this hiring implies for a **seller** of what *you* sell (or a general read if you leave `offering` blank).
- **`recruitingAngle`** — one sentence for a **recruiter**: what talent this company is competing for.

If no open roles are found for a company, it still comes back with `isHiring: false`, `growthSignal: "none"` and an honest note — the run always succeeds.

***

### Three ways people use it

- **Sales intent / buying signals from hiring** — find out **which companies are hiring for X** and turn it into pipeline. A company staffing up RevOps or sales ops is about to buy tooling; a company hiring its first security lead needs compliance software. Feed your target accounts and let the AI flag the **growth signals** that mean "reach out now".
- **Recruiting market intel** — see what talent your competitors are fighting for, which functions they're scaling, and where (remote vs. hubs) — a live read on the **hiring market** for the roles you place.
- **Competitor headcount tracking** — watch a list of competitors over time: rising `openRolesCount` and new `departmentsGrowing` expose expansion, new product bets and go-to-market pushes before any press release.

***

### How it works

This Actor is an orchestrator. It calls the public [`noniner/career-site-jobs-api`](https://apify.com/noniner/career-site-jobs-api) Actor once with all your companies, mapping each domain to its likely career-board handle across the supported applicant-tracking systems. Boards that don't exist for a company are skipped silently (never charged); boards that do exist return their open roles in one clean schema. The tracker then aggregates those roles per company and sends only the aggregated picture to OpenAI for the signal read — so the LLM is grounded in real postings, not guesses, and token cost stays tiny.

***

### Input

| Field | Type | Notes |
|---|---|---|
| `domains` | array | **Required.** Company domains, website URLs or emails (domain is extracted). One per line. |
| `keywords` | array | Roles/skills to flag, e.g. `["security","RevOps","sales"]`. Matching titles come back as `matchedRoles`. Empty = track all. |
| `offering` | string | What you sell. If set, `buyingSignalInterpretation` is sharpened for you as a seller. |
| `postedWithinDays` | integer | Only count roles posted within this many days. Default `30`. `0` = no date filter. |
| `maxJobsPerCompany` | integer | Cap on roles collected per company before aggregation. Default `50`. |
| `maxResults` | integer | Max companies to track. Default `50`. One charge per company. |
| `maxConcurrency` | integer | Companies interpreted in parallel. Default `3`. |
| `model` | string | Override the OpenAI model. Default `gpt-4o-mini`. |

#### Minimal input example

```json
{
  "domains": ["stripe.com", "notion.so"],
  "keywords": ["security", "sales"],
  "offering": "We sell a SOC 2 compliance automation platform for scaling SaaS companies."
}
```

***

### Output example

```json
{
  "domain": "stripe.com",
  "companyName": "Stripe",
  "isHiring": true,
  "openRolesCount": 47,
  "roleCategories": { "Engineering": 24, "Sales": 8, "Ops": 6, "Product": 5, "Security": 3, "Other": 1 },
  "matchedRoles": ["Security Engineer, Detection & Response", "Enterprise Account Executive"],
  "topLocations": ["Remote (US)", "San Francisco", "Dublin"],
  "remoteCount": 19,
  "growthSignal": "high",
  "departmentsGrowing": ["Engineering", "Sales", "Security"],
  "hiringSummary": "Stripe is hiring broadly across engineering, sales and a growing security team.",
  "buyingSignalInterpretation": "A new security team plus heavy engineering growth is a strong buying signal for a SOC 2 compliance platform — compliance scope is expanding faster than headcount can cover manually.",
  "recruitingAngle": "They're competing hard for detection-and-response security engineers and enterprise AEs, mostly remote-US."
}
```

A company with no discoverable open roles comes back with `isHiring: false`, `openRolesCount: 0`, `growthSignal: "none"` and an honest summary.

***

### Pay-per-event pricing

This Actor uses **pay-per-event** billing with a single event:

| Event | Price | Charged when |
|---|---|---|
| `company-tracked` | $0.15 | Once per company whose open roles were collected and interpreted into hiring, growth and buying signals. |

The Actor logs its OpenAI token usage and the estimated AI cost at the end of every run, so the event price stays safely above the model cost.

***

### Setup

The AI layer calls the OpenAI API. Set the environment variable / secret **`OPENAI_API_KEY`** on the Actor. Collecting open roles runs without it; only the signal interpretation needs it.

***

### Use it from an AI agent (Apify MCP server)

This Actor is available through the [Apify MCP server](https://mcp.apify.com), so AI agents (Claude, ChatGPT, or anything that speaks MCP) can call it as a tool — hand it a list of `domains` and an `offering`, and read back the hiring signals — with no custom integration code.

***

### Run it locally

```bash
npm install
## put your input in storage/key_value_stores/default/INPUT.json
export OPENAI_API_KEY=sk-...   # required for the signal interpretation
apify run -p
```

***

### Related actors

- [Career Site Jobs API](https://apify.com/noniner/career-site-jobs-api) — Every open job from Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Recruitee and Workable in one schema. The organ this tracker reads from.
- [B2B Intent Radar](https://apify.com/noniner/b2b-intent-radar) — Spot buying intent across the web for your target accounts.
- [B2B Talent Sourcing Brief](https://apify.com/noniner/b2b-talent-sourcing-brief) — Turn a role into a sourcing brief with the market and talent landscape.
- [AI Company Enrichment](https://apify.com/noniner/ai-company-enrichment) — Turn domains into structured firmographic profiles with contacts, socials and ICP fit.

***

**Part of the [No Niner](https://noniner.io) toolkit** — no-code web scraping, enrichment & AI data tools, all pay-per-use. Browse the full set at **[noniner.io](https://noniner.io)**.

# Actor input Schema

## `domains` (type: `array`):

Company domains, website URLs or emails (the domain is extracted). One per line. The tracker locates each company's career board (Greenhouse, Lever, Ashby, Recruitee, Workable) from the domain's name.

## `datasetId` (type: `string`):

Optional. Read the domains from a previous Actor run's dataset — for no-code chaining via the Integrations tab.

## `datasetField` (type: `string`):

Which dataset field holds the domain/URL. Leave blank to auto-detect (domain, website, companyDomain, url, companyUrl).

## `keywords` (type: `array`):

Roles or skills to flag, e.g. \["security", "RevOps", "sales"]. Matching job titles are returned as matchedRoles. Leave empty to track all roles.

## `offering` (type: `string`):

Describe what your company sells. If set, the buying-signal interpretation is sharpened for YOU as a seller — what this company's hiring implies for your deal.

## `postedWithinDays` (type: `integer`):

Only count roles posted within this many days. Roles without a posting date are always kept.

## `maxJobsPerCompany` (type: `integer`):

Cap on open roles collected per company before aggregation.

## `maxResults` (type: `integer`):

Max companies to track. One pay-per-event charge per company tracked.

## `maxConcurrency` (type: `integer`):

How many companies to interpret in parallel.

## `model` (type: `string`):

Override the model (default gpt-4o-mini).

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "notion.so"
  ],
  "keywords": [],
  "postedWithinDays": 30,
  "maxJobsPerCompany": 50,
  "maxResults": 50,
  "maxConcurrency": 3
}
```

# Actor output Schema

## `companies` (type: `string`):

All tracked companies with their open roles and AI signal read in the default dataset.

# 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 = {
    "domains": [
        "stripe.com",
        "notion.so"
    ],
    "keywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("noniner/b2b-hiring-signal-tracker").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 = {
    "domains": [
        "stripe.com",
        "notion.so",
    ],
    "keywords": [],
}

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

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

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

```

## CLI example

```bash
echo '{
  "domains": [
    "stripe.com",
    "notion.so"
  ],
  "keywords": []
}' |
apify call noniner/b2b-hiring-signal-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,noniner/b2b-hiring-signal-tracker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3ImFYJA4CotbSg7Sw/builds/u7hQjjKgvlW8KRMlX/openapi.json