Will AI Replace Software Engineers? Durable and Exposed Skills

Will AI replace software engineers? In April 2026, TrueUp counted more than 67,000 open software engineering positions — the highest figure in three years. Year to date in 2026, more than 128,000 tech workers have been cut, with the losses falling heaviest on mid-level managers and entry-level coders. Salesforce froze new engineering hiring for FY2026 and said it would lean on AI coding agents instead. OpenAI is doubling its headcount to 8,000 by the end of 2026, most of that in engineering and research, and Google is rehiring 20% as boomerang workers.

Read as one story about headcount, that is noise. Read as a question about skills, it resolves cleanly. The useful question is not whether AI will replace software engineers or any other technical role. It is which skills inside the role hold their value, and which ones move.

We put that question to approximately 2.85 million active job descriptions across nine core engineering, data and ML roles, covering June 2025 to June 2026 in Draup's role-filtered index. We used our upcoming Curie Deep Research capability, which goes live on the Draup platform shortly, to write this report. One structural pattern held across all nine roles without exception: the skills commanding the highest posting frequency and the fastest growth are those requiring judgment, accountability and system-level reasoning. Not those requiring typing.

Will AI replace software engineers? The durability test

The classification underneath this report is a reasoned judgment about the work, not a label the platform emits. A skill tends to stay durable when it requires judgment under ambiguity — deciding what to build and what "good" means; system-level reasoning about trade-offs across scale, cost, security and failure; accountability for whether something is correct, safe and fit to ship; or human context in the form of domain depth, communication and stakeholder influence.

A skill tends to shift when it is routine and repeatable, easy to specify well enough that a clear prompt produces a usable first draft, recall-based rather than reasoning-based, or now self-serviceable by non-specialists using AI and no-code tools. AI raises the floor on routine output, so human value moves up the stack toward design, review and orchestration. The role does not disappear. Its centre of gravity moves.

The market is growing while its composition changes

Total active postings across the nine roles grew year over year. Software Engineer remains the largest role by raw volume — the Software Engineer and Senior Software Engineer titles together account for over 111,000 postings — and the single most-posted title in Software Engineer, Data Engineer and DevOps each exceeds 40,000 active postings. This is an expanding market.

Volume growth masks the compositional shift underneath it. The fastest-growing titles inside each role are not the generalist variants. "AI Software Engineer" is up 57% year over year at 1,297 postings. Staff Software Engineer, Principal Software Engineer, Staff Machine Learning Engineer, Principal Data Engineer, ML Ops Engineer and Data Governance Analyst are all outgrowing their generic counterparts. The market is not hiring more of the same. It is hiring more of the harder, more senior, more specialised version of each role, and it is quietly deprioritising the junior execution layer that AI is absorbing.

What is durable and what is exposed, role by role

• Software Engineer — Durable core: Architecture, debugging, code-review judgment · Most exposed to change: Hand-writing routine code; syntax recall
• Frontend Engineer — Durable core: Accessibility, performance, UX judgment · Most exposed to change: Boilerplate UI and CSS; pixel-pushing
• Backend Engineer — Durable core: API and data design, security, scalability · Most exposed to change: CRUD and glue code; standard tests
• DevOps / SRE — Durable core: Reliability strategy, incident judgment · Most exposed to change: Hand-written IaC and config; log triage
• QA / Test Engineer — Durable core: Test strategy, exploratory testing · Most exposed to change: Writing test cases; manual regression
• Data Engineer — Durable core: Data modeling, reliability, governance · Most exposed to change: Routine ETL, connector and SQL code
• Data Analyst — Durable core: Problem framing, storytelling, domain depth · Most exposed to change: Routine SQL and dashboards; ad-hoc pulls
• Data Scientist — Durable core: Problem framing, statistics, causal rigour · Most exposed to change: AutoML-able modeling and tuning
• ML Engineer — Durable core: MLOps, AI-systems and software rigour · Most exposed to change: Hand-written model and training boilerplate

The frequency data puts weight behind the classification. For software engineers, Debugging appears in 166,851 postings, Systems Design in 100,687, Distributed Systems in 93,732 and Secure Coding in 19,177, while Unit Testing (77,250) and Technical Documentation (51,534) sit on the exposed side. Application Development and Maintenance accounts for 62% of the software engineering role's volume and is the highest-automation-risk workload within that role.

Data Engineer shows the same split in a different vocabulary: Data Quality (106,975), Data Modeling (85,110) and Data Governance (67,320) are durable, while SQL (243,456), ETL (165,151) and connector and orchestration boilerplate are exposed. Data Analyst is the most disrupted of the data roles — SQL (182,810), Power BI (131,115) and Tableau (85,119) are precisely the work that business users now self-serve — and PwC, McKinsey, EY, KPMG and Deloitte have all been cutting analyst and support roles as they push AI adoption. Gartner expects some of those reductions to reverse by 2027 under different job titles.

AI fluency is now a baseline, not a differentiator

GitHub Copilot, Cursor and Claude are named explicitly in employer requirements at scale. In the Software Development Engineer role alone, GitHub Copilot appears in 22,961 postings, Cursor in 17,905 and Claude in 12,860. Across all nine roles, those three tools together exceed 60,000 postings. They show up in QA, in DevOps, in data engineering and in data science, not only in software.

Employers have stopped asking whether engineers use AI tools. They are asking whether engineers can direct them well — specify intent, review the output, and own the security and correctness of what ships. Any organisation still treating AI tool proficiency as a nice-to-have is already hiring below the market baseline.

The pay data prices durability independently

We did not use compensation as an input to the durability classification. It nonetheless lines up almost perfectly. Median US base pay runs from Machine Learning Engineer at $166,764, through Data Scientist ($148,922), DevOps Engineer ($142,433), Data Engineer ($135,847), Software Development Engineer ($135,650) and Backend Engineer ($133,386), down to Frontend Engineer ($116,270), Quality Assurance Engineer ($99,647) and Data Analyst ($88,140). Roles with the highest proportion of judgment-intensive, accountability-heavy, system-level work command the highest pay. That is the market pricing durability in real time — independent validation of the framework.

Two gaps in that table are worth acting on directly. The $22,553 spread between Data Analyst and a governance-oriented analyst role argues for a formal Data Governance Analyst track with its own levelling and compensation. The $17,842 spread between Data Scientist and ML Engineer argues for an internal MLOps and production-AI systems track, or you will lose senior data science talent to competitors who offer the title.

What to change first

The deepest change is to the early-career path, because the routine tasks juniors once cut their teeth on are the most automated ones. Give new hires code-review ownership, test strategy and architecture exposure from month three rather than year three. A junior pipeline built on task execution will produce talent that is partially obsolete by mid-level.

Alongside that, three moves are worth making inside ninety days. Write named AI tools into technical job descriptions as explicit hiring criteria. Create the formal Data Governance Analyst track described above. Prioritise Data Engineer hiring and retention above other data roles, because AI initiatives stall on data infrastructure gaps far more often than on model quality. Defining "AI Software Engineer" inside your own job architecture before title inflation defines it for you, and building the internal MLOps and production-AI systems track for senior data scientists, belong to the next three to twelve months rather than the first ninety days. Further out still, add AI safety and responsible AI evaluation to senior ML and data science requirements — Responsible AI already appears in 1,910 data scientist and 1,618 ML engineer postings, and it is growing.

The underlying instruction is simple to state and hard to execute. Stop organising technical talent around the tasks people perform today, and start organising it around the capabilities that stay valuable when AI can perform those tasks itself. AI is not replacing software engineers or eliminating technical work. It is redistributing value inside it, and the redistribution is already visible in what employers write down and what they pay.