рдореБрдЦреНрдп рдордЬрдХреБрд░рд╛рдХрдбреЗ рдЬрд╛
JobCannon
рд╕рд░реНрд╡ рдХреМрд╢рд▓реНрдпреЗ

Staff+ Career Navigation

тмв рд╢реНрд░реЗрдгреА 1рд╕реЙрдлреНрдЯ рд╕реНрдХрд┐рд▓реНрд╕
рдЙрдЪреНрдЪ
рдкрдЧрд╛рд░рд╛рд╡рд░реАрд▓ рдкрд░рд┐рдгрд╛рдо
12 рдорд╣рд┐рдиреЗ
рд╢рд┐рдХрдгреНрдпрд╛рд╕ рд▓рд╛рдЧрдгрд╛рд░рд╛ рд╡реЗрд│
рдХрдареАрдг
рдХрд╛рдард┐рдгреНрдп
тАФ
рдХрд░рд┐рдЕрд░реНрд╕
рдПрдХрд╛ рджреГрд╖реНрдЯрд┐рдХреНрд╖реЗрдкрд╛рдд

Staff+ engineering is the IC track to $250kтАУ$700k+ without managing people. Rare (5тАУ10% of engineers), high-impact alternative to management. Career path: Senior тЖТ Staff (L6, $200тАУ$350k, multi-quarter scope) тЖТ Principal (L7, $350тАУ$500k+, company strategy) тЖТ Distinguished/Fellow (L8, $500тАУ$700k+, industry influence). Success archetype: Tech Lead (owns system), Architect (designs future), Solver (fixes hard problems), Right Hand (executive advisor). Takes 12+ months deliberate practice: RFCs, design docs, political savvy, mentoring leverage, 'glue work' (coordination, visibility).

Staff+ Career Navigation рдореНрд╣рдгрдЬреЗ рдХрд╛рдп

Navigate IC career beyond Senior: Staff, Principal, Distinguished. Technical strategy, scope expansion, organizational impact. Alternative to management track. Learning Curve: Hard (requires experience + self-awareness)

ЁЯФз рд╕рд╛рдзрдиреЗ рдЖрдгрд┐ рдкрд░рд┐рд╕рдВрд╕реНрдерд╛
Will Larson's The Staff Engineer's Path (book + 40 interviews on StaffEng.com)RFC/ADR writing (design documents, architectural decision records)Technical leadership frameworks (Larson's 4 archetypes: Tech Lead, Architect, Solver, Right Hand)StaffEng.com interview database (case studies, promotion paths)Glue work concept (Tanya Reilly essay on invisible multiplier tasks)Mentoring + leverage (multiplying impact through others, not direct code)Organizational navigation (influencing without authority, reading politics)High-leverage work identification (80/20 scope expansion)Lethain's 'Irrational Exuberance' blog (Staff+ transition essays)Reforge Staff+ Accelerator (cohort-based, $3k, deep dive)Peer advisory groups (Staff+ peer networks, learning by comparison)Conference speaking + open source thought leadership

ЁЯУЛ рд╕реБрд░реВ рдХрд░рдгреНрдпрд╛рдкреВрд░реНрд╡реА

ЁЯТ░ рдкреНрд░рджреЗрд╢рд╛рдиреБрд╕рд╛рд░ рдкрдЧрд╛рд░

рдкреНрд░рджреЗрд╢рдЬреНрдпреБрдирд┐рдпрд░рдордзреНрдпрдорд╕реАрдирд┐рдпрд░
US_SFтАФтАФтАФ
US_NYCтАФтАФтАФ
US_REMOTEтАФтАФтАФ
US_AUSTINтАФтАФтАФ
UK_LONDONтАФтАФтАФ

ЁЯОУ рдкреНрд░рдорд╛рдгрдкрддреНрд░реЗ

Will Larson: The Staff Engineer's Path (O'Reilly book, Reforge cohorts, no formal cert but gold standard)
Tanya Reilly: The Staff Engineer's Path (book + essays, mentorship model)
StaffEng.com interviews + guides (self-paced, portfolio-based portfolio credibility)

тЪЦ рдпрд╛рдВрдЪреНрдпрд╛рд╢реА рддреБрд▓рдирд╛ рдХрд░рд╛

тЭУ FAQ

What's the difference between Staff Engineer and Senior Engineer?
Senior Engineer is a 'deep expert on their team' ($150тАУ$200k, 3тАУ5 year tenure). Staff Engineer is 'organization-wide technical authority' ($200тАУ$350k, 12+ months to reach). The gap: Senior owns a subsystem deeply; Staff shapes strategy across multiple teams. Senior writes perfect code; Staff unblocks teams by clarifying direction. Senior's impact is tech quality; Staff's impact is org velocity. You become Staff by proving you can drive multi-quarter initiatives, write RFCs others follow, and mentor Seniors into excellence.
Staff Engineer vs Engineering Manager, which path is for me?
Manager path: you enjoy mentoring, 1-on-1s, hiring, performance reviews, team culture. Comp: $180тАУ$350k (capped at director). IC path: you love technical depth, solving hard problems, influencing via ideas not authority. Comp: $200тАУ$700k+. The honest truth: both get $200тАУ$300k overlap at Senior/Staff/Manager ranges. But IC scales higher ($700k+ for Distinguished), while management caps at $400k (VP). Pick based on energy: do you want to grow people or ideas? (Many try both, it's OK to switch back.)
What are the 4 Staff archetypes and which should I become?
Will Larson defines 4 types. (1) Tech Lead: runs the roadmap, final say on technical decisions, owns one system deeply (e.g., database team lead). (2) Architect: designs the future, decouples teams, reduces complexity long-term (no immediate delivery, high visibility). (3) Solver: unblocks teams in crisis, fixes hard problems fast, travels between teams (high demand, high stress). (4) Right Hand: advises executives, translates biz to eng, often reporting to CTO/VP (high trust, political). Most orgs value 2тАУ4 Architects, 1тАУ2 Solvers, 1 Right Hand, 3тАУ5 Tech Leads. Pick based on your strengths: political savvy тЖТ Right Hand. System mastery тЖТ Tech Lead. Long-term vision тЖТ Architect. Problem-solving тЖТ Solver.
Can I go from Staff back to Senior or Manager?
Yes, and it's common. Some paths: (1) Staff тЖТ Manager (take people lead role, gives you context for C-suite). (2) Staff тЖТ Switch companies as Senior (Staff role didn't materialize, new company needs experienced IC). (3) Staff тЖТ Consulting (monetize your expertise as advisor). (4) Staff тЖТ Start-up co-founder (10 years IC experience builds judgment needed for early-stage). The sticky part: going Staff тЖТ IC Senior is rare, once promoted you're not expected to downlevel. But Staff тЖТ Manager is often encouraged by companies wanting technical directors.
What's 'glue work' and why does it matter?
Glue work = invisible tasks that multiply team output: documentation, code reviews, unblocking juniors, running retros, fixing test infra, building shared libraries. Senior Engineers do glue work and ship features. Staff Engineers do MOSTLY glue work + a few high-leverage bets. Problem: glue work is invisible to promoters (no metric, no blog post, no metrics). Solution: (1) Measure glue work (RFCs written, blockers unblocked, people mentored). (2) Make it visible (share in weekly updates, talk about it in 1-on-1s). (3) Set a ratio (60% glue, 40% you projects). Too little glue = team stagnates. Too much glue = you don't grow.
How do I actually get promoted to Staff Engineer?
Promotion is 40% performance + 40% visibility + 20% timing. (1) Performance: drive 2тАУ3 multi-quarter projects that impact org velocity (not just code quality). Write RFCs that change how teams work. (2) Visibility: talk about your work in leadership meetings, present to board if possible. Make your impact legible. (3) Timing: have a 'Staff slot' open (your org needs another Staff). Get allies in skip-level 1-on-1s, build sponsorship from leadership. (4) Portfolio: collect evidence (RFCs, emails from teams saying you unblocked them, adoption metrics). Write a Staff case during promotion cycle. Most companies: 12тАУ18 months from Senior тЖТ Staff if aligned. Some fast-track at 6mo if exceptional.
How much do Staff/Principal engineers actually make?
Ranges by region and company: US SF: Staff $250тАУ$400k (base $200тАУ$250k + bonus $30тАУ$50k + equity $80тАУ$150k/yr). Principal $450тАУ$700k. US NYC/remote: Staff $200тАУ$350k, Principal $350тАУ$550k. UK London: Staff ┬г150тАУ┬г200k, Principal ┬г200тАУ┬г300k. Top quartile (FAANG): Staff can hit $500k, Principal $700k+. Seed-stage: Staff $150тАУ$250k (mostly salary, little equity). The gap between Senior ($150тАУ$200k) and Staff ($250k+) is real and worth 12тАУ18 months of effort. TotalComp calculators: Levels.fyi, Blind, BlindCompensation.com.

рд╣реЗ рдХреМрд╢рд▓реНрдп рддреБрдордЪреНрдпрд╛рд╕рд╛рдареА рдпреЛрдЧреНрдп рдЖрд╣реЗ рдХрд╛, рдпрд╛рдЪреА рдЦрд╛рддреНрд░реА рдирд╛рд╣реА?

рдХрд░рд┐рдЕрд░ рдореЕрдЪ рдХрд░реВрди рдкрд╛рд╣рд╛ тАФ рдЖрдореНрд╣реА рдпреЛрдЧреНрдп рдорд╛рд░реНрдЧ рд╕реБрдЪрд╡реВ.

рдорд╛рдЭреНрдпрд╛рд╕рд╛рдареА рд╕рд░реНрд╡реЛрддреНрддрдо рдХреМрд╢рд▓реНрдпреЗ рд╢реЛрдзрд╛ тЖТ

рддреБрдордЪрд╛ рдЖрджрд░реНрд╢ рдХрд░рд┐рдЕрд░ рдорд╛рд░реНрдЧ рд╢реЛрдзрд╛

реи,релреирез рдХрд░рд┐рдЕрд░рдордзреНрдпреЗ рдХреМрд╢рд▓реНрдпрд╛рдВрд╡рд░ рдЖрдзрд╛рд░рд┐рдд рдЬреБрд│рдгреА. рдореЛрдлрдд, ~3 рдорд┐рдирд┐рдЯреЗ.

рдХрд░рд┐рдЕрд░ рдореЕрдЪ рдХрд░реВрди рдкрд╛рд╣рд╛ тАФ рдореЛрдлрдд тЖТ