What happened
Snowflake held the inaugural CTO Circle event during Snowflake Summit 2026 in San Francisco, bringing together more than 350 CTOs from financial services, telecommunications, retail and technology to discuss how to build AI-native engineering organizations. The discussion centered on three themes: using AI in production, balancing velocity and risk, and redesigning engineering teams for AI.
Why it matters
There is no established playbook for building an AI-native engineering organization, and these conversations typically remain within individual companies. The event surfaced concrete lessons from leaders navigating the same transformation—including how Snowflake increased its internal developer Net Promoter Score by more than 30 points in 18 months, resulting in a 4:1 ratio of satisfied to dissatisfied developers. The insight that treating developers as customers and institutionalizing proven AI workflows (rather than simply deploying tools) creates competitive advantage applies across industries.
What to watch
The discussion revealed a shift in how success is measured: away from who generates the most code or consumes the most tokens, and toward who builds the simplest, fastest, and most effective engineering system. Leaders also emphasized that moving to AI-native practices requires full organizational commitment—what one speaker called "burning the boats"—rather than creating isolated AI product teams.
Summaries like this, in your inbox every morning.
The inaugural CTO Circle reveals a maturation in how large organizations approach AI adoption. Rather than treating AI as a point solution—coding assistants that make developers faster—the discussion focuses on fundamental organizational redesign. The pattern that emerges across multiple speakers is that technical capability alone is insufficient; what matters is embedding AI into the processes, decision-making, and team structures of the entire engineering organization.
Snowflake's own transformation illustrates this principle. By treating developers as customers and applying product management discipline to developer experience, the company achieved measurable results: a 30-point improvement in Net Promoter Score and a shift from majority dissatisfaction to a 4:1 satisfaction ratio. The insight that moved beyond simple tool deployment is the concept of progression—adoption, mastery, and optimization—where competitive advantage comes from institutionalizing workflows, not from the tools themselves. When every developer has the same AI assistant but only some know the proven patterns, the difference in output becomes dramatic.
A second theme is that velocity without operational foundation creates risk. As AI agents make more decisions and interact with more systems, observability and data architecture become critical. Netflix's experience shows that AI reliability depends on unified context—not just better data, but the ability for AI to reason over semantics, ontologies, relationships, and business context. Organizations that keep telemetry fragmented across disconnected systems constrain what AI can achieve, whereas unified data foundations enable both humans and AI to reason effectively.
The tension between speed and governance runs through the discussion. One speaker described the required mindset shift as "burning the boats"—organizations must commit fully to AI-native practices rather than running parallel centralized AI teams. Yet another emphasized that in regulated industries, speed only creates value when matched with governance and trust. The resolution appears to be that the fastest organizations invest in shared platforms and operational discipline that allow rapid experimentation without compromising reliability.
For example, today's edition would include:
AI-summarized, only the topics you pick: one digest a day via Email, LINE, or Slack.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
