| Takeaway | Detail |
|---|---|
| The AI wage-growth prediction is partly a parsing artifact. | Identical skills and wages can be tagged as AI or non-AI depending on whether a sentence contains a task verb such as 'train,' 'fine-tune,' or 'deploy.' |
| Dice's 73% AI-skills rate is a keyword-mention metric, not a task-demand metric. | A tech posting may say 'AI' without specifying an AI work activity; O*NET separates Software Skills from Work Activities, so the count depends on which field is searched. |
| The gap between AI mention and AI task explains how the wage-growth prediction can fail to appear. | A worker who chases job titles containing 'AI'—but not task verbs—may not receive the advertised raise, because the underlying duties did not change. |
| PwC data and O*NET parsing need to be read together before acting on 73% or any wage-growth figure. | Dice reports that 73% of tech postings require AI skills, but the PwC AI Jobs Barometer's wage-growth figure cannot be interpreted without knowing whether the parser counted mentions or tasks. |
According to Dice, 73% of tech job postings now require AI skills. But the way postings are parsed matters: a posting can mention AI in a tool list while the actual task—training a model, fine-tuning a prompt, deploying a system—appears in another sentence. Mention-based counting and task-based counting are not the same.
Parsing also drives the wage-growth prediction. The PwC AI Jobs Barometer is often cited for that figure, but it is not a clean wage premium. When the same skill is labeled AI because 'machine learning' appears nearby, and non-AI when it does not, the wage gap reflects sentence structure and keyword proximity as much as actual work. O*NET classifies Software Skills under Worker Requirements and Work Activities under Occupational Requirements, so the choice of taxonomy changes which postings count as AI.
Skill nuance is the practical lesson. A raise is advertised for AI jobs, but a posting that merely says 'AI' is not the same as one that asks a worker to deploy or fine-tune a model. Chasing the label without chasing the task will not produce the promised growth. Treat 73% as a ceiling, not a guarantee, and look for the verbs that describe actual AI work.
The Parsing Effect: Why an “AI” Tag
Lightcast’s job-posting parser assigns a posting to the “AI-demand” category when any of its AI-skill terms — “machine learning,” “PyTorch,” “transformers” — appears anywhere in the text. The parser does not check whether the term sits under requirements, responsibilities, or company boilerplate. O*NET separates Worker Requirements (Software Skills, Essential Skills, Transferable Skills, Knowledge) from Occupational Requirements (Work Activities, Work Context), but the tag ignores that boundary. A single sentence in an employer’s boilerplate about “using machine learning to improve internal tools” can flag a posting that never asks the applicant to touch a model.
On the wage side, Lightcast parses employer-supplied salary ranges embedded in the same posting text and compares median advertised wages between AI-flagged and non-AI-flagged postings within the same O*NET SOC code. That makes the comparison an advertised-wage differential, not a realized-wage differential from payroll records. Advertised ranges are strategic documents: employers can post a wide range to attract AI-filtered searches, or use a range for pay banding while actual offers come in lower. No payroll record checks whether anyone is paid those numbers.
The tag is also manufactured by the recruitment market. Candidates filter job boards by “AI” and “machine learning”; applicant-tracking tools such as Indeed, SeekOut, and Eightfold AI rank candidates by keyword overlap. So employers insert AI terms for search visibility even when the daily work does not change. This is not a small measurement error; it is the mechanism that decouples the label from the task.
The leverage point is the ontology threshold. Acemoglu, Autor, Hazell, and Restrepo’s NBER paper counts a small share of U.S. online vacancies as core-AI. Expanding the term list to any generic “artificial intelligence” mention, as Lightcast’s expanded ontology does, sharply increases the count. Add many non-core postings to the AI-flagged bucket and the measured premium mechanically compresses: when most added postings carry no wage signal, the median difference between flagged and unflagged postings shrinks. The “AI tag” on a job board is not a fixed thing; it is a function of where the parser drew the line.
| Ontology / parser | What it counts | Effect on the premium |
| Core-AI (Acemoglu et al.) | U.S. online vacancies naming AI in core work content | Baseline; task-embedded test still required |
| Expanded generic (Lightcast) | Any “AI” mention; count rises sharply | Mechanically compresses the measured premium |
| Lightcast wage parse | Advertised salary ranges in same posting, same O*NET SOC | Advertised differential, not realized payroll; verify task content |
Because the tag cannot distinguish an embedded tool from a decorative keyword, it functions as a verify-the-task trigger. If a named AI skill is tied to a daily task — a tool, an object, and data — the premium is meaningful; if it is preferred or boilerplate, the premium is absent. The tag tells you to go look; it does not tell you the number. The premium is a label-selection artifact, not a human-capital payoff.
The Evidence
PwC's AI Jobs Barometer attached a headline number to U.S. jobs that require AI skills. A narrower comparison—restricted to the same BLS occupation code and to core AI tools rather than broad "AI" mentions—produces a lower number. That gap between the raw and adjusted premiums is the first trace of the label-selection effect.
That adjustment is necessary because AI-tagged postings are not randomly distributed across the economy. They concentrate in management, professional, and technical occupations that carry higher baseline wages. Any simple comparison of AI-tagged versus untagged postings therefore mixes occupation mix with skill-level return. The within-occupation figure removes that mix, which is why the adjusted number — not the headline — is the one a job seeker can anchor on.
Task specificity, not scarcity, explains the residual premium. Burning Glass Institute's analysis of U.S. online postings found that ads naming a specific AI tool, such as TensorFlow or PyTorch, carried a higher posted-wage premium than ads mentioning only "machine learning" or "AI" without a tool. That gap is driven by task specificity: a named tool implies a concrete daily task with an object and a data flow, while a bare AI mention carries far less wage signal.
The supply side points the same direction. LinkedIn Economic Graph's AI Skills update showed the number of members adding AI skills to their profiles grew strongly over the period it measured. Since then, the supply of AI-labeled candidates has caught up with demand, so the forward-looking premium is closer to the adjusted figure than to the headline. Scarcity was never the mechanism; specificity is.
The occupation code itself is a moving target. O*NET updates a rotating set of occupations each year, drawing on research that includes over 42,000 surveys, expert interviews, and analysis of job postings. A posting's "same occupation" status may not hold as the taxonomy rotates, so the within-occupation comparison is a revision, not a fixed boundary. When a posting names a tool embedded in a daily task — tool, object, data — that is the signal that survives reclassification. Marketplace framing, like Dice's homepage tagline "AI Skills. Bigger Chances. Better Jobs.", tells you what the label promises, not what the within-occupation wage data delivers.
| Evidence source | What it measured | Premium found | Verdict for the anchor |
|---|---|---|---|
| PwC AI Jobs Barometer | U.S. jobs requiring AI skills; adjusted to same BLS occupation code and core tools | Headline raw figure; lower adjusted figure | The adjusted figure beats the headline as the negotiation anchor. |
| Burning Glass Institute | U.S. online postings | Higher premium with named tool (TensorFlow, PyTorch); lower premium with generic "AI"/"machine learning" | The tool-named premium wins over the generic premium; task specificity carries the signal. |
| LinkedIn Economic Graph | AI skills added to member profiles | Strong growth over the measured period | Supply caught up with demand, confirming the adjusted figure, not the headline, as the forward-looking premium. |
The winning anchor is the adjusted figure, and only for postings that name a specific tool embedded in a concrete task. When a posting lists AI as preferred or boilerplate, the evidence says that tag is decoration; the wage signal is the task, not the label.
Decision Framework: Task-Embedded vs. Decorative AI Skills
Dice's source data reports a 73% AI-skills posting rate — a figure that reads like proof of scarcity. It is not. The same AI tag in a posting can be a strong anchor, a weaker anchor, or no anchor at all, and the only thing separating them is where the term sits in the posting's structure. The parser codes "core AI" for both task-embedded and qualification-labeled mentions, so the raw flag alone tells you almost nothing. You have to decode the structure line by line.
The distinction is positional. Task-embedded language describes a daily work activity: a tool acting on an object, appearing under the "Responsibilities" heading. Qualification-labeled language describes a credential the candidate must bring, appearing under "Requirements." Decorative language is neither — it shows up in company boilerplate or "nice-to-have" sentences. Each pattern carries a different supported premium, and only the task-embedded pattern matches the within-occupation evidence.
A single posting can contain all of these patterns in different sections; the parser resolves each mention independently, so decode the posting field by field rather than taking its overall AI tag at face value.
| What the posting says | How the parser codes it | Supported wage premium | Verdict |
|---|---|---|---|
| Task-Embedded: AI term under Responsibilities with a tool and an object — e.g., "train a churn model in PyTorch." | Core AI flag | Higher premium | Winner |
| Qualification-Labeled: AI term under Requirements as a standalone credential — e.g., "must have machine-learning experience." | Core AI flag | Lower premium | Apply only if you already have the exact tool |
| Decorative: AI term in boilerplate or "nice-to-have" language — e.g., "we love AI" or "familiarity with AI preferred." | Non-core or no AI flag | No premium | Ignore the AI tag; negotiate on the occupation's non-AI median |
Task-Embedded is the only row in which the higher premium matches the within-occupation evidence. The other rows are selection artifacts — the employer chose the label, not the task — so they should not move a wage anchor. A standalone machine-learning credential under Requirements signals candidate screening, not daily work; it carries a smaller premium than the embedded case, and boilerplate carries none. The premium figure does not prove that AI skills are scarce and valuable. It proves that the market prices a concrete tool embedded in a daily task; the label alone is noise.
Apply the decision tree in order, treating every AI mention as a verify-the-task trigger:
Rule 1. If the AI term appears under Responsibilities with a tool and an object — anchor your negotiation at a premium above the occupation's non-AI median.
Rule 2. If the AI term appears under Requirements as a standalone credential — anchor at a lower premium, and apply only if you already have the exact tool named elsewhere in the posting.
Rule 3. If the AI term appears only in boilerplate or "nice-to-have" language — do not add an AI premium; ignore the AI tag and negotiate on the occupation's non-AI median.
Rule 4. If your occupation's AI-skills posting rate is anywhere near Dice's 73% figure — treat every tag as a verification trigger, because in a high-rate market most tags are selection labels, not task descriptions.
Rule 5. After verification, negotiate on the tool, not the label: a named tool embedded in a daily task earns the higher anchor; a named tool used only as a credential does not.
What the Data Doesn’t Tell You
Revelio Labs data on U.S. online postings put most of them in the no-salary-range bucket. That means the entire AI-premium calculation is built on the disclosing minority of employers—a group skewed toward large firms and pay-transparency states. The advertised premium is a selection-biased estimate, not a market-wide wage fact.
The distribution behind that mean premium is bimodal before it is anything else. The computer and mathematical occupation group commands a substantial premium over its non-AI occupation median, while office and administrative support occupations receive no premium. Applying the headline mean to any single SOC code misleads: the same AI tag is a wage signal in technical occupations and a non-signal in clerical ones. The scarcity myth fails here—if AI skills were scarce and valuable, the premium would not be absent for an entire occupation group.
Felten, Raj, and Seamans's AI-exposure research supplies the most direct counterweight. In routine-intensive occupations, AI exposure is negatively correlated with wage growth. An AI skill tag may therefore predict displacement risk rather than a raise in exactly the jobs where the label is most often decorative. The verify-the-task trigger matters because the label alone cannot tell these futures apart.
Reverse causality is unresolved. In firms that raise pay grades, HR departments are more likely to rewrite postings with AI terms to justify the new grade. The label can be a consequence of wage growth, not its cause. This does not invert the canonical decision rule; it says the high anchor is only trustworthy after you confirm the skill is embedded in a daily task—tool plus object plus data—rather than in a compensation committee’s after-the-fact description.
The last limitation is the one most job seekers miss: advertised wages are not paid wages. State administrative wage records show that realized wage growth for workers who accept AI-tagged jobs is lower than the advertised premium, and many leave the AI-tagged job soon after. The advertised premium is a negotiation anchor, not a return forecast.
| What the data cannot tell you | Evidence | Implication for the decision rule |
|---|---|---|
| A uniform premium across occupations | Computer/math: substantial premium; office/admin: no premium | Use the occupation-specific anchor, never the overall mean, for a SOC code. |
| A market-wide estimate from all postings | Most postings lack a salary range; a minority disclose (Revelio Labs) | Adjust for the large-firm and pay-transparency-state skew. |
| AI exposure as future wage growth | Routine-intensive occupations: AI exposure negatively correlated with wage growth (Felten, Raj, Seamans) | Treat the AI tag as a displacement-risk flag until task content is verified. |
| The label as the cause of the raise | HR may add AI terms after a pay grade increase | Confirm the tool + object + data task before using the high anchor. |
| Advertised wage as realized wage | Realized wage growth is lower than advertised; many leave AI-tagged jobs quickly | Use the premium as a negotiation anchor, not a guaranteed wage-growth forecast. |
The table’s edge cases refine the thesis instead of refuting it: the premium is a label-selection artifact, not a human-capital payoff. Use every AI skill mention as a verify-the-task trigger. If the skill is embedded in a daily task, anchor at the decision rule’s high end above the occupation’s non-AI median; if it is preferred or boilerplate, do not add an AI premium. The counter-evidence above explains when that anchor is fragile—it does not change the direction of the rule.
Worked Case
The edge case matters. Change the posting to “AI experience preferred” with no deployment verb, no named tool, no data object, and the same SOC code is not a premium posting; the correct anchor is the occupation’s non-AI median. The task-embedded relation—tool + object + data—is the verify trigger, not the AI vocabulary.
Dice, the tech-career marketplace, says generative AI has been "a game changer" for recruiting. True — but not in the way most job seekers read it. The premium is a label-selection artifact, and the label lives inside the posting, not inside the worker. The myth to drop is that the figure proves AI skills are scarce and therefore valuable. Scarcity would show up across every AI mention; the parsing effect shows up only when the AI term is embedded in a daily task.
Rule 2 — Run the same-SOC test. Pull the BLS Occupational Employment and Wage Statistics (OES) median for the posting's SOC code and compare it with the posted salary. A genuine task-embedded AI posting should put the posted salary at a premium to the OES median; a decorated posting will show little or no premium. That ratio is a fingerprint: it reveals which anchor the employer actually used, regardless of the wording around it.
| Checkpoint | Result | Anchor |
|---|---|---|
| Baseline: management analyst, BLS OES median | Median wage | Non-AI comparison wage |
| AI-tagged posting text | “Build churn-prediction models using Python and LightGBM; deploy to Snowflake; tune features; present risk scoring to finance leadership.” | Core-AI flag triggered: tool + object + data |
| Predicted posted wage with the Stanford AI Posting Panel coefficient | Predicted wage | Employer range |
| Candidate’s move from non-AI median to AI-tagged role | Wage increase | Matches the prediction only because the skill is task-embedded |
| Decorative AI mention (preferred, no daily task, no named tool) | No premium | Anchor at the occupation’s non-AI median |
Rule 3 — Calculate skill overlap. For a job seeker, count the overlap between your current resume's hard skills and the posting's hard skills. If overlap is low, retraining costs will consume more than the advertised gain. Treat that offer as a career-change offer, not a raise — and negotiate on trajectory, not the AI tag.
How to Choose Well
Rule 4 — The manager's sentence test. Hiring managers should add an AI skill to a posting only when the sentence "This job uses [tool] to [task] on [data]" can be completed truthfully. If it cannot, omit the skill. Otherwise the posting carries the hiring premium for a credential that is never used in daily work — you pay for a tag the parser reads as demand.
Rule 5 — Verb-ratio comparison. When choosing among multiple AI-tagged offers, compute the ratio of AI-specific task verbs (train, fine-tune, deploy, prompt, evaluate) to total task verbs in the responsibilities section. If the ratio is low, the posting is not genuinely AI task-based. Evaluate it against the non-AI wage distribution and decide on non-AI fundamentals — team, scope, base salary — because the premium will not materialize as wage growth.
Choose well by choosing the posting where the tool names the task. Everything else is decoration.
Rule 4 — The manager's sentence test. Hiring managers should add an AI skill to a posting only when the sentence "This job uses [tool] to [task] on [data]" can be completed truthfully. If it cannot, omit the skill. Otherwise the posting carries the hiring premium for a credential that is never used in daily work — you pay for a tag the parser reads as demand.
Rule 5 — Verb-ratio comparison. When choosing among multiple AI-tagged offers, compute the ratio of AI-specific task verbs (train, fine-tune, deploy, prompt, evaluate) to total task verbs in the responsibilities section. If the ratio is low, the posting is not genuinely AI task-based. Evaluate it against the non-AI wage distribution and decide on non-AI fundamentals — team, scope, base salary — because the premium will not materialize as wage growth.
| Check | Condition | Anchor |
|---|---|---|
| AI term placement | Responsibilities bullet with tool + output (e.g., "fine-tune GPT-4o on support tickets") | Premium above non-AI median |
| AI term placement | Preferred qualifications only | No premium — evaluate on non-AI median |
| Same-SOC ratio | Posted salary at a premium to OES median | Genuine task-embedded premium |
| Same-SOC ratio | Posted salary with little or no premium to OES median | Decorated posting — no premium |
| Resume skill overlap | Low overlap with posting's hard skills | Career-change offer, not a raise |
| Manager's sentence test | "This job uses [tool] to [task] on [data]" | Add the AI skill only when true |
| AI task-verb ratio | Low AI-specific verb ratio | Choose on non-AI fundamentals |
Choose well by choosing the posting where the tool names the task. Everything else is decoration.
What to do next
| Step | Action | Why it matters |
|---|---|---|
| 1 | In the posting's responsibilities section, locate the AI-skill term (e.g., "machine learning," "PyTorch," "transformers") and check whether a task verb—"train," "fine-tune," or "deploy"—appears in the same sentence. | A mention without a task verb is a keyword hit, not a task demand; flagging it prevents anchoring at the wrong wage level. |
| 2 | Open O*NET for the target occupation and verify whether the skill sits under Worker Requirements (Software Skills) or Occupational Requirements (Work Activities). | If the skill appears only under Software Skills with no matching Work Activity, the posting counts as AI by taxonomy choice, not by actual duties. |
| 3 | Measure the posting against Dice's 73% figure—treat 73% as a keyword-mention ceiling, not a guarantee that the role requires AI work. | A tech posting can say "AI" in a tool list without specifying an AI work activity; this gap is the parsing artifact driving overcounting. |
| 4 | Before citing PwC's AI Jobs Barometer, confirm whether the parser behind the wage-growth figure counted mentions or tasks for your occupation's postings. | The prediction fails to appear for workers who chase the "AI" label without task verbs, because the underlying duties did not change. |
| 5 | If the skill is embedded in a daily task with a tool + object + data (e.g., "fine-tune the transformers model on customer-support transcripts"), anchor negotiation at a premium above the occupation's non-AI median. | Task-embedded skill mentions meet the verify-the-task trigger; this is the only condition that justifies the wage-growth anchor. |
| 6 | If the AI skill appears as "preferred" or inside employer boilerplate (e.g., "using machine learning to improve internal tools"), do not add an AI premium. | Preferred or boilerplate mentions don't change the underlying work, so chasing the label without chasing the task will not produce the advertised raise. |
Frequently Asked Questions
If a job posting says 'machine learning' only in company boilerplate, does Lightcast count it as an AI-demand posting?
Yes—Lightcast's parser assigns a posting to the 'AI-demand' category when any of its AI-skill terms — 'machine learning,' 'PyTorch,' 'transformers' — appears anywhere in the text, without checking whether the term sits under requirements, responsibilities, or company boilerplate.
What exactly does Dice's 73% AI-skills rate measure?
Dice's 73% AI-skills rate is a keyword-mention metric, not a task-demand metric.
Is the AI wage premium measured from actual payrolls or advertised salary ranges?
It is an advertised-wage differential, not a realized-wage differential from payroll records, because Lightcast parses employer-supplied salary ranges embedded in the same posting text and compares median advertised wages between AI-flagged and non-AI-flagged postings within the same O*NET SOC code.
Which type of posting carries a stronger posted-wage premium: one naming TensorFlow or one saying only 'AI'?
Burning Glass Institute's analysis found ads naming a specific AI tool, such as TensorFlow or PyTorch, carried a higher posted-wage premium than ads mentioning only 'machine learning' or 'AI' without a tool.
Why does expanding the AI ontology to generic 'AI' mentions lower the measured wage premium?
Add many non-core postings to the AI-flagged bucket and the measured premium mechanically compresses: when most added postings carry no wage signal, the median difference between flagged and unflagged postings shrinks.
When should I treat an AI posting's wage premium as a real negotiation anchor?
The winning anchor is the adjusted figure, and only for postings that name a specific tool embedded in a concrete task; when a posting lists AI as preferred or boilerplate, the evidence says that tag is decoration.
Quick answers
| What is Dice's 73% AI-skills rate? | Dice's 73% AI-skills rate is a keyword-mention metric, not a task-demand metric. |
| Why is the PwC AI Jobs Barometer's wage-growth figure not a clean wage premium? | It is not a clean wage premium; when the same skill is labeled AI because 'machine learning' appears nearby, and non-AI when it does not, the wage gap reflects sentence structure and keyword proximity as much as actual work. |
| What does O*NET separate? | O*NET separates Software Skills from Work Activities. |
| What happens to a worker who chases job titles containing 'AI' but not task verbs? | A worker who chases job titles containing 'AI'—but not task verbs—may not receive the advertised raise, because the underlying duties did not change. |
| How does Lightcast's job-posting parser assign a posting to the 'AI-demand' category? | Lightcast's job-posting parser assigns a posting to the 'AI-demand' category when any of its AI-skill terms — 'machine learning,' 'PyTorch,' 'transformers' — appears anywhere in the text. |
Sources: Reddit, arXiv, arXiv, Reddit, Reddit
Also worth reading: Top Compliance Software Solutions Experts Forecast for 2026: Top Compliance Software Solutions Experts · Best Compliance Management Software for Modern Tech Leaders in 2026: Best Compliance Management Software for · Your Essential HR Compliance Guide for 2026: Your Essential HR Compliance Guide