Each episode of Tech Leadership with Fexingo is a structured dialogue between Lucas and Luna, dissecting the decisions that define engineering organizations. Lucas, with a journalist's precision, and Luna, probing from the practitioner's chair, examine real CTO playbooks — from Netflix's architecture team restructuring to how Stripe scaled its engineering manager track. They walk through the trade-offs in code review velocity vs. quality, the economics of platform teams, and the talent signals that predict a VP of Engineering hire. The show is built for people who actually run technical organizations: engineering managers deciding whether to centralize infrastructure, CTOs weighing a monorepo migration, and tech leads who need to justify architectural choices to a board. Every conversation is grounded in specific metrics — deployment frequency, on-call load, and hiring leaky-funnel data — and each episode ends with a concrete tension that the listener can adapt to their own stack. What happens when your best individual contributor doesn't want to manage, but your only path to staff engineer requires it? How do you kill a project your team loves without destroying morale? Lucas and Luna don't offer templates; they surface the logic behind the choices that separate durable engineering cultures from those that burn out.

Support FexingoRSS Feed