Advancing Beyond Staff: A Mobile Engineer's Journey in Big Tech
summary
Claims that fewer than 1% reach principal and that each level expects roughly a 10x business impact per level (napkin math: $1M → $10M → $100M) guide promotion thinking; staff typically leads 1–3 teams, senior staff owns orgs of ~50–200 people and spends >50% of time on leadership; mobile engineers face a scope problem: either lead many mobile engineers or become a cross‑functional product leader; practical moves include building frameworks or CI (Docker, Python, backend services, IDE plugins), abandon being an Android engineer, work in founder mode and avoid “snacking.”
AI-written summary · about
chapters (11)
- 0:00Mobile engineer’s journey intro
- 3:53Big Tech career levels
- 7:01Senior staff engineer role
- 12:15Staff vs senior staff
- 16:27Impact and contribution factors
- 21:01Leadership roles in engineering
- 23:45Senior staff downsides
- 27:57Mobile glass ceiling
- 31:02Tips for mobile engineers
- 34:11Should you pursue senior staff or not?
- 36:16Q&A
related talks
30miOS at
32mThe Power to Make Things Work — From Android Engineer to Manager and Beyond?
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
36mWhat’s next for senior developers? The IC track missing manual
30mBeyond senior: lessons from the technical career path
24mReal-life Tips and no-BS Stories of Exceptional Engineering Leaders
24mManaging Out: Strategies for Leveling Up
43mA Career as an Android Engineer