Mentors who lead engineering teams
Book a session with experienced tech leads on running a team's technical direction while still building — delegation, code review, and holding a quality bar without becoming a bottleneck.
Before you book a tech lead mentor
How do I choose the right tech lead mentor?
Becoming a tech lead is the first time your output stops being what you personally produced. The characteristic first-year mistake is trying to keep your old throughput and add the new responsibilities on top, which works for about three months. A mentor who has been through it can help you decide what to stop doing.
What should I bring to a tech lead mentor session?
Bring a concrete problem: a project that is slipping, a disagreement you are refereeing, or a teammate whose work you keep rewriting. Generic leadership advice is abundant and useless; specific situations are where a session pays for itself.
Ask how they handled the shift in code review — from finding bugs to teaching judgement — and how they avoided becoming the person every decision waits on.
What people bring to these sessions
- Making the shift from personal output to team output
- Delegating work you could do faster yourself
- Code review as teaching rather than gatekeeping
- Refereeing technical disagreements
- Keeping a quality bar without being a bottleneck