Up nextGis bi ci topp
Which Jobs Are Most Exposed to AI
Askan wi
GUIDE Sosiete
AI is unlikely to replace software developers as a profession in the near term, but coding assistants are changing which tasks developers do and which skills employers value most.
It matters because well-specified coding work is increasingly delegated to tools, while requirements, design, review and ownership of production systems grow in importance.
AI is unlikely to replace software developers as a profession in the near term, but it is changing which tasks developers spend time on and which skills employers pay for. Coding assistants such as GitHub Copilot (released as a technical preview in 2021), Cursor, Claude Code and ChatGPT can write boilerplate, generate tests, explain unfamiliar code and complete small, well-specified changes. Agentic tools can also work across many files and run commands, which extends what can be delegated. The tasks that shift most have clear specifications and easy verification: routine endpoints, data transformations, test scaffolding, documentation and library migrations. The tasks that shift least involve ambiguity: working out what users actually need, designing systems that will be maintained for years, making security and reliability trade-offs, and debugging failures that span several services. Evidence on productivity is mixed. Vendor and lab studies have reported faster completion on contained tasks, while a 2025 randomized study by METR found that experienced open-source developers working in codebases they knew well took longer with AI tools, even though they believed the tools had sped them up. Gains depend on the task, the codebase and how the tools are used. Hiring trends are hard to attribute to AI alone. Tech hiring slowed after 2022 alongside higher interest rates and post-pandemic corrections, and entry-level roles have been especially competitive. A real concern is that if junior tasks are automated, fewer people gain the experience needed to become senior engineers. A common misconception is that writing code is the whole job. Much of the work is reading code, clarifying requirements, reviewing changes and owning outcomes in production. Skills that grow in value include code review, system design, testing strategy, security awareness, domain knowledge and specifying problems precisely.
Gaañ-gaañu IA yu mag yi ak yu bës bu nekk yépp a ngi aju ci ki xam risk yi ak ki mëna def dara.
Liggéeyukaay ak xam-xam bu ñépp bokk mooy wane ndax politiku kaaraange bu dëgër mën na am ci wàllu politik.
Faram-fàcce yu leer dañuy wàññi li ñuy jàpp ci hype, PR lab, ak tiyaatar bu leerul.
Most careful analyses describe a change in the shape of the job rather than its disappearance, but no one can reliably predict future employment numbers. If software becomes cheaper to build, demand for software may grow, an effect related to the Jevons paradox, though whether that holds here is uncertain. The biggest open question is the entry-level pipeline: companies that stop hiring juniors may face a shortage of experienced engineers later. Developers who combine technical depth with product sense, review discipline and domain expertise are in the strongest position.
A backend developer has an assistant scaffold unit tests for an existing payment module, then uses the saved time to add edge-case tests for refunds and currency rounding that the AI missed.
A team uses an agentic coding tool to upgrade a codebase to a new framework version across dozens of files, with every change going through normal pull-request review and CI.
An engineering manager revises interviews to weight code review and system design exercises more heavily, since candidates can produce basic code with AI.
A junior developer asks an assistant to explain an unfamiliar legacy module, then tests their understanding by making a small change and asking a senior colleague to review it.
Jàppale risku nekk gi ni siyaas fiksioŋ fekk kàttan gi dafay yokk.
Jaxasoo kaaraange produit surface ak jubluwaay ci suufu autonomie bu kawe.
Bàyyi nit ñi xamul làkku Àngle ak ñi xamul làkku Angale, ñu am balluwaay yu baaxul.
Tàqale loraange yi ci produit bi, jëfandikoo bu baaxul, ak risku ñàkka mëna yor / ñàkka méngoo.
Laajteel ban firnde mooy soppi sa xalaat ci kalendriye yi ak tar gi.
Danga taamu balluwaay yu njëkk yi ak jàngat yu fëgër yi moo gën waxtaanu njaay mi.
Xaarandil benn yoonu jëf: liggéey, politik, xaalis, wala xam-xam — du xam-xam kese.
Free newsletter
Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.
One email each weekday. Unsubscribe in one click. We never sell or share your address.
Test yourself
Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.
Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation
AI is unlikely to replace software developers as a profession in the near term, but coding assistants are changing which tasks developers do and which skills employers value most. It matters because well-specified coding work is increasingly delegated to tools, while requirements, design, review and ownership of production systems grow in importance.
The guide argues the job is changing shape: well-specified coding shifts to tools, while judgment-heavy work grows in importance.
Clear specs and easy verification make a task easy to delegate and check. Ambiguous tasks shift least.
The study found a gap between perceived and measured productivity for experienced developers in familiar codebases, showing gains depend on context.
Several economic factors changed at the same time, so a hiring slowdown cannot simply be credited to AI.
Agents act iteratively, using command and test output as feedback, which is why reliable tests make them far more effective.
Weyal di jàng
Tann nañu yeneen njiit ngir topic bii
Up nextGis bi ci topp
Which Jobs Are Most Exposed to AI
Askan wi