Staff-role evidence with limits

Reviewed 2026-09-22. The earlier summary overgeneralized across ladders and included statistics read through excerpts. Its exact archetype ratios, company-size cutoffs, survey percentages and AI speed claims are withdrawn as current evidence. The claim ledger C09–C10 links the exact retained pages and marks their publication age unknown.

Dropbox's IC5 framework describes multi-team direction and organizational impact. That is evidence about one employer's framework, not a universal senior/staff boundary or proof that coding expectations cease rising. StaffEng's Tech Lead, Architect, Solver and Right Hand categories are useful descriptive vocabulary, not an exhaustive taxonomy or a staffing-ratio formula. Neither undated page counts as a recent interview event.

Curriculum choices

We ask a senior candidate to own a coherent technical decision and its failure behavior; the lead extension asks who coordinates the cross-team constraint, migration, operating budget and recovery authority. Practice producing a short design with alternatives, a migration plan that reaches completion, and a record linking decisions to measured consequences. Those deliverables make the intended skill observable; they do not prove a promotion outcome.

A promotion packet, sponsorship and glue work may matter in a specific organization. Verify the target employer's current framework and manager expectations rather than turning a personal narrative into a mandatory recipe. Our interview ledger explicitly retains gaps for current named-company lead loops and does not fill them with engineering blogs.