No Fluff Jobs Scraper — Poland job listings with salary

Extract No Fluff Jobs job listings with salary, location and posting date for Poland market research, recruiting and lead generation.

What you get

• Every job on nofluffjobs.com that matches your keywords, as one structured row each: title, company, location, employment type, posting date and the canonical job URL — exact matches only, never the board's "you might also like" filler.
• Salary normalized to gross EUR per month (salary.minEurMonth / salary.maxEurMonth) next to the raw label the board printed, so rows priced in different currencies sort together. No Fluff Jobs publishes a range on most postings, which is what makes this board worth scraping.
• A stable id of the form nofluffjobs:<board job id>, so repeat runs deduplicate against your own database instead of against a row number.

Sample item

{
  "id": "nofluffjobs:mid-software-engineer-python-guidewire-software-krakow-1",
  "url": "https://nofluffjobs.com/pl/job/mid-software-engineer-python-guidewire-software-krakow-1",
  "title": "Mid Software Engineer - Python",
  "company": "Guidewire Software",
  "companyUrl": null,
  "location": { "raw": "Kraków", "city": "Kraków", "country": "PL" },
  "remote": false,
  "employmentType": "FULL_TIME",
  "salary": {
    "min": 18500,
    "max": 22000,
    "currency": "PLN",
    "period": "month",
    "raw": "18 500 – 22 000 PLN / mies.",
    "minEurMonth": 4295,
    "maxEurMonth": 5107
  },
  "postedAt": "2026-07-29",
  "expiresAt": null,
  "description": null,
  "tags": ["Python", "FastAPI", "SQLAlchemy", "Docker", "Mid"],
  "source": {
    "board": "nofluffjobs",
    "boardJobId": "mid-software-engineer-python-guidewire-software-krakow-1",
    "scrapedAt": "2026-08-22T09:14:03.221Z"
  }
}

remote has three states, and false is not the same answer as null. It is true when the board's own "fully remote" flag is set or the card's location reads as remote ("Zdalnie", "Remote"), false when the board marks the posting as hybrid or office-based, and null when the posting says nothing about it at all. Filter on remote === true for remote-only work, and do not read a missing flag as an office job.

description and expiresAt are filled in only when includeDetails is on — they live on the job's own page, not on the listing. postedAt, the salary and the skills tags come off the listing itself, so the cheap run already dates every row. Anything the board did not publish is null, never missing.

Input

Field	Type	Default	What it does
keywords	array of strings	[]	One search per keyword (job title, skill, company). Empty runs the board's default listing.
location	string	""	City or region, in the board's own language. location is matched client-side against the card's location text (the board has no stable location URL filter); accents are optional, so "krakow" finds Kraków.
maxItems	integer	100	Hard stop after this many jobs. This is the cost dial.
includeDetails	boolean	false	Also open each job's own page for description, expiry date and better salary data. Roughly 10x slower.
postedWithinDays	integer	0	Keep only jobs posted in the last N days. 0 disables the filter.
startUrls	array	[]	Listing URLs on nofluffjobs.com to crawl directly instead of building searches from keywords.
extra	object	{}	Board-specific filters. region: pl | cz | sk | hu (default pl) — the board's own country prefix. category: backend, frontend, fullstack, mobile, devops, testing, data, ai, security, … — crawls that category's listing instead of the region's front page, and combines with keywords when both are given.
proxyConfiguration	object	Apify proxy	Apify datacenter proxy groups only; residential groups and custom proxy URLs are rejected.

Keywords are applied by the board, not by this actor: they become ?criteria=keyword%3D<keyword> on the listing URL, which No Fluff Jobs filters server-side. That filter answers from the board's Polish index whatever region you ask for, so pair keywords with extra.category — or leave region alone — if you want Czech, Slovak or Hungarian rows. Each row's location.country is the country the board itself files the posting under, not the region you typed, so a run never labels a Polish job as Czech.

Pricing

$2 per 1,000 jobs, plus $2 per 1,000 when includeDetails is on. No subscription.

Limitations

Public listing data only — no data behind a login. The crawler obeys nofluffjobs.com's robots.txt, including for URLs you pass in startUrls, and runs on datacenter proxies without any CAPTCHA or challenge circumvention: a challenge page is reported as an error, not retried through another browser. Apify datacenter proxy groups only; residential groups and custom proxy URLs are rejected before the run starts. Jobs the board removes between the listing page and the detail fetch are skipped rather than shipped half-filled.

Descriptions are stripped of e-mail addresses, phone numbers and any line naming a contact ("Kontakt: …"), and capped at 20,000 characters, so no row carries a route to a named recruiter. That is a filter on the description text, not a guarantee about every field the board prints.

Three things this board does that show up in the data.

• Deferred salaries. Some employers hold the range back until an interview. Those cards print "Sprawdź wynagrodzenie" and their rows carry a null salary rather than an invented one — about 30% of the rows on a busy category. The amounts are not in the page at all, hidden or otherwise.
• Day rates. Plenty of contract postings are quoted per day. Those rows keep their amounts, their currency and the board's own label, but ship period: null and leave minEurMonth / maxEurMonth null rather than report a day rate as a monthly wage twenty times too small. Read the raw label when you need to tell a day rate from an unpriced row.
• Suggestion cards. A keyword search that runs out of exact matches fills the rest of the page with "you might also like" postings answering a different search. This actor drops them, so a narrow keyword run returns fewer rows — and bills for fewer rows — than the page appears to show, and stops as soon as the real matches do.

employmentType is normalized to the vocabulary the job pages use, so a listing-only run and a includeDetails run agree: the board's b2b becomes CONTRACTOR and permanent becomes FULL_TIME, and anything else is passed through in upper case.