Swinging the Engineer/Manager Pendulum
summary
Engineers swing between IC and manager roles because the work genuinely differs: running 185 microservices across 20 data centers for tens of billions of accounts requires different metrics and meetings than shipping code. Management is not a promotion but accountability for hiring, performance plans, staffing and stopping failed projects; common failure modes are the hero fix, boredom, or chasing a promotion. Recommended tour of duty is tour of duty 2–4 years and expect to relearn engineering mechanics if you return.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:04Role at Google
- 3:30Work at Google
- 6:01Individual contributor role
- 11:17Transitioning to Tech Lead
- 14:36Frustrations of a Tech Lead
- 16:58Role of a manager
- 22:26Challenges in management
- 25:06Google's management traits
- 29:11Management best practices
- 31:40Career transitions
- 35:23Management pitfalls
- 39:14Management accountability
- 40:06Returning to engineering
- 42:09The pendulum approach
- 45:01Conclusion
related talks
33mThe Engineer/Manager Pendulum Goes Mainstream
50mThe Engineer/Lead pendulum: A Practical Experience
25mThe staff engineer vs manager path A window over the tech career paths
31mFrom Engineer to Engineering Manager
01h 01mBecoming an Engineering Manager Without Losing Your Technical Soul
05mManage your Engineers as Managers
42mPanel: The Role of Engineering Manager
48mFrom Developer to Manager... and Back
