Jul 17, 2019 · 49m · y-combinator
Camille Fournier on Managing Technical Teams · Y Combinator
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, technology executive and author Camille Fournier shares deep insights on engineering management, covering the transition from developer to manager, team dynamics, and performance management. She advocates treating engineering leadership as a distinct technical discipline and offers practical strategies for building psychological safety, maintaining technical credibility, and leading effectively.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
The partners as informed peer 3.4 Guest teaching 5.6 Guest disagreement 1.2 The partners pushing back 0.7
speaking balance: gold is the partners, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 26:45 Dismantling side project illusions
Fournier sharply cautions leaders against believing that toy hobby projects in Go or Kubernetes equate to real production operational expertise.
Hardest push from the partners ▶ 33:40 Demanding concrete behavioral metricsTan pushes back on vague interpersonal advice, pressing Fournier to define exact tangible expectations rather than abstract guidance.
Biggest teaching moment ▶ 40:45 The manager telephone trapFournier breaks down why non-technical managers add little value when they merely relay messages between product teams and developers.
The partners hold their own ▶ 14:40 Identifying distributed remote constraintsTan brings in concrete operational context regarding time-zone boundaries to ground the discussion on remote management.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The partners as informed peer | Guest teaching | Guest disagreement | The partners pushing back | Why |
|---|---|---|---|---|---|---|
| The Evolution of Anti-Management Ideology in Startups | 4 | 5 | 1 | 1 | Tan frames the historical startup skepticism toward management and asks Fournier to break down why small teams adopt that flawed ideology. Fournier provides historical context from 2010s Silicon Valley and Goldman Sachs to explain the transition from IC to manager. | |
| The Power of Regular One-on-Ones and Psychological Safety | 4 | 6 | 1 | 1 | Tan brings in past podcast insights from FAIR founder Max regarding introversion and team intimidation. Fournier educates on the necessity of regular one-on-ones as psychological safety valves to prevent silent turnover. | |
| Building Cohesive Teams and Managing Remote Workplaces | 4 | 5 | 1 | 1 | Fournier explains the concept of parallel play among engineers and the need to build shared team routines, admitting candidly that she is not a full-time remote expert. Tan supports her point by emphasizing time zone overlap constraints. | |
| Rookie Manager Mistakes: Coding Default and Interpersonal Avoidance | 3 | 6 | 1 | 0 | Fournier outlines common rookie manager pitfalls, specifically the reflex of trying to write code to solve execution delays instead of fixing planning bottlenecks. Tan listens and prompts for common personality issues. | |
| Managing Underperformance, Performance Improvement Plans, and Firing | 3 | 6 | 1 | 0 | Fournier delivers direct advice on performance improvement plans, distinguishing between concrete productivity deficits and uncoachable toxic attitudes. Tan agrees and seeks clarity on firing triggers. | |
| Overcoming Maker Guilt and Evaluating Dual Career Tracks | 3 | 5 | 2 | 1 | Fournier challenges the romanticized view of side projects, warning that tinkering at home gives leaders false confidence about complex production systems. Tan builds on this by discussing how chasing shiny tech hurts scaling. | |
| Coping with Overwhelm, Delegation, and Executive Coaching | 3 | 5 | 1 | 0 | Fournier advises new managers on shedding low-leverage tasks, delegating hiring loops, and asking for help rather than silently drowning. Tan raises the role of executive coaching. | |
| Aligning Team Values, Hiring Screening, and Internal Fit | 4 | 6 | 2 | 2 | Tan challenges vague cultural standards, prompting Fournier to give concrete examples of operational discipline and design reviews. Fournier also pushes back on standardized hiring loops that fail to match engineers to proper organizational tracks. | |
| Effective Recognition Practices and Peer Appreciation Rituals | 3 | 6 | 1 | 1 | Fournier explains why engineering managers must remain technically grounded to avoid becoming inefficient telephone relays between product and engineers. Tan queries how non-coding leaders maintain technical credibility. | |
| A Three-Part Framework for Leadership versus Management | 3 | 6 | 1 | 0 | Fournier introduces her three-part framework of execution, strategy, and interpersonal charisma to define leadership and explain how leaders provide clarity amidst ambiguity. Tan concludes with a shared observation on condescending tech archetypes. |
Statements from this episode (18)
Fournier: Good management is essential, not waste or overhead
“The thing that I'm observing is that actually like management is pretty important, that good management is actually a pretty important part of making engineering teams effective, making companies effective. It just simply isn't true that management is overhead…”
Fournier: Engineering management is a distinct technical discipline
“Help them understand that it's kind of a hard and a special discipline, but it's also a technical discipline and not just something that, you know, any random people manager can do.”
Fournier: Management becomes necessary once startup teams outgrow direct constant alignment
“At some point you get enough people that you need to really coordinate work Amongst people who are not just like joined at the hip talking to each other all the time, completely on the same wavelength. And that's when structure and hierarchy and some kind of m…”
Fournier: Early startup success creates a false belief that management is unnecessary
“When you have a lot of people who have seen success at these very small stages and they're, they believe incorrectly that the thing that made them successful was just like, well, we just got these smart people together and let them do what they thought was rig…”
Fournier: Regular one-on-ones prevent minor workplace issues from causing resignations
“The reason that you have one-on-ones, the reason that you try very hard to honor whatever frequency is the right frequency for your team, Even if you don't have anything planned to talk about is that like, you need to make it comfortable for them to feel like …”
Fournier: Engineering teams devolve into parallel play without deliberate team-building
“I think that a lot of engineering sometimes feels like parallel play, where it's, like, People, they aren't really working together exactly. They're kind of each working on their own project separately, and maybe they give each other code reviews, but making y…”
Fournier: Engineering managers cannot code their way out of delivery problems
“New managers tend to default to writing code to solve their problems. So new managers who used to be ICs, they look at a team, and they look at a team that's struggling, and the thing that they want to do is be like, I can just take some of these tickets, I ca…”
Fournier: Managers must proactively resolve interpersonal conflicts instead of separating teammates
“A big mistake that I see rookie managers make is like just not dealing with interpersonal issues on their team proactively. If two people are not getting along, And you just let that sit and fester. It's just gonna cause you problems. There's, you can't just b…”
Fournier: Directly fire chronically negative employees instead of putting them on PIPs
“There are sometimes when you shouldn't pip someone. You should just say, you know what, this is just not working out, and we just need to part ways. And I think that people who clearly are just unhappy, that they clearly don't want to be there they're super ne…”
Fournier: Firing negative employees boosts team productivity far more than expected
“The impact, the positive impact on the team when you get rid of that negative energy is always shocking to me. Because it's always more than you think it's gonna be. Like, the team is always so much happier and healthier and therefore more productive once they…”
Fournier: Quality tech companies offer senior career tracks without people management
“Most companies that I see that I would consider to be quality companies. They have separate tracks that do not require like you managing A lot of people or any people at all to become a very senior person, a very well, you have a career.”
Fournier: Side projects cannot substitute for production experience when evaluating technologies
“Knowing a little bit of like Go or like having like spun up Kubernetes on my, you know, on a test, test cluster at home is not nearly enough to have an informed good opinion about A new language or like a new system. Like you have to run those systems in produ…”
Fournier: Managing leaders who never ask for help is much harder
“Speaking for myself as a manager of managers, it's much harder to manage someone who never asks you for help and doesn't,
Doesn't know, doesn't think that they're, they should, you know, lean on you occasionally than someone who knows when to come to you and a…”
Fournier: Tech hiring competition makes trial employment periods unrealistic
“I think trial periods are a very nice idea. I think in the current competitiveness for staffing, you would be very lucky to get away with trying to do that.”
Fournier: Large companies should reassign misplaced talent rather than fire them
“I also think that like, if your company is big enough you should be trying, if you hire someone and you think they're great, but they don't work out on the job you put them in, as long as you think they're a general cultural fit for the company, you should try…”
Fournier closes all-hands meetings with peer-to-peer appreciation shoutouts
“Every time we do an all hands, we do at the very end, we say like, you know, who's done something awesome. And I ask people to just stand up and thank their coworkers for doing great things. And that's something that we started at rent the runway and I've carr…”
Fournier: Managers who only play 'management telephone' add very little value
“If you, if all you're doing is playing management telephone, your manager is adding very little value to the team. And so that's why, like, I think management is not just about people management because people management is just not all of the job.”
Fournier: Asking insightful technical questions builds immediate credibility with engineers
“Being able to ask good questions is what makes you legit to engineers, right? If they feel like you actually understand what they're telling you that they're working on and can ask them like an insightful question about that system, like you get a lot of cred …”