# Hiring Signals — Companies Hiring for Your Roles (`tacps126/hiring-signals`) Actor

Buying-intent signals for sales teams: see which target companies are hiring for the roles you sell to, how many roles, how fresh, and what's new since last week. Scored per company, from career pages and job searches. Schedule it for a weekly intent feed.

- **URL**: https://apify.com/tacps126/hiring-signals.md
- **Developed by:** [Tapaswai Ashok Choudhary](https://apify.com/tacps126) (community)
- **Categories:** Lead generation, Jobs
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 company signals

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 Signals — Companies Hiring for Your Roles

Know which companies are about to buy. When a company opens roles for the team you sell to — data engineers, security, RevOps, support — it's usually expanding that team and about to spend on its tools. This Actor watches your **target accounts' career pages** (or discovers companies through job searches) and gives you **one scored signal per company**: how many matching roles, how fresh, which functions, seniority and locations, and **what's new since last week**.

**Built for** SDRs and account executives prioritising outreach, RevOps teams feeding intent data into the CRM, founders doing account-based selling, recruiters and agencies spotting growing teams, and investors tracking portfolio and competitor growth.

### Why this Actor

- **Signals, not job dumps.** One row per company, ranked by a simple score (more matching roles, fresher roles, and new roles since last run score higher), with the matching roles listed underneath. Ready to hand to a sales team.
- **Your definition of intent.** Choose the role keywords that matter for your product, and narrow by seniority, job function, work mode, employment type, region and recency. Require tech-stack mentions (e.g. roles that mention `Snowflake`) for technographic signals, and exclude existing customers.
- **Tracks change over time.** Every signal shows new matching roles and the change in the company's total open roles since the previous run. With *Only new or changed companies*, a weekly schedule becomes an intent feed — you're charged only for changes.
- **Reads whole career pages.** Supports Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Recruitee, Personio and Teamtailor — paste the company's jobs page link. No API keys or logins.
- **Fast and cheap to run.** A small native program — no browser — that runs in 256 MB. A dozen target accounts take a few seconds.
- **Handles rate limits for you.** Waits as long as a site asks when it says "slow down" (HTTP 429), and retries timeouts and dropped connections automatically.

### How to use it

1. Paste your target accounts' **career pages** — for example `https://boards.greenhouse.io/stripe`. Or add **job searches** (like `data engineer` in `Germany`) to discover companies you don't know yet. You can combine both.
2. Enter the **roles that signal intent** for you, and anything to ignore.
3. Press **Start**. Then schedule it weekly with **Only new or changed companies** and connect Slack, Google Sheets or your CRM.

#### Example input

```json
{
  "companies": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/spotify",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "searches": ["data engineer"],
  "searchLocation": "Germany",
  "roleKeywords": ["data", "analytics", "machine learning"],
  "excludeKeywords": ["intern"],
  "postedWithinDays": 30,
  "onlyChanged": true
}
```

### What you get

One record per company with matching roles, highest score first:

| Field | Description |
|-------|-------------|
| `company` / `companySlug` / `companyLogo` | Company name, its career-page handle, and logo when available |
| `signalScore` | 0–100: volume of matching roles (up to 50) + roles posted in the last 7 days (up to 30) + new roles since last run (20) |
| `matchingRoles` / `newMatchingRoles` | Roles matching your criteria, and how many are new since the last run |
| `rolesPostedLast7Days` | Matching roles opened in the past week |
| `totalOpenRoles` / `openRolesChange` | All open roles at the company, and the change since the last run |
| `functions` / `seniority` / `topLocations` | Breakdown of the matching roles (e.g. `{"data": 6, "engineering": 4}`) |
| `matchedKeywords` | Which of your keywords matched, and how often |
| `remoteShare` | Share of matching roles that are remote (%) |
| `newestRolePostedAt` / `firstSeenAt` | Newest matching role, and when the company first showed a signal |
| `roles` | The matching roles (new ones first): title, link, location, seniority, function, work mode, posting date |
| `board` / `scrapedAt` | Where the roles came from, and when |

Example (shortened):

```json
{
  "company": "Stripe",
  "signalScore": 100,
  "matchingRoles": 11,
  "newMatchingRoles": 2,
  "rolesPostedLast7Days": 4,
  "totalOpenRoles": 708,
  "openRolesChange": 12,
  "functions": { "data": 6, "engineering": 4, "sales": 1 },
  "roles": [
    { "title": "Data Engineer, Payments", "url": "https://stripe.com/jobs/search?gh_jid=…", "location": "Dublin", "seniority": "mid", "isNew": true }
  ]
}
```

### Weekly intent feed

Turn on **Only new or changed companies** and schedule the Actor weekly. The first run reports every company with a signal; after that you only get companies that are new or opened new matching roles. Connect Slack, e-mail, Google Sheets, HubSpot or Salesforce (via Zapier or Make) so your team sees them where they work.

### Use it as an instant API

The Actor also runs in **Standby mode** — an always-ready endpoint that returns signals straight in the response, handy for enrichment workflows and AI agents. Find the URL on the **Standby** tab and `POST` the input as JSON.

### Pricing

Pay per result: about **$10 per 1,000 company signals** — one cent per company with matching roles (lower on higher Apify plans), plus a tiny start fee. Companies without matching roles, and (when monitoring) unchanged companies, are free. See the **Pricing** tab, and set a maximum charge per run to cap spend.

On Apify's **free plan** each run returns up to 50 companies — enough to try it on your accounts. Any paid Apify plan removes the limit.

### FAQ

**Which career pages work?** Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Recruitee, Personio and Teamtailor. Paste the page where the company lists its jobs.

**How is "new" decided?** The Actor remembers which matching roles it saw for each company in the previous run with the same input (or the same *state key*). Roles it hasn't seen before are new.

**Is it legal?** The Actor reads publicly posted job listings. Use the results within the privacy and marketing rules that apply to you.

### Support

Found a problem or need a board or field that isn't there yet? Open an issue on the **Issues** tab — requests genuinely decide what gets built next.

# Actor input Schema

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

Your target accounts' jobs pages — Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Recruitee, Personio or Teamtailor links. Every open role is read.

## `searches` (type: `array`):

Find companies you don't know yet: job searches like `data engineer` or `head of security`. Every company hiring for it becomes a signal.

## `searchLocation` (type: `string`):

Where to search, e.g. `Germany`, `London`, `United States`.

## `roleKeywords` (type: `array`):

A role counts when its title contains any of these words — the teams that buy what you sell (e.g. `security`, `data engineer`, `revops`). Leave empty to count every open role.

## `excludeKeywords` (type: `array`):

Roles whose title contains any of these never count, e.g. `intern`, `working student`.

## `locations` (type: `array`):

Only roles whose location contains any of these, e.g. `Germany`, `Remote`, `New York`.

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

Only roles posted in the last N days count (roles without a date always count). 0 = any age.

## `seniorities` (type: `array`):

Keep only these seniority levels.

## `jobFunctions` (type: `array`):

Keep only these job functions (engineering, data, sales, …).

## `workModes` (type: `array`):

Keep only these work arrangements. Jobs whose posting doesn't state it are dropped when this is set.

## `employmentTypes` (type: `array`):

Keep only these employment types.

## `descriptionIncludes` (type: `array`):

Count a role only if its description or skills mention any of these, e.g. `Snowflake`, `Kubernetes` — great for tech-stack signals.

## `companyExcludes` (type: `array`):

Never report companies whose name contains any of these (e.g. existing customers, recruiters).

## `minMatchingRoles` (type: `integer`):

Report a company only when at least this many roles match.

## `includeRoles` (type: `boolean`):

Include each company's matching roles (title, link, location, seniority, date) in its record.

## `maxItems` (type: `integer`):

Maximum number of company signals to return (highest score first).

## `maxSearchPages` (type: `integer`):

How many result pages to read per discovery search (about 10 jobs each).

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

Report a company only the first time it shows a signal, or when it opens new matching roles since the last run with the same input. You pay only for changes.

## `monitorName` (type: `string`):

Optional name for the change-tracking history, so several watchlists can run side by side.

## `proxyConfiguration` (type: `object`):

Recommended for large discovery searches; not needed for career pages.

## `tenantId` (type: `string`):

Optional label used to keep separate histories for different clients or teams.

## `debug` (type: `boolean`):

Save extra diagnostics with the run (for support requests).

## Actor input object example

```json
{
  "companies": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/spotify",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "roleKeywords": [
    "data",
    "analytics",
    "machine learning"
  ],
  "excludeKeywords": [
    "intern"
  ],
  "postedWithinDays": 30,
  "minMatchingRoles": 1,
  "includeRoles": true,
  "maxItems": 200,
  "maxSearchPages": 10,
  "onlyChanged": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "debug": false
}
```

# Actor output Schema

## `signals` (type: `string`):

One record per company hiring for your roles, highest score first.

## `summary` (type: `string`):

Counts, warnings, and unchanged companies.

# 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": [
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/spotify",
        "https://jobs.ashbyhq.com/ramp"
    ],
    "roleKeywords": [
        "data",
        "analytics",
        "machine learning"
    ],
    "excludeKeywords": [
        "intern"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tacps126/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": [
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/spotify",
        "https://jobs.ashbyhq.com/ramp",
    ],
    "roleKeywords": [
        "data",
        "analytics",
        "machine learning",
    ],
    "excludeKeywords": ["intern"],
}

# Run the Actor and wait for it to finish
run = client.actor("tacps126/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": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/spotify",
    "https://jobs.ashbyhq.com/ramp"
  ],
  "roleKeywords": [
    "data",
    "analytics",
    "machine learning"
  ],
  "excludeKeywords": [
    "intern"
  ]
}' |
apify call tacps126/hiring-signals --silent --output-dataset

```

## MCP server setup

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