Career path
Become Staff
Build influence beyond your own team.
Technical leadership, ownership, RFCs, architecture reviews, cross-team alignment and decision making.
Senior engineers trying to cross the staff/principal gap without becoming managers.
Are you on this path?
Signs you are here
- Your technical depth is real, but your scope is invisible.
- Your impact lives in your commits, not in other engineers' work.
- You keep solving problems privately instead of durably.
- You are clearly senior, but the staff bar feels undefined.
Your first move
Choose one problem that affects more than one team and write the one-page document that makes your judgment durable.
Staff work is influence made visible.
This path is for senior engineers whose technical depth is real, but whose scope needs to become legible across teams.
- 01
Pick problems that affect more than one team.
- 02
Use RFCs and architecture reviews to make judgment durable.
- 03
Mentor through systems, not only private advice.
- 04
Show how your decisions improve the work of other engineers.
Books for this path
Altitude - The missing bridge between Senior Mobile Engineer and Staff Engineer
Staff mobile systems engineering
Altitude
Think like a staff-level mobile systems engineer across client, backend, security, reliability and production tradeoffs.
Get the bookArchitect Blueprint
Become a mobile architect
Architect Blueprint
Step into staff level and architect roles with the judgment they require.
Join the waitlistFree resources
template
Mobile Architecture RFC Template
A mobile architecture RFC template that forces the decision to show constraints, rejected options, rollout risk, ownership and rollback.
checklist
Staff iOS Engineer Scope Map
A scope map for checking whether your work reads as senior, staff or architect-level impact, using evidence instead of job-title vibes.
Writing for this path
Work the become staff path deliberately.
Use the material in order, or jump straight to the thing you need to handle this week.
