Acme Co · Engineering Division

Engineering Career Ladder

Eight levels covering both IC and Management tracks. Each entry defines scope of impact, technical expectations, collaboration behaviors, and the promotion signal your manager is looking for.

L1

Associate Engineer

Scope: assigned tasks with clear specs · 0–18 months

Technical

  • Learns codebase with guidance from senior engineers
  • Fixes well-scoped bugs; writes unit tests for own code
  • Understands the team's primary language, tools, and deploy process
  • Asks good clarifying questions before writing code

Collaboration

  • Pairs with senior engineers to ship features
  • Participates in code review as observer and learner
  • Communicates blockers to manager or tech lead promptly

Leadership

  • Accountable for own code quality within assigned tasks
  • Reads internal docs and design specs unprompted
Promotion signal: Completes assigned work independently with minimal oversight; no regressions in owned features for 2+ sprints; actively seeks more scope.
L2

Engineer I

Scope: feature-sized work with defined requirements · 1–3 years

Technical

  • Owns a feature end-to-end: design, implementation, test, deploy
  • Writes clear PRs with context; addresses review feedback completely
  • Identifies and surfaces technical debt within own work area

Collaboration

  • Works productively within team without close supervision
  • Participates in sprint planning and retrospectives constructively
  • Coordinates with QA and design to ship with quality

Leadership

  • Takes technical ownership of own work
  • Informally mentors interns and onboarding associates
Promotion signal: Ships features with consistent quality; reliable estimates; beginning to mentor others; seeking cross-team visibility.
L3

Engineer II

Scope: multiple features, some ambiguity · 3–6 years

Technical

  • Designs components and APIs used by the broader team
  • Reviews others' PRs with useful, actionable feedback
  • Proactively identifies risks before they become incidents
  • Owns debugging of complex, cross-layer issues

Collaboration

  • Coordinates cross-functionally with product and design
  • Represents the team in technical stakeholder discussions
  • Gives clear estimates and explains trade-offs plainly

Leadership

  • Actively mentors L1/L2 engineers in 1-on-1 or paired settings
  • Leads small technical projects end-to-end
  • Contributes to team norms and engineering culture
Promotion signal: Raises the technical bar for the team; known as the go-to for a specific domain; mentors consistently; shows readiness to operate at team-wide scope.
L4

Senior Engineer

Scope: team-wide impact · 5–10 years

Technical

  • Owns subsystems with complex domains; defines their long-term direction
  • Makes architectural decisions that affect the whole team
  • Sets technical quality bar — code standards, testing culture, incident response
  • Leads or participates in system design reviews

Collaboration

  • Technical voice in product roadmap and sprint planning
  • Bridges engineering and product/design on complex trade-offs
  • Interviews and evaluates engineering candidates

Leadership

  • Sets technical direction for the team
  • Has structured mentorship relationships with L2/L3 engineers
  • Drives delivery of large, multi-sprint projects
Promotion signal: Impact consistently exceeds the team boundary; writing RFCs that influence other teams; developing L3s into strong engineers; asking for broader scope unprompted.
L5

Staff Engineer

Scope: multi-team, cross-cutting concerns · 8–15 years

Technical

  • Authors RFCs that change practices across multiple teams
  • Leads architecture for systems shared by multiple product areas
  • Defines platform and infrastructure strategy
  • Identifies systemic risks before they affect production

Collaboration

  • Works across engineering, product, and design at org level
  • Aligns multiple teams on shared technical standards
  • Represents engineering in quarterly and annual planning

Leadership

  • Unblocks teams by resolving complex technical dependencies
  • Sponsors and advocates for L4 promotions
  • Contributes to engineering hiring bar and interview design
Promotion signal: Known outside Acme for technical contributions; shaping a technical domain that didn't exist before their involvement; multiplying the output of 3+ teams.
L6

Principal Engineer

Scope: org-wide technical strategy · 12+ years

Technical

  • Shapes the multi-year technical strategy for the engineering org
  • Solves problems that no one else can see or scope
  • Defines the technical vision that Acme engineering hires into

Collaboration

  • Trusted advisor to VP Engineering and CTO
  • Participates in M&A technical due diligence
  • Collaborates with external partners on technical integrations

Leadership

  • Multiplies the output of the entire engineering organization
  • Contributes to defining the career ladder itself
  • Builds a reputation that improves Acme's engineering hiring
Promotion signal: This level is awarded, not applied for. There is no clear Principal path — it is created by the person filling it.
EM

Engineering Manager

Scope: team of 4–8 engineers · transition from L3/L4 IC

People

  • Runs effective 1-on-1s focused on growth and unblocking
  • Gives clear, timely performance feedback
  • Hires well; raises the bar with each new team member
  • Handles PIPs and difficult performance conversations professionally

Delivery

  • Owns the team's quarterly commitments end-to-end
  • Removes blockers before they become misses
  • Reports status to leadership clearly and without spin

Culture

  • Creates an environment where engineers do their best work
  • Models the technical and behavioral bar expected of the team
  • Retains strong engineers; understands flight risks early
Promotion signal: Team ships reliably; engineers are growing; EM is absorbing increasing scope from their own manager and developing senior engineers.
SR EM

Senior Engineering Manager

Scope: multiple teams or complex org · 2–5 years management experience

People

  • Manages other Engineering Managers
  • Runs a healthy org: low regrettable attrition, high engagement
  • Sponsors ICs for Staff and Principal promotions

Strategy

  • Partners with product and design on roadmap and resourcing
  • Makes resourcing trade-offs across teams
  • Inputs to engineering org design and structure

Culture

  • Defines the engineering management culture for the org
  • Builds the interview and onboarding process for new EMs
  • Visible to engineers org-wide as a trusted, accessible leader
Promotion signal: Their EMs are growing; the org runs well even when the Sr EM is unavailable; contributing to engineering strategy at VP level.