Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations

Many engineering teams build internal developer platforms that nobody adopts. In this episode, Lucas and Luna unpack why — and what one team did differently. They walk through a real case: a mid-size SaaS company whose API platform team spent eight months building a developer portal with every feature the team could imagine, only to find that six months after launch, fewer than 20 percent of servi...

In this episode, Lucas and Luna discuss how an internal developer platform (IDP) can dramatically reduce deployment times and cognitive load for engineering teams. Lucas shares a specific case study from a mid-stage startup that built a lightweight IDP using backstage and custom scaffolder templates, cutting average deploy time from 45 minutes to 8 minutes and reducing onboarding from two weeks to...

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into a real-world case study of how a mid-sized SaaS team reduced their AWS bill by 40% over six months — without sacrificing latency or developer velocity. They unpack the specific tactics that worked: from right-sizing instances and committing to reserved capacity, to implementing a 'cost per feature' tracking process that made...

Lucas and Luna break down how a CTO at a mid-stage SaaS company used lightweight Request for Comments (RFCs) to eliminate decision debt. They walk through a real example from a team that was paralyzed by recurring architecture debates until they enforced a written proposal process. The hosts discuss why RFCs force clarity, how to keep them short (under 500 words), and why the best RFCs include a c...

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into a case study of a mid-stage SaaS company that slashed its mean time to acknowledge (MTTA) from 12 minutes to under 4 minutes — a 70% improvement — without adding headcount or buying expensive tools. They break down the three specific changes the team made: redesigning the on-call rotation to use a 'follow-the-sun' model, imp...

Lucas and Luna break down why traditional on-call rotations damage engineering culture and what to do instead. Using concrete examples from a mid-sized SaaS company that cut burnout by 40 percent and increased incident response speed by 30 percent by switching to a dedicated response team model. They discuss the hidden costs of interrupt-driven work, the myth of equal rotation, and how to build an...

Episode 23 of Tech Leadership with Fexingo dives into the surprisingly high-stakes world of API style guides. Lucas and Luna discuss why a well-crafted guide is more than just naming conventions — it's a tool for reducing cognitive load, speeding up onboarding, and preventing production incidents. They break down specific examples: the difference between RESTful and RPC-style endpoints, the hidden...

Episode 22 of Tech Leadership with Fexingo explores the concept of a congestion budget for engineering teams — a powerful tool to prevent bottlenecks before they form. Lucas and Luna unpack a real case: a mid-stage fintech company that used congestion budgets to cut deployment wait times by 60 percent and unblock feature velocity. They discuss how to measure congestion using cycle time, work-in-pr...

In this episode, Lucas and Luna explore the concept of a congestion budget for engineering teams—inspired by traffic flow theory. They discuss how a $12 million Series A startup used a congestion budget to slash deployment time from 45 minutes to 12 and reduce rollbacks by 60 percent. The conversation covers the three metrics of a congestion budget: WIP limits, queue depth, and batch size. Lucas s...

Lucas and Luna explore the story of a single senior engineer who transformed a struggling team's deployment pipeline from a painful two-hour manual process to a fully automated ten-minute rollout. They discuss the cultural resistance, the decision to let one person redesign the system, and the unexpected ripple effects on team morale and on-call burnout. Specific metrics: deployment frequency went...

Episode 19 of Tech Leadership with Fexingo: Lucas and Luna dive into Architectural Decision Records (ADRs) — lightweight documents that capture the context and rationale behind technical choices. They walk through a real example from a mid-stage startup that used ADRs to avoid repeating a costly database migration mistake. Lucas explains the five essential sections of an ADR: title, status, contex...

Lucas and Luna explore the role of an Incident Commander (IC) during major outages. Using the example of a real e-commerce platform outage that cost $300,000 in lost revenue per hour, they explain how a designated IC prevents chaos, reduces mean time to resolution, and empowers engineers to focus on fixing. Lucas breaks down the IC responsibilities: triaging, communicating, and making rapid decisi...

Most engineering teams spend their hackathons building features that never ship. Lucas and Luna explore a different approach: the structured glitch day where teams intentionally break their own systems to expose fragility, test incident response, and build muscle memory for real outages. Drawing parallels to Netflix's Chaos Monkey and a medical-device company that found a race condition in its fac...

In this episode of Tech Leadership, Lucas and Luna explore how proactive observability can prevent outages rather than just help you debug them. They unpack a real case: a mid-size fintech company whose SRE team built a canary-based anomaly detection system that caught a memory leak in staging, two hours before a scheduled production deploy. The conversation covers the difference between monitorin...

Episode 15 of Tech Leadership with Fexingo explores the rise of platform engineering. Lucas and Luna discuss why companies like Spotify and Zalando have invested in platform teams to accelerate development, reduce cognitive load, and standardize infrastructure. They break down the key principles: treating internal developers as customers, measuring platform adoption, and avoiding the trap of build...

Episode 14 of Tech Leadership with Fexingo explores the concept of a code-freeze day — one regular day per week or sprint where no production code is written. Lucas and Luna discuss how companies like GitHub and Basecamp have used this practice to reduce cycle time, improve code quality, and give engineers breathing room. They cite a 2025 study from Stripe showing that teams with a code-freeze day...

Lucas and Luna dive into the pre-mortem technique—a structured exercise where an engineering team imagines a project has failed six months in the future and reverse-engineers what went wrong. Lucas shares how a pre-mortem at his former company caught a critical scaling flaw in a new payment service before launch, saving $2 million in potential rework. Luna contrasts this with standard post-mortems...

Episode 12 of Tech Leadership with Fexingo dives into why technical writing is a superpower for senior engineers. Lucas and Luna discuss how one CTO at a mid-stage SaaS company used a mandatory three-page technical design doc to surface architecture issues that were invisible in code reviews. They explain why writing forces clarity, how to evaluate writing without being a grammar snob, and a surpr...

Lucas and Luna explore how technical debt accumulates in engineering teams and, more importantly, how to measure and prioritize it. Drawing on a real case from a Series B fintech startup, they discuss the 'debt-to-asset ratio' for codebases, why most teams measure the wrong things, and how one CTO convinced her board to allocate 20% of engineering capacity to reducing debt — without slowing down p...

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into the messy reality of engineering career ladders. Most companies copy-paste a generic matrix from a blog post and call it a day. Lucas argues that a good ladder must be specific to your company's stage, culture, and technical challenges. He walks through the concrete example of a Series B startup he advised that had 30 engine...

Lucas and Luna explore the common but painful pattern where high-performing senior engineers get promoted into management and struggle. Lucas shares data from a 2025 GitLab survey showing 63% of engineering managers received zero management training before their first role. They break down the 'Peter Principle in tech' using the case of a mid-size SaaS company where a top backend engineer became a...

In this episode of Tech Leadership with Fexingo, Lucas and Luna dig into why blameless postmortems are the single highest-leverage practice for engineering teams. Lucas breaks down a real example from Stripe's early days: how a 2015 outage caused by a single bad deploy led to a cultural shift that eliminated repeat incidents. They explore the psychology of blame, the difference between 'root cause...

Lucas and Luna explore the concept of a decision log — a lightweight document that records every major technical decision, who made it, why, and what alternatives were considered. They walk through a real example from a fintech startup that used a decision log to save months of rework during a platform migration. The hosts discuss how decision logs prevent knowledge loss, speed up onboarding, and...

Most technical strategy documents are never read by the people they're written for. Lucas and Luna unpack why—and how one engineering team at a mid-stage SaaS company rewrote their approach, cutting a 47-page document down to 6 pages that actually drove decisions. They walk through the 'one-pager test,' the pyramid principle applied to system architecture, and why a CTO should spend as much time o...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore a counterintuitive problem: senior engineers who become bottlenecks despite their brilliance. They examine a real case from a Series B fintech startup where a single principal engineer was the sole approver for production deployments, causing delays that added $2.3 million in opportunity cost over 18 months. Lucas explains the...