# Hiring Signals Monitor (`itsoul/hiring-signals-monitor`) Actor

- **URL**: https://apify.com/itsoul/hiring-signals-monitor.md
- **Developed by:** [Mahmoud Alhamdo](https://apify.com/itsoul) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.00 / 1,000 company analyzeds

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

## Hiring Signals Monitor

Turn a list of company names into **hiring intelligence**: how many roles are open, which teams are growing, what changed since the last run, and a simple growth score. Data comes straight from each company's public careers board on **Greenhouse, Lever and Ashby**. No login, no proxy, no API key.

### What you get per company

- `openJobs`, `postedLast30Days`
- `newJobs`, `closedJobs`, `changePct` and `newJobTitles` since the previous run
- `departments`, `topLocations`, `seniorityMix`, `remoteShare`
- `growthScore` (0-100) and `signal`: `surging`, `growing`, `stable`, `shrinking` (or `baseline` on the first run)
- `ats`, `boardUrl` so you can verify every number

### Use cases

- **Sales and outbound**: reach companies the week they start hiring for the team you sell to.
- **Recruiting agencies**: spot employers with growing demand.
- **Investors and analysts**: track headcount momentum of a watchlist.
- **Competitive intelligence**: see which functions a competitor is building.

### How to use

1. Add company names (`Stripe`), domains (`stripe.com`) or careers-page URLs (`https://jobs.lever.co/spotify`).
2. Run it. Schedule it daily or weekly with the same **State store name** to get changes between runs.
3. Export to JSON, CSV or Excel, or connect it to n8n, Make, Zapier or Google Sheets.

### Input

| Field | Description |
| --- | --- |
| `companies` | Names, domains or careers-page URLs |
| `trackChanges` | Remember each board between runs (default on) |
| `stateStoreName` | Key-value store that holds the previous snapshot |
| `maxCompanies` | Hard cap per run |

### Example output

```json
{
  "company": "Linear",
  "ats": "ashby",
  "openJobs": 31,
  "previousOpenJobs": 30,
  "changePct": 3.3,
  "newJobs": 3,
  "closedJobs": 2,
  "growthScore": 49,
  "signal": "stable",
  "departments": { "GTM": 16, "Product": 13 },
  "seniorityMix": { "mid": 17, "lead": 7, "manager": 7 }
}
```

### How the growth score works

On the first run the score reflects how fresh the board is (share of roles posted in the last 30 days). From the second run on it is 70% net change in open roles since the previous run and 30% freshness. 50 means flat. Open-role counts are a hiring indicator, not an exact headcount.

### Limits

- Covers companies that publish on Greenhouse, Lever or Ashby (about 8 in 10 tech companies we tried by name). If a company is not found, paste its careers-page URL. Companies with custom career sites are listed in the `SUMMARY` record under `notFound` and are **not charged**.
- Only public job postings are read. No personal data is collected.

### Pricing

Pay per event: one small fee when the Actor starts and a fee per company analyzed. Companies without a public board are free.

# Actor input Schema

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

Company names (e.g. Stripe), domains (stripe.com) or careers-page URLs on Greenhouse, Lever or Ashby. A URL is the most reliable way to point at the right board.

## `trackChanges` (type: `boolean`):

Remember each board between runs to report new jobs, closed jobs and growth trend. Use the same state store name on every scheduled run.

## `stateStoreName` (type: `string`):

Name of the key-value store that keeps the previous snapshot of each company.

## `maxCompanies` (type: `integer`):

Hard cap on companies analyzed per run. You are charged per company analyzed.

## Actor input object example

```json
{
  "companies": [
    "Stripe",
    "Notion",
    "https://jobs.lever.co/spotify"
  ],
  "trackChanges": true,
  "stateStoreName": "hiring-signals-state",
  "maxCompanies": 100
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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": [
        "Stripe",
        "Notion",
        "https://jobs.lever.co/spotify"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("itsoul/hiring-signals-monitor").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": [
        "Stripe",
        "Notion",
        "https://jobs.lever.co/spotify",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("itsoul/hiring-signals-monitor").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 '{
  "companies": [
    "Stripe",
    "Notion",
    "https://jobs.lever.co/spotify"
  ]
}' |
apify call itsoul/hiring-signals-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,itsoul/hiring-signals-monitor"
        }
    }
}
```

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/ws5HFvV1gq8kIwnw3/builds/jsmI9nhscm098oAdZ/openapi.json