Current overview
Main stats for Austria, Germany and Switzerland
Where are the jobs located?
Top cities by listings
| City | Listings | Avg days |
|---|
The live postings behind the map
The listings can be filtered by choosing the role/city on the map or by filling in the filters manually.
| Title | Employer | City | Family | Level | Days open |
|---|
Compare two cities head to head
Pick any two cities having at least 3 live postings, and optionally narrow the comparison to a single role. NOTE: Small cities are noisy.
Actual figures
Which technical skills do postings ask for? READ CAVEAT
Pick a role: the left chart shows what its postings ask for, the right subtracts the market rate to show what makes it distinctive. Denominators are per role. These are floors, not requirement rates — the API caps descriptions at 500 characters, so this only counts tools named up front. Comparing tools holds; reading one percentage as the real requirement rate does not.
Share of postings mentioning it
Difference from the market-wide rate
Role and seniority (Austria, Germany and Switzerland)
Does seniority change how long a job stays open?
Comparison between the different software roles and their posting lenghts
Absolute postings per job title
Average days open per job title
How many jobs are still open after n days?
Every point answers one question: out of 100 live postings, how many have been open at least this many days? Switch roles with the buttons below.
Which country asks for which role?
Every country hires Backend Developers, so raw shares mostly repeat what you already know. This shows the opposite: how far each country's demand for a role sits above or below the DACH average. Orange means over-represented, blue means under-represented, pale means normal. Click any cell to see those postings.
Which company has the most listings?
This pipelines own error rates
Most dashboards do not publish how wrong they might be. These are measured on every run: the share of records rejected by quality rules, the share of source descriptions the API truncated, and the accuracy of the tool matcher where it has been measured.
What this pipeline will not tell you
- One aggregator is not the whole market, and its coverage is not equally deep in all three countries. Cross-country comparisons should be read as indicative.
- The posting date is the aggregator's, which may be when it indexed the job rather than when the employer published it.
- Roles are classified from the job title with keyword rules, not from the description, which the aggregator truncates.
- Ten role families, and the rules run most specific first (security, embedded, gamedev, QA, DevOps/SRE, cloud/platform, mobile, frontend, fullstack, then backend as the catch-all). A generic "software developer" or "softwareentwickler" title with no more specific signal lands in backend, which is why it is the largest bucket.
- The boundaries between role families are judgement calls. A title naming both "full stack" and a backend language is counted as fullstack, checked before the backend catch-all; "cloud engineer" is counted separately from "DevOps/SRE" even though the two overlap in practice. Reasonable people would draw these lines differently, and the rules live in the classification migration so you can check where yours would differ.
- Entry programmes are excluded (Ausbildung, duales Studium, Werkstudent, Praktikum, Trainee), along with Controlling and finance roles and data-centre infrastructure jobs pulled in by keyword search.
- Reposts are detected by content hash (title, company, city, first 200 characters).
- Listings link out, they are not republished. The postings browser shows title, employer, city, role family and age, and every row links to the aggregator. Job descriptions and salary estimates are not redistributed.
- A posting in the browser is not necessarily open. It was live at the last refresh (see the footer). Nothing here re-checks whether a job has since been filled or withdrawn.