Operate as a staff engineer without becoming a bottleneck

Steps

1. 1Pick one org-level problem per quarter; decline everything else explicitly
2. 2Write decision documents others execute — code is your worst multiplier
3. 3Maintain apprenticeship: two engineers growing toward your current scope
4. 4Schedule recurring alignment with peer staff across teams
5. 5Measure success by decisions improved, not lines or tickets touched
6. 6Escalate systemic blockers once, then build the mechanism preventing recurrence

Common Pitfalls

• ▲Hero-debugging everything while org-level debt compounds
• ▲Strategy docs nobody reads because teams weren't involved

Commands

$ npx skills add aniruddhaadak80/skills --skill staff-plus-track-staff-eng-operating-model

$ npx skills add aniruddhaadak80/skills --skill staff-plus-track-staff-eng-operating-model -g

Tags