Pracuj.pl Salary Benchmark by Job Title and City
Get a salary benchmark for any job title from pracuj.pl postings in Poland: gross monthly median, quartiles and range in PLN, share of postings showing pay, listings, direct employers and agencies, top employers, work modes and contract types. One price per benchmark.
- on apify
v0iddo/pracuj-pl-salary-benchmark- category
- jobs, automation
- build
- 0.1.2, built 2026-11-17
- billing
- Apify bills it per result; the price for your plan is on the actor's page.
What you get
Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.
The main fields of each row:
- Job title (
jobTitle) - City (
location) - Listings (
listingsOnSite) - Salaries (
salariesUsed) - Min (
salaryMin) - Median (
salaryMedian) - Max (
salaryMax) - Show pay % (
salarySharePercent) - Direct employer % (
directEmployerPercent) - Search (
searchUrl)
Run it on Apify
- Open pracuj-pl-salary-benchmark on Apify and sign in, or make an Apify account.
- On the Input tab, fill in the fields listed below. The form opens with example values filled in.
- Click Start. Rows appear on the Output tab while the run works.
- Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
- To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.
What you can set
- Job titles (
jobTitles): Job titles as postings name them, one per line, for example księgowa, kierowca or Java developer. Each title gets its own benchmark. - City (
location): Optional city or town such as Warszawa, Kraków or Gdańsk, for a benchmark of that place; empty means all of Poland. English names such as Warsaw are read as the Polish one. - Distance (km) (
distanceKm): How far from the city postings may be. pracuj.pl uses 0, 10, 20, 30, 50 or 100 km; other numbers are rounded down to one of those. Used only with a city. Default:30. - Contract types (
contractTypes): Optional. Only postings that offer one of these contract types; empty means all. Options: Employment contract, Contract for specific work, Mandate contract, B2B, Replacement contract, Agency contract, Temporary employment, Internship, Employment contract: 0, Contract for specific work: 1, Mandate contract: 2, B2B: 3, Replacement contract: 4, Agency contract: 5, Temporary employment: 6, Internship: 7, Employment contract: permanent, Contract for specific work: specific-task, Mandate contract: mandate, B2B: b2b, Replacement contract: substitution, Agency contract: agency, Temporary employment: temporary. - Position levels (
positionLevels): Optional. Only postings at one of these levels; empty means all. Options: Intern, Assistant, Junior, Mid, Senior, Expert, Team leader or coordinator, Manager, Director, President, Manual worker, Intern: 1, Assistant: 3, Junior: 17, Mid: 4, Senior: 18, Expert: 19, Team leader or coordinator: 5, Manager: 20, Director: 6, President: 21, Manual worker: 2, Team leader or coordinator: team-leader, Manual worker: blue-collar. - Postings read per benchmark (
listingsPerBenchmark): Postings counted for each benchmark, in pracuj.pl's order (50 a page). More postings give a steadier median; the price per benchmark stays the same. Default:200. - Posting pages read per benchmark (
detailPages): Posting pages read for each benchmark: first those whose search card does not say gross or net, then spread over the other postings. They give gross pay per contract type, the direct employer and agency shares, categories and technologies. 0 skips them for a faster run. Default:20. - Matching titles only (
titleMustMatch): Count only postings whose title holds every word of the job title (case and Polish letters ignored, and a final vowel: księgowa counts Księgowy). Switch it off to count every posting pracuj.pl's search returns, which also lists postings that only mention the words in their text. Default:true. - Search URLs (
searchUrls): pracuj.pl search result pages copied from your browser, one benchmark each, for example https://www.pracuj.pl/praca/księgowa;kw/warszawa;wp?rd=30 . Filters in the URL are kept. - Maximum results (
maxItems): The run stops after this many result rows. It also caps what one run can cost. Default:100. - Proxy configuration (
proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.
Example input
This is the input the actor is tested with every day.
{
"jobTitles": [
"księgowa"
],
"location": "Warszawa",
"listingsPerBenchmark": 100,
"detailPages": 10,
"maxItems": 20
}Run it from Python
The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.
# pip install apify-client
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN") # your own API token, from the Apify Console
run_input = {
"jobTitles": ["księgowa"],
"location": "Warszawa",
"listingsPerBenchmark": 100,
"detailPages": 10,
"maxItems": 20,
}
run = client.actor("v0iddo/pracuj-pl-salary-benchmark").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)Limits
- Reads pracuj.pl's public search pages and a sample of posting pages, the same pages as our Pracuj.pl Scraper. Its robots.txt is obeyed. Contact phone numbers, e-mail addresses and recruiter names are not collected.
- Salaries are gross monthly pay (brutto) in PLN. A range counts as its midpoint. Net pay, B2B rates (net plus VAT), hourly pay or pay without a period, another currency and outliers (under a fifth or over five times the median) are left out and counted in salariesLeftOut.
- A search card does not always say gross or net; the posting page states it for each contract type. Posting pages are read first for those postings, then spread over the others (detailPages); a card left open whose page was not read is counted in salariesLeftOut.grossOrNetNotShown.
- salarySharePercent is the share of the postings counted that show a salary at all. salaryByLevel and salaryByCity give a median where 5 salaries or more are left for one position level or city.
- By default only postings whose title holds the words of the job title are counted (listingsCounted; titleMatchPercent is their share of the postings read): pracuj.pl's search also lists postings that only mention the words in their text, and reading stops after 2 pages without a matching title. listingsOnSite is pracuj.pl's own count for the search.
- contractTypes, workModes and positionLevels count the postings that offer each, in English (employment contract, B2B, mandate contract; onsite, hybrid, remote; junior, mid, senior); a posting can offer several.
- directEmployerPercent and agencyPercent come from the posting pages read, where pracuj.pl shows whether the employer posted the job itself. topCategories and topTechnologies come from them too and stay in Polish as published.
- topEmployers leaves out employers listed under what reads as a person's name, and gives an employer's median pay from 3 salaries.
- Not affiliated with pracuj.pl or Grupa Pracuj.
- On an Apify account without a paid plan a run returns up to 1 result; on any paid Apify plan it returns up to Maximum results.
- Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
- The actor reads only pages that the site's robots.txt leaves open to automated access.
- Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
- Each run sends the developer a short usage record: the number of results, success or the kind of error, paid plan or not, how it was started and a hashed account code, so repeat runs count once. Nothing from your input or results is sent.
Questions
Do I need an account on pracuj.pl, cookies or an API key?
No. The actor reads only what every visitor of pracuj.pl can see, without logging in. You only need an Apify account to start it.
How many results can one run return?
Up to 1,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.
Why did my run return no results?
The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.
Can I run it on a schedule?
Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.
Which formats can I export?
JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.
More
- Pracuj.pl Scraper: Poland Jobs, Salaries, Contract Type
- ATS Jobs Scraper: Greenhouse, Lever, Workday, Ashby
- Computrabajo Scraper: LATAM Jobs and Salaries
- Computrabajo Salary Benchmark by Job Title and Country
- Freelancer.com Jobs and Projects Scraper
- Gupy Jobs Scraper: Brazil Job Vacancies
- All our scrapers on the Apify Store
every fact here is read from the actor's public data on Apify, every day; it last changed on