Anthropic Just Mapped the Jobs AI Is Replacing First - Here's What the Data Actually Says
<p>Anthropic published something last month that didn't get nearly enough attention: a detailed map of which white-collar jobs AI is most likely to displace first.</p> <p>Software engineers. Financial analysts. Lawyers. Accountants. Marketing managers. HR specialists. Middle management.</p> <p>If your job involves sitting at a computer processing information, writing things, or analyzing data - you're on the list.</p> <h2> The Numbers Are Not Comforting </h2> <p>A survey of 2,500 white-collar tech workers found <strong>61% believe AI will replace their current role within three years</strong>. Not eventually. Three years.</p> <p>Goldman Sachs puts the global figure at <strong>300 million jobs at risk</strong>.</p> <p>In February, AI executive Matt Shumer published an essay on X comparing t
Anthropic published something last month that didn't get nearly enough attention: a detailed map of which white-collar jobs AI is most likely to displace first.
Software engineers. Financial analysts. Lawyers. Accountants. Marketing managers. HR specialists. Middle management.
If your job involves sitting at a computer processing information, writing things, or analyzing data - you're on the list.
The Numbers Are Not Comforting
A survey of 2,500 white-collar tech workers found 61% believe AI will replace their current role within three years. Not eventually. Three years.
Goldman Sachs puts the global figure at 300 million jobs at risk.
In February, AI executive Matt Shumer published an essay on X comparing the current moment to February 2020 - right before COVID hit. That essay was viewed 85 million times.
Then Citrini Research published a scenario they called the 'Global Intelligence Crisis.' Their model: AI agents replace software engineers and financial advisors faster than the economy can adapt. Unemployment spikes above 10%. The Dow fell 800 points the week it published.
What the Data Shows
Anthopic's research maps why jobs are at risk: high text output + structured reasoning = highly automatable (legal, finance, accounting, software engineering). The pattern: if your primary output is a document, a report, or a piece of code - AI can produce that output.
The Workers Who Are Thriving
The workers thriving right now learned to work with AI. They use tools like Claude, Cursor, and OpenClaw to do in two hours what used to take two days. Their output went up. Their value went up. Their employers kept them.
You don't need to become an AI engineer. You need to become the person on your team who uses AI better than anyone else. That's the job that doesn't get replaced.
I made a video breaking all of this down with the actual data: Watch it here
What's your take - is your field on the list?
DEV Community
https://dev.to/boehner/anthropic-just-mapped-the-jobs-ai-is-replacing-first-heres-what-the-data-actually-says-de8Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
claudemodelmarket
quarkus-chat-ui: A Web Front-End for LLMs, and a Real-World Case for POJO-actor
Note: This article was originally published on SciVicsLab . quarkus-chat-ui: A Web Front-End for LLMs, and a Real-World Case for POJO-actor quarkus-chat-ui is a web UI for LLMs where multiple instances can talk to each other — built as a real-world use case for POJO-actor . Each quarkus-chat-ui instance exposes an HTTP MCP server at /mcp , so Instance A can call tools on Instance B, and Instance B can reply by calling tools back on A. The LLM backend — Claude Code CLI, Codex, or a local model via claw-code-local — acts as an MCP client that can reach these endpoints. The question was how to wire that up over HTTP, and how to handle the fact that LLM responses take tens of seconds and arrive as a stream. quarkus-chat-ui is the bridge that makes this work. Each instance wraps one LLM backend
I'm under 18, broke, and I just designed an open-source AI chip. Here's the full story.
I don't have a team. I don't have funding. I don't have a lab. I have a laptop, an internet connection, and an obsession with chips. This is the story of T1C — Tier 1 Chip — and why I built it. It started with a frustration. Every time I read about AI hardware, it was the same story. NVIDIA charges $30,000 for an H100. TSMC charges millions for a custom fab run. Apple Silicon is beautiful but completely closed. Intel, Qualcomm, AMD — all of them — locked behind NDAs, closed architectures, and billion-dollar relationships. I kept thinking: why does no one make an open-source AI chip that a real person can actually fabricate? Not a toy. Not a demo. A real architecture with real specs, real physics, and a real path to silicon. So I built one. T1C uses Digital In-Memory Computing — D-IMC. Inst
Qodo vs Cody (Sourcegraph): AI Code Review Compared (2026)
Quick Verdict Qodo and Sourcegraph Cody are both AI tools for software teams, but they solve fundamentally different problems. Qodo is a code quality platform - it reviews pull requests automatically, finds bugs through a multi-agent architecture, and generates tests to fill coverage gaps without being asked. Cody is a codebase-aware AI coding assistant - it understands your entire repository and helps developers navigate, generate, and understand code through conversation and inline completions. Choose Qodo if: your team needs automated PR review that runs on every pull request without prompting, you want proactive test generation that closes coverage gaps systematically, you work on GitLab or Azure DevOps alongside GitHub, or the open-source transparency of PR-Agent matters to your organ
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!