StepStone Jobs Scraper (Search / Details / Contacts)

Search StepStone, enrich individual vacancies, and surface salary, work-model, company, and public-contact fields.

Scrape StepStone jobs by keyword, location, search URL, or job URL. HTTP-only, no browser. Includes pagination, full job details, salary/work model fields, company data, and public email/phone contact extraction.

All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.

🚀 What this Actor does

• Flexible collection: SEARCH, URLS, DETAILS.
• Structured output: clean JSON records organized into overview views.
• Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
• Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.

🎛️ Modes and workflows

Mode or workflow	What it does
SEARCH	Search by keyword, location, country, recency, and job filters.
URLS	Process StepStone result/search URLs directly.
DETAILS	Enrich exact job URLs with full descriptions, salary, company, work model, and optional public contacts.

💡 Common use cases

• European job-market research
• Salary and remote-work analysis
• Employer and public-contact discovery

📥 Input schema

Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.

Field	Type	Description	Default
mode	string	SEARCH builds listing URLs from keywords. URLS crawls StepStone URLs you provide. DETAILS fetches direct job pages only. Allowed: SEARCH, URLS, DETAILS.	SEARCH
startUrls	array	StepStone search URLs, work URLs, or direct job URLs. Used in URLS and DETAILS modes.	[]
keywords	array	One or more job keywords, for example software developer, data engineer, product manager.	[]
keyword	string	Convenience field for one keyword. Used when Keywords is empty.	``
location	string	City or region slug, for example berlin, munich, deutschland. Leave empty for all locations.	``
country	string	StepStone country domain for generated keyword searches. Allowed: DE, AT, FR, DK.	DE
postedWithin	string	Filter by posting age when StepStone accepts the age facet. Allowed: all, 1d, 3d, 7d, 14d.	all
maxItems	integer	Maximum number of jobs to push to the dataset across the whole run.	100
maxPagesPerSearch	integer	Hard cap on pagination depth for each search URL or keyword.	10
includeDetails	boolean	Fetch each job detail page and enrich the row with full description / JSON-LD fields when available.	false
includeContacts	boolean	Extract public emails and phone numbers from the detail page text. Requires Include full job details.	false
excludeRecommended	boolean	Drop section=recommended jobs that StepStone may add when a filtered page has too few exact matches.	true
remoteOnly	boolean	Keep only jobs marked by StepStone as remote-friendly when that field is available.	false
salaryOnly	boolean	Keep only jobs where salary text or structured salary data is available.	false
outputMode	string	Compact returns clean normalized fields. Full keeps more StepStone native fields. Allowed: compact, full.	compact
rawOutput	boolean	Attach the raw StepStone job object under _raw for debugging or custom pipelines.	false
debugLog	boolean	Save a small HTML/API debug sample to the key-value store when StepStone parsing fails. Keep off for normal runs.	false
maxConcurrency	integer	How many HTTP requests may run in parallel.	8
maxRetries	integer	Retries for HTTP 403, 408, 425, 429, 5xx and parse failures.	6
maxProxyRetries	integer	Dedicated proxy / transport retry budget per request.	6
requestDelayMs	integer	Optional delay before each request. Keep 0 for fastest runs.	0
proxyConfiguration	object	Apify Proxy configuration. Residential Germany is recommended because StepStone is Akamai and EU geo sensitive.	{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "DE"}

▶️ Example input

{
  "mode": "SEARCH",
  "keywords": [
    "product designer"
  ],
  "location": "Berlin",
  "country": "DE",
  "postedWithin": "7d",
  "maxItems": 50,
  "includeDetails": true
}

📦 Output schema

Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.

overview — Overview

A compact table for fast scanning and export.

Fields: id, title, companyName, location, workModel, salary, salaryMin, salaryMax, datePosted, section, jobUrl, sourceUrl

📤 Example output

{
  "id": "DEMO-STEPSTONE-01",
  "title": "Product Designer",
  "companyName": "Example Labs",
  "location": "Berlin",
  "workModel": "Hybrid",
  "salary": "€60,000-€72,000",
  "salaryMin": 60000,
  "salaryMax": 72000,
  "datePosted": "2026-08-15",
  "jobUrl": "https://www.stepstone.de/stellenangebote--DEMO-STEPSTONE-01"
}

Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.

🔌 API example

Replace the placeholder with an Apify token and send the same input used in the Console:

curl -X POST "https://api.apify.com/v2/acts/trakk~stepstone-jobs-scraper/runs?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"mode": "SEARCH", "keywords": ["product designer"], "location": "Berlin", "country": "DE", "postedWithin": "7d", "maxItems": 50, "includeDetails": true}'

For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.

🧩 Automation and exports

• Schedule recurring runs from the Apify Console.
• Trigger downstream systems with webhooks when a run succeeds or fails.
• Reuse named monitoring keys or stores where the selected workflow supports change tracking.
• Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.

❓ FAQ

Do I need a login or browser session?

Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.

Why can some fields be empty?

Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.

How should I run this at scale?

Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.

Is the example data real?

No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.