Programmers Are 75% 'Exposed' to AI. What That Means

The headline number in Anthropic's jobs study, that computer programmers are 75% "exposed" to AI, does not mean 75% of programmers will lose their jobs. It is a task coverage score: how much of an occupation's work shows up as real, work-related use of Claude. The same study found no systematic rise in unemployment among the most exposed workers since late 2022. Its one warning sign is narrower: hiring of workers aged 22 to 25 into exposed jobs looks weaker, and the authors call that result "just barely statistically significant".

This article walks through what Anthropic actually measured, why the gap between what AI can do and what it does do is the real story, what the data does and does not prove, and what to do with it if you are a developer, a student or someone who hires. We also check it against the U.S. Bureau of Labor Statistics' new projections. For the labor-market side of the same period, see our guide to the fastest-growing jobs through 2035.

#Key takeaways

• 75% is coverage, not job loss. It scores tasks, not people.
• AI is used far below its theoretical reach. For Computer & Math jobs, theory says 94% of tasks and observed usage says 33%.
• No clear unemployment effect yet. The gap between exposed and unexposed workers is "small and insignificant".
• The one signal is at the entry point. Job-finding for ages 22 to 25 in exposed jobs fell about 14% against 2022, barely significant, with no such drop for older workers.
• The causes aren't established. The authors list several non-AI explanations.

#What did Anthropic actually measure?

The report ("Labor market impacts of AI: A New Measure and Early Evidence", Maxim Massenkoff and Peter McCrory, March 5, 2026) builds a measure called observed exposure. It starts from tasks that a large language model could theoretically do faster, using the Eloundou et al. (2023) ratings from O*NET's roughly 800 occupations. It then keeps only tasks that actually appear in work-related Claude usage in the Anthropic Economic Index, and weights automated use fully and augmentative use at half.

Two checks make the base credible. 97% of tasks seen across four Economic Index reports fall in categories rated theoretically feasible, and tasks the model rated infeasible are only 3% of usage. So Claude is mostly used on work an LLM can plausibly do.

A caution built into the design: usage data comes from one company's product. Whatever Claude users do shapes the scores, so "observed exposure" is a view through Anthropic's window, not a census of all AI use.

#The gap that matters: capability vs. use

The most important finding is that actual AI use is a fraction of what is feasible. The report says "actual coverage remains a fraction of what's feasible."

If you remember one thing, make it this: "could" and "does" are very different numbers. Adoption, trust, regulation, integration cost and workflow change all sit in between. A related MIT estimate, that AI can technically perform tasks worth about 11.7% of U.S. wages, is also a capability measure, not an adoption or displacement measure.

#So who is most and least exposed?

Most exposed: computer programmers at the top with 75% coverage, then customer service representatives (whose main tasks appear heavily in Anthropic's first-party API traffic), then data entry keyers at 67%.

Least exposed: 30% of workers have zero coverage because their tasks appeared too rarely in the data to count. The report names cooks, motorcycle mechanics, lifeguards, bartenders, dishwashers and dressing room attendants. "Zero" means not observed in Claude data, not "permanently safe".

Who they are: compared with the unexposed group in 2022, the most exposed workers were more educated and better paid.

That reverses the usual picture of automation hitting low-wage work first, at least for language-model exposure.

#Is AI causing unemployment? Not so far

The authors compare unemployment between the top-exposure quartile and workers with no exposure, using the Current Population Survey. The change in the gap since ChatGPT launched is "small and insignificant".

They also tell you what they would have seen. A one-percentage-point differential would be detectable. A "Great Recession for white-collar workers" scenario, with national unemployment doubling from 5% to 10%, would lift the exposed group's rate from 3% to 6% and "should be visible". It isn't. That scenario is the authors' stress test, not a prediction, though some headlines treated it as one.

Their own caution: the impacts of AI "might be less like COVID and more like the internet or trade with China", meaning slow and uneven, and hard to see in aggregates. They also note that even decades-old predictions of offshoring risk (about 25% of jobs flagged) left employment healthy a decade later.

#The one warning sign: workers aged 22 to 25

Here the data shows something, though weakly. In Figure 7, hiring of 22-to-25-year-olds into highly exposed occupations diverges from less exposed ones around 2024.

• Job-finding rates at less exposed occupations stay stable at about 2% a month.
• Entry into the most exposed jobs falls by about half a percentage point.
• Averaged over the post-ChatGPT period, that is a 14% lower job-finding rate than in 2022, "just barely statistically significant".
• There is no such decrease for workers older than 25.

Common mistakes in coverage of this:

• "Entry-level hiring is down 14%." The report says the job-finding rate in exposed occupations is 14% lower than its 2022 level. It is not a total-hiring figure.
• "AI is eliminating entry-level jobs." The authors say the young workers who weren't hired "may be remaining at their existing jobs, taking different jobs, or returning to school," and that survey job-transition data may be mismeasured. Some may leave the labor force rather than count as unemployed.
• A figure in the original report was corrected on March 8 (its top-quartile and zero-exposure labels had been reversed), so anything quoted before that date should be rechecked.

Why hiring could move before unemployment (our interpretation, general economics rather than a finding of the report): a company can quietly stop adding junior roles without laying anyone off, so the first effect on a labor market can show up as fewer hires and not more unemployed. That is why this signal, if real, would appear first among new entrants.

#What other research says

Not every study agrees on the size of the young-worker effect. Stanford's team has also published follow-up work on other drivers of young-worker employment, such as interest rates and timing. We could not open that note, so we don't cite its conclusions.

#What the U.S. government's projections add

On August 27, 2026, BLS published its 2025–35 projections and, for the first time, an AI-exposure category for each of 831 occupations. One of its five inputs is Anthropic's observed-exposure work, so the two are not fully independent. BLS stresses that exposure "does not imply job loss, productivity gains, automation probability, or wage effects."

Our calculations from BLS's workbook:

The three occupations Anthropic found most exposed are all projected to shrink. But exposure is not destiny: the "very high" exposure tier grows about 2% in total, and it holds both data scientists (+34.6%) and data entry keyers (−25.5%). One reading, which is our interpretation, is that writing code line by line is exposed while building software is changing rather than vanishing. Customer service also shows why projections need care: that job loses 141,800 positions yet has 289,500 openings a year from turnover.

#What the study does not say

• It does not say 75% of programmers lose their jobs.
• It does not say AI caused any change it finds, since the design compares exposed and unexposed workers.
• It does not forecast the future.
• It does not tell you whether to study computer science.
• It cannot say what happens outside Claude's use cases, such as image generation or robotics.

#What to do with it

These suggestions are our inference, not Anthropic's.

Developers. Treat the exposure as a prompt to move toward the parts of the job that are hardest to automate: system design, debugging real production failures, security, and checking AI output. The BLS data points the same way, with developers growing while programmers shrink.

Students and new graduates. The weakest evidence is for your group, and the most worrying. Build visible projects, learn to work with AI tools and prove you can verify their work. A task audit helps: list your daily tasks, mark which an AI tool could already speed up, and invest in the rest.

Managers. Use the same audit on roles, not people. Exposed tasks are a reason to redesign work and keep a junior pipeline, since senior skills grow out of junior work. If you are building AI into products, our guides to what AI agents are and reliable AI agents in production cover how to keep humans in the loop.

#Limits of this evidence

• The measure reflects Claude usage only.
• The 14% result is barely significant and based on survey data.
• Unemployment may miss people who leave the workforce.
• The authors say the framework is a first step and plan to update it as new data arrive.

#Want AI built into your product without the guesswork?

If you are deciding which tasks an AI agent should take on and which need a person, get a scope estimate for your AI agent, or read about our AI agent development service.

#FAQ

#What does "75% AI exposure" mean for programmers?

It means that, by Anthropic's measure, about 75% of a programmer's tasks (weighted by how they are used) appear in real work usage of Claude. It does not mean 75% of programmers will be replaced.

#Is AI replacing workers yet?

Anthropic found no systematic increase in unemployment for highly exposed workers since late 2022. It did find suggestive evidence that hiring of 22-to-25-year-olds into exposed jobs has slowed.

#Is AI reducing entry-level hiring?

There is weak evidence of a drop in job-finding for young workers in exposed occupations, about 14% against 2022, barely statistically significant. The report does not show AI is the cause.

#What is observed exposure?

Observed exposure combines tasks an LLM could theoretically speed up with tasks actually seen in work-related Claude use, giving full weight to automated use and half weight to augmentation.

#Which jobs are most and least exposed?

Computer programmers, customer service representatives and data entry keyers are most exposed. About 30% of workers, such as cooks, lifeguards and bartenders, have no measurable coverage.

#Should I still become a software developer?

The study does not answer that. Official projections show software developers growing about 10% over 2025–35 while computer programmers decline, so the specific work you do matters.

#Sources

• Anthropic: Labor market impacts of AI: A new measure and early evidence
• BLS: AI exposure categories and Employment Projections 2025–35
• Stanford Digital Economy Lab: Canaries in the Coal Mine?
• NBER: Still Waters, Rapid Currents (Humlum & Vestergaard)
• ILO: One in four jobs at risk of being transformed by GenAI
• Fortune: Is AI about to take your job?
• PYMNTS: MIT Iceberg Index (11.7% of U.S. wages technically automatable)