European Job Search

Search twenty European national job boards in a single run. This actor queries each board in parallel, normalizes every posting to a common schema, and removes duplicates of the same job appearing on multiple boards. One search, one unified feed.

No login. No cookies. No account.

What it does

• Searches 20 European job boards at once: Arbetsförmedlingen (SE), CV.lv (LV), CVbankas (LT), CVKeskus (EE), Duunitori (FI), eJobs (RO), France Travail (FR), Jobs.bg (BG), Jobs.cz (CZ), Kariyer.net (TR), Karriere.at (AT), MojPosao (HR), Net-Empregos (PT), NoFluffJobs (PL), Poslovi Infostud (RS), Profesia (SK), Profession (HU), ProUnity (BE), StepStone (DE), VDAB (BE).
• Normalizes every posting to a common schema (title, company, location, salary, contract type, sector, source).
• Deduplicates the same job posted on several boards by matching title, company, and location.
• Returns one clean, country-tagged feed sorted by country and title.

How to scrape European job board data

1. Enter a role or keywords in the Search Query field, for example software engineer, nurse, or accountant. A common role name gives the broadest match across countries.
2. Optionally restrict to certain countries with the Countries field (for example ["DE", "AT"]). Leave it empty to query every board.
3. Set Max Items Per Board to control how many postings are pulled from each board.
4. Run the actor. Each board is queried in parallel, results are normalized and deduplicated.
5. Open the dataset. Each row is one unique job with the board it came from.

Input

Field	Type	Description
searchQuery	string	Job title or keywords. Defaults to software engineer.
countries	array	Optional country filter. Empty means all boards.
maxItemsPerBoard	integer	Max postings per board (1–200, default 20).
timeoutPerBoardSecs	integer	Max seconds to wait per board (30–600, default 120).
proxyConfiguration	object	Proxy settings passed to the underlying scrapers. Residential recommended.

Example input

{
    "searchQuery": "data analyst",
    "countries": ["DE", "AT", "PL"],
    "maxItemsPerBoard": 25,
    "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Output

Each item in the dataset is one unique job posting:

{
    "title": "Senior Data Analyst",
    "company": "Acme GmbH",
    "location": "Berlin",
    "country": "DE",
    "salary": "€65,000 - €80,000",
    "contractType": "Full-time",
    "sector": "IT",
    "url": "https://...",
    "source": "StepStone",
    "postedDate": "2026-06-12",
    "scrapedAt": "2026-06-15T18:00:00.000Z"
}

Field	Description
title	Job title.
company	Hiring company or employer, if available.
location	City or region, if available.
country	ISO country code of the source board.
salary	Salary text as listed (format varies by board).
contractType	Employment or contract type, if available.
sector	Industry or category, if available.
url	Link to the original posting.
source	Name of the board the job came from.
postedDate	Posting date, if available.
scrapedAt	ISO 8601 timestamp.

A final __SUMMARY__ item lists which boards answered, which failed, the total unique jobs, and how many duplicates were removed.

How deduplication works

Postings are deduplicated by a key built from the normalized title, company, and location. The first occurrence of each unique job is kept. This collapses the same role that appears on multiple boards (common for large employers and aggregator-fed boards) into a single entry, while keeping genuinely distinct postings separate.

Use cases

• Building a cross-border talent-market dataset for a specific role.
• Salary benchmarking across countries for the same job title.
• Feeding a recruitment or labor-market dashboard with normalized listings.
• Monitoring hiring activity for a sector across multiple European markets.

Notes

• This is a meta-actor. It orchestrates our individual national job-board scrapers and runs them in parallel, so a single run can cover many countries at once.
• Salary and posted-date fields depend on each board exposing them; not all boards provide every field.
• Coverage for a given query depends on each underlying board returning results for it. A broad role name matches more boards than a narrow or local-language niche term.
• Use residential proxies for the most reliable results.