Beyond senior: lessons from the technical career path
summary
Principal-level work shifts from coding to coordinating: leads a 2022 community-product initiative that touches payments, checkout and integrations and requires working with three core pods plus at least five other teams across the org; proposes a fully managed Kafka streaming design for rearchitecting notifications but cuts it for cost; pairs a new digital-downloads feature with security work to unlock creator revenue; builds an archiving feature whose cost analysis shows payback by the end of the quarter. Core takeaways: four lessons for the role and rearchitected notifications as a cautionary example.
AI-written summary · about
chapters (8)
- 0:00Welcome
- 0:49Speaker journey
- 3:39Principal engineer role
- 11:06Avoiding burnout
- 15:45Mentorship
- 19:19Technical strategy
- 27:00Redefining staff-plus
- 29:10Key takeaways
related talks
17mBeyond Senior Dev: The next steps for the technical career
36mWhat’s next for senior developers? The IC track missing manual
31mBeing a principal engineer. The world is your oyster.
30mForging Your Path to Senior Developer
48mPanel Discusson: Road To Staff/Principal Engineer
38mFrom Engineer to Director of Engineering and how to Become a Technical Leader
23mSenior to leader: Taking the next step
25mRethinking the Developer Career Path