AI Writes the Code Now. What Is Left for Software Engineers?

A few weeks ago, the SF Standard ran a headline that stopped me mid-scroll: "AI Writes the Code Now. What's Left for Software Engineers?" It is the kind of question that makes you stare at your terminal a little differently.

Sam Altman confirmed what many of us suspected — that "AI washing" is now a real phenomenon in layoffs. Companies are using AI as cover for cuts that have more to do with cost restructuring than genuine automation. But the numbers are still sobering. In 2026 alone, there have been 132 tech layoffs affecting over 51,330 people. Jack Dorsey cut 40% of Block's workforce. Salesforce replaced entire customer support divisions with AI agents. The anxiety is real, and it is not irrational.

But here is the part that rarely makes the headlines: a Gartner report found that only about 20% of organizations have actually cut jobs because of AI. Even more telling, Gartner predicts half of those roles will be rehired by 2027 — just under new titles, with different expectations. The work is not disappearing. It is transforming.

I have been building software for over fifteen years. I have seen waves come and go — cloud computing was going to eliminate ops teams, no-code was going to eliminate developers, blockchain was going to eliminate banks. None of those predictions came true as expected. But this wave feels different, not because AI is replacing engineers, but because it is genuinely changing what engineering means.

What AI Can Actually Do Today

Modern AI coding assistants are genuinely impressive at a specific class of tasks. Here is what AI handles well right now:

• Writing boilerplate — CRUD endpoints, data models, API clients, configuration files
• Generating unit tests for well-defined functions with clear inputs and outputs
• Translating between programming languages and refactoring existing code
• Writing documentation and explaining unfamiliar codebases

I use AI coding tools every day, and the productivity gain is real. Tasks that used to take an hour — scaffolding a new service, writing migration scripts, creating test fixtures — now take minutes. But here is the thing: the tasks AI excels at are the ones experienced engineers were already doing on autopilot. AI did not take the hard part of our jobs. It took the boring part.

What AI Still Cannot Do

For all the progress, most of the things AI struggles with are the things that actually make or break a project.

Understanding business context. AI does not know that your platform processes $2M on Black Friday and that a 500ms latency spike costs real money. It does not know your CEO just announced a pivot to enterprise, or that legal flagged GDPR concerns about the new analytics feature. Context is everything in software, and AI has none of it.

Making architectural decisions. Monolith or microservices? PostgreSQL or DynamoDB? These decisions depend on team size, expected scale, budget, existing infrastructure, and a dozen other factors AI cannot weigh. It can describe the tradeoffs. It cannot make the call.

Debugging production incidents under pressure. It is 2 AM. The payment service is returning 500s. Revenue is hemorrhaging. You need to read logs, form hypotheses, check recent deploys, coordinate with the on-call DBA, communicate status updates, and make high-stakes decisions with incomplete information simultaneously. This is a deeply human skill — part technical, part emotional, part political.

Navigating organizational complexity. Half of engineering is not engineering at all. It is figuring out which team owns a service, convincing a skeptical VP that a refactor is worth it, or managing the politics of a reorg. No LLM is attending that meeting for you.

Handling ambiguous requirements. When a PM says "make it faster," what do they mean? The ability to ask the right clarifying questions — and to know when a requirement is underspecified — separates senior engineers from junior ones. AI takes requirements at face value. Good engineers interrogate them.

The Skills That Matter More Than Ever

If AI is handling more of the "writing code" part, engineer value increasingly lies in everything around the code.

System design and architecture thinking. AI can generate components, but someone needs to decide how they fit together, how data flows between them, and how the system behaves under failure. If you cannot whiteboard a system that handles 10x current load or design a migration path between architectures, those are the gaps to fill.

Problem decomposition. The hardest part of software engineering is not writing the solution — it is defining the problem. The ability to take "we need better retention" and decompose it into concrete, buildable chunks is the most valuable skill an engineer can have. Ironically, the better you are at decomposition, the more AI amplifies your output.

Communication and stakeholder management. The best engineers can explain a complex technical decision to a non-technical executive in three sentences, write an RFC that gets buy-in from five teams, and present a realistic timeline without sandbagging. As AI handles more implementation, the ability to communicate about what to build and why becomes the primary differentiator.

Security mindset. AI-generated code introduces subtle vulnerabilities — SQL injection vectors, insecure defaults, improper input validation — that look correct at first glance. Beyond code-level security, AI agents with tool access create entirely new attack surfaces: prompt injection, data exfiltration, privilege escalation. Engineers who instinctively ask "how could this be exploited?" are more essential than ever.

AI orchestration. This is the new meta-skill: knowing when and how to use AI effectively. Which tasks should you delegate? When should you write code yourself because the AI will produce something subtly wrong? How do you review AI-generated code efficiently? Engineers who treat AI as a tool — understanding its strengths, limitations, and failure modes — will outperform both those who refuse to use it and those who blindly trust it.

The New Developer Workflow

The daily rhythm of software development is changing. The shift is from "coder" to "technical director." You receive a ticket, sketch a design, describe the implementation to an AI agent, review what it produces, refine and course-correct, verify the output against your mental model, and ensure test coverage is meaningful — not just green.

You are still deeply technical. But your primary output is no longer the code itself. It is the decisions about what code should exist, how it should work, and whether what was generated actually meets the bar. Engineers who derive their identity from lines of code written per day will struggle. Engineers who derive it from the quality of systems they ship will thrive.

Career Strategies for the AI Age

Go deep, not wide. Generalists who can "do a bit of everything" are exactly the profile most at risk. AI is also a generalist — and it works 24/7 without burnout. Become the person who understands distributed consensus protocols, real-time video processing, or financial compliance systems. Deep specialization is hard to replicate and compounds over time.

Build domain expertise. An engineer who understands healthcare billing, securities trading, or logistics optimization is not just writing code — they are translating complex domain knowledge into software. AI cannot replace that because it does not have the lived experience of working in that domain.

Focus on problems AI cannot solve. Novel architectures for unprecedented problems, cross-system integration spanning organizational boundaries, ethical decision-making under uncertainty — orient your career toward the complex, the ambiguous, and the interpersonal.

The Jobs That Are Growing

While some roles contract, others are expanding rapidly:

• AI Infrastructure Engineering — serving, scaling, and monitoring AI models in production
• ML Ops and AI Platform Engineering — training pipelines, model versioning, feature stores, deployment automation
• Agent Engineering — designing and maintaining autonomous AI agents, including tool design, memory architecture, and safety guardrails
• Security Engineering — AI-specific threats like prompt injection, training data poisoning, and model extraction
• Platform Engineering — internal developer platforms that provide self-service infrastructure and standardized tooling

The common thread: deep technical expertise combined with systems thinking. These roles are about building and maintaining the infrastructure that makes modern software possible.

The Path Forward

The software engineering profession is going through a genuine transformation, and not everyone will navigate it smoothly. Engineers who built their careers on writing basic CRUD apps are facing real headwinds.

But the best engineers have always adapted. When we moved from assembly to high-level languages, the good engineers embraced the new abstractions and built bigger systems. When we moved from bare metal to cloud, they learned distributed systems and built things that were previously impossible. AI is the next abstraction layer — and the scope of what a single engineer can accomplish is expanding dramatically.

The engineers who thrive will see AI not as a replacement but as a lever. They will use it to move faster, think bigger, and focus human energy on the parts that actually require a human — the judgment calls, the creative leaps, the messy communication that turns a good idea into a shipped product.

Craftsmanship does not disappear when the tools improve. It evolves. The carpenter who feared the power saw is long forgotten. The one who mastered it built things that hand tools never could.

The code is changing. The craft endures.