Staff Engineer: “Here be dragons”
summary
Argues that a Staff Engineer is a problem finder not just a solver, and spends weekdays on code reviews, hiring, onboarding, pairing, mentoring, and documenting playbooks rather than full‑time coding. Describes concrete tools and rituals: reviews, pairing sessions, one‑on‑ones, benchmarks and profiling, and notes that success is measured by team throughput and decisions aligned to a technical direction. Uses the cartographer metaphor to show iterative loops of observe generalize guide and advises focusing on high‑impact work and building networks.
AI-written summary · about
chapters (4)
- 0:00Start
- 8:29a staff engineer is a problem finder
- 22:23Make yourself visible
- 24:06Be one before becoming one
related talks
22mThe Staff Engineer’s playbook: Intellectual shift to systemic impact
16mSo That's a Good Spot, Staff Engineer? 😉
58mBeing Staff Plus
22mWhat the Best Engineering Leaders Do Differently
31mBeing a principal engineer. The world is your oyster.
42mPanel: The Role of Engineering Manager
26mCare and Feeding of Engineers
31mFrom Engineer to Engineering Manager