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

Fexingo
  • 0.0 (0)
  • Business
  • Updated Daily

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

  1. 8h ago

    How Palantir Rebuilt Its Gotham Platform for AI-Native Decision Making

    In this episode, Lucas and Luna dive into the architecture behind Palantir's Gotham platform, focusing on its recent overhaul to integrate large language models and real-time data pipelines. They explore how Palantir rebuilt its ontology layer to support AI-native decision making, handling over 10 million daily queries for defense and commercial clients. The discussion covers the shift from batch to streaming data, the embedding of LLMs into core workflows, and the engineering trade-offs between latency and accuracy. Specific numbers include a 40% reduction in decision latency and a 3x increase in data ingest throughput. Lucas brings his usual concrete detail, while Luna challenges the scalability and security implications. A must-listen for anyone interested in the intersection of AI and enterprise architecture. #Palantir #Gotham #AI #EnterpriseArchitecture #LLM #RealTimeData #Streaming #DecisionMaking #Ontology #DataPipelines #DefenseTech #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #CTOPodcast #TechLeadership #EngineeringOrg #Architecture Keep every episode free: buymeacoffee.com/fexingo

    10 min

  2. 21h ago

    How DoorDash Rebuilt Its Logistics Engine for 25 Million Daily Orders

    In this episode, Lucas and Luna dive into DoorDash's 2025–2026 architecture overhaul of its logistics engine to handle 25 million daily orders across 7,000 cities. We walk through the key decision to move from a centralized dispatch service to a sharded, event-driven system with per-market autoscaling. Lucas explains how the team used Kafka for order lifecycle events, built a custom geo-partitioning layer using S2 cells, and introduced speculative dispatching to reduce average delivery wait times by 12%. Luna questions the tradeoffs around consistency guarantees and how DoorDash handles peak surges like Super Bowl Sunday. A concrete look at what it takes to scale real-time logistics at global food-delivery scale. #DoorDash #LogisticsEngine #ArchitectureOverhaul #EventDriven #Kafka #GeoPartitioning #S2Cells #SpeculativeDispatching #Scalability #RealTimeSystems #FoodDelivery #TechLeadership #EngineeringOrg #CTOPodcast #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #SystemDesign Keep every episode free: buymeacoffee.com/fexingo

    8 min

  3. 1d ago

    How Slack Rebuilt Its Real-Time Messaging for 10 Million Concurrent Connections

    In this episode, Lucas and Luna break down how Slack re-architected its real-time messaging layer to handle 10 million concurrent connections. They walk through the migration from a single-room event bus to a sharded, multi-region WebSocket mesh; the decision to decouple presence from message delivery; and the surprising bottleneck that emerged from emoji reactions. Along the way, they discuss tradeoffs around client-side backpressure, the cost of preserving message ordering across shards, and why Slack ultimately chose to write its own load balancer rather than use a commercial alternative. If you're building any kind of real-time system — chat, notifications, live collaboration — this episode has one concrete lesson you can borrow. #Slack #RealTimeMessaging #WebSocket #BackendArchitecture #DistributedSystems #ConcurrentConnections #Scalability #SystemDesign #EngineeringLeadership #CTO #TechPodcast #Infrastructure #EventBus #LoadBalancing #PerformanceEngineering #Business #Technology #FexingoBusiness Keep every episode free: buymeacoffee.com/fexingo

    12 min

  4. 1d ago

    How Shopify Rebuilt Checkout for One-Click Conversions

    Lucas and Luna examine how Shopify's engineering team completely rearchitected its checkout flow to support one-click conversions across 1.7 million merchants. They break down the architectural shift from a monolithic Rails app to an event-driven, headless checkout service — and the surprising trade-offs around latency, fraud detection, and developer experience. The hosts walk through how Shopify handled state management across sessions, payment gateways, and third-party apps, and why the team chose to isolate checkout as its own service rather than incrementally refactor. A concrete look at scaling a critical transaction path without breaking the merchant experience. #Shopify #CheckoutArchitecture #OneClickCheckout #EventDriven #Microservices #HeadlessCommerce #Rails #PaymentGateways #StateManagement #TransactionScaling #EngineeringOrg #Ecommerce #LatencyOptimization #DevEx #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheCTOPodcast Keep every episode free: buymeacoffee.com/fexingo

    12 min

  5. 2d ago

    How Netflix Rebuilt Its Encoding Pipeline for 4K HDR Streaming

    Episode 105 of The CTO Podcast dives into Netflix's massive re-architecture of its video encoding pipeline to support 4K HDR streaming at scale. Lucas and Luna break down how Netflix moved from a one-size-fits-all encoding approach to a per-title optimization model that saved 20% bandwidth while improving quality. They discuss the technical trade-offs—per-scene encoding decisions, the shift from CPU to GPU-based processing, and the operational challenge of encoding over 10,000 titles daily. The conversation also explores how this architecture paved the way for adaptive bitrate streaming and the open-source tools Netflix contributed to the community. A behind-the-scenes look at the engineering that powers your favorite shows. #Netflix #VideoEncoding #4KHDR #StreamingArchitecture #CTO #TechLeadership #PerTitleEncoding #GPUEncoding #AV1 #OpenSource #Business #Technology #FexingoBusiness #BusinessPodcast #EngineeringOrg #MediaEngineering #Codec #BandwidthOptimization Keep every episode free: buymeacoffee.com/fexingo

    10 min

  6. 2d ago

    How Stripe Rebuilt Its Payment Infrastructure for 100 Million API Calls a Day

    In this episode, Lucas and Luna dig into Stripe's 2025 architecture overhaul to handle 100 million API calls per day. They explore the specific bottlenecks—from database contention in PostgreSQL to the migration toward a new ledger service and idempotency keys at scale. Lucas explains how Stripe split its monolithic Payments monolith into domain-oriented services, the trade-off between strong consistency and availability, and why they chose a custom event-sourcing layer over off-the-shelf solutions. Luna challenges the cost of such a rebuild, and they weigh the 'if it was worth it' bet. A technical deep dive for engineers and leaders building at scale. #Stripe #PaymentsInfrastructure #APIArchitecture #EventSourcing #DomainDrivenDesign #PostgreSQL #LedgerService #Idempotency #Scalability #Microservices #FinancialSystems #EngineeringLeadership #CTOPodcast #FexingoBusiness #BusinessPodcast #SystemDesign #TechArchitecture #100MillionAPI Keep every episode free: buymeacoffee.com/fexingo

    12 min

  7. 3d ago

    How Spotify Rebuilt Its Recommendation Engine for Podcasts

    In episode 103 of The CTO Podcast, Lucas and Luna explore the architectural overhaul behind Spotify's podcast recommendation system. They break down how Spotify moved from a music-first collaborative filtering model to a neural network that understands spoken content, processes 500 million daily listening events, and serves 100 million podcast listeners. The conversation covers the shift from sparse audio features to NLP embeddings, the decision to abandon user-item matrices for two-tower neural nets, and how the team solved cold-start problems for new shows. Lucas explains why podcast recommendations require fundamentally different engineering than music, and Luna challenges whether personalization trades off against serendipity. A focused look at one of the most complex recommender systems in the world. #Spotify #PodcastRecommendation #RecommendationEngine #MachineLearning #NeuralNetworks #NLP #AudioEmbeddings #CollaborativeFiltering #ColdStartProblem #Personalization #TwoTowerModel #Technology #Business #FexingoBusiness #BusinessPodcast #CTOPodcast #TechLeadership #EngineeringArchitecture Keep every episode free: buymeacoffee.com/fexingo

    11 min

  8. 3d ago

    How Stripe Rebuilt Its Payment Infrastructure for 100 Million API Calls a Day

    In this episode, Lucas and Luna dive into Stripe's architectural overhaul of its core payment processing pipeline to handle over 100 million API calls per day. They explore the key decisions: migrating from a monolithic Rails app to a service-oriented architecture, the introduction of a custom idempotency layer, and how Stripe used deterministic simulation testing to ensure correctness at scale. Lucas breaks down the trade-offs between consistency and availability in payment systems, and Luna questions the operational complexity of managing hundreds of microservices. The conversation also touches on Stripe's cultural approach to reliability—embedding SRE principles directly into development teams rather than centralizing them. No hype, just concrete engineering details from one of the most demanding production environments in fintech. #Stripe #PaymentInfrastructure #APIScale #Microservices #Idempotency #DeterministicSimulation #SRE #PaymentProcessing #Fintech #SystemArchitecture #Scalability #Reliability #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #CTOPodcast #TechnicalLeadership #EngineeringOrg Keep every episode free: buymeacoffee.com/fexingo

    11 min
See All (109)

About

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

Information