Creating technical leadership in context
summary
Company scales from ~20 to ~300 engineers and experiments with three models since 2020: a backend Council doing monthly 5% side work (which produces many half‑baked, low‑priority projects), an architecture council that prototypes and ships a few re‑architectures to unwind the internal "Bermuda Triangle", and a 10–15 senior IC program that uses RFCs, a weekly Eng review, a tighter spec template, on‑site prototyping and explicit buy‑in to turn clear problem statements into funded work.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 3:41Iterative learning process
- 12:07Refining the senior IC program
- 14:17Technical leadership framework
- 15:30Leading by example
- 17:30Improving decision making
- 20:55Building community
- 22:08Aligning and scaling impact
related talks
59mTech leadership, one year after
53mScaling Engineering by Hacking Conway's Law
15mManaging During Growth & Change
16mEveryone architect!
29mUsing architecture groups to scale people and technology
46mHow to scale a unicorn-building engineering team (and stay sane)
36mWhat’s next for senior developers? The IC track missing manual
18mAgile leadership and technical mastery, a harmonious alliance