Talent.com Scraper — Job Ads From 21 Countries

Export job postings from Talent.com in any of 21 national markets — company, city, apply link and description snippet — to JSON, CSV or Excel. Pick the country from a dropdown. Keyless, no login.

What does Talent.com Scraper do?

Talent.com aggregates vacancies from employer career sites, staffing agencies and other boards, and publishes them on a separate domain for each market. This Actor reads those listings directly — server-rendered HTML, no API key, no account, no cookies.

One Actor covers every market. Choose the country in the input and the run switches domain and interface language automatically: de.talent.com for Germany, fr.talent.com for France, ca.talent.com for Canada, and so on across 21 countries. There is no reason to run twenty separate scrapers for what is the same site.

Two markup details decide whether the output stays clean. Talent.com's class names carry per-build hashes (JobCard_title__X32Qk), so any selector pinned to a full class name breaks on the next deploy — this Actor matches the stable prefix instead. And the contract-type chip is only rendered on some national sites; where the market does not publish it, the column is left out of the row entirely rather than shipped as a permanently empty field.

Supported countries

United States · Canada · United Kingdom · Ireland · Germany · Austria · Switzerland · France · Belgium · Netherlands · Italy · Spain · Portugal · Poland · Sweden · Mexico · Brazil · Argentina · Australia · India · South Africa

Who is it for?

• Recruitment agencies tracking hiring activity across several markets from one pipeline.
• B2B sales teams using hiring signals to spot companies that are growing.
• Job boards and aggregators filling a country feed without a data licence.
• Market analysts comparing demand between countries and cities.
• Relocation and remote-work platforms sourcing roles by destination.

Use cases

• Compare how many developer roles are open in Germany versus Poland this month.
• Build a weekly list of every company hiring nurses in a given city.
• Track posting volume per country to time a market entry.
• Feed a niche board with fresh listings from five markets using five scheduled runs.
• Spot the moment a target company opens its first role in a new country.

Why use this Actor?

• 21 countries, one Actor — country is a dropdown, not twenty separate tools.
• Keyless — no account, no token, no login.
• Hash-proof selectors — matches class prefixes, not build hashes.
• Honest columns — contract and salary fields appear only where the market publishes them.
• Description snippet included, so rows are triageable without opening each ad.
• Time-budgeted — a slow page ends the run cleanly with rows saved rather than being killed.

What data can you extract?

Field	Type	Description
jobId	string	Talent.com posting ID
title	string	Job title
jobUrl	string	Public posting page
companyName	string	Hiring company
location	string	City and region as published
employmentType	string	Contract type — France only, where the site renders it
salaryLabel	string	Salary as advertised, where the market publishes it
salaryFrom	number	Numeric floor for sorting
quickApply	boolean	One-click apply available
updatedLabel	string	How recently the ad was refreshed
snippet	string	Opening of the description
country	string	Market name, e.g. Germany
countryCode	string	Two-letter market code
source	string	Origin marker, e.g. talent_de
scrapedAt	string	Run timestamp (ISO 8601)

Example output

{
  "jobId": "631370092951112258",
  "title": "Gesundheits- und Krankenpfleger (m/w/d)",
  "jobUrl": "https://de.talent.com/view?id=631370092951112258",
  "companyName": "Confidential - DE",
  "location": "Moabit, Germany",
  "quickApply": true,
  "updatedLabel": "Last updated: 2 days ago",
  "country": "Germany",
  "countryCode": "de",
  "source": "talent_de"
}

How to use it

1. Pick the country from the dropdown.
2. Enter a keyword in the local language — or leave it empty to walk the newest postings.
3. Optionally add a city and a search radius.
4. Set Maximum results and run, then export JSON, CSV or Excel.

Input example

{
  "country": "de",
  "query": "entwickler",
  "location": "Berlin",
  "maxResults": 1000
}

Additional input fields

These optional fields are also available in the input form and API:

Field	Type	Default	Description
proxyConfiguration	proxy	{"useApifyProxy": true}	Talent.com serves plain HTML; the default datacenter proxy is enough.

Notes and limits

• Keywords work in the local language of the market you pick. "developer" returns results in most markets; "entwickler" or "desarrollador" return far more.
• Only France renders a contract-type chip. Other markets omit employmentType, salaryLabel and salaryFrom entirely rather than returning empty columns.
• Talent.com is an aggregator, so the same role can appear from more than one upstream source. Rows are de-duplicated by posting ID within a run.
• This Actor exports listing cards, not full descriptions — that is what keeps bulk runs cheap. Open jobUrl for the full text.
• You are responsible for how you use employer data, including under GDPR where it applies.

FAQ

Do I need a Talent.com account? No. Postings are public and this Actor needs nothing from you.

Can I scrape several countries in one run? One run covers one market. Schedule one run per country — the dropdown makes each task a one-line change.

Is salary included? Only where Talent.com publishes it, which today is France. Everywhere else no salary column is emitted, because an always-empty field is worse than none.

Will it break when Talent.com restyles? It is built to survive that: selectors match class prefixes rather than build-hashed names.

How am I charged? Pay per result — you pay for the postings delivered.

---

*Maintained: last verified 2026-11-01 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).

---

Related scrapers

Other Actors from the same collection:

• Shine.com
• Saramin
• eJobs.ro
• Naukri Job

How much Talent.com data can you extract in one run?

A single run returned 54 job ads in 17 seconds on the example input. That example is deliberately narrow; the result limit and the input list are both yours to widen. That is roughly 190 job ads a minute.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Talent.com itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

Talent.com scraping — frequently asked questions

Do I need a Talent.com API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Talent.com data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Talent.com scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the job ads you care about really do change that fast.

How many job ads can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

Is scraping Talent.com legal?

This Actor collects only information that Talent.com publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Talent.com blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

Legal and compliance

This Actor collects publicly available information from Talent.com only. It does not log in, does not circumvent access controls, and collects no private data. You are responsible for using the output lawfully, including under GDPR and comparable regimes where the rows contain personal data, and for respecting Talent.com's terms where they apply to you.

This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Talent.com; Talent.com and all other trademarks mentioned here are the property of their respective owners.

📝 Changelog

2026-11-01

• Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
• README refreshed: independence disclaimer added; documented 1 additional input field.

2026-10-15

• Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
• A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
• A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
• Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
• Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
• The prefilled example for maxResults is now 200 (was 500).
• The default used when the field is left out for maxResults is now 3,811 (was 500).

2026-09-23

• Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
• Output verified on a live run: 12 columns returned, 100.0% of cells populated.
• Run reliability reviewed: 100.0% of public runs succeeded in the last 30 days.
• Input schema, output schema and pricing configuration reviewed.

2026-09-01

• Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
• Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
• No change to input, output fields or scraping logic.

2026-08-11

• Maintenance release: refreshed the build and dependencies.
• Re-verified live execution, non-empty structured output and dataset field/type integrity.
• Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.