Is Staff Engineering valuable at a small company?
summary
The answer is yes with a big asterisk: staff work matters at small companies when it produces concrete outcomes not titles. Impact comes from defining problems with one‑pagers, from reducing wasted developer time by shaping system architecture, from doing real coding while scaling others, and from hands‑on research like 19 hours of interviews that yield engineering principles. Examples include choosing simpler ops (no Kubernetes) and shipping changes that noticeably change throughput or cycle time.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:02Staff engineering at small companies
- 2:29Defining staff engineering work
- 3:53Staff engineering daily
- 6:39Balancing staff and team work
- 8:24Avoiding overwhelm
- 9:28Generalist skills
- 10:30System architecture importance
- 11:33Avoiding FANG tooling
- 12:16Focusing on problems
- 14:21Non-scalable activities
- 15:46Engineering from user research
- 16:27Mapping architecture
- 17:30Monitoring reviews
- 18:52Title impact
- 19:54Is staff engineering valuable?
- 20:34Rewards of staff engineering
related talks
58mHow to survive and thrive as an engineering leader
42mHow to Hit the Ground Running as a Staff + Software Engineer at a New Company
45mGrowing Engineers with Weekly Investment Time
37mAdvancing Beyond Staff: A Mobile Engineer's Journey in Big Tech
50mLevel Up Your Career
58mBeing Staff Plus
20mImpact: Growing as an Engineer
06mInterview to Sven Peters