Stepstone Scraper

Scrape Stepstone jobs and export Stepstone data to CSV, JSON, or Excel for research and reporting. This Stepstone API alternative collects public job listings with clear inputs and structured output.

Collect public Stepstone job listings by keyword, location, or a direct search URL. Export job titles, employers, locations, work-from-home labels, posting-age labels, short descriptions, badges, and listing links.

What data can you extract from Stepstone?

Each dataset row is one job listing. The field names below are the keys in the JSON export; optional fields remain null when the public source does not supply a value.

Field	Description	Example
jobId	Stepstone internal job ID	"14538729"
title	Job title	"Software Engineer (m/w/d) – Operations Research"
company	Hiring company name	"flaschenpost SE"
location	Job location(s) as shown on the listing	"Münster, Berlin, Köln"
workFromHome	Remote-work hint (e.g. 'Teilweise Home-Office'), if shown	"Teilweise Home-Office"
datePosted	Relative publish date label as shown on the site (e.g. 'vor 1 Tag')	"vor 1 Tag"
salary	Salary/pay range if shown; usually null because Stepstone hides salary from anonymous visitors	null
description	Short description snippet shown on the job card	"Wir liefern den Wocheneinkauf innerhalb von 120 Minuten zu un…
badges	Listing badges such as 'Anschreiben nicht erforderlich'	["Anschreiben nicht erforderlich"]
url	Full URL to the job posting	"https://www.stepstone.de/stellenangebote--Software-Engineer-m…

How to scrape Stepstone

1. Enter keywords, a location, or a Stepstone searchUrl copied from a search results page.
2. Optionally set radiusKm, workFromHome, a supported domain, and maxItems.
3. Run the actor; each dataset row represents one visible job card.
4. Download the results as CSV, JSON, or Excel and keep the source url for follow-up.

A run stores its results in the default dataset. Review a few rows there before exporting, especially if you plan to combine several searches or compare snapshots over time. Keep the record ID or source URL in your export so you can remove duplicates and return to the public page behind a result.

Input

Enter these values in the actor input. A prefilled example is a starting point, while a default is the value used when the field is omitted. Required inputs are identified below.

Name	Type	Default	Description
keywords	string	"Software Engineer"	Job title or keywords to search for (e.g. 'Software Engineer'). Leave empty to browse all jobs in a location.
location	string	"Berlin"	City or region to search in (e.g. 'Berlin'). Leave empty to search nationwide.
searchUrl	string	""	A full Stepstone job-search URL to use instead of keywords/location, e.g. https://www.stepstone.de/jobs/software-engineer/in-berlin. Overrides keywords/location when set.
domain	string	"www.stepstone.de"	Stepstone country domain to search on when using keywords/location.
radiusKm	integer	0	Radius in kilometers around the location to include. 0 = site default.
workFromHome	boolean	false	Only include jobs offering full or partial work-from-home.
maxItems	integer	100	Stop after this many job listings. 0 = as many as available (Stepstone exposes at most about 1000 per search).
proxyConfiguration	object	{"useApifyProxy": true}	Apify Proxy is used automatically; override only if needed.

A realistic input:

{
  "keywords": "Software Engineer",
  "location": "Berlin",
  "maxItems": 50
}

The example keeps the run small enough to inspect while showing the main search path. Increase the item limit only after the initial results match your intended scope. When multiple filters are available, start with the most important one and then refine the next run based on the public results.

Output example

The following item came from a successful published run. Long review or description text is shortened here for readability; the dataset keeps the full value.

{
  "jobId": "14538729",
  "title": "Software Engineer (m/w/d) – Operations Research",
  "company": "flaschenpost SE",
  "location": "Münster, Berlin, Köln",
  "workFromHome": "Teilweise Home-Office",
  "datePosted": "vor 1 Tag",
  "salary": null,
  "description": "Wir liefern den Wocheneinkauf innerhalb von 120 Minuten zu unseren Kund:innen. Gemeinsam mit über 20.000 Kolleg:innen schaffen wir es, eine komplette Branche neu zu erfin…",
  "badges": [
    "Anschreiben nicht erforderlich"
  ],
  "url": "https://www.stepstone.de/stellenangebote--Software-Engineer-m-w-d-Operations-Research-Muenster-Berlin-Koeln-flaschenpost-SE--14538729-inline.html"
}

The example shows the shape of one record, not a guarantee that every optional value will be present in every result. CSV and Excel exports present the same fields as columns. JSON retains the native number, boolean, array, and null values that make further filtering easier.

Use cases

• Recruiters can survey publicly listed openings for a specific title and location.
• Labor-market researchers can compare hiring volume across cities using separate focused searches.
• Career services can build a current list of job links for a target occupation.
• Competitive intelligence teams can track which employers advertise particular roles.
• Remote-work researchers can inspect visible work-from-home labels for selected searches.

These workflows use public listing or review data as a starting point. Check the linked source page before acting on a single record, because public content, counts, and availability can change after a run. Store the run date alongside each export when comparing data over time.

How much does it cost to scrape Stepstone?

The price is $0.80 per 1,000 results, with platform usage included. Charges scale with the number of results produced: 100 results cost $0.080, 1,000 results cost $0.80, and 5,000 results cost $4.00. The 5,000-result figure is a pricing illustration, not a promise that a single search exposes that many public results. Set the item limit for the amount of data you need and check the actual result count after the run.

Tips for best results

Prefer a focused keyword and location because broad searches hit the visible-result ceiling sooner. The location and radiusKm inputs help keep the search relevant, and workFromHome requests the site’s remote or partial-home-office filter. If you already have a filtered Stepstone search page, supply searchUrl; it takes precedence over the generated keyword and location path. The site domain setting applies only when building a URL from keywords or location. Use maxItems to stop after the needed number of distinct job IDs. Run separate searches for different cities or occupations and deduplicate by jobId if combining exports.

When creating a repeatable workflow, save the input that produced a useful dataset. Compare later exports by stable ID where available, and inspect a few source links whenever a value matters to a decision. A narrow input usually makes the output easier to validate and reduces time spent processing unrelated results.

Limits

A Stepstone result view exposes roughly 40 pages with about 25 cards each, or about 1,000 jobs, even when the site displays a higher total. The actor stops at page 40, the end of results, or maxItems. Output comes from search-result cards, so description is a short snippet rather than a complete job description. datePosted is a relative label such as “vor 1 Tag,” not a normalized date. Salary is usually null for anonymous visitors because the site hides it behind a login wall. Optional work-from-home text and badges are absent on some cards.

These limits come from the public data exposed to the actor at run time. Source pages can change, so a run can return fewer rows than its requested maximum. A maximum item count is a stop condition, not a minimum or a guarantee of coverage. Use the source URL in each row when you need to verify a particular detail.

Use with AI agents (MCP)

The actor can be called through the Apify MCP connection with the same input fields shown above. Ask for a bounded result set and name the fields that matter to the task. A useful prompt also asks for source links, so each conclusion can be checked against its public record.

• “Find public Software Engineer jobs in Berlin and return company, location, work-from-home label, and URL.”
• “Compare current Stepstone openings for two cities using separate searches, grouped by employer.”

For recurring research, keep the search input and the requested output columns consistent. Compare records by their IDs or source URLs when results from different runs are combined. If an optional field is missing, keep it empty in downstream analysis instead of guessing a value.

FAQ

Is it legal to scrape this data? This actor reads public data. Follow the source site’s terms, applicable law, and GDPR requirements. Do not misuse personal data or republish material without the rights to do so.

Do I need to provide proxies? No. The default proxy configuration is already supplied. You can override proxyConfiguration if your workflow requires different settings.

How fast is a run? Time depends on the number of pages or products, the selected limits, and how quickly public pages respond. Start with a small limit to estimate the time for your search; fetching optional detail pages can add time.

Can I schedule and monitor runs? Yes. Use Apify scheduling and run monitoring for repeat collections. Save each run’s dataset so you can compare snapshots and spot missing or changed records.

Can I export to Google Sheets or Excel? Yes. Download CSV, JSON, or Excel from the dataset, or connect the dataset to Google Sheets through an integration. Keep IDs or URLs as columns for deduplication.

What if a field is empty? The public source did not supply that value for the record, or the value was unavailable in the view used. Treat null as missing data, not as zero or a negative answer.

Can I use a filtered search URL? Yes. Put a Stepstone search-results URL in searchUrl; it overrides keywords and location.

Is datePosted an ISO timestamp? No. It preserves the relative label shown on the listing card.

Why is salary often empty? Stepstone usually hides salary from anonymous search-result visitors.

Integrations

Use the Apify API to start runs and read the default dataset. Webhooks can notify another system when a run finishes; Zapier, Make, and n8n can move results into reporting workflows or Google Sheets. Scheduling supports regular snapshots, and exported CSV or Excel files work for manual analysis. Keep the source record ID and URL in downstream systems so updates can be matched to earlier exports.

Support

Open an issue on the Issues tab; we reply within 24h and add fields on request.