Choose compounding projects for promotion

Promotion advice gets weird because people talk about “impact” like it’s a vibe. But the useful version is much simpler. Promotions tend to follow work that keeps paying off after you finish the first push. That is the core idea behind these career threads — choose projects that compound, then make sure the compounding is visible. ### What makes a project “compound”? A compounding project is one where the first win creates the conditions for the next win. Infrastructure that speeds up every team. A hiring loop that improves candidate quality every quarter. A planning process that reduces thrash for multiple orgs. The point is not that the project is huge. The point is that the return keeps accruing after the launch. Staff-level guidance describes this as work that affects many people, lasts over time, and changes how the organization operates — not just what one person shipped this sprint. (staffeng.com) ### Why doesn’t raw output get you there? Because promotions above senior usually stop rewarding local heroics. Past that point, companies look for leverage. One Staff engineer example from Google puts it bluntly — lower levels can succeed by building good technical solutions, but Staff is where accountability starts to include business strategy. That changes the game. The best story is no longer “I did a lot.” It is “I changed the system, and other people got faster because of it.” (staffeng.com) ### So what should you actually pick? Three filters show up again and again. First, system depth — the work touches architecture, process, or decision-making, not just one feature. Second, cross-team pull — other teams need to coordinate with you, which proves scope. Third, measurable business effect — latency down, revenue up, incidents down, hiring time down, customer pain reduced. If you cannot imagine the promotion packet bullet before you start, the project may be too fuzzy. (staffeng.com) ### Why does visibility matter so much? Because invisible leverage barely counts. Promotion guidance for Staff roles treats the packet less like a ceremonial write-up and more like a map you build over time. Basically, you should know what evidence the org will accept before you do the work. That means collecting outcomes, naming stakeholders, and making sure your manager understands why the project matters beyond your team. Great work hidden inside a subsystem often loses to slightly less impressive work that the organization can clearly see and retell. (staffeng.com) ### What if you’re choosing between IC and management? Do not treat management as the default upgrade. That is one of the clearest through-lines in modern engineering career advice. The IC path and the management path ask for different instincts. One is centered on technical and organizational leverage. The other is centered on people, staffing, prioritization, and team health. Good companies increasingly formalize both tracks and argue they should carry comparable status and pay. (staffeng.com) ### Why is that distinction important for promotion? Because the wrong ladder creates fake progress. If you move into management just to keep advancing, you can end up doing a job that drains you and makes the team worse. And if you stay IC while acting like a super-senior ticket closer, you stall for the opposite reason. The promotion question is really a fit question first — what kind of leverage do you want to own for years? (charity.wtf) ### What does this mean for a new manager? New managers usually need to stop grading themselves on personal output. The job shifts toward unblocking, staffing, feedback, and translating strategy into team motion. That can feel less tangible than coding or shipping, but turns out that is the leverage. Manager ladders frame the role as owning people and team effectiveness, while tech leads own the system. Mixing the two is possible, but confusing them is costly. (charity.wtf) ### Bottom line? If you want a promotion, pick work that keeps creating value after you touch it once. Then choose the ladder — IC or manager — that matches the kind of leverage you actually want to practice. That is the story companies promote. (staffeng.com) (github.com)