Growing your scope

Promotion is mostly a story about scope. Titles track how large a problem you can be trusted with, how little clarity you need to start, and how far your decisions ripple. Years and lines of code are weak proxies.

This page is the map. The pages below are the rungs: what scope looks like day to day, where high-leverage work hides, how to volunteer without fragmenting, and how to make impact visible so promotion committees can see it.

Leverage is impact per hour. The engineer who still waits for well-specified tickets after three years is stuck at junior scope. The engineer who finishes a multi-week feature, then asks what painful problem the team should tackle next, is already practicing SDE2. The jump after that is a problem that crosses teams — playbooks, shims, sequenced rollouts — not a harder ticket.

Concepts in this section

Read them in order.

Step	Concept	What it answers
1	The scope ladder	What does each rung own, and what does a jump look like?
2	High-leverage work	Where do you find work worth that scope?
3	Volunteering for scope	How do you take it on without starting five things?
4	Making impact visible	How do you leave evidence calibration can use?

A weekly rhythm

Weekly: ask "what is the most expensive recurring pain I can see?" Write one bullet in the brag doc for anything you shipped or unblocked.

Monthly: review your ladder with your manager. Name the rung you are practicing and the evidence you still lack. Ask for a project that fills the gap — or propose one with the half-page template.

Quarterly: pick one finishable growth project. Defend it against drive-by work. Ship it. Demo it. Write it up.

People who wait to be tapped for scope often wait forever. People who grab scope without finishing earn the wrong reputation. The middle path is propose → contract → finish → broadcast. Talk about the work in scope language — "I owned X end to end," "I aligned three teams on Y," "I moved metric Z from A to B" — because that is how ladders are read.

Common mistakes

Ticket hero. Always available, never building project muscle.
Secret owner. Production stays up, calibration sees nothing.
Scope hoarding. Five starts, zero finishes, reputation for unreliability.
Waiting for a ticket labeled "promo project." High-leverage work hides in pain.

Key takeaways

Scope is the main axis of level: task → feature → project → multi-team problem.
High-leverage work hides in on-call themes, stuck metrics, roadmap gaps, and team friction.
Finish before expanding. Volunteer for the gap your next level requires, with an explicit success metric.
Impact that is not written down, measured, or demoed often does not exist in calibration.