Promotion & leveling threads
Two high‑traction threads laid out a repeatable 'auto‑promo' framework for moving from junior to senior roles and clarified Senior vs Staff responsibilities—Seniors own team features, Staff drive cross‑team architecture and standards. Both pieces emphasize visibility, strategic tradeoffs, and preventing systemic problems. (x.com) (x.com)
Public leveling guides from companies that publish their ladders map “team-owned feature delivery” to senior IC expectations and “multi-team architecture, standards, and systemic fixes” to staff ICs, with Square explicitly describing scope and impact as the differentiator in its engineering growth framework. (developer.squareup.com) RFCs and formal design docs are the documented mechanism companies use to make cross-team tradeoffs visible: a curated library now hosts 1,000+ real design-doc examples and major orgs (HashiCorp, Google-style teams) use RFC templates to route decisions to stakeholders before implementation. (designdocs.dev) (hashicorp.com) Industry playbooks recommend a measurable “act-as-next-level” window of continuous behavior; a recent practitioner guide and a first‑hand promotion essay both suggest sustaining staff‑level signals for roughly 6–12 months before promotion is treated as routine rather than a leap. (freecodecamp.org) (jcmartinez.dev) Operational anti‑patterns the threads warned about—undocumented shortcuts, local hacks, and implicit ownership—are the same failure modes engineering blogs flag as causes of repeated incidents; pragmatists recommend arch reviews, playbooks, and runbooks to convert tribal knowledge into enforceable standards. (pragmaticengineer.com) (leaddev.com) Concrete repeatable moves that map to promotion evidence in public engineering handbooks: publish an RFC (mini or full) and gather written feedback, run a cross‑team spike with an implementation proposal, ship a library or standard and record 3+ peer reviews, then log the change in an org‑accessible changelog. (resend.com) (lambrospetrou.com) Leveling frameworks and skills matrices used in hiring and calibration explicitly tie promotion decisions to observable artifacts—impact narratives, cross‑team outcomes, and competency matrices—so promotion packets that include RFCs, incident metrics, and 360° feedback align with what calibration committees evaluate. (sprad.io) (peoplebox.ai)
