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 engineers and zero clear promotion criteria. The result: top performers left because they didn't see a path, and junior engineers felt stuck. Lucas explains how they built a lightweight ladder based on four dimensions — technical scope, ownership, mentorship, and impact — and how they tied it to real projects, not arbitrary tenure. Luna challenges whether ladders can ever be fair across roles like backend and frontend. Lucas acknowledges the tension but says the goal should be transparency, not perfection. The hosts also touch on how the rise of staff-plus roles has changed expectations. A practical episode for any CTO or engineering manager wrestling with retention and growth.

#CareerLadder #EngineeringManagement #TechLeadership #StaffPlus #Retention #PromotionCriteria #SeriesB #CTO #EngineeringCulture #Mentorship #TechnicalScope #Impact #Ownership #GrowthPath #Transparency #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

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 bottleneck as a manager — not because he lacked skill, but because the promotion changed the nature of his work entirely. Luna pushes back on the idea that empathy can be taught, and Lucas offers a concrete alternative: the 'staff-plus' track, a non-management career path that keeps top talent coding without forcing them into meetings. The episode closes on a forward-looking question about how companies can redesign incentives to reward technical contribution, not just headcount management. No ads. No filler.

#EngineeringManagement #TechLeadership #PeterPrinciple #StaffPlusTrack #PromotionPitfalls #ManagerTraining #GitLabSurvey #TechCareerGrowth #EngineeringCulture #IndividualContributor #CTOAdvice #TechPodcast #Technology #FexingoBusiness #BusinessPodcast #LeadershipDevelopment #SaaS #EngineeringManager

Keep every episode free: buymeacoffee.com/fexingo

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' and 'systemic cause', and how to run a postmortem that doesn't punish the person who pressed enter. If your team still points fingers when something breaks, this is the episode to hear.

#BlamelessPostmortems #EngineeringCulture #IncidentManagement #Stripe #SiteReliabilityEngineering #DevOps #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #SoftwareEngineering #Postmortem #RootCauseAnalysis #NoBlameCulture #EngineeringManager #CTO #ContinuousImprovement #LearningFromFailure

Keep every episode free: buymeacoffee.com/fexingo

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 make architecture reviews less political. They also touch on the common failure modes: logs that become too bureaucratic or too sparse. By the end, you'll have a concrete template you could implement next sprint.

#DecisionLog #TechLeadership #EngineeringManagement #CTO #TechnicalDecisionMaking #Architecture #KnowledgeManagement #Onboarding #PlatformMigration #Fintech #Startup #Documentation #TechnicalStrategy #TeamCulture #FexingoBusiness #BusinessPodcast #Technology #Leadership

Keep every episode free: buymeacoffee.com/fexingo

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 on document structure as on code structure. Specific examples include how the team replaced abstract principles with concrete trade-off tables and why they stopped writing background sections entirely. If your engineering org writes strategy docs that gather dust, this episode will change how you think about documentation.

#TechnicalStrategy #EngineeringLeadership #CTO #TechDocs #Documentation #EngineeringManagement #StrategyWriting #PyramidPrinciple #OnePagerTest #TechCommunication #SystemArchitecture #TradeOffs #SaaS #Technology #FexingoBusiness #BusinessPodcast #TechLeadership #DecisionMaking

Keep every episode free: buymeacoffee.com/fexingo

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 'truck factor' concept and how to measure it, while Luna shares a story from her own experience where a team used bus factor tracking to speed up releases by 30 percent. They discuss practical solutions like rotating code review responsibilities, setting WIP limits per developer, and enforcing documentation standards. The episode also covers how to identify bottleneck behavior without demotivating star performers, and why the best engineers sometimes need to be moved into mentoring roles. Listeners walk away with a concrete framework for diagnosing and fixing team throughput issues.

#EngineeringBottleneck #SeniorEngineer #BusFactor #TechLeadership #FexingoBusiness #BusinessPodcast #SoftwareEngineering #TeamThroughput #CodeReview #WIPLimits #PrincipalEngineer #FintechStartup #OpportunityCost #MentoringEngineers #DeploymentProcess #DeveloperProductivity #CTOAdvice #EngineeringManagement

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into a controversial topic: should your CTO still be writing production code? They examine the case of a former Google VP of Engineering who, upon becoming CTO of a mid-stage startup, stopped coding entirely — and how that decision actually improved engineering velocity. Lucas walks through the opportunity cost of CTOs writing code, citing data from a 2025 survey of 500 CTOs that found those who code more than 20% of their time have 30% lower team throughput on average. Luna pushes back with stories of technical founders who stayed hands-on, like the CTO of a fintech unicorn who still reviews pull requests. They discuss the 'coder CTO' trap, delegation versus abdication, and the one question every CTO should ask themselves: 'Am I the bottleneck?' The episode ends with a practical framework: the 80/20 rule for CTO time allocation, where 20% goes to deep technical work (architecture, code review, debugging) and 80% to leadership, strategy, and people. No hot takes — just nuanced, data-driven conversation for engineering leaders.

#CTO #EngineeringLeadership #TechnicalDebt #CodingVsManagement #EngineeringVelocity #TechLeadership #StartupLessons #VPEngineering #CodeReview #Delegation #TechStrategy #PeopleManagement #Google #Fintech #Podcast #TechLeadershipWithFexingo #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore the controversial but common decision to let go of a top-performing individual contributor who undermined team culture. Using the real-world example of a senior engineer at a late-stage startup who shipped code faster than anyone but refused code reviews, hoarded knowledge, and burned out juniors, they break down the metrics that matter beyond output: bus factor, feedback ratio, and mentorship throughput. Lucas cites a 2023 study from the Stanford Center for Professional Development showing that teams with one high-conflict high-performer see 27 percent higher turnover. Luna shares a story from her own experience at a fintech company where a star engineer's departure improved team velocity by 15 percent within two quarters. They discuss frameworks like the 'No Asshole Rule' and how to handle the exit gracefully, including retention interviews and documentation handoffs. The episode closes with a question every CTO should ask: 'Is your best engineer making everyone else better — or just making themselves look good?'

#TechLeadership #EngineeringManagement #CTO #TeamCulture #HighPerformer #Firing #SoftwareEngineering #BusFactor #Mentorship #CodeReview #Retention #StanfordResearch #Fintech #CultureFit #NoAssholeRule #EngineeringManager #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Episode 2 of Tech Leadership with Fexingo. Lucas and Luna unpack a specific case study: a mid-market SaaS company whose CTO reduced monthly cloud spend from 2.4 million dollars to 1.4 million dollars over six quarters — without layoffs, without a cloud migration, and without hiring outside consultants. They walk through the exact three-phase playbook: mapping resource utilization by service tag, applying reserved instances to stable workloads, and building an internal dashboard that gave every engineering team a weekly cost-per-feature figure. The conversation also touches on why most cost-cutting efforts fail within 90 days, the psychology of shared ownership, and why the CTO framed this as a 'reliability project' rather than a 'cost project' to get buy-in. No theory — just the tactical steps that actually moved the number.

#CloudCostOptimization #EngineeringLeadership #CTOStrategies #AWSCosts #FinOps #TechPodcast #TechLeadership #SaaS #CloudEngineering #CostReduction #ReservedInstances #EngineeringCulture #DevOps #Technology #BusinessPodcast #FexingoBusiness #TechLeadershipWithFexingo #PodcastEpisode

Keep every episode free: buymeacoffee.com/fexingo

In the debut episode of Tech Leadership with Fexingo, Lucas and Luna dive into a real-world crisis: a mid-stage SaaS startup whose AWS bill ballooned from $12,000 to $50 million per month in just 18 months. They explore how the CTO navigated the tension between growth and cost, the architectural decisions that led to the spike, and the cultural shift needed to bring engineering teams into financial accountability. Using concrete numbers and a before-and-after breakdown, the hosts set the stage for the kinds of conversations this show will have going forward: messy, honest, and deeply technical. No hot takes, no breathless hype — just two experienced leaders unpacking the decisions that define real engineering organizations. This episode establishes the show's rhythm: a single case study, a specific metric, and a practical lesson that applies beyond any one company.

#CloudCosts #AWS #EngineeringLeadership #CTO #StartupScaling #FinOps #Infrastructure #SaaS #TechnicalDebt #CostOptimization #EngineeringCulture #CloudArchitecture #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #Episode1 #RealWorldEngineering

Keep every episode free: buymeacoffee.com/fexingo