LinkedIn Jobs Scraper with Hiring Signals

Scrape LinkedIn job postings worldwide with full descriptions, salary, applicants, and rank companies by open positions to detect active hiring.

What it does

Extracts job postings from LinkedIn's public guest API without requiring login or cookies. Optionally enriches each posting with full description, salary range, applicant count, and seniority level. Produces two datasets: a primary dataset of individual job postings and a secondary dataset ranking companies by open positions with a hiring signal strength indicator. Works globally — any country, city, or remote.

Why it's different

• Hiring signals — ranks companies by open positions with signalStrength (low/medium/high). Not available in most LinkedIn scrapers.
• Applicants count — includes applicant numbers when LinkedIn exposes them. Unique differentiator.
• Global coverage, no login — uses LinkedIn's public guest endpoint. Works for any location, no LinkedIn account needed.

Usage examples

Example 1 — SDR hiring surge (US)

{
  "keywords": "sdr",
  "location": "United States",
  "datePosted": "past-month",
  "maxItems": 500,
  "enrichDetails": true,
  "generateHiringSignals": true
}

Expected: several hundred jobs and 300+ companies ranked, with top employers showing multiple open positions and signalStrength: medium or high.

Note: for maxItems greater than 1,000, enable the datacenter proxy option in the input to avoid LinkedIn throttling.

Example 2 — Remote roles globally

{
  "keywords": "react developer",
  "location": "Remote",
  "datePosted": "past-week",
  "maxItems": 300,
  "enrichDetails": true,
  "generateHiringSignals": true
}

Example 3 — Quick market exploration (cheaper mode)

{
  "keywords": "data engineer",
  "location": "Austin, TX",
  "datePosted": "past-month",
  "maxItems": 200,
  "enrichDetails": false,
  "generateHiringSignals": true
}

This example shows the cheaper mode (without enrichment) for quick exploration of a specific market.

Output schema

Jobs dataset (default, 15 fields)

Field	Type	Description
jobId	string	LinkedIn job posting ID
title	string	Job title
company	string	Company name
companyUrl	string	LinkedIn company page URL
location	string	Job location
postedAt	string	Posting date (ISO)
jobUrl	string	Direct link to job posting
description	string (nullable)	Full job description
seniority	string (nullable)	Seniority level
employmentType	string (nullable)	Employment type
salary	string (nullable)	Salary range
applicants	string (nullable)	Applicant count
daysSincePosted	number (nullable)	Days since posting
enriched	boolean	Whether enrichment ran
scrapedAt	string	Extraction timestamp (ISO)

Hiring signals dataset (named, 11 fields)

Field	Type	Description
company	string	Company name
companyUrl	string	LinkedIn company page URL
openPositions	number	Number of open positions found
jobIds	array[string]	IDs of jobs for this company
titles	array[string]	Titles of open positions
locations	array[string]	Unique locations for this company
avgDaysSincePosted	number (nullable)	Average days since posting
mostRecentPostingDate	string (nullable)	Most recent posting date
topSeniority	string (nullable)	Most common seniority level
signalStrength	string (enum)	high | medium | low
scrapedAt	string	Extraction timestamp (ISO)

Note: the hiring-signals dataset is accessed via the Storage tab of the run (named dataset).

Pricing

Event	When charged	Price per 1,000
Actor start	Per run (automatic)	$0.00005 per run
Job listed	Per job extracted	$0.60
Job enriched	Per job successfully enriched	$1.20
Hiring signal	Per company ranked	$0.30

A typical run of 1,000 enriched jobs with hiring signals costs approximately $2.04.

Known limitations

• Rate limits — LinkedIn may throttle cookie-less IPs. For runs >1,000 jobs, enable datacenter proxy.
• Proxy guidance — datacenter proxy is sufficient for most workloads. Residential proxy is intentionally not used to keep costs predictable for both users and the Actor operator.
• Sequential pagination — pages fetched one by one with 300-800ms delay. Large runs take longer.
• Salary not always available — only ~20-30% of postings expose salary ranges. Field is null when absent.

Legal note

Scrapes only public guest endpoints. No cookies or user credentials used. Users are responsible for compliance with LinkedIn's terms and applicable laws.