Stage 1 · Lesson 7 of 8
Monthly progress check-ins
only help if you look at them again. Set aside a short, regular slot for , such as 15 minutes in one a month. In it, you review your evidence against each expectation and decide what to work on next.
Bring a line or two per expectation: what you did, what changed and what is still missing. This shows your manager your progress long before . It also gives them time to find you the right work.
Common traptreating the promotion conversation as a once-a-year event. That is when you discover that the project you counted on did not show what you thought it would.
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