Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

A new engineering role, akin to Developer Experience (DevEx), will focus on building the infrastructure, guardrails, and feedback loops necessary to enable AI agents to autonomously and effectively improve systems, such as optimizing a website's conversion rate.

Related Insights

Software engineering is evolving from line-by-line coding to managing fleets of AI agents. This new paradigm resembles a sorcerer casting spells, demanding skills in high-level direction, prompt engineering, and oversight, rather than manual implementation.

Beyond traditional engineers using AI and non-technical "vibe coders," a third archetype is emerging: the "agentic engineer." This professional operates at a higher level of abstraction, managing AI agents to perform programming, rather than writing or even reading the code themselves, reinventing the engineering skill set.

AI isn't eliminating software engineering but fundamentally changing it. Demand for traditional programming is declining, while demand for "AI native" engineers—who manage entire systems from prompt to deployment using agentic tools—has grown 143%. The role is shifting from writing code to orchestrating AI systems at a higher abstraction level.

In an AI-first world, an engineer's role shifts from writing feature code to building leverage. They become akin to staff engineers for AI agents, creating the systems, documentation, and automated tests (the "harness") that empower AI to produce high-quality work autonomously.

Since every AI agent needs human oversight, companies are creating a new specialization. These engineers don't just write code; they manage the company's central "super-agent," ensuring it works correctly, fixing its mistakes, and integrating it into workflows, often by "talking" to it in Slack.

Top-performing engineering teams are evolving from hands-on coding to a managerial role. Their primary job is to define tasks, kick off multiple AI agents in parallel, review plans, and approve the final output, rather than implementing the details themselves.

Building an AI agent is the starting point, not the finish line. The real, ongoing work lies in optimizing its performance and training it on new information. This creates an essential new human-in-the-loop role focused on continuous improvement.

Experienced engineers using tools like Claude Code are no longer writing significant amounts of code. Their primary role shifts to designing systems, defining tasks, and managing a team of AI agents that perform the actual implementation, fundamentally changing the software development workflow.

The debate isn't between manual coding and blindly trusting AI ("vibe coding"). A new discipline, "agentic engineering," is emerging. This involves creating new best practices, security controls, and governance for using AI agents to build software. This structured approach will replace the current era of unchecked individual developer experimentation.

The role of a software engineer is evolving. Instead of manually writing all code, they are increasingly becoming managers of specialized AI agents that write, test, refactor, and deploy code. This moves their focus to a higher level of system design and orchestration.