# Job Posting Parser — Salary, Skills, Remote & Visa from Text (`northbell/job-posting-parser`) Actor

Parse your own job postings (text or HTML): pay range as min/max/currency/period plus yearly, skills, seniority, employment type, remote/hybrid and visa sponsorship, each with the sentence it came from. Bonuses and funding are not read as pay. No scraping.

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

## Pricing

from $0.80 / 1,000 posting parseds

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 Posting Parser

**Already have job postings — from your own ATS export, a CSV, a partner feed or another scraper — and need the same fields out of every one?** Give this Actor the text (plain or HTML) and get back, per posting: the **pay range** as min / max / currency / period plus the yearly equivalent, the **skills** it asks for, the **seniority** from the title, the **employment type**, whether it is **remote or hybrid**, and whether it **sponsors a visa**. Remote and visa come with the sentence they were read from, so you can check them. Nothing is scraped: the Actor only reads what you send.

**$1 per 1,000 postings**, plus $0.01 per run.

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

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

### Why not a regex for "$"

Most dollar amounts in a job posting are not pay. `Raised $20M from investors`, `New hire bonus: $5,000`, `$800 billion market` — a plain pattern returns all of them. The pay reader here is the one behind our [LinkedIn Salary Scraper](https://apify.com/northbell/linkedin-jobs-salary-scraper): an amount counts as pay only when it carries a pay signal of its own (a period like "per year" or "/hr", or a label like "base salary" or "pay range"). Bonuses, funding, budgets and allowances are left out. "Up to X" and "from X" are kept at the number given.

### Run it again and again

- **On a schedule** — save your input as a task and add a **Schedule**: right after your job scraper's scheduled run (call it from your pipeline through the API). Send each run to Google Sheets, Slack or email with an integration on the task.
- **In bulk** — Send all of the day's postings in **Postings** in one call.

### Example

Input:

```json
{
  "postings": [
    {
      "id": "example-1",
      "title": "Senior Data Engineer",
      "location": "United States",
      "description": "We are hiring a Senior Data Engineer. You know Python, SQL, Spark and AWS. This role is fully remote within the US. The base salary range is $150,000 - $185,000 per year. New hire bonus: $5,000. We are unable to sponsor visas for this position."
    }
  ]
}
```

Output (a real run of this input):

```json
{
  "type": "posting",
  "id": "example-1",
  "title": "Senior Data Engineer",
  "salaryFound": true,
  "salaryMin": 150000,
  "salaryMax": 185000,
  "currency": "USD",
  "period": "year",
  "annualMin": 150000,
  "annualMax": 185000,
  "salaryText": "$150,000 - $185,000 per year",
  "seniority": "senior",
  "employmentTypes": [],
  "workplace": "remote",
  "workplaceText": "This role is fully remote within the US.",
  "visaSponsorship": false,
  "visaText": "We are unable to sponsor visas for this position.",
  "skills": ["Python", "AWS", "SQL", "Spark"],
  "skillCount": 4
}
```

The $5,000 bonus is not read as pay.

### What you get

| Field | |
|---|---|
| `salaryMin`, `salaryMax`, `currency`, `period` | the pay as written (`period`: hour, day, week, month or year) |
| `annualMin`, `annualMax` | the same pay as a yearly figure, so hourly and yearly postings compare |
| `salaryText`, `salarySource` | the exact text the pay was read from; `description`, or `salary-field` when you pass a `salary` value |
| `skills`, `skillCount` | skills from a dictionary of 456 (languages, frameworks, cloud, data and AI, DevOps, security, business tools, certifications, spoken languages) |
| `seniority` | intern, entry, mid, senior, lead, manager, director or executive, from the title — the same words as every northbell job scraper |
| `employmentTypes` | full-time, part-time, contract, temporary, internship — from the `employmentType` you pass and the title |
| `workplace`, `workplaceText` | `remote`, `hybrid` or `onsite` only when the text says so, with the sentence |
| `visaSponsorship`, `visaText` | `true` / `false` only when the text says so, with the sentence |

**Unknown is `null`, never a guess.** A posting that says nothing about remote work gets `workplace: null`, not `onsite`. "We build remote sensing satellites" is not a remote job.

### Input

`postings`: a list. Each item is either the posting text as a string, or an object with `description` (plain text or HTML) and optionally `id`, `title`, `location`, `salary` (a pay field from your source, read first) and `employmentType`. Pass `title` when you have it: seniority and some employment types come from the title. `location` decides which dollar a `$` is (US, Canada, Australia…). Up to 10,000 postings per run.

### Pricing

**$1 per 1,000 postings**, plus $0.01 per run. Error rows are free. Put all your postings in one run.

### For AI agents

Call with `{"postings": ["<posting text>"]}` — a few seconds. Each row has `type`: `posting` or `error`. Every field that could not be read is `null`.

### Where the postings come from

If you do not have postings yet: [LinkedIn Salary Scraper](https://apify.com/northbell/linkedin-jobs-salary-scraper) (LinkedIn jobs with pay already read) · [Jobs API](https://apify.com/northbell/job-aggregator-scraper) (461 tech companies' own job boards) · [Greenhouse Jobs Scraper](https://apify.com/northbell/greenhouse-jobs-scraper). For pay statistics by title and place, see the [LinkedIn Salary Benchmark](https://apify.com/northbell/linkedin-salary-benchmark); for the skills a role asks for most, the [LinkedIn Skills Demand](https://apify.com/northbell/linkedin-skills-demand) report.

# Actor input Schema

## `postings` (type: `array`):

Your job postings. Each one as {"id": "...", "title": "...", "description": "...", "location": "..."} (id and location optional; description may be HTML), or just the posting text as a string. Up to 10,000 per run.

## `includeSkills` (type: `boolean`):

Match the text against a dictionary of 456 skills (languages, frameworks, cloud, data and AI, DevOps, security, business tools, certifications, spoken languages). Turn off if you only need pay and the other fields.

## Actor input object example

```json
{
  "postings": [
    {
      "id": "example-1",
      "title": "Senior Data Engineer",
      "location": "United States",
      "description": "We are hiring a Senior Data Engineer. You know Python, SQL, Spark and AWS. This role is fully remote within the US. The base salary range is $150,000 - $185,000 per year. New hire bonus: $5,000. We are unable to sponsor visas for this position."
    }
  ],
  "includeSkills": true
}
```

# Actor output Schema

## `postings` (type: `string`):

Pay, skills, level, employment type, remote and visa for each posting.

# 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 = {
    "postings": [
        {
            "id": "example-1",
            "title": "Senior Data Engineer",
            "location": "United States",
            "description": "We are hiring a Senior Data Engineer. You know Python, SQL, Spark and AWS. This role is fully remote within the US. The base salary range is $150,000 - $185,000 per year. New hire bonus: $5,000. We are unable to sponsor visas for this position."
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northbell/job-posting-parser").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 = { "postings": [{
            "id": "example-1",
            "title": "Senior Data Engineer",
            "location": "United States",
            "description": "We are hiring a Senior Data Engineer. You know Python, SQL, Spark and AWS. This role is fully remote within the US. The base salary range is $150,000 - $185,000 per year. New hire bonus: $5,000. We are unable to sponsor visas for this position.",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("northbell/job-posting-parser").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 '{
  "postings": [
    {
      "id": "example-1",
      "title": "Senior Data Engineer",
      "location": "United States",
      "description": "We are hiring a Senior Data Engineer. You know Python, SQL, Spark and AWS. This role is fully remote within the US. The base salary range is $150,000 - $185,000 per year. New hire bonus: $5,000. We are unable to sponsor visas for this position."
    }
  ]
}' |
apify call northbell/job-posting-parser --silent --output-dataset

```

## MCP server setup

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

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/MppiLcFgoQbJ9WAS0/builds/MBrVH4jje3z7AJ257/openapi.json