# Company Hiring Signals: Job Changes, AI Roles & Growth (`feedwise/company-hiring-signals`) Actor

See which companies are hiring and for what: roles opened and closed since your last run, hiring surges and slowdowns, new AI/ML and leadership roles, new teams and locations. Reads Greenhouse, Lever, Ashby, Workday and 5 more job boards. For sales, recruiting and investors.

- **URL**: https://apify.com/feedwise/company-hiring-signals.md
- **Developed by:** [Feedwise Data](https://apify.com/feedwise) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 company reports

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

## Company Hiring Signals — who is hiring, for what, and what changed

Give it a list of companies. Get **one report per company** saying how many roles are open, which teams
are hiring, and, on every repeat run, **what changed since last time**: roles opened and closed, hiring
surges and slowdowns, first AI/ML roles, new leadership openings, new teams and new locations.

Schedule it weekly and you have a hiring-intent feed for your target accounts.

- **Plain-English signals** you can paste into a CRM or Slack: "Hiring surge: 40 new roles since 2026-09-24 (+26.8% net)", "First AI/ML roles: Applied AI Engineer; Data Scientist", "New leadership opening: VP Sales EMEA", "New location: Spain".
- **9 career platforms read directly**: Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, Recruitee, Personio, Breezy HR. Data comes from each company's own public job board at run time, not a stale database.
- **Breakdowns**: open roles by team (Engineering, AI & ML, Sales, Marketing, Customer, Finance, People and more), by seniority (Leadership, Senior, Mid, Entry), top locations, remote share, roles posted in the last 7 and 30 days.
- **Pay per company report**, not per job. Use `onlyChanged` to skip, and not pay for, companies with no change.

### Who uses this

- **Sales and SDR teams**: hiring is a buying signal. A company opening 10 data-engineering roles needs data tools; a new "Head of Security" means a security budget.
- **Recruiters and agencies**: spot companies scaling a team before the roles hit job boards.
- **Investors and analysts**: track headcount momentum across a portfolio or watchlist.
- **Job seekers**: watch dream companies for new teams and locations.

### Input

```json
{
  "companies": [
    "greenhouse:airbnb",
    "https://jobs.ashbyhq.com/ramp",
    "https://jobs.lever.co/palantir",
    "https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"
  ],
  "compareWithLastRun": true,
  "stateKey": "my-target-accounts",
  "onlyChanged": false
}
```

| Company format | Example |
|---|---|
| Careers page URL | `https://jobs.lever.co/palantir`, `https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite` |
| `ats:slug` | `greenhouse:airbnb` |
| Plain slug (auto-detect) | `airbnb` (not Workday, which needs its URL) |

The first run saves a baseline and reports current hiring (including roles posted in the last 7 and
30 days). Every later run with the same `stateKey` compares against the previous run.

### Output (one row per company)

```json
{
  "company": "ramp",
  "ats": "ashby",
  "openJobs": 156,
  "postedLast7Days": 12,
  "postedLast30Days": 60,
  "aiRoles": 9,
  "leadershipRoles": 7,
  "remoteShare": 0.08,
  "byFunction": { "Sales": 61, "Engineering": 40, "AI & ML": 9, "People": 9 },
  "bySeniority": { "Senior": 70, "Mid": 72, "Leadership": 7, "Entry": 7 },
  "comparedWith": "2026-09-24T09:00:00.000Z",
  "newJobs": 40,
  "closedJobs": 7,
  "netChange": 33,
  "changePct": 26.8,
  "newByFunction": { "Sales": 18, "Engineering": 12, "AI & ML": 9 },
  "newJobTitles": ["Applied AI Engineer", "Account Executive, Mid-Market"],
  "newLeadershipTitles": [],
  "newAiTitles": ["Applied AI Engineer", "Data Scientist"],
  "newLocations": [],
  "signals": [
    "Hiring surge: 40 new roles since 2026-09-24 (+26.8% net).",
    "First AI/ML roles: Applied AI Engineer; Data Scientist; AI Solutions Engineer."
  ]
}
```

Teams and seniority come from job titles and departments, so treat them as good estimates rather than
an official org chart.

### Pricing

Pay per company report. Companies that can't be read, and unchanged companies when `onlyChanged` is
on, are free.

### FAQ

**Why do some very large companies show "Very large board"?** Workday career sites list at most
2,000 roles. For bigger boards the counts are a lower bound and closed roles aren't tracked, but new
roles are still detected.

**Is this allowed?** It reads the public job-board endpoints that these platforms provide so companies
can show their jobs on their own websites and on job boards. No login, no personal data.

**Want every job as its own row?** Use the companion actor
[Company Jobs API](https://apify.com/feedwise/ats-jobs-unified).

# Actor input Schema

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

One per line. A careers page URL (https://jobs.lever.co/palantir, https://boards.greenhouse.io/airbnb, https://jobs.ashbyhq.com/ramp, https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite), an explicit "ats:slug" (greenhouse:airbnb) or a plain slug (airbnb) for auto-detection. Workday boards need the careers URL.

## `compareWithLastRun` (type: `boolean`):

Save each company's open roles and, on the next run, report roles opened and closed since then. Schedule the actor weekly to get a weekly change report.

## `stateKey` (type: `string`):

Name for this tracking list. Use a different name for each separate list you track, so their histories don't mix.

## `onlyChanged` (type: `boolean`):

On repeat runs, skip (and don't charge for) companies with no roles opened or closed since the last run. First runs always report, to create the baseline.

## `maxTitles` (type: `integer`):

How many example titles to include in each list of new, leadership and AI roles.

## `concurrency` (type: `integer`):

How many companies to read at the same time.

## Actor input object example

```json
{
  "companies": [
    "greenhouse:airbnb",
    "https://jobs.ashbyhq.com/ramp",
    "https://jobs.lever.co/palantir"
  ],
  "compareWithLastRun": true,
  "stateKey": "default",
  "onlyChanged": false,
  "maxTitles": 15,
  "concurrency": 5
}
```

# Actor output Schema

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

One row per company: open roles by team and seniority, changes since the last run, and plain-English hiring signals.

# 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": [
        "greenhouse:airbnb",
        "https://jobs.ashbyhq.com/ramp",
        "https://jobs.lever.co/palantir"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("feedwise/company-hiring-signals").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": [
        "greenhouse:airbnb",
        "https://jobs.ashbyhq.com/ramp",
        "https://jobs.lever.co/palantir",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("feedwise/company-hiring-signals").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": [
    "greenhouse:airbnb",
    "https://jobs.ashbyhq.com/ramp",
    "https://jobs.lever.co/palantir"
  ]
}' |
apify call feedwise/company-hiring-signals --silent --output-dataset

```

## MCP server setup

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

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/OqfsNuTFwe8c5bEjl/builds/nSQFESETaVFvDqFcZ/openapi.json
