Just Join IT & No Fluff Jobs Scraper — Poland IT Jobs, Salary
Pricing
from $0.64 / 1,000 jobs
Just Join IT & No Fluff Jobs Scraper — Poland IT Jobs, Salary
Poland IT jobs from Just Join IT and No Fluff Jobs in one table: salary range per contract type (B2B, employment contract) when published, required skills, experience level, remote / hybrid / office and every city. Or get only the jobs new since your last run. No login.
Pricing
from $0.64 / 1,000 jobs
Rating
0.0
(0)
Developer
Northbell
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Security
Limited permissionsShare
Just Join IT & No Fluff Jobs Scraper
Every IT job on Just Join IT and No Fluff Jobs — Poland's two big IT job boards — for your words and city, in one table with the same columns: the salary range for each contract type (B2B or employment contract, per month or hour), the required skills, experience level, remote / hybrid / office, every city the offer is open in and the full description, as clean JSON. Pick one site or both. Schedule it and you get only the offers posted since the last run.
**$0.80 per 1,000 jobs**, plus $0.01 per run. **Measured, not estimated:** 400 jobs in 153 s, about **$0.0118 of Apify platform usage per 1,000 jobs** at 512 MB (our running cost, included in the price, nothing on top) (2026-10-11). **Which of these employers are growing?** Paste the `company` column into [LinkedIn Company Scraper — Employee Count & Headcount Growth](https://apify.com/northbell/linkedin-company-growth-scraper): plain names work, each company comes back with the headcount LinkedIn counts, and from your second run, how many people it added since the last one.Don't know which companies to watch? The Greenhouse Jobs Scraper searches 4,800 companies by job title, with no company names needed, and reports exactly which matching roles are new or closed each run.
How "new since last run" works
The Actor remembers which jobs each search returned last time. A job it has not seen before is marked isNewSinceLastRun: true.
If the whole search fits within Max jobs, the comparison is exact and jobs that disappeared come back as type: "closed" rows. If the search is bigger than Max jobs, a job only counts as new when it was also posted after your previous run, so an old job that merely moved into view is never reported as new.
Filters (title, location text, salary, remote) never change the comparison, so changing a filter never makes jobs look new.
What you get
| Field | |
|---|---|
title, company | as listed on the site (Just Join IT also gives companyWebsite and companySize) |
location, locations, countryCode | the main city and every city the offer is open in, and the country (ISO) |
workplaceType, remote | remote / hybrid / office, and true only for fully remote |
experienceLevel, category | e.g. junior / mid / senior, and the site's category (e.g. devops, backend, data); No Fluff Jobs also gives the main technology |
contractTypes, employmentType | the contracts offered (B2B, permanent, mandate contract, internship…); Just Join IT also gives workingTime (full_time / part_time…) |
salaries | one entry per contract type: min, max, currency, interval (month / hour…) and gross (Just Join IT: employment contracts gross, B2B net + VAT; null where the site does not say). Only the employer's own currency — not the site's conversions |
salaryMin, salaryMax, salaryCurrency, salaryInterval | the first published range from salaries, for one-table use — null when the salary is hidden or shown as 0 |
requiredSkills | {name, level} — the level (1–5) on Just Join IT, null on No Fluff Jobs. Just Join IT also gives niceToHaveSkills and languages |
description | the full offer text (on No Fluff Jobs, turn off with Include the full description); Just Join IT also gives applyUrl |
postedAt, updatedAt | publication and the last refresh (Just Join IT also gives expiresAt) |
isNewSinceLastRun | true / false, or null on the first run (unknown, not "old") |
jobUrl | link to the job on Just Join IT and No Fluff Jobs |
search, site | which of your searches returned it (and on which site: justjoin.it or nofluffjobs.com) |
Does the job need Polish?
Every job row ends with four columns that say how much Polish (the local language) the job asks for, read from what the job text says — not from the language the ad is written in, so "fluent German (C1) required" in an English ad counts as required.
| Field | |
|---|---|
localLanguageNeed | required, preferred (a plus), one-of (this or another language), not-required (said outright), unknown (the text says nothing), or null (no text was read) |
localLanguageLevel | native, fluent, good, basic, or a CEFR level such as B2, when the text names one |
localLanguage | the language this is about |
languagesRequired | every language the text names: { language, level, need, matched, evidence } — matched are the words that decided it and evidence the sentence, so you can check each call |
Jobs that don't need Polish keeps only jobs that say so (or, in the second option, where it is only a plus). Silence is unknown, never "not required". Words only, no AI model, so the same text always gives the same answer.
Changed 2026-10-15: these four columns were added at the end of each row; existing columns and their order are unchanged.
Input
Put one search per line in Searches (e.g. devops) and optionally a Location (e.g. Warszawa). Pick one or both Sites (both by default) — each row says which site it came from. Many searches in one run are cheaper than one run each.
A search the site refuses comes back as an error row and the run carries on. When the job board itself is down or failing (HTTP 5xx or no answer), the error row says so and carries sourceDown: true, so you can tell it from a problem in this Actor; nothing is charged for what could not be read.
How the search works. Just Join IT: the Actor keeps the offers whose address (company, title, city and category) contains all of your words — e.g. python, java senior, devops — newest first, then reads each offer page; required skills come with their level (1–5) and salaries are listed per contract type in the employer's own currency. No Fluff Jobs: the words go to the site's search as they are — a technology such as python is searched as a required skill, several words such as data engineer as one phrase; the site adds remote offers below a city search and this Actor leaves those out (put remote as the Location to get them). Location is a city on both (Warszawa, Kraków, Wrocław… — English names such as Warsaw and Cracow work too). An offer open in several cities comes back once per site, with all of them in locations.
Get only the new jobs every morning (3 steps)
- Open this Actor in Apify Console, fill in your searches, set What to return to Only jobs that are new since the last run, and click Save as a new task.
- On the task, add a Schedule, for example daily at 07:00.
- Open the task's Integrations tab and connect Slack, email, Google Sheets (or Zapier / Make / a webhook). Each morning you get only the new jobs.
You pay only for the new jobs plus $0.01 per run, so a quiet day costs about a cent. When you export by hand, pick the Jobs view: 14 tidy columns, title first, instead of every raw field.
Pricing
$0.80 per 1,000 jobs, plus $0.01 per run. Closed-job rows and errors are free. With Only jobs that are new since the last run, a daily schedule only pays for the new ones.
For AI agents
For a fast answer call with {"searches": ["devops"], "maxJobsPerSearch": 20, "includeDescription": false}. It takes about 20 seconds. The defaults (up to 200 jobs with full descriptions) can take about 5 minutes, which is longer than many agent tool timeouts. Each row has type: job, closed or error. isNewSinceLastRun: null means "no previous run to compare with".
Same filters on every site (10/2026): experience level (read from the title: intern → executive, returned as a seniority column) and employment type (the site's own words normalised into full-time / part-time / contract / temporary / internship, returned as employmentTypes). They only narrow what is returned, with no extra requests and no extra cost.
Zero rows is never ambiguous. The run's status message says why, per search, e.g. "zzz": no results on the site, results found but all removed by your filters or nothing new since the last run, and the OUTPUT record in the run's key-value store has the same as JSON: perSearch[].status is ok, no-results, all-filtered, nothing-new or error, with listed, read, returned, new and closed. Set summaryRows: true to get it as free type: "summary" rows instead.
Same core columns on every northbell job scraper (15 job sites + 10 company-career-page scrapers), so you can stack them into one table: jobId, title, company, location, countryCode (ISO, job sites), remote (true / false / null), employmentType (the site's own words), postedAt, jobUrl, salaryMin, salaryMax, salaryCurrency, salaryInterval, isNewSinceLastRun. Unknown is null, never a guess.
More job scrapers from northbell
Job sites: SEEK · Instahyre · Reed · InfoJobs · XING · Dice · HelloWork · Computrabajo · Foundit · jobs.ch · Arbeitsagentur · Arbeitnow · Remote OK · We Work Remotely.
Company career pages with exact new/closed tracking: Greenhouse · Lever · Workday · AI companies.