# Hiring Velocity: Company Hiring Signals by Domain (`octopull/hiring-velocity`) Actor

Company hiring signals from a daily history of career pages and job postings: new jobs in 7 and 30 days, hiring velocity vs the month before, closed roles, hiring by team and seniority, tools in job ads and salaries. Look up companies by domain or ATS link. Pay only for companies found.

- **URL**: https://apify.com/octopull/hiring-velocity.md
- **Developed by:** [Yogi Wahyu Prasida](https://apify.com/octopull) (community)
- **Categories:** Lead generation, Jobs
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $17.50 / 1,000 company with hiring signals

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Velocity: Company Hiring Signals by Domain

Company **hiring signals**: find out **which companies are suddenly hiring**, and for which team. Give it a list of company domains and
get back, for each one: roles opened in the last 7 and 30 days, how that compares with the 30 days before
(**velocity**), roles taken down, open roles by team and seniority, tools named in the job ads, and published
salaries.

The numbers come from a **daily crawl of thousands of company career pages** (Greenhouse, Lever, Ashby,
Workday, Workable, SmartRecruiters, Recruitee, Personio), so they measure *change over time*, not a single
snapshot. A company opening 15 sales roles this month, up from 3, is a company that is buying.

**Built for:** B2B sales and RevOps teams building account lists (works well from Clay, n8n, Make or the API),
recruiters looking for teams that are scaling, and analysts tracking growth.

| input | openJobs | newJobs30d | newJobsPrev30d | velocity30d | newByFunction30d | historyDays |
|---|---|---|---|---|---|---|
| stripe.com | 745 | 229 | 190 | +39 | engineering 96, sales 41, … | 30 |
| notion.com | 146 | 37 | 22 | +15 | sales 14, engineering 9, … | 30 |

*(Illustrative.)*

### Input

One company per line, mixed freely:

| You enter | Example |
|---|---|
| A website domain (best) | `stripe.com` |
| A careers page or job board URL | `https://www.notion.com/careers`, `https://jobs.lever.co/spotify` |
| A company name | `Linear` (guessed from the name, so it can match the wrong company: prefer domains) |

**Live snapshot** (on by default): if we don't track a company yet, the Actor reads its job board now and
returns the same fields from that one snapshot (`source: "live"`, `historyDays: 0`).

### Output

One row per input. Main fields:

- `found`, `source`: `history` (from our daily crawls), `live` (one snapshot taken now) or null (not found, with a `reason`).
- `matchedBy`: how we matched your input: `domain`, `board` (you gave a board URL), `careersPage` (linked from the
  website), or `name` / `domainName` (guessed from the company or domain name: check `boardUrl` for these).
- `openJobs`, `newJobs7d`, `newJobs30d`, `newJobsPrev30d`, `velocity30d`, `closedJobs30d`.
- `byFunction`, `newByFunction30d`, `bySeniority`, `countries`, `remoteShare`.
- `topTools` (e.g. Snowflake, Salesforce, dbt), `medianSalaryYear`, `salaryCurrency`.
- `historyDays` and `asOf`: how much daily history backs the numbers, and the date of the latest crawl.

**How "new" is counted:** a role is new on the day our crawl first sees it. Before our history covers a full
window, roles that were already open count by the posting date the board publishes, when it publishes one.
`closedJobs30d` needs history: it counts roles that disappeared between our crawls.

### Pricing

Pay per company **found**: **$25 per 1,000** companies on the Free plan, $22.50 on Bronze, $20 on Silver and $17.50
on Gold and above. Rows without signals (company not found, no job board) are free. Set a maximum charge per run
in Apify as usual; the Actor stops at your limit.

### Notes and limits

- Only public career pages and their public job-board feeds. No LinkedIn, no logins, no personal data.
- Companies on other hiring systems (or with no public board) come back as not found, free.
- Tool mentions are not available for Workday and SmartRecruiters boards yet.

### Development

Shared code lives elsewhere in the repo; this builds a copy with it outside the repo (`apify push` skips git-ignored files) and pushes:

```bash
python scripts/vendor_hiring_actor.py --push
```

The signals store (`HIRING_SIGNALS_STORE_ID` in `.actor/actor.json`) is refreshed by the runner's daily
`python -m gryphon.hiring daily` (see `gryphon/hiring/export.py`). Tests: `python -m pytest -q actors/hiring-velocity/tests`.

# Actor input Schema

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

One per line: a website domain (stripe.com), a careers page URL, a job board URL (https://jobs.lever.co/spotify) or a company name. Domains work best and fit Clay tables.

## `liveSnapshot` (type: `boolean`):

If a company isn't in the daily history, read its job board now and return the same signals from that one snapshot (historyDays = 0; new-role counts then rely on posting dates). Charged like a history lookup. Off: such companies come back as free not-found rows.

## Actor input object example

```json
{
  "companies": [
    "stripe.com",
    "https://jobs.ashbyhq.com/notion",
    "Anthropic"
  ],
  "liveSnapshot": true
}
```

# Actor output Schema

## `companies` (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.com",
        "https://jobs.ashbyhq.com/notion",
        "Anthropic"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("octopull/hiring-velocity").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.com",
        "https://jobs.ashbyhq.com/notion",
        "Anthropic",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("octopull/hiring-velocity").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.com",
    "https://jobs.ashbyhq.com/notion",
    "Anthropic"
  ]
}' |
apify call octopull/hiring-velocity --silent --output-dataset

```

## MCP server setup

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

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/hevfJpFqFiWmukPXc/builds/39RuLCdVERcBFVNRO/openapi.json