Engineering Enablement by DX
Lessons from Twilio’s multi-year platform consolidation
· Summarized
Key takeaways
- Migration processes are complex and require a focus on both technical and human aspects.
- AI plays an essential role in modernization but needs to be approached pragmatically.
- Developer experience should be a priority, treated as a product to encourage voluntary adoption.
- Evaluation of AI tools should consider costs and scalability, ensuring they fit organizational needs.
- Cultural change is crucial in adapting to new technologies, including personalized support systems.
- A balance between tool standardization and creative experimentation with AI is necessary for future success.
Summary
Navigating Platform Consolidation and Complexity
Jesse Adametz discusses the challenges Twilio faces in its multi-year platform consolidation, especially after acquiring multiple companies. He emphasizes the non-linear nature of integration and the importance of human factors such as advocacy, training, and alignment within teams. The conversation highlights that every migration is complex and requires both technical and cultural shifts.
The Role of AI in Modernization
AI is seen as a critical element in Twilio's modernization efforts. Jesse expresses a grounded approach where AI will not write code automatically but help automate parts of the modernization process. There are discussions about leveraging AI tools for better efficiency and enabling easier migrations using frameworks.
Developer Experience as a Product
The podcast delves into the idea that developer experience should be treated as a first-class product. Jesse argues that to foster voluntary adoption methods, platforms need to demonstrate value, feedback loops, and advocate for change rather than impose it as a mandate. His approach emphasizes improving ease of use for developers.
Evaluation of AI Tools and Adoption
Throughout the episode, Jesse highlights the multitude of AI tools available and the importance of evaluating them based on scalability and value to the organization. He discusses insider strategies for tool adoption, addressing costs associated with usage, and the reliability aspects that Twilio requires.
Cultural Shifts and Support Systems
Jesse addresses the need for cultural shifts within engineering teams to adapt to new technologies. He suggests that internal support capabilities for developers should mirror those provided to external customers, emphasizing the importance of a single point of contact for assistance and maintaining high-quality documentation.
The Future of Platform and AI Integration
The final segment discusses the future of Twilio's platform, advocating for a balance between experimentation with AI and standardization. Jesse envisions a future where platform teams leverage AI for efficiency and ensure that innovations do not overwhelm the engineering teams.
Sponsors
- The AI Measurement Framework · which offers research-based metrics for tracking AI adoption, measuring real impact, and making smarter investment decisions. You can learn more about the AI measurement framework and how to use it by visiting.
- Experian · helping companies like booking.com and others with AI adoption.
- Twilio · the core platform this episode revolves around.
- Kubernetes · discussed as a tool that may not fit all of Twilio's workloads.
- Copilot · one of the AI tools being evaluated.
- Claude Code · discussed as one of the new wave tools.
- Windsurf · mentioned as a tool comparable to AI tools.
- Cursor · another tool reviewed in the conversation.
- Bedrock · used for evaluating AI models and tools.
- Transact-SQL · referenced in relation to database experience and engineering skills.
Show notes
In this episode, host Laura Tacho speaks with Jesse Adametz, Senior Engineering Leader on the Developer Platform at Twilio. Jesse is leading Twilio’s multi-year platform consolidation, unifying tech stacks across large acquisitions and driving migrations at enterprise scale. He discusses platform adoption, the limits of Kubernetes, and how Twilio balances modernization with pragmatism. The conversation also explores treating developer experience as a product, offering “change as a service,” and Twilio’s evolving approach to AI adoption and platform support.
Where to find Jesse Adametz:
• LinkedIn: https://www.linkedin.com/in/jesseadametz/
• X: https://x.com/jesseadametz
• Website: https://www.jesseadametz.com/
Where to find Laura Tacho:
• LinkedIn: https://www.linkedin.com/in/lauratacho/
• Website: https://lauratacho.com/
• Laura’s course (Measuring Engineering Performance and AI Impact) https://lauratacho.com/developer-productivity-metrics-course
In this episode, we cover:
(00:00) Intro
(01:30) Jesse’s background and how he ended up at Twilio
(04:00) What SRE teaches leaders and ICs
(06:06) Where Twilio started the post-acquisition integration
(08:22) Why platform migrations can’t follow a straight-line plan
(10:05) How Twilio balances multiple strategies for migrations
(12:30) The human side of change: advocacy, training, and alignment
(17:46) Treating developer experience as a first-class product
(21:40) What “change as a service” looks like in practice
(24:57) A mandateless approach: creating voluntary adoption through value
(28:50) How Twilio demonstrates value with metrics and reviews
(30:41) Why Kubernetes wasn’t the right fit for all Twilio workloads
(36:12) How Twilio decides when to expose complexity
(38:23) Lessons from Kubernetes hype and how AI demands more experimentation
(44:48) Where AI fits into Twilio’s platform strategy
(49:45) How guilds fill needs the platform team hasn’t yet met
(51:17) The future of platform in centralizing knowledge and standards
(54:32) How Twilio evaluates tools for fit, pricing, and reliability
(57:53) Where Twilio applies AI in reliability, and where Jesse is skeptical
(59:26) Laura’s vibe-coded side project built on Twilio
(1:01:11) How external lessons shape Twilio’s approach to platform support and docs
Referenced:
Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account