Switching Disciplines as a Tech Lead
summary
Switches from iOS build work to product back-end, moving from running Bazel for a team that grew from one to eight and supported 100 iOS engineers to writing Kotlin microservices on a cloud product stack using misc, gRPC, protobufs, Kafka, CI and Terraform. Day one leadership focuses on design docs, onboarding gaps and enqueuing jobs instead of UI details. The change is hard but succeeds: higher breadth, more hiring options, and the new systems and team practices prove workable.
AI-written summary · about
chapters (7)
- 0:00Introduction and overview
- 3:59What is a tech lead?
- 9:23What are technical disciplines?
- 15:02Switching disciplines as a tech lead
- 21:05What changes and what stays the same
- 31:54Is it worth switching?
- 39:26Q&A session
related talks
36mBecoming a tech lead - Lessons learned
38mFrom Engineer to Director of Engineering and how to Become a Technical Leader
43mHow to Lead? Testimonial of a Lead Android Engineer
50mMaking the Leap to Tech Lead
11mTips on scaling your leadership outside of your comfort zone
13mMy Transition from Platform Engineer to Platform Product Manager
37mHow Android development experience applies outside Android development
59mTech leadership, one year after