# Company Hiring Signals: Open Roles & Hiring Velocity (`vicarious_film/company-hiring-signals`) Actor

Hiring signals for any company domain: ATS, open roles, roles by function, seniority and location, new roles in the last 7 and 30 days, and a hiring velocity score. One row per company from official Greenhouse, Lever, Ashby and Workable job-board APIs.

- **URL**: https://apify.com/vicarious\_film/company-hiring-signals.md
- **Developed by:** [Zac P](https://apify.com/vicarious_film) (community)
- **Categories:** Lead generation, AI, Developer tools
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 company profileds

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

### What does Company Hiring Signals do?

**Company Hiring Signals turns a company domain into one hiring-signal row.** Send `ramp.com` and you get back which **ATS** the company uses, how many **open roles** it has, the mix by **function, seniority and location**, the **remote share**, **roles added in the last 7 and 30 days**, a **hiring velocity score**, and ready-to-filter **signals** like `hiring_sales`.

It's built for **sales and growth teams** who use hiring as a buying signal ("they're hiring 3 SDRs, they need our tool"), in **Clay, n8n and Make**, and for **AI agents** over MCP. No LinkedIn, no scraping of job aggregators, and no job rows to count yourself. Data comes from the **official public job-board APIs** of Greenhouse, Lever, Ashby and Workable.

**1,000 accounts ≈ $6.** You pay $0.006 per company only when a job board is found. Companies with no supported board, or that can't be reached, are free.

#### 30-second example

Input:

```json
{ "companies": ["ramp.com"] }
```

Output (real run, 2026-09-27, trimmed):

```json
{
    "input": "ramp.com",
    "domain": "ramp.com",
    "status": "ok",
    "ats": "ashby",
    "boardUrl": "https://jobs.ashbyhq.com/ramp",
    "openRoles": 158,
    "newRoles7d": 19,
    "newRoles30d": 60,
    "newestPostedAt": "2026-09-26",
    "byFunction": { "sales": 37, "engineering": 33, "customer_success": 33, "product": 10, "operations": 8 },
    "bySeniority": { "mid": 103, "senior": 19, "manager": 10, "lead": 8, "director": 7 },
    "topLocations": [
        { "name": "New York, NY", "count": 122 },
        { "name": "London", "count": 11 }
    ],
    "remoteShare": 0.09,
    "salaryDisclosedShare": 0.96,
    "medianSalaryUsd": 204000,
    "techMentioned": ["Python", "Salesforce", "SQL", "LLM", "AWS"],
    "hiringVelocity": 90,
    "signals": ["hiring_sales", "hiring_engineering", "hiring_customer_success", "hiring_leadership", "hiring_surge"],
    "datesSource": "ats",
    "errors": []
}
```

#### Why use it?

- **One row per company, in your order.** You get one row per input, in the same order, with your input echoed. It drops straight into a Clay column or a spreadsheet.
- **A domain is enough.** It finds the company's ATS from its website, or from its careers page or board URL if you have one.
- **Right company or nothing.** A board is only used when the company's own site links to it, or the board itself points back to the company's domain. A different company that happens to share the name ("acme") is never returned. When nothing checks out you get `no_board_found`, free.
- **Priced per company, not per job.** A 150-role company costs $0.23–$0.60 with per-job scrapers; here it's $0.006.
- **Watch mode** lists the roles opened and closed since your last run. Put it on a weekly schedule for alerts.

### Output fields

| Field | What it is |
|---|---|
| `input`, `domain` | Your input, and the company domain it resolved to |
| `status` | `ok` (board found, charged), `no_board_found` (free), `unreachable` (free) |
| `ats`, `boardUrl` | `greenhouse`, `lever`, `ashby` or `workable`, and the public board |
| `openRoles` | Open roles on the board |
| `newRoles7d`, `newRoles30d`, `newestPostedAt` | Roles posted in the last 7 and 30 days, from the ATS's own posting dates |
| `byFunction` | Roles per function: engineering, data, product, design, sales, marketing, customer\_success, operations, finance, people, legal, other |
| `bySeniority` | Roles per level: intern, junior, mid, senior, lead, manager, director, executive |
| `topLocations` | The 5 most common primary locations |
| `remoteShare` | Share of roles marked remote |
| `salaryDisclosedShare`, `medianSalaryUsd` | Share of roles with a pay range, and the median annual midpoint in USD (converted at approximate rates) |
| `techMentioned` | Technologies named in two or more postings |
| `hiringVelocity` | 0–100: how many roles opened in 30 days, and what share of the board they are |
| `signals` | `hiring_<function>` (a function with at least 10% of the board or of recent roles), `hiring_leadership`, `hiring_surge`, `hiring_slowdown`, `expanding_new_location:<place>`, `remote_friendly` |
| `newRoles`, `closedRoles` | Watch mode only: roles opened and closed since the previous run |
| `detectedAts` | For `no_board_found`: an unsupported ATS we recognised, e.g. `workday` |
| `errors` | Plain-language notes: why a board wasn't found, or a cap that was hit |

Function and seniority come from deterministic rules on the job title. Seniority is about 92% accurate and function about 83% on titles the rules have never seen, so treat them as a strong guide rather than an audit. The rules are tuned every week.

### Input

| Field | Default | Notes |
|---|---|---|
| `companies` | `["gitlab.com"]` | Domains, careers URLs or board URLs. Required |
| `includeJobs` | `false` | Also write one row per job to a second dataset, at $0.001 per job row. No description text |
| `watchMode` | `false` | Return `newRoles` and `closedRoles` since the previous run |
| `departments` | `[]` | Filter the job rows by department. The summary always covers the whole board |
| `maxJobsPerCompany` | `2000` | Hard cap per board |
| `maxConcurrency` | `25` | Companies in parallel |

### How much does it cost?

| Event | Price | When |
|---|---|---|
| Company profiled | $0.006 | `status` is `ok` |
| Job row | $0.001 | Each job row, only with `includeJobs` on |

There's no start fee and no charge per dataset item. `no_board_found` and `unreachable` are free, and a duplicate input is charged once.

### Use it in Clay, n8n, Make or an AI agent

**Clay:** add an Apify integration column (or an HTTP column calling the Actor's run-sync endpoint) with `{"companies": ["{{Domain}}"]}`, one row per account. Then filter on `signals` contains `hiring_sales`.

**n8n / Make:** use the Apify node. Run the Actor with your list, then read the dataset. For weekly alerts, schedule it with `watchMode: true` and send the rows where `newRoles` isn't empty.

**AI agents (MCP):** add the Actor to the [Apify MCP server](https://mcp.apify.com). An agent only needs `{"companies": ["ramp.com"]}` to answer "Is Ramp hiring engineers in London?"

**API:**

```bash
curl -X POST "https://api.apify.com/v2/acts/vicarious_film~company-hiring-signals/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' -d '{"companies":["ramp.com","gitlab.com"]}'
```

### FAQ

**Is there a 200-job cap?** No. Boards are read in full up to `maxJobsPerCompany` (2,000 by default, up to 10,000), and the counts cover every job read.

**Do date filters work?** Yes. The new-role counts use each ATS's own publish date (`first_published`, `createdAt`, `publishedAt`, `published_on`), not the time of the scrape.

**Will I get "403 – not subscribed" errors?** No. There's no third-party backend to subscribe to: the Actor calls the vendors' public board APIs directly.

**Which companies aren't covered?** Companies on Workday, iCIMS, SuccessFactors, Taleo and other enterprise ATSs return `no_board_found` with `detectedAts` set, and aren't charged. A few companies only show their board through JavaScript on their own site, and some of those can't be found from the domain. Pass the board URL instead.

**Is any personal data returned?** No. No recruiter, hiring-manager or applicant names are ever output, and job rows carry no description text.

**Pairs well with** [Company Domain Profiler](https://apify.com/vicarious_film/domain-profiler): contacts, tech stack and email infrastructure for the same accounts.

# Actor input Schema

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

Company domains to profile. A domain is enough (ramp.com); careers page URLs and ATS job-board URLs (jobs.ashbyhq.com/ramp) work too. You get one row per input, in the same order, and only companies with a job board found are charged.

## `includeJobs` (type: `boolean`):

Also write every open job (title, function, seniority, department, locations, remote, posted date, salary if disclosed, link) to a second dataset. Charged per job row. The summary row is always produced.

## `watchMode` (type: `boolean`):

Compare each company's board with the previous run of this Actor on your account, and list the roles opened (newRoles) and closed (closedRoles) since then. The first run records the baseline. Best on a schedule (e.g. weekly) over a fixed list.

## `departments` (type: `array`):

Optional. Only write job rows whose department contains one of these words (e.g. Sales, Engineering). The summary always covers the whole board.

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

Hard cap on jobs read per board, so very large boards stay bounded. Counts cover the jobs read.

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

How many companies to profile in parallel. Requests to each ATS are rate-limited regardless.

## Actor input object example

```json
{
  "companies": [
    "gitlab.com"
  ],
  "includeJobs": false,
  "watchMode": false,
  "departments": [],
  "maxJobsPerCompany": 2000,
  "maxConcurrency": 25
}
```

# Actor output Schema

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

No description

## `jobsDatasetId` (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": [
        "gitlab.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("vicarious_film/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": ["gitlab.com"] }

# Run the Actor and wait for it to finish
run = client.actor("vicarious_film/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": [
    "gitlab.com"
  ]
}' |
apify call vicarious_film/company-hiring-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vicarious_film/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/XrJBEFRdi7b0U6ln6/builds/cRvh8XphDhvqOfbmx/openapi.json