# Hiring Manager Finder (`thenetaji/linkedin-hiring-manager-finder`) Actor

Find who owns an open role and how to reach them. Returns a company's current openings with the leader of the team each one sits in, their work email, and how long the role has been open — the longer it has sat, the more welcome the call.

- **URL**: https://apify.com/thenetaji/linkedin-hiring-manager-finder.md
- **Developed by:** [The Netaji](https://apify.com/thenetaji) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 open roles

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Hiring Manager Finder

Candidates sent through a job portal disappear into an applicant tracking system. Candidates sent to the person who actually needs the hire get read. The Actor returns a company's open roles, the leader of the team each role sits in, that person's work email, and how long the role has been sitting unfilled.

That last number is the point. A role open for two months means whoever owns it has a problem they have not solved, which is when an approach is welcome rather than annoying.

### Accepted input

| Field | Type | Default | Description |
|---|---|---|---|
| `target_company` | array of strings | `["Stripe"]` | Required. One line per company. A name, a LinkedIn company URL, or a website — all work. |
| `keywords` | string | — | Optional role keywords, e.g. `backend engineer`. Leave empty for every open role. |
| `min_days_open` | integer | `0` | Only return roles open at least this long. `30` is a good starting filter. |
| `verify_emails` | boolean | `false` | Confirm each address against the company's mail server. |
| `maxItems` | integer | `100` | Maximum open roles to save. `0` removes the limit. |
| `email_domain` | array of strings | `[]` | Override. Leave empty unless the company mails from a domain other than its website. |

```json
{
  "target_company": ["Northwind Robotics"],
  "keywords": "backend engineer",
  "min_days_open": 30
}
```

The company's email domain is worked out from the company line; the override is there for the rare case that lookup gets wrong.

### What comes back

Each row pairs one open role with one person: the job title, location, posting date, `days_open`, and the function it belongs to — then the leader's name, headline, seniority, LinkedIn profile, and best-match work email with a confidence score.

### How the manager is identified

The Actor matches each role to its function, then returns the most senior person it can confirm in that same function at that company — the head of the team the hire would join.

This is stated on every row in `manager_basis`, because it is an inference rather than a published reporting line. Nobody discloses org charts, so the honest claim is "the most senior engineering leader we could confirm at this company", not "this role's manager". For most teams those are the same person; for large companies with several parallel teams they may not be.

Everyone returned is confirmed to hold a current role at the company. Ex-employees and people who merely mention the company are excluded.

### What it cannot do

Coverage depends on what search engines have indexed, so smaller companies and those with sparse public profiles return fewer leaders. Where no leader can be confirmed for a role's function, the role is still returned with `manager_basis` set to `no leader found`, so you can see the opening even when the contact is missing.

Some company domains accept mail addressed to anything, so no service can confirm a mailbox there. That is detected before anything is spent, reported on the row, and never charged for.

### Pricing

Charged per open role returned. A company with no matching roles costs nothing. The verified add-on is charged only when a mailbox is actually confirmed.

# Actor input Schema

## `target_company` (type: `array`):

One line per company. A name (Stripe), a LinkedIn company URL, or a website (stripe.com) — all work. The email domain and everything else is worked out from this.

## `keywords` (type: `string`):

Optional role keywords, e.g. 'backend engineer'. Leave empty for every open role.

## `min_days_open` (type: `integer`):

Only return roles that have been open at least this long. A role that has sat for weeks is the strongest signal that whoever owns it wants help. Set 0 for every open role.

## `verify_emails` (type: `boolean`):

Confirm each address against the company's mail server before returning it. Around 40% of company domains accept every address (catch-all), where no mailbox can be confirmed by anyone — those are reported as unverifiable rather than guessed at, and are never charged for.

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

Maximum open roles to save. Set 0 for no limit.

## `email_domain` (type: `array`):

Leave empty. Only set this if the company sends mail from a domain other than its website, and then pair it line-for-line with Companies.

## Actor input object example

```json
{
  "target_company": [
    "https://www.linkedin.com/company/datadog/"
  ],
  "keywords": "Data Scientist",
  "min_days_open": 30,
  "verify_emails": false,
  "maxItems": 20,
  "email_domain": []
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# 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 = {
    "target_company": [
        "https://www.linkedin.com/company/datadog/"
    ],
    "keywords": "Data Scientist",
    "min_days_open": 30,
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/linkedin-hiring-manager-finder").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 = {
    "target_company": ["https://www.linkedin.com/company/datadog/"],
    "keywords": "Data Scientist",
    "min_days_open": 30,
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/linkedin-hiring-manager-finder").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 '{
  "target_company": [
    "https://www.linkedin.com/company/datadog/"
  ],
  "keywords": "Data Scientist",
  "min_days_open": 30,
  "maxItems": 20
}' |
apify call thenetaji/linkedin-hiring-manager-finder --silent --output-dataset

```

## MCP server setup

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

```

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/3D81xDJzuAitUz5ht/builds/p54LT8f7s0T5D6mYW/openapi.json