Every Eng a CTO: Technical Leverage in the Agentic Organization Keynote

A CTO's job is to make difficult technical and organizational decisions, building and tuning up an engine that in turn creates code, infrastructure, and other valuable technical outputs. A good CTO optimizes processes, makes hard calls, and occasionally jumps down to ground level to put out a fire.

More and more, the work of ground-level engineers is growing to resemble the description above. A capable engineer in 2026 is increasingly managing a reproducible process that creates infrastructure. The AI-assisted engineer orchestrates agents, moves quickly from decision point to decision point, and develops metainfrastructure. (And, yes, whips out the IDE, text editor, or terminal to put out the occasional agent-generated fire.) In short, the modern agent-assisted engineer is looking a lot like ... a CTO.

In this low-BS talk, we'll consider the transformations we're seeing at organizations aggressively adopting not just AI-assisted coding, but also infrastructure that incorporates AI. We'll outline three natural stages of agentification (experiment, pipeline, framework) and present a case study from Chainguard's development and adoption of an agentic framework for reducing drift.

We'll then think hard about leverage within an organization and how AI changes organization dynamics, such as by moving engineering time from problems to metaproblems. We'll look at a rough typology of AI adoption among engineers and consider that engineers slow to adopt AI might still be a critical asset. We'll also outline both milestones and pitfalls for your own organization's agentic journey. Come for the hot takes about CTOs, engineers, and organizational leverage, stay for the memes.

https://javascript-conference.com/generativeai/agentic-engineering-technical-leverage/