Building a Global Engineering Team and AI Agents with Netlify CTO Dana Lawson

Building a global engineering team (plus AI agents) with Netlify

Netlify CTO Dana Lawson manages a lean R&D team of approximately 50 employees that currently powers 5% of the internet. This globally distributed organization operates as “controlled chaos,” prioritizing a written culture to bridge time zones and languages. The team is now leveraging AI Agent Runners to automate live pull requests directly from natural language prompts.

Why This Matters

Technical leadership frequently struggles with the friction between theoretical organizational frameworks and the reality of global execution. Dana Lawson argues that maintaining 5% of the web requires moving beyond rigid models like the “Spotify model” in favor of autonomous, self-organizing teams that balance rapid innovation with the operational burden of legacy monoliths and massive Mongo clusters. In a globally distributed environment, success depends on a radical written culture and the strategic use of AI to supplement human expertise rather than replace it.

Key Insights

• Netlify maintains 5% of the internet with a lean R&D organization of only 40 to 50 employees (Source: Dana Lawson, 2026).
• Google’s Site Reliability Engineering book (2012) predicted self-healing machines, a concept Netlify is now realizing through AI agent runners.
• The engineering team utilizes AI note-takers to maintain a “written culture,” which is essential for bridging global time zones and multiple spoken languages.
• Operational reliability is prioritized over raw speed in polyglot environments, often choosing proven tools over nascent technologies like Rust for core services.
• Netlify’s Agent Runners allow users to trigger live pull requests and site changes via natural language chat, lowering the technical barrier for builders.
• Technical debt is addressed as a persistent reality, with the team managing multiple monoliths and large-scale Mongo clusters within a 10-year-old infrastructure.

Practical Applications

• Use case: Implementing AI Agent Runners to allow non-technical stakeholders to preview and commit site changes via chat. Pitfall: Allowing “decision by committee” to stall execution in lean, high-tempo startup environments.
• Use case: Utilizing Slack public channels for “controlled chaos” transparency across global time zones. Pitfall: Relying on private DMs, which creates expertise silos and leads to repetitive double-work in distributed teams.
• Use case: Cross-training engineers in specialized languages like Rust to ensure operational coverage and prevent single points of failure. Pitfall: Over-scheduling developers for 43 hours in a 40-hour week, which eliminates the cognitive space required for innovation.

References:

• https://stackoverflow.blog/2026/03/19/building-a-global-engineering-team-netlify/