Camille Fournier on PM-Engineering Dynamics, Rewrites, and Platform Engineering

Camille Fournier on PM-Engineering Dynamics, Rewrites, and Platform Engineering

transcriptlennys-podcastengineering-managementplatform-teamspm-engineeringrewritesmanagement-path

Camille Fournier on PM-Engineering Dynamics, Rewrites, and Platform Engineering

Source: Lenny’s Podcast Speaker: Camille Fournier Date: ~2024 Link: https://www.lennysnewsletter.com/p/engineering-leadership-camille-fournier

Key ideas

  • Four PM anti-patterns that annoy engineers. (1) Hoarding credit — PMs are front-facing and can inadvertently take all the glory; fix by letting engineers speak about their own work. (2) Ignoring technical details — signals lack of empathy for the craft. (3) Playing telephone — acting as middle-man for questions you cannot actually answer; better to connect people directly. (4) Hoarding ideas — when engineers feel excluded from product ideation they find creative outlets in over-engineering and unnecessary rewrites. The PMs who work best with engineers are not threatened by engineers having ideas.
  • Rewrites are almost always a trap. Engineers systematically underestimate migration time — moving users/data from the old system to the new one takes far longer than expected. Legacy systems contain undocumented business logic that only surfaces during migration. Key diagnostic: if you could leave the system untouched for a long time without harming the business, ask whether a rewrite is worth it at all. Prefer staged evolution — uplift a well-contained component rather than going dark for six to twelve months.
  • Engineering management: get to mastery first. Do not move into management until technical skill is “in your bones” — a second-language fluency you retain even after years away from the keyboard. Heuristic: ~10 years of serious hands-on coding (undergraduate + graduate + 4–5 years full-time). After the transition, stay technically credible not by writing code but by surrounding yourself with smart engineers, listening to their war stories, and asking good questions — not prescribing library choices.
  • One-on-ones: less is more. One-on-ones with direct reports and your own manager are sacred. Beyond that, the practice does not scale linearly as organisations grow. Bilateral stakeholder one-on-ones also create a weakness: your happy and unhappy stakeholders never hear each other, making complaints harder to contextualise. Test your default: if you’re having one-on-ones with everyone out of habit rather than necessity, you are probably ticking a checkbox rather than generating value.
  • Platform engineering as a product discipline. Platforms are products. Platform teams require software engineers (not just SRE/DevOps), systems engineers, and dedicated product managers. Measure with outcome-based impact: cycle time reduction, cost efficiency, removing scaling blockers — not activity metrics. Stakeholder management is the hardest part. Start building a platform team at ~50+ engineers. Platform projects run longer and involve more migrations than typical agile cadences; adjust your operating model accordingly.

Overview

Camille Fournier is the author of The Manager’s Path (widely regarded as the definitive guide to engineering management careers) and co-author (with Ian Nolan) of Platform Engineering (O’Reilly). Her career includes CTO of Rent The Runway, VP Technology at Goldman Sachs, global head of engineering and architecture at JP Morgan Chase, and head of platform engineering at Two Sigma. The episode covers: the four things PMs do that most annoy engineers and how to fix them; why major rewrites almost always disappoint; when to move from IC to engineering management and how to stay technically credible after the transition; a contrarian take on one-on-one proliferation; and a practitioner’s guide to building and working with platform teams.