Being a principal engineer. The world is your oyster.
summary
Role means steering technical and product strategy, not just coding: guide choices like databases versus managed services, Kubernetes versus VMs, or language decisions; report structure matters (typically paired to a VP and peered with managers); act as the bridge between product roadmaps and technical execution; calibrate performance without direct reports; use incidents as learning — a mail pipeline survives a planned Black Friday fiber failure because failure modes were anticipated. Expect orgs to scale 30 people to thousands, avoid expensive one‑way doors, stay close during incidents, and focus influence on outcomes rather than micromanaging.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:40Who am I
- 2:19Career Ladder
- 2:55Assumptions
- 4:24Management
- 6:15IC Ladder
- 7:07Technical Leader
- 13:26Risk Mitigation
- 16:10Senior IC
- 22:36Lighthouse
- 24:11The Real World
- 24:41Stereotypes
- 26:15Stay in touch
- 28:11Team support
- 29:26Summary
related talks
30mBeyond senior: lessons from the technical career path
58mHow to survive and thrive as an engineering leader
38mWho is a Lead Engineer today
13mMoving Beyond “Getting It Done”
29mStaff Engineer: “Here be dragons”
42mPanel: The Role of Engineering Manager
30mBeyond senior: lessons from the technical career path
48mPanel Discusson: Road To Staff/Principal Engineer