How I became a VP of Engineering
summary
Joins a small backend team, builds the first scalability layer: database sharding and a database service tier that justifies a new owning team; company grows ~10x in four years. Chooses management after two years, repeatedly reorganizes — once handing off 40 people when managing ~80 — and treats the role as owning scope and impact rather than just coaching. Later leads a full on‑premises-to‑cloud migration and starts productizing AI for unstructured content. Recommends reading First Break All the Rules and Five Dysfunctions.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:27PhD to industry
- 3:36Joining Box as engineer
- 5:46Engineer to manager
- 10:23Successful management
- 13:55Senior EM evolution
- 15:22Director promotion
- 18:53VP of Engineering
- 24:03Career step functions
- 25:47Challenges at Box
- 27:14Leadership advice
- 27:54Recommended books
- 29:40Legacy code refactoring
related talks
36mVenturing into Product as an Engineer
24mConfessions of a First-Time Engineering Manager
24mFrom Developing Code To Developing People
25mYou’ve Got To Pivot Your Career, Just Like Your Products: How I Got Into Data
45mFrom Agile coach to manager. And back. Or did I go back
32mLessons in Leadership
51mTeaching and managing for technologists
31mBeing a principal engineer. The world is your oyster.