Who is a Lead Engineer today
summary
Argues that every engineer is a leader and gives concrete guidance: move beyond single-language chops (Java/JavaScript/Spring Boot, Kubernetes, React/Vue) into systems thinking and owning the code path from workstation to production; cites a UI prototype for network-management devices that proved the idea and shipped after platform/backend changes. Recommends choosing production fixes over flashy features, growing influence across product portfolios of 12–15 products, and fighting three learning enemies: fear, clarity and power.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:35Lead engineer definition
- 7:25Engineering complexity today
- 15:27Growth beyond lead engineer
- 23:34Knowledge and its challenges
- 30:41Practical advice for engineers
- 35:27Closing remarks
related talks
42mPanel: Becoming an engineering leader
58mHow to survive and thrive as an engineering leader
12mLeader or engineer? Navigating our technical identity crisis
47mLeading in Tech
43mLeading in Tech
29mThe Constant Life of a Tech Lead
43mHow to Lead? Testimonial of a Lead Android Engineer
58mMy Journey to Understanding Technical Leadership
