7 lessons learned from becoming a senior engineer
summary
Seven concrete lessons from a 15‑year engineering career and time at Google: be explicit about career goals, document and write your work for others, build small reproducible projects like Kubernetes and Serverless demos, set up real CI/CD pipelines and measure deployment frequency, treat rejections as data not failure, mentor and ask for feedback, and ship and own failures — several demos and pipelines are shown, some succeeded in production and some revealed surprising blind spots.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 1:32Career journey to senior engineer
- 11:32Importance of clear career goals
- 18:28Difference between good and great engineers
- 21:13Learning from others' mistakes
related talks
34m7 tips for Senior Engineers
08m"7 things I learned in 7 years of my career"
27mTell Us Another Story Grandpa: Lessons Learned over 16 Years as a Developer
48m10 things that helped me advance my career
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
20m7 Secrets of Highly Successful Developers with Kim Maida
52mThe Only Constant Is Change: Lessons from a 25 Year SRE Career
28mLessons learned after more than 20 years working in IT