Designing an engineering team: Making room for everyone
summary
Argues for hiring by mapped skills not vague titles, showing concrete comparisons (2017 had zero commercial jet deaths after role-based fixes), recommending explicit operating room roles on teams, measuring who owns product metrics, and keeping teaching hospitals (students) to lower failure rates. Gives tooling examples — on‑prem provisioning versus Fargate vs bare metal — and a promotion system example (Medium’s Snowflake). Proposes custom interview panels that test claimed skills, an onboarding that exchanges team and candidate abilities, and hiring people to fill missing roles.
AI-written summary · about
chapters (4)
related talks
48mDesigning Your Team Before You Hire
16mEnlarge your team!
32mPanel discussion: The journey to building effective engineering teams
28mBuilding happier engineering teams
43mBuild “boring” engineering orgs
01h 02mHow to hire great engineers
21mGrowing engineering managers: Breaking down the monolith
24mSo You Want To Hire for Platform Engineering?
