Career Growth: Senior to Lead to Staff/Principal
Career growth for Rust specialists tracks expanding scope: from owning features, to leading squad outcomes, to fleet-wide architecture and multi-year strategy - with evidence tied to reliability, delivery, and people impact.
Recipe
Quick-reference recipe card - copy-paste ready.
# Promotion evidence themes (Rust specialist)
**Senior:** Shipped L feature with tests/observability; mentored junior; led incident fix
**Lead:** Squad CFR down; ADR portfolio; delegation with backups; PM partnership
**Staff:** Cross-squad RFC adopted; platform standard (clippy/deny); game day program
**Principal:** Multi-year Rust platform roadmap; exec-aligned reliability strategyWhen to reach for this:
- Calibration and promotion cycles
- IC asking "what's next?"
- Structuring leveling rubric for Rust craft
- Retention conversations
Working Example
## Staff packet excerpt (anonymous)
- Authored ADR-0038 workspace standard adopted by 4 squads
- Led edition 2024 migration train; CFR unchanged during cutover
- Built cargo-vet policy reducing CVE exposure MTTR 40%
- Mentored 3 engineers to senior via pairing on async/sqlx reviewsConcrete artifacts beat "deep Rust knowledge" claims.
Deep Dive
Level Signals
| Level | Scope | Rust craft examples |
|---|---|---|
| Mid | Task/feature | Axum route + sqlx + tests |
| Senior | Epic/service area | Crate boundaries, incident RCA |
| Lead | Squad | Tech bar, roadmap, on-call health |
| Staff | Fleet/multiple squads | Standards, migrations, RFC quality |
| Principal | Org | Platform bets, build vs buy, hiring bar |
Paths
- Management - EM path; less daily Rust, more people and planning.
- Staff IC - Deep technical leverage without direct reports.
- Hybrid tech lead - Squad lead + coding; common in startups.
Development Actions
- Present RFC at design review.
- Own post-mortem action to guardrail.
- Write SME article or internal talk.
- Lead game day for tier-1 service.
Gotchas
- Promotion = best coder - Fix: Rubric includes impact and influence.
- Staff without cross-team work - Fix: Explicit multi-squad initiative.
- Lead as permanent bottleneck - Fix: Delegation evidence required.
- Rust trivia interviews - Fix: System design + code review simulation.
Alternatives
| Alternative | Use When | Don't Use When |
|---|---|---|
| Dual ladder equal pay | Retain staff ICs | Company has no IC track |
| Rotation to product | Broaden T-shape | Critical platform owner |
| External OSS visibility | Industry staff bar | Company discourages public work |
FAQs
Must staff manage people?
No on most IC ladders; influence without direct reports.
How much coding at staff?
Often 30-50% prototypes and critical reviews; varies by org.
Principal vs distinguished?
Org-specific titles; principal often multi-team strategy.
Switch lead to staff?
Possible lateral if scope shifts from one squad to fleet.
Document expectations?
Public leveling guide + Rust-specific examples appendix.
Related
- Mentoring & Leveling - growing others
- Leadership Best Practices - lead craft
- Delegation & Spreading Context - scale self
- Roadmap Contributions - strategy
- Governance Best Practices - fleet norms
Stack versions: This page was written for Rust 1.97.0 (edition 2024), Tokio 1.x, Axum 0.8, serde 1.0, sqlx 0.8, clap 4, and Polars 0.46+.