Stage 1 · Lesson 3 of 8
Impact over output
Output is what you produced: closed, merged, lines of code written. Impact is the difference it made. Examples: fewer failed payments, a release that takes 10 minutes instead of 2 hours, or a team that no longer gets woken at night by .
At most companies, promotion decisions are based on impact. Two engineers can close the same number of tickets and change very different things. Choosing starts with how you describe your work: "I did X, which changed Y, measured by Z." Measuring impact is also what the in a later stage depends on.
Common trapa busy calendar full of low-value work that feels productive, and describing your work as a list of activity with no result.
A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock
Resources for this stage
Start with
- GitHub repoFreePath to Senior Engineer Handbook
Jordan Cutler · Intermediate
Start with the sections on what senior means and how scope grows
Keep handy
Also worth your time
- Google Software Engineer Levels Explained: L3 to L10 and the Terminal Level (opens in a new tab)Read
How scope changes from L4 to L5 to L6 at a company with a well-documented ladder
The senior and tech lead parts, with concrete expectations at each level