AIToday
AI Business & IndustrySnowflake AI BlogPublished: Aug 7, 2026, 19:00 JST

CTO Circle brings 350 engineering leaders together to share lessons on building AI-native organizations

CTO Circle brings 350 engineering leaders together to share lessons on building AI-native organizations

3 Key Points

  1. What happened

    Snowflake hosted 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 engineering organizations are being redesigned for AI. The discussion centered on three themes: using AI in production, balancing velocity and risk, and designing engineering teams for AI.

  2. Why it matters

    Engineering leaders face uncertainty about how to structure teams and invest in AI as foundation models improve. The event provided a rare peer-to-peer forum to compare what works in production rather than remain siloed within individual companies. Snowflake's own experience—increasing internal developer Net Promoter Score by more than 30 points in 18 months—shows that treating developers as customers and institutionalizing successful AI workflows drives measurable productivity gains and competitive advantage.

  3. What to watch

    Leaders emphasized that sustainable AI adoption requires three stages (adoption, mastery, and optimization) and that speed only creates value when paired with governance and reliable infrastructure. Organizations must move beyond coding assistants to redesign how teams build products, make decisions, and incorporate AI as foundational to business operations.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The CTO Circle event reflects a broader challenge facing engineering leadership: there is no established playbook for building AI-native organizations, and competitive pressures have kept these conversations largely private within individual companies. Snowflake's decision to convene this peer forum addresses a real gap—engineering leaders need to compare what works in production and challenge assumptions about team structure, investment priorities, and risk management as AI becomes embedded throughout the software development lifecycle.

The three themes that emerged from the discussion—AI in production, velocity-and-risk balance, and team design—represent a maturation of AI adoption beyond early coding assistants. Snowflake's own transformation demonstrates that treating developer productivity as a customer problem, then institutionalizing successful workflows into organizational knowledge, creates measurable competitive advantage. This approach differs fundamentally from simply deploying another AI tool; instead, it emphasizes depth of usage, mastery, and optimization as the stages through which organizations must progress. Similarly, Jeremy Burton's argument that context (semantics, ontologies, APIs, business relationships) matters as much as data quality, and Aditya Gaur's example of Netflix's investment in data architecture before AI agents, underscore that production success depends on foundational infrastructure decisions, not AI models alone. The tension between velocity and governance—highlighted by Chris Kozlowski's emphasis on matched speed and control in regulated environments—signals that the organizations moving fastest are those investing deliberately in both innovation and reliability.

FAQ
What were the three main themes discussed at CTO Circle?
The discussion converged around using AI in production, balancing velocity and risk, and designing engineering teams for AI. Leaders explored what breaks and scales in production, how to invest in architectures that enable both speed and reliability, and how to restructure teams to capitalize on AI capabilities.
How did Snowflake improve developer productivity with AI?
Snowflake treated developer productivity as a product, interviewing engineers to understand friction points and establishing baseline metrics before running experiments. The approach increased internal developer Net Promoter Score by more than 30 points in 18 months, resulting in a 4:1 ratio of satisfied to dissatisfied developers, and demonstrated that the highest leverage comes from depth of usage and mastery of tools at scale—progressing through adoption, mastery, and optimization stages.
What does 'burning the boats' mean in the context of AI adoption?
CTO Caitlin Colgrove at Hex used this phrase to describe the need for organizations to commit fully to becoming AI-native by restructuring how teams build products, make decisions, and incorporate AI into everyday work, rather than maintaining a partially AI-native approach. Hex disbanded its centralized AI product team and distributed AI responsibility across every product team to embed AI capabilities throughout the product and avoid organizational bottlenecks.
Snowflake AI BlogRead Original Article

Get the latest AI Business & Industry news every morning

For example, today's edition would include:

  • Meta taps CJ Desai to lead new enterprise AI unitSiliconANGLE AI · 10m ago
  • 1Password ties AI agent access to individual tasksSiliconANGLE AI · 10m ago
  • ServiceNow's Bhakti Pitre: rogue AI agents need risk-based kill switchSiliconANGLE AI · 10m ago

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

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.

Questions and answers are published on this page.

Related Articles

Next articleHSP GRUPPE reports 84% weekly ChatGPT usage