# The Resume-Skill Demand Signal Reference, One Row per Signal

*You will be able to take any skill on your resume and read the seven public demand signals correctly to decide feature, keep, or retrain.*

- Canonical URL: https://www.refolk.ai/candidates/guides/resume-skill-demand-signal-reference
- Pillar: Reading the market
- Format: Reference
- Published: 2026-09-21
- Last reviewed: 2026-09-21
- Reading time: 17 min
- Keywords: are my resume skills still in demand, how to tell if a skill is in demand, in-demand vs declining skills, which skills to put on resume market data, growing and declining job skills

## Key takeaways

- A skill present in nearly three-quarters of US postings, like business operations, is table stakes, not a differentiator - ubiquity and demand are different signals.
- AI skills carry roughly a 28% advertised-salary premium, nearly $18,000 a year, but only about 23% of postings show any salary, so premium data rests on a thin sample.
- In Refolk's index the US Python pool is about 585,371 profiles against 3,384 for Rust, so a hot niche can be 173x smaller in supply than a mainstream skill.
- Automation exposure is a fork, not a verdict: the same high-exposure label means augmentation for engineers and substitution for data-entry clerks.
- Velocity and level diverge by design - education shows 200% genAI posting growth off the lowest base while marketing sits at 8% of postings, so reading one number alone picks the wrong winner.
- WEF projects 39% of existing skill sets will be transformed or outdated between 2025 and 2030, which is why direction matters more than this year's ranked list.

You have a resume skill and a decision: feature it, keep it quietly, or retrain out of it. The "top skills employers want" articles will not settle it, because they contradict each other, they expire, and they never tell you how to read a skill they did not happen to list. This reference names each demand signal one at a time, states what it proves, states how it lies, and points to the public source that publishes it, so you can evaluate any skill on your own resume instead of memorizing this year's ranking.

It is for job seekers deciding what to put forward, and for anyone weighing a retrain or a move. Read it end to end once, then jump to the row you need.

## Why one ranked list can never answer "are my resume skills still in demand"

The short answer: every "most in-demand skills" list is built from one source measuring one thing over one horizon, so two honest lists disagree without either being wrong. A skill can top a survey of what employers expect by 2030 and be flat in today's postings at the same time.

The three big public sources literally measure different quantities. The World Economic Forum's Future of Jobs Report surveys employers about where skills are heading; it drew on over 1,000 leading global employers representing more than 14 million workers across 22 industry clusters and 55 economies. The Bureau of Labor Statistics models numeric employment change over a ten-year window. Indeed's Hiring Lab counts live postings right now. Ask them the same question and you get three answers because they answer three different questions.

The stakes are not academic. WEF projects that 39% of existing skill sets will be transformed or become outdated between 2025 and 2030. That is why the durable move is to read signals, not rankings. A ranking tells you where a skill sat when the article was written. A signal tells you how to check today, and again next quarter.

> A ranking tells you where a skill sat last year. A signal tells you how to check it yourself, today and next quarter.

## The seven demand signals, and what each one proves

There are seven observable signals that recur across the primary sources. Each proves one narrow thing and lies in one predictable way. Learn the row, not the ranking.

| Signal | What it proves | How it misleads | Public source |
|---|---|---|---|
| Posting frequency | Present breadth of demand | Ubiquity reads as strength; a table-stakes skill looks like an asset | Indeed Hiring Lab, Lightcast |
| Year-over-year velocity | Direction of demand | Triple-digit growth off a near-zero base looks explosive | Indeed Hiring Lab |
| Salary premium | Willingness to pay for the skill | Thin salary data makes a delta a sampling artifact | Lightcast |
| Survey projection | Where employers say demand is heading | Says nothing about who is hiring today | WEF Future of Jobs |
| Time-to-fill | Latent scarcity of supply | Long fill can mean a broken process, not scarcity | SHRM, LinkedIn |
| Geographic concentration | Whether demand is national or clustered | National numbers hide metro-level oversupply | Indeed Job Postings Index |
| Automation exposure | Technical feasibility of automation | Exposure is not displacement; it can mean augmentation | Pew, Upjohn, O*NET |

Two of these are the ones people misread most, so hold them together. Posting frequency without velocity is the classic trap: business operations skills appeared in nearly three-quarters of all US job postings in one recent quarter, more than any other category. That does not make "business operations" a differentiator on your resume. It makes it a baseline the employer already assumes. Frequency proves the skill is expected. Velocity proves whether demand for it is still growing.

> **Rule:** Never read level without velocity
>
> A skill's share of postings tells you if it is expected. Its year-over-year change tells you if demand is still growing. A high, flat skill is table stakes; a moderate, rising skill is a differentiator.

## The public sources and the exact unit each publishes

Before you trust a number, know its unit. Each source reports in its own currency, and mixing them is how people build contradictory conclusions.

| Source | Unit it publishes | Best for |
|---|---|---|
| WEF Future of Jobs | % of employers expecting a skill to rise or fall | Direction to 2030 |
| BLS Employment Projections | Numeric jobs and % change over 10 years | Long-run role survival |
| O*NET | Importance 1 to 5, level 0 to 7 per occupation | What a skill is worth inside a role |
| Indeed Hiring Lab | Job Postings Index (Feb 1 2020 = 100) and % share | Live demand and velocity |
| Lightcast | Unique vs total postings, advertised-salary premium | Pay signal and skill extraction |

A few grain notes that save you from misreading. O*NET assesses all 35 skills for each of 968 occupations, with importance rated 1 to 5 where 1 means not important and 5 means extremely important; these are analyst ratings, not counts of jobs. Indeed's index is anchored so that February 1, 2020 equals 100, which keeps comparisons consistent across time and countries. When you read an Indeed figure of 112, that means 12% above the pre-pandemic baseline, not 112 jobs.

Refolk works in a different currency again: supply. The tables below use counts from Refolk's index of professional profiles, which tells you how many people already hold a skill, a number the posting sources cannot give you.

## Supply is a signal too, and scarcity only pays when paired with velocity

Supply tells you how crowded the field of people holding a skill already is. On its own it proves nothing about demand, but paired with rising postings it turns a scarce skill into a genuine advantage.

**173x - How much smaller the US Rust pool is than the US Python pool in Refolk's index**

Rust sits at 3,384 profiles against 585,371 for Python - scarcity on the supply side.

Here is the supply picture directly from Refolk's index.

| Skill | Country | Professionals in index | Derived ratio |
|---|---|---|---|
| Python | United States | 585,371 | baseline |
| Python | Germany | 79,319 | 0.14x US (US = 7.4x) |
| Rust | United States | 3,384 | 0.006x US Python (173x smaller) |

Read this correctly. The US Python pool is about 7.4 times the German Python pool, and Rust is roughly 0.58% the size of the US Python pool. That scarcity is real, but scarcity is a supply fact, not a demand signal. It becomes a demand signal only when posting velocity confirms employers actually want it. The confirming layer exists here: since late one recent February, software developer postings in the US rose almost 15% while postings overall declined 7%. Scarce supply plus rising postings is the combination that earns interviews. Scarce supply with flat postings is just a small field.

You can check the supply side of any skill directly against Refolk's index.

Ask me this: `Software engineers who list Rust and have shipped production systems, in the US, currently at Series A-C startups.` - [run the search](https://www.refolk.ai/start?q=Software%20engineers%20who%20list%20Rust%20and%20have%20shipped%20production%20systems%2C%20in%20the%20US%2C%20currently%20at%20Series%20A-C%20startups.).

*Returns the actual population of people holding the scarce skill in your target segment, so you can see how crowded the field really is before you bank on scarcity.*

## Velocity and level diverge by design, so read them together

Velocity and level pull in opposite directions across sectors, and reading one without the other picks the wrong winner. High growth almost always sits on a low base; high level almost always grows slowly.

The clearest illustration is AI adoption across sectors, where the growth rates and the current levels tell nearly opposite stories.

| Sector | Postings requiring AI | Annual growth |
|---|---|---|
| Marketing / PR | 8% | 50% |
| Human Resources | not stated | 66% |
| Finance | low baseline | 40% |
| Education / Training | lowest | 200% (genAI) |

Education shows 200% generative-AI growth, but off the lowest base of any sector, so the absolute number of jobs is small. Human resources shows 66% growth. Data and analytics is a different regime entirely: nearly 45% of data and analytics postings now contain AI-related terms, compared with about 15% in marketing and 9% in human resources. So AI in data and analytics is already table stakes at a high level, while AI in education is a fast-rising sliver. If you list an AI skill, which sector you are applying into decides whether it reads as expected or as a rare edge.

#### Level versus velocity for a resume skill

Horizontal axis runs from Low current posting share to High current posting share. Vertical axis runs from Low velocity to High velocity.

| Quadrant | What it means |
| --- | --- |
| Emerging bet | Feature only if you can also show the confirming posting rebound |
| Hot and expected | Feature, and expect it to be a baseline soon |
| Fading niche | Drop or retrain unless a metro or premium rescues it |
| Saturated baseline | Keep on the resume but do not lead with it as a strength |

*A skill's demand posture is set by where it falls on current share and year-over-year growth.*

## Automation exposure is a fork, not a death sentence

Exposure tells you a skill's tasks are technically feasible to automate. It does not tell you the job goes away. Both Pew and the Treasury emphasize that these scores measure potential technical exposure, not actual displacement; exposure identifies feasibility, it does not predict whether jobs will be eliminated or transformed.

That distinction changes the verdict on the same score. In 2022, 19% of American workers were in jobs most exposed to AI, and those jobs cluster in white-collar, higher-education roles, while clerical jobs built on routine cognitive tasks are projected to keep shrinking. So the identical "high exposure" label means augmentation for an engineer and substitution for a data-entry clerk. WEF's own breakdown matches this: the fastest-growing roles are technology-related, including big data specialists, fintech engineers, and AI and machine learning specialists, while the largest absolute declines fall on clerical and secretarial workers, cashiers, postal service clerks, bank tellers, and data entry clerks.

BLS adds a timing caution worth internalizing before you retrain in a panic. The historical record shows technology impacts occupations gradually, not suddenly, and it can take time for employers to figure out how to incorporate new technology. Overall, BLS projects total employment to grow from 170.0 million in 2024 to 175.2 million in 2034, an increase of 3.1%. Exposure is a reason to check whether your skill is on the augmented side or the substituted side, not a reason to abandon it overnight.

> **Note:** Exposure tells you which way to read, not that a skill is finished
>
> Locate your occupation in the Pew or Upjohn tiers, then ask: are the exposed tasks the routine core of the job, or the parts a tool speeds up? The first points to substitution; the second points to augmentation.

## Time-to-fill and geography, the two signals people skip

Time-to-fill measures how long a role sits open, and a long fill relative to the baseline usually means the underlying skill is scarce. But it also breaks in a specific way, so anchor it against a benchmark before you infer demand.

| Segment | Days to fill | Read |
|---|---|---|
| All industries (avg) | 44 | The baseline to judge everything against |
| Tech / engineering | 55-62 | Scarce skills, roughly three weeks over baseline |
| Healthcare / nursing | 49 | Modestly tight supply |
| Retail / hospitality (frontline) | 16-22 | Fast fill, ample supply |

Average time to fill fell from 48 days in 2023 to 41 days in 2024, so the baseline itself moves; re-check it rather than memorizing a number. Tech roles take an average of 62 days to fill, nearly three weeks longer than the all-industry average, which points to genuine scarcity. But a long fill can also mean a broken hiring process, so compare against the 44-day baseline before you read scarcity into it.

Geography can flip a national signal on its head. A skill that looks in demand nationally can be oversupplied exactly where its workers cluster. Indeed's index has shown large tech metros running near or below their pre-pandemic baseline while mid-size metros averaged 112.0 and small metros 115.5. If your scarce skill is concentrated in the same handful of metros as everyone else who holds it, the national number is hiding your real local market. That is when featuring the skill may quietly imply relocation.

## How to triage one resume skill

The job is to run each skill through the signals in order and end with a keep, drop, or retrain verdict. Budget one to two hours the first time; it goes faster once the sources are bookmarked.

#### Triage one resume skill against the market

1. **Name the skill at the right grain** - Decide if it is a tool, a category, or a role, and map it to a term a source tracks - an O*NET element, an Indeed category, or a Lightcast skill.
2. **Read posting frequency** - Pull the share of postings in your occupation that name it, and note the category baseline to compare against.
3. **Read velocity, not just level** - Check year-over-year posting growth and label the skill rising, flat, or declining.
4. **Check salary premium** - Compare advertised salaries for postings that name versus omit the skill, and record how many postings actually showed pay.
5. **Cross-check the survey projection** - Confirm direction against WEF Future of Jobs, and flag any conflict as a horizon difference rather than an error.
6. **Check automation exposure** - Locate the occupation in Pew or Upjohn tiers and decide if the skill is complemented or substituted by AI.
7. **Check geographic concentration** - Determine whether demand is national or clustered in specific metros, and whether that implies relocation.
8. **Score and decide** - Feature skills that are high-frequency and rising, or that carry a salary premium with low substitution risk; assign each skill a keep, drop, or retrain verdict.

The figure below shows the same flow as a pipeline, so you can see where a skill can drop out.

#### Skill triage pipeline

1. **Name at grain** - Map the skill to a tracked term
2. **Level and velocity** - Is it expected, and is it still growing
3. **Premium and exposure** - Does the market pay, and is it augmented or substituted
4. **Geography** - National demand or clustered in a few metros
5. **Verdict** - Feature, keep, or retrain

*Each stage can change the verdict, so run them in order rather than stopping at the first signal.*

Once you have verdicts, the tailoring problem is real: the skills you feature should shift per posting to match what that employer actually names. This is exactly where [Refolk](/candidates) removes friction, tailoring the resume to each posting from your own history and scoring how well you fit, so the featured skills track the signal you just read rather than a static master file.

Here is a compact rubric you can copy into your notes and apply to each skill.

**Per-skill demand scoring rubric**

```
Skill: ____________________  Occupation/category: ____________________

Posting frequency vs baseline:  above (2) / at (1) / below (0)
Year-over-year velocity:        rising (2) / flat (1) / declining (0)
Salary premium (and # of salaried postings): clear + N>=50 (2) / weak or N<50 (1) / none (0)
Survey projection (WEF direction): rising (2) / mixed (1) / declining (0)
Automation exposure:            augmented (2) / neutral (1) / substituted (0)
Geographic concentration:       national (2) / few metros, I am in one (1) / few metros, I am not (0)

Verdict rule:
- FEATURE if velocity=2 AND (frequency>=1 OR premium=2) AND exposure>=1
- KEEP    if frequency=2 but velocity<=1 (baseline, do not lead with it)
- RETRAIN if velocity=0 AND exposure=0
```

*Score each skill 0-2 per line, then apply the verdict rule at the bottom.*

## How this goes wrong: the eight failure modes

Most bad calls come from reading one signal in isolation or trusting a number that rests on thin data. These are the specific ways the signals lie.

1. **Mistaking ubiquity for demand.** A skill in about 75% of postings, like business operations, is table stakes, not a strength. Featuring it as a differentiator is the false positive. Check whether its share is rising or flat before you lead with it.
2. **Velocity off a tiny base.** The 200% generative-AI growth in education is a large percentage of almost nothing. Always pull absolute posting counts alongside the growth rate.
3. **Salary premium from thin data.** With only about 23% of postings advertising pay in some markets, a premium can be a sampling artifact. Check the count of salaried postings, not just the delta.
4. **Reading exposure as demand.** High AI exposure does not mean the skill is dying; exposure identifies feasibility, not whether jobs are eliminated or transformed. It may mean augmentation.
5. **Treating a survey/live mismatch as an error.** WEF's 2030 projections and today's postings measure different horizons. A skill rising in WEF can be flat in postings now. That is a horizon gap, not a contradiction.
6. **Taxonomy drift mistaken for a trend.** Vendors change how they extract skills, and Indeed cautions that its taxonomy evolution may contribute to differences in results over time alongside genuine labor market trends. A jump in share can be a measurement change.
7. **National numbers hiding geographic concentration.** A skill can be in demand only in a few metros. When large tech metros run near baseline while mid-size metros run at 112 and small metros at 115, the national average hides where your competition actually is.
8. **Confusing time-to-fill with prestige.** A long fill can mean a scarce skill or a broken process. Check against the 44-day baseline before inferring demand from a slow hire.

> **Watch out:** Two thin-data traps that fool careful people
>
> Salary premiums are computed from the minority of postings that show pay, and vendor taxonomy changes can move a skill's share without any real market shift. Treat a single striking number from either as a hypothesis to confirm, not a finding.

One more honest limit. There is no published universal cutoff for calling a skill "in demand." Practitioners read a skill's share of advertised roles relative to a category baseline, because baselines differ wildly by occupation and by vendor. A fixed threshold like "X% means in demand" is not established publicly and would break the moment you moved between occupations. When you want a number, always state the baseline it is measured against.

## Before you finalize which skills to feature

Run this check across your whole skill list, not skill by skill, so the resume reads as a coherent set rather than a pile of individually defensible entries.

#### Final demand check before you feature

- [ ] Every featured skill is either high-frequency and rising, or carries a real salary premium with low substitution risk.
- [ ] No skill is featured as a strength solely because it appears in most postings for the role.
- [ ] For every growth figure I trusted, I checked the absolute posting count behind it.
- [ ] For every salary premium I cited, I noted how many postings actually showed pay.
- [ ] I flagged any WEF-versus-postings conflict as a horizon difference, not treated it as one source being wrong.
- [ ] I classed each high-exposure skill as augmented or substituted, and dropped or reframed the substituted ones.
- [ ] I checked whether my scarce skills are clustered in the same metros as everyone else who holds them.
- [ ] Each skill has a written keep, drop, or retrain verdict I can defend from a source.

## Keeping the read current

Demand signals move, so this is a re-check habit, not a one-time audit. Re-run the triage on your two or three lead skills each quarter, and any time you consider a new target role or metro. The mechanisms are stable even when the numbers are not: level versus velocity, premium against thin data, exposure as a fork, and geography inverting the national picture. Bookmark the primary sources and read them in their own units rather than through a listicle that repackages them. When a new ranked list crosses your feed, do not memorize it - use it as a prompt to check the one skill you actually care about against the signal that proves what you need to know.

## Frequently asked questions

### Which single list of most in-demand skills should I trust for my resume?

None of them, and that is the point. Ranked listicles are time-bound and mutually contradictory because each is built from a different source with a different unit: WEF surveys employers about 2030, BLS models ten-year employment, and Indeed counts live postings. Instead of trusting one list, read the underlying signal for your specific skill. Posting frequency tells you present demand, velocity tells you direction, and survey projections tell you durability. Combine at least two before you feature or cut anything.

### Is a high salary premium proof a skill is in demand?

Not on its own. A premium can reflect short-term scarcity rather than durable demand, and the data behind it is thin because most postings hide pay. In one example only about 23% of physician assistant postings in Seattle advertised a salary, so a premium can be a sampling artifact from a small number of postings. Always check how many postings actually showed pay, then pair the premium with posting velocity and substitution risk before you conclude anything.

### How do I tell an in-demand skill from a declining one?

Read level and velocity together, never level alone. A skill in three-quarters of postings but with flat growth is a saturated baseline requirement, not a differentiator. A skill with rising posting share and a confirming survey projection is genuinely growing. Declining skills show falling posting share and appear in survey and BLS decline categories, such as clerical and data-entry roles. The direction of change matters more than the current rank.

### Does high AI exposure mean my skill is dying?

No. Exposure scores measure technical feasibility of automation, not actual displacement. The same high-exposure label means augmentation for some roles and substitution for others: engineers whose work is exposed tend to be complemented by AI, while routine clerical roles built on the same exposed tasks keep shrinking. Treat exposure as a fork that tells you which way to read, not a verdict that a skill is finished.

### A skill shows 200% growth. Should I feature it?

Check the absolute base first. High velocity off a near-zero baseline, like the 200% generative-AI growth in education, looks explosive but represents very few real jobs. Always pull the absolute posting count alongside the percentage. A skill with modest growth off a large base can represent far more actual openings than a triple-digit growth rate off almost nothing. Level and velocity only mean something read together.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/resume-skill-demand-signal-reference*