Panel Discusson: Road To Staff/Principal Engineer
summary
Panel recounts concrete routes to staff/principal: building a company-wide design system and front-end platform, migrating many apps into an NX monorepo and upgrading to Angular 14 (16 months of work), and unifying OAuth and Marketplace so one Marketplace app serves all products. Outcomes include one P0 incident after rollout, measurable reduction in toil, and a reusable internal product; tactics use surveys, cross-team facilitation, draw.io diagrams, and the book The Staff Engineer’s Path.
AI-written summary · about
chapters (8)
- 0:00Introduction to panel
- 1:46Staff vs senior engineer
- 6:22Becoming staff engineer
- 17:20Key projects for promotion
- 28:57Imposter syndrome challenges
- 41:12Managing scope and stakeholders
- 42:57Mentors and support
- 47:10Closing remarks
related talks
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
24mFrom Developing Code To Developing People
32mPanel discussion: The journey to building effective engineering teams
30mBeyond senior: lessons from the technical career path
59mTech leadership, one year after
13mMoving Beyond “Getting It Done”
22mThe Staff Engineer’s playbook: Intellectual shift to systemic impact
36mWhat’s next for senior developers? The IC track missing manual