Question 1

What are the key takeaways from Camille Fournier's episode on Lenny's Podcast?

Accepted Answer

1. Great product managers are not threatened by engineers having ideas—they embrace collaboration while recognizing each role's unique value, creating environments where engineers feel heard without over-engineering as their creative outlet. 2. System rewrites are often a trap because engineers massively underestimate migration time and the hidden logic buried in legacy systems—evolve systems incrementally rather than going away to build something new. 3. Don't stop being hands-on technical until mastery is 'in your bones'—roughly a 10-year range of serious coding before transitioning to management, especially crucial for underrepresented people who face assumptions about technical ability. 4. Management is a service job, not a position of authority—you don't own your time anymore, the company and team do, and your job is to serve and guide rather than make all the decisions. 5. Overwork lets you sidestep the hard work of figuring out what's important—challenge yourself to focus, delegate, and regularly audit your time rather than filling hours with low-value activities.

Question 2

What does Camille Fournier say about engineering-management and technical-leadership?

Accepted Answer

"I'm going to find that in places where they are so quashed their creativity for the actual business or product that they're building and their voice in that is so ignored that they don't have any outlets in that space and so, they are going to use the space that they have an outlet in, the place where they have some control and that's usually the technology choices and the details there." - Camille Fournier "I think the product managers that have done the best, they're not threatened by other people having ideas. They're not threatened by the engineering team being full of smart people because they realize that yeah, some of the engineers may have good ideas, but they still don't really know how to do the product job." - Camille Fournier "You think, 'Oh, we kind of know what's going on, so it's not going to be that big a deal.' Engineers notoriously, notoriously, notoriously, massively underestimate the migration time for old system to new system and that causes a lot of problems. By the way, you still have to support the old system while you're working on the new system." - Camille Fournier

Question 3

What are Camille Fournier's views on engineering-management, technical-leadership, career-growth?

Accepted Answer

Camille Fournier: "One piece of advice I give everybody is don't stop being a hands-on technical until you feel like it's in your bones. You feel like you've got mastery that you could... if you know a second language fluently or if you played an instrument really, really seriously for a long time, you'll be familiar with the—I haven't done that in a long time, but if I was to pick it up, it would be rusty, but I would get there pretty quickly." Camille Fournier: "What people care about with technical leaders in my experience is they want people who actually seem like they sort of understand what you're doing and can ask good questions and help guide you to better decisions without actually being the one who's like, 'Oh no, you need to use this library instead of that library.'"

Camille Fournier

The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”)

TRANSCRIPT

Camille Fournier

The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”)

Camille Fournier

The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”)

TRANSCRIPT

Camille Fournier

The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”)