เชฎเซเช–เซเชฏ เชธเชพเชฎเช—เซเชฐเซ€ เชชเชฐ เชœเชพเช“
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 widely read)
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.

เช–เชพเชคเชฐเซ€ เชจเชฅเซ€ เช•เซ‡ เช† เช•เซŒเชถเชฒเซเชฏ เชคเชฎเชพเชฐเชพ เชฎเชพเชŸเซ‡ เช›เซ‡?

เช•เชฐเชฟเชฏเชฐ เชฎเซ‡เชš เชŸเซ‡เชธเซเชŸ เช†เชชเซ‹ โ€” เช…เชฎเซ‡ เชฏเซ‹เช—เซเชฏ เชŸเซเชฐเซ‡เช•เซเชธ เชธเซ‚เชšเชตเซ€เชถเซเช‚.

เชฎเชพเชฐเชพ เชถเซเชฐเซ‡เชทเซเช -เชซเชฟเชŸ เช•เซŒเชถเชฒเซเชฏเซ‹ เชถเซ‹เชงเซ‹ โ†’

เชคเชฎเชพเชฐเซ‹ เช†เชฆเชฐเซเชถ เช•เชฐเชฟเชฏเชฐ เชชเชพเชฅ เชถเซ‹เชงเซ‹

2,521 เช•เชพเชฐเช•เชฟเชฐเซเชฆเซ€เช“เชฎเชพเช‚ เช•เซŒเชถเชฒเซเชฏ-เช†เชงเชพเชฐเชฟเชค เชฎเซ‡เชšเชฟเช‚เช—. เชฎเชซเชค.

เช•เชฐเชฟเชฏเชฐ เชฎเซ‡เชš เชŸเซ‡เชธเซเชŸ เช†เชชเซ‹ โ€” เชฎเชซเชค โ†’