The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org cover art

The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org

The CTO Podcast with Fexingo: Technical Leadership, Architecture, and Engineering Org

By: Fexingo
Listen for free

Lucas and Luna sit down in front of a whiteboard to dissect the decisions that shape technical organizations. Each episode of The CTO Podcast with Fexingo examines a specific engineering leadership challenge — from scaling a microservices architecture without creating a distributed monolith, to managing the cognitive load of a 200-engineer org, to choosing between a monorepo and polyrepo strategy based on team topology. The conversations are grounded in real-world cases: how Etsy restructured its data pipeline after a 2019 outage, why Stripe’s API versioning policy reduces breaking changes, or what Basecamp’s choice of SQLite over PostgreSQL says about product philosophy. Lucas brings the journalistic rigor — citing commit histories, RFCs, and postmortems — while Luna pushes back with the pragmatics of org dynamics, hiring constraints, and technical debt. There are no hot takes, no vendor pitches, no ‘best practices’ without trade-offs. Each episode ends with a specific tension left unresolved: the optimal number of direct reports for a VP of Engineering, the point at which a monolith should be broken apart, or whether a platform team should own the CI/CD pipeline. The listener is a senior engineer, a staff+ IC, or a new CTO who wants to learn from the decisions others have made — without the hype. After an episode, you’ll have a framework, not a checklist, and a clear sense of the questions you should be asking your own team. #CTOPodcast #TechnicalLeadership #EngineeringOrg #SoftwareArchitecture #SystemDesign #EngineeringManagement #Microservices #Monorepo #PlatformEngineering #Scalability #TechDebt #DevOps #Infrastructure #SiteReliability #DistributedSystems #Business #FexingoBusiness #Technology Keep every episode free: buymeacoffee.com/fexingo© 2026 Fexingo. All rights reserved. Economics
Episodes
  • How Stripe Built a Payment Infrastructure for 100 Countries

    How Stripe Built a Payment Infrastructure for 100 Countries
    Jun 29 2026
    In this episode of The CTO Podcast, hosts Lucas and Luna dive into Stripe's architectural journey from a simple payment API to a global infrastructure handling payments in over 100 countries and 135 currencies. They explore how Stripe tackled regulatory complexity, latency, and reliability at scale — from its early days of processing a few thousand transactions to now handling billions of dollars annually. The conversation covers Stripe's core system design, including its use of idempotency keys, event-driven architecture, and a multi-region deployment strategy. Lucas shares insights from Stripe's engineering blog and talks about the trade-offs they made: choosing consistency over availability in payment processing, and building a custom database layer to handle financial transactions. Luna questions how Stripe manages compliance across jurisdictions, and Lucas explains their approach to modular compliance and local data residency. The episode wraps with a reflection on whether Stripe's bet on developer experience over traditional sales-driven growth was the right call. #PaymentInfrastructure #Stripe #GlobalPayments #FinancialTechnology #CTO #EngineeringOrg #SystemArchitecture #API #EventDrivenArchitecture #Idempotency #MultiRegionDeployment #Compliance #Latency #Reliability #TechLeadership #FexingoBusiness #BusinessPodcast #BusinessAndTechnology Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    9 mins
  • How Datadog Rebuilt Its Observability Pipeline for 100 Trillion Events Daily

    How Datadog Rebuilt Its Observability Pipeline for 100 Trillion Events Daily
    Jun 28 2026
    Episode 79 of The CTO Podcast dives into the engineering behind Datadog's core pipeline. Hosts Lucas and Luna unpack how Datadog re-architected its ingestion, processing, and storage layers to handle over 100 trillion events per day by mid-2026. They explore the shift from a monolithic intake to a sharded, stream-oriented architecture, the decision to build custom compression rather than use off-the-shelf codecs, and how the team maintained sub-second query latencies while scaling throughput by 10x over three years. Along the way, they discuss tradeoffs between consistency and availability, the role of probabilistic data structures for sampling, and why Datadog eventually rewrote parts of its query engine in Rust. This episode offers a concrete look at what it takes to keep observability observant when the data never stops growing. Perfect for engineering leaders and senior architects wrestling with scale. #Datadog #Observability #DataPipeline #Architecture #Engineering #Scalability #StreamProcessing #Compression #Rust #QueryEngine #APM #Telemetry #CloudInfrastructure #BigData #SRE #BusinessAndTechnology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    14 mins
  • How Figma Built a Real-Time Multiplayer Design Engine

    How Figma Built a Real-Time Multiplayer Design Engine
    Jun 28 2026
    Lucas and Luna dive into the technical architecture behind Figma's real-time collaboration engine. They explore how Figma moved from a standard web app to a custom multi-user sync layer using Operational Transform and CRDT-inspired techniques, handling hundreds of simultaneous designers editing the same vector without conflict. With specific numbers on latency and data structures, they break down the core challenge: making a complex design tool feel as snappy as a local app while running entirely in the browser. Luna pushes on edge cases like offline editing and conflict resolution, and Lucas explains Figma's migration from WebGL 1 to WebGL 2 for rendering performance. The episode also covers how Figma handled the 'onboarding cliff' when enterprise teams brought 50+ designers into a single file. Listeners will learn one concrete thing: why Figma chose to build its own implementation instead of using existing CRDT libraries, and the trade-offs involved. #Figma #RealTimeCollaboration #CRDT #OperationalTransform #WebGL #BrowserEngine #DesignTools #Multiplayer #VectorGraphics #ConflictResolution #Latency #Architecture #Engineering #BusinessAndTechnology #TechnicalLeadership #FexingoBusiness #BusinessPodcast #CTOPodcast Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    10 mins
adbl_web_anon_alc_button_suppression_t1
No reviews yet