# Job Title Normalizer — Seniority, Department & Core Title (`northbell/job-title-normalizer`) Actor

Turn messy job titles into the same columns: core title without level words, places or years; department (engineering, sales, data, people…); seniority (intern to executive); and whether the role leads people. For lead lists, pay tables and hiring counts. No scraping.

- **URL**: https://apify.com/northbell/job-title-normalizer.md
- **Developed by:** [Northbell](https://apify.com/northbell) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.40 / 1,000 title normalizeds

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

## Job Title Normalizer

**One list says `Sr. Product Manager, Payments`, another says `Senior PM`, a third `Product Manager II (Remote)`.** To count, filter or price by role you need the same columns for every title. Give this Actor your titles — from a lead list, a CRM, an ATS export or a job feed — and get back the **core title** (level words, brackets, places and years removed), the **department**, the **seniority** from intern to executive, and whether the role **leads people**. Nothing is scraped: the Actor only reads the titles you send.

**$0.50 per 1,000 titles**, plus $0.01 per run.

**The middle step of the northbell job data toolkit.** Each step reads data you already have:

1. [Job Posting Parser](https://apify.com/northbell/job-posting-parser): posting text → pay, skills, remote, visa
2. **Job Title Normalizer** (this one): title → department, seniority, core title

### Example

Input:

```json
{
  "titles": [
    "Senior Software Engineer II (Remote)",
    "Sr. Product Manager, Payments",
    "Account Executive - Enterprise | NYC",
    "Executive Assistant to the CEO",
    "Head of People"
  ]
}
```

Output (a real run of this input):

| title | coreTitle | function | seniority | leadsPeople |
|---|---|---|---|---|
| Senior Software Engineer II (Remote) | Software Engineer | engineering | senior | false |
| Sr. Product Manager, Payments | Product Manager, Payments | product | senior | false |
| Account Executive - Enterprise | NYC | Account Executive | sales | mid | false |
| Executive Assistant to the CEO | Executive Assistant to the CEO | admin | mid | false |
| Head of People | Head of People | people | director | true |

"Executive Assistant to the CEO" is not an executive, and a product manager does not manage people — the rules know both.

### Run it again and again

- **On a schedule** — save your input as a task and add a **Schedule**: whenever your lead list or ATS export changes (call it through the API). Send each run to Google Sheets, Slack or email with an integration on the task.
- **In bulk** — Send every title in **Job titles** in one call.

### What you get

| Field | |
|---|---|
| `coreTitle` | the title without level words (Senior, Sr., Junior, Staff, Principal, II, Level 2, Intern, Early Career…), text in brackets, a trailing place or work mode (`- NYC`, `\| Remote`) and years (`Summer 2027`) |
| `function` | one of: engineering, data, security, product, design, it, customer, sales, marketing, finance, people, legal, operations, executive, admin, healthcare, education, manufacturing, hospitality — or `null` when none fits |
| `seniority` | intern, entry, mid, senior, lead, manager, director or executive — the same words as every northbell job scraper, so you can join the two |
| `leadsPeople` | `true` for manager, director and executive titles; product, account, program and other "managers" who do not manage people are `false` |

**Unknown is `null`, never a guess.** A title that matches no department (`Cards Experience Guide`) gets `function: null`, not "other". The rules are written for English titles; titles in other languages get a seniority when they use common level words, and a department only when an English word matches.

### Use it for

- **Lead lists** — keep the director-and-above people in sales or engineering
- **Pay tables** — group salaries by department and level instead of by thousands of spellings
- **Hiring counts** — how many open roles each company has per department

### Input

`titles`: one title per line. Through the API you can also send `{"id": "...", "title": "..."}` objects to keep your own ids. Up to 50,000 per run.

### Pricing

**$0.50 per 1,000 titles**, plus $0.01 per run.

### For AI agents

Call with `{"titles": ["Sr. Product Manager, Payments"]}` — about a second. Each row has `type: "title"`.

### Related

Pay, skills, remote and visa from whole job postings: [Job Posting Parser](https://apify.com/northbell/job-posting-parser). Company headcount and growth: [LinkedIn Company Scraper](https://apify.com/northbell/linkedin-company-growth-scraper). Jobs with these same seniority words: [Jobs API](https://apify.com/northbell/job-aggregator-scraper).

# Actor input Schema

## `titles` (type: `array`):

One job title per line, as written in your list, CRM, ATS export or job feed. Through the API you can also pass objects {"id": "...", "title": "..."} to keep your own ids. Up to 50,000 per run.

## Actor input object example

```json
{
  "titles": [
    "Senior Software Engineer II (Remote)",
    "Sr. Product Manager, Payments",
    "Account Executive - Enterprise | NYC",
    "Executive Assistant to the CEO",
    "Head of People"
  ]
}
```

# Actor output Schema

## `titles` (type: `string`):

Core title, department, seniority and whether the role leads people.

# 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 = {
    "titles": [
        "Senior Software Engineer II (Remote)",
        "Sr. Product Manager, Payments",
        "Account Executive - Enterprise | NYC",
        "Executive Assistant to the CEO",
        "Head of People"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbell/job-title-normalizer").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 = { "titles": [
        "Senior Software Engineer II (Remote)",
        "Sr. Product Manager, Payments",
        "Account Executive - Enterprise | NYC",
        "Executive Assistant to the CEO",
        "Head of People",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("northbell/job-title-normalizer").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 '{
  "titles": [
    "Senior Software Engineer II (Remote)",
    "Sr. Product Manager, Payments",
    "Account Executive - Enterprise | NYC",
    "Executive Assistant to the CEO",
    "Head of People"
  ]
}' |
apify call northbell/job-title-normalizer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,northbell/job-title-normalizer"
        }
    }
}
```

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/L3zcbpgv9pOUD2icW/builds/14XF0dhUDTCunAoBc/openapi.json