Skills in Demand: What Employers Are Hiring For Now

Not a list of jobs — a list of skills, ranked by how many employers are asking for them today. Type a role, get the skills behind it, who is hiring, at what level, and what each skill is asked for alongside.

Reads seven public job boards. No API key, no account, no proxy.

What does this do?

Every job scraper hands you postings. Nobody needs 1,600 postings; they need the answer to "what does this market actually want?"

This Actor reads the postings, opens each one, and reports the market instead of the list.

flowchart LR
    A[Role or keyword] --> B[7 public job boards<br/>~1,700 live postings]
    B --> C[Read each posting:<br/>skills, level, pay]
    C --> D[One row per skill:<br/>demand, employers, co-skills]

Who is it for?

You are	You use it to
Recruiters and sourcers	Write a spec that matches the market, and see who else is hiring for it
Course and bootcamp creators	Choose a curriculum from what employers ask for, not from last year's syllabus
Career changers and job seekers	See the skill that keeps appearing next to the one you already have
Analysts and journalists	Quote real counts for "the most in-demand skills" instead of a vendor's press release
Founders and hiring managers	Benchmark your job ad against every other ad for the same role
Content marketers	Publish a skills report with live numbers behind it

What data do you get?

One row per skill:

Field	Meaning
skill, category	The skill and what kind it is (language, cloud, data, design, marketing, process…)
postings, sharePercent	How many postings ask for it, and what share of the role's market that is
topCompanies	The employers asking for it most
topLocations	Where those postings are open
seniorityMix, seniorPlusPercent	Entry, mid, senior and lead split
topCoSkills	What it is asked for alongside, with percentages
postingsWithPublishedPay, publishedPayPercent	How many of those postings publish pay at all
boards, sampleJobs	Where the postings came from, and three to click

Turn on Also return every posting as a row for a second table: title, company, board, level, the skills found in it, and any pay it published.

Example: three roles, one run

A real run on 17 September 2026, 1,676 live postings, 26 seconds:

Software engineer	Product manager	Data engineer
React 43.5%	Product Management 97.2%	SQL 68.2%
AWS 41.9%	Roadmapping 69.4%	Python 63.6%
TypeScript 38.7%	Agile 16.7%	ETL 54.5%
Kubernetes 37.1%	Customer Success 16.7%	AWS 50.0%
Observability 37.1%	LLMs 15.3%	Airflow 40.9%

Two things jump out of that table: Kubernetes and Observability appear in exactly the same 37% of engineering postings and are each other's top co-skill, and one in seven product manager ads now asks for LLMs.

Seniority is in every row too: Kubernetes postings are 91% senior or above, Airflow only 56%.

What this does not do, and why

It does not report salaries. Across these boards, pay is published on about 3% of postings, and what is published mixes annual salaries with hourly contractor rates. A median built on that would be invented, so the skill rows report how many postings publish pay, and the actual figures stay on the postings themselves, annualised and labelled.

It is a snapshot, not a trend line. These are postings open right now. Schedule the Actor and compare runs to see movement.

It reads remote-first boards, so the picture is the remote and distributed market: strong on software, data, product, marketing, support and finance; thin on anything that needs a site.

How it reads a posting

• Skills come from the title and description only. Board tags are ignored on purpose: RemoteOK auto-tags a junior payroll job with excel, dev, marketing and sys admin, and counting those turned every second posting into a Golang job.
• Ambiguous words are read from the title alone, where boilerplate cannot reach them. "Our recruitment process has four stages" is not a recruiting job; "swift response" is not the language.
• The language Go is tracked as golang, because a bare "go" matches every posting ever written. The same goes for "R".
• Add anything the dictionary misses with Extra skills to track.

How to use it

1. Put one or more roles in, one per line. Leave it empty to analyse the whole market.
2. Optionally add extra skills of your own.
3. Raise Ignore skills with fewer postings than for a shorter, sharper table.
4. Run it. Seven boards and 1,700 postings take about 25 seconds.

Pay-per-event pricing

Event	Price
Role analysed	$0.05
Posting analysed	$0.0005

Three roles across 156 matching postings: $0.23. The whole market, 1,676 postings: $0.89.

Popular skill reports

• Most In-Demand Skills Right Now, From Live Job Ads — every posting on all seven boards
• Software Engineer Skills Employers Ask For in 2026 — "software engineer" postings
• AI Engineer Skills: What the Job Ads Actually Ask For — "ai engineer" postings
• Data Engineer Skills in Demand: SQL, Python, ETL, Cloud — "data engineer" postings
• Data Scientist Skills From Live Job Postings — "data scientist" postings
• DevOps Engineer Skills: CI/CD, Kubernetes, Terraform — "devops engineer" postings
• Product Manager Skills From Live Job Ads — "product manager" postings
• Product Designer Skills: Figma, Wireframing, UX Research — "product designer" postings
• Account Executive Skills From Live Sales Job Ads — "account executive" postings
• Customer Success Skills From Live Job Postings — "customer success" postings
• Marketing Manager Skills From Live Job Ads — "marketing manager" postings
• Engineering Skills in Demand Across Every Engineer Role — "engineer" postings
• Design Skills in Demand: Figma, Wireframing, Adobe — "designer" postings

Each page is this Actor with a different role. Open one, put your own role in, and run it.