What job postings actually ask for
We read live postings from company career sites and count what they require. Not a survey, not an estimate — a tally of the words employers put in their own job descriptions.
Counted across 5,978 postings in 19 role families, all seen in the last 90 days. A role appears here once we hold at least 50 postings for it — below that a percentage is noise, so we publish nothing rather than something shaky. Last verified against live postings on ; re-checked every six hours.
- Sales1,224 postings
- Software Engineer1,144 postings
- Solutions Architect634 postings
- Operations514 postings
- Machine Learning Engineer296 postings
- Customer Success287 postings
- Product Manager281 postings
- Finance256 postings
- Engineering Manager225 postings
- Marketing216 postings
- Security Engineer206 postings
- Data Scientist143 postings
- AI Strategy98 postings
- Legal88 postings
- DevOps / SRE87 postings
- People / HR79 postings
- Designer76 postings
- Recruiting67 postings
- Data Engineer57 postings
How these numbers are counted
Where does this job market data come from?
Public job postings published by employers on their own career sites, retrieved through the official Greenhouse, Lever and Ashby job-board APIs — documented, unauthenticated endpoints, not scraping. The corpus currently holds 5,978 postings across 19 role families with enough coverage to report on.
How are the percentages calculated?
Each posting's full text is read once and the skills it names are extracted. A term is counted a single time per posting no matter how often it repeats, so one keyword-stuffed listing cannot inflate a figure. The percentage is that count divided by the number of postings in the role family, and every page shows both numbers.
How current is it?
Postings are re-checked every six hours, and a posting drops out of the window once it hasn't been seen for 90 days. Every figure therefore describes roles being hired for now, not a historical archive.
Why are some roles missing?
A role is published only once at least 50 postings back it. Below that a percentage swings wildly on a handful of listings, so nothing is shown at all — the same threshold the résumé match report uses before it will quote market context to a user.
See how your résumé reads against these
Upload once and every gap the posting asks for is reported honestly — never invented, never quietly written in.
Check my résumé