Expertini Jobs Scraper — Postings, Salary, Company

Scrape structured job postings from Expertini, the multi-country job-search aggregator. Pick a country, then pull the freshest jobs from its feed or the full posting corpus from its sitemaps. Every posting comes back as one clean, flat record: title, hiring company (with logo), location, salary (when disclosed), employment type, industry, posting and expiry dates, and the full job description — each tagged with a machine-readable parse_confidence score.

This Expertini Jobs Scraper is built for job-market analytics, recruitment and sourcing tools, salary-benchmarking and labour-market research that need structured postings across many countries without maintaining a fragile in-house scraper.

What Expertini data you get

One row per job posting (recordType: "job"):

• title — the job title as listed
• company / companyUrl / companyLogo — the hiring organization
• city / region / country / streetAddress / postalCode — the job location
• employmentType — e.g. Permanent, FULL_TIME, CONTRACTOR
• industry — the posting's industry label
• salaryValue / salaryMin / salaryMax / salaryCurrency / salaryUnit — pay when the source discloses it, plus salaryDisclosed (a boolean — we never invent a number)
• datePosted / validThrough — when the posting went live and when it expires
• descriptionText — the full description as clean plain text, plus descriptionHtml with the original markup
• url — the canonical posting URL
• jobId — the source's posting identifier
• pubDate — the feed publish timestamp (feed mode)
• parse_confidence — 1.0 when the core hiring fields are present

How to scrape Expertini

1. Set Country to the Expertini national index you want (us, uk, de, ca, au, in, …).
2. Choose Discovery mode:
   • Freshest feed — reads the country's RSS feed (newest postings, with publish dates). Fast and small.
   • Full sitemap — walks the site's sitemaps to reach the whole posting corpus. Use it for volume.
3. Set Max results to cap cost. Run. Postings stream into the dataset, each enriched from its detail page.

The actor reads each posting from Expertini's own embedded schema.org/JobPosting data and de-duplicates by job id.

How much does it cost?

Pay per result — there is no subscription. You are billed per posting returned, so a small trial run costs cents. The actor runs on Apify's RESIDENTIAL proxy billed to your own Apify account — there is no extra proxy fee from us and no key to supply.

Example output

{
  "recordType": "job",
  "jobId": "senior-data-engineer-new-york-acme-corp-3722111",
  "title": "Senior Data Engineer",
  "company": "Acme Corp",
  "companyLogo": "https://github.cdn.expertini.com/images/resource/company-logo/5.webp",
  "employmentType": "FULL_TIME",
  "industry": "Information Technology",
  "city": "New York",
  "region": "New York",
  "country": "United States",
  "salaryDisclosed": true,
  "salaryMin": 120000,
  "salaryMax": 160000,
  "salaryCurrency": "USD",
  "salaryUnit": "YEAR",
  "datePosted": "2026-06-23",
  "validThrough": "2026-08-02",
  "url": "https://us.expertini.com/job/senior-data-engineer-new-york-acme-corp-3722111/",
  "parse_confidence": 1.0
}

Why this Expertini Jobs Scraper

• Reads the posting from Expertini's own data layer — the parser walks the page's embedded JobPosting JSON and picks fields by their schema.org meaning, not brittle CSS class names, so it keeps working through redesigns.
• Honest salary — pay is reported only when the source discloses it; salaryDisclosed tells you which postings carry a real figure, and we never fabricate one.
• Two discovery modes — pull just the freshest jobs for monitoring, or the full corpus for bulk analysis, from the same actor.
• Many countries — switch the national index with one input field.
• Reliable access built in — every request is routed through Apify's RESIDENTIAL proxy for a stable egress; no key to supply.
• Quality signal built in — parse_confidence lets you trust the data and drop incomplete rows automatically.

FAQ

Do I need an Expertini login or API key? No. The actor reads public Expertini pages.

Which data does it cover? Public job postings indexed by Expertini for the country you select.

Can I search by keyword? This version discovers postings by recency (feed) or by the full sitemap; results cover all roles in the chosen country. Filter the returned dataset by title/industry/location downstream.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.