> Markdown version of [/videos/608-throwing-off-the-burdens-of-scale-in-engineering?t=1750](https://www.wearedevelopers.com/videos/608-throwing-off-the-burdens-of-scale-in-engineering?t=1750). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Throwing off the burdens of scale in engineering

David Singleton proves massive scale doesn't have to destroy engineering velocity. Discover how Stripe uses sensible architecture, friction logging, and AI to ruthlessly eliminate organizational drag.

- **Speakers:** David Singleton, [Thomas Pamminger](https://www.wearedevelopers.com/@thomas-pamminger)
- **Event:** World Congress 2023
- **Published:** August 11, 2023
- **Duration:** 32:00
- **URL:** https://www.wearedevelopers.com/videos/608-throwing-off-the-burdens-of-scale-in-engineering

## Summary

Scaling an engineering organization often introduces friction, slowing down product velocity and distancing developers from end-users. In this discussion, Stripe CTO David Singleton explores how the global finance infrastructure provider combats the inherent "burdens of scale" by rigorously defending a developer-centric culture. From its origins of making money movement as frictionless as data transfer, Stripe evolved its engineering practices to sustain extremely high availability while continuously shipping to production. Maintaining this momentum requires what Singleton calls a "sensible architecture," separating core financial primitives from fast-moving UI layers so distributed teams can innovate independently. To prevent technical debt from stalling progress, Stripe implements gradual deployment rollouts and treats operational excellence as a continuous learning process to fix entire classes of errors rather than isolated incidents. Furthermore, the engineering culture emphasizes direct user empathy; cross-functional teams observe real-world API adoption and run OODA loops (Observe, Orient, Decide, Act) to iterate on unreleased products alongside end-users. Quality API design also relies on internal domain review groups and exhaustive "friction logging," where engineers record a stream-of-consciousness experience of navigating their own developer tools to identify usage roadblocks. This meticulous attention to workflows scales efficiently through hosted low-code solutions that relieve clients from writing boilerplate while driving revenue uplifts. Singleton also highlights how the judicious adoption of AI, specifically deploying GitHub Copilot to automate test creation and integrating large language models into conversational documentation agents, further accelerates engineer leverage so developers can focus purely on unique business logic.

**Keywords:** engineering team scaling, b2b api design, gradual deployment rollouts, operational excellence, continuous deployment pipelines, software architecture design, technical pace layers, friction logging methodology, cross-functional product teams, ooda loop product iteration, developer onboarding strategies, github copilot for testing, conversational documentation agents, developer experience (dx), low-code payment integration

## Chapters

1. **Building a developer-centric infrastructure for financial services** (00:13) — Eliminating friction for early-stage founders drove the initial product market fit for instant payment onboarding.
1. **Evolving engineering culture across global product teams** (05:33) — Expanding from single payment solutions to embedded financial services requires tight user feedback loops and rigorous operational excellence.
1. **Managing technical debt with sensible software architecture** (10:33) — Defining stable foundational primitives enables isolated product teams to ship code continuously without breaking core monetary flows.
1. **Equipping cross-functional teams with direct user context** (14:38) — Connecting software engineers directly with enterprise users maintains a visceral understanding of the architectural problems being solved.
1. **Ensuring API backward compatibility and robust domain modeling** (17:57) — Subjecting early product designs to internal review groups and friction logging safeguards long-term integration resilience.
1. **Hiring builders and accelerating early developer onboarding** (20:30) — Structured onboarding paths allow new engineering hires to successfully push code to production within their first few weeks.
1. **Providing scale through hosted flows and generative AI** (23:41) — Offering hosted payment interfaces and integrating conversational agents into documentation reduces unnecessary coding for platform users.
1. **Accelerating boilerplate test generation with AI pair programming** (27:57) — Leveraging assistive tools speeds up boilerplate creation and allows developer focus to shift to core application logic.
1. **Powering global commerce for the next generation of AI** (29:10) — Abstracting the complexity of financial systems enables emerging technology platforms to launch new monetization flows and scale globally.

## Related Moments

- [Pivoting product strategy toward platform engineering](https://www.wearedevelopers.com/videos/100122-how-agentic-devops-gave-us-dev-time-back) (from "How Agentic DevOps gave us Dev time back")
- [Transitioning automated delivery pipelines into internal developer platform solutions](https://www.wearedevelopers.com/videos/815-gitops-for-the-people) (from "GitOps for the people")
- [Summarizing the organizational benefits of platform engineering](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) (from "Platform Engineering vs. DevOps Why not both?")
- [Engineering scale and strategic pillars for internal operational efficiency](https://www.wearedevelopers.com/videos/1433-transforming-task-management-integrating-camunda-with-scalable-frontend-solutions) (from "Transforming Task Management: Integrating Camunda with Scalable Frontend Solutions")
- [Platform engineering as the foundation for scaling AI tools](https://www.wearedevelopers.com/videos/100266-ai-won-t-fix-your-engineering-culture) (from "AI Won't Fix Your Engineering Culture")
- [Overview of the developer experience scope at PayPal](https://www.wearedevelopers.com/videos/194-breaking-down-silos-between-design-and-development) (from "Breaking Down Silos Between Design and Development ")

## Related Articles

- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai)
- [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)
- [Why developer experience matters](https://www.wearedevelopers.com/magazine/514-why-developer-experience-matters)

## Related Jobs

- [Principal Software Engineer](https://www.wearedevelopers.com/jobs/ext/267591-principal-software-engineer) at **Twilio**
- [Principal Software Engineer](https://www.wearedevelopers.com/jobs/ext/146806-principal-software-engineer) at **Twilio**
- [Principal Software Engineer](https://www.wearedevelopers.com/jobs/ext/267587-principal-software-engineer) at **Twilio**
- [Principal Software Engineer](https://www.wearedevelopers.com/jobs/ext/115163-principal-software-engineer) at **Twilio**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Senior Software Engineer,Billing](https://www.wearedevelopers.com/jobs/ext/1991843-senior-software-engineer-billing) at **GitHub**