Stage 1 · Lesson 2 of 8
Handling ambiguity
is the gap between a vague problem and a plan someone can act on. "Checkout feels slow" is ambiguous. Now compare: "Checkout takes 4 seconds or more for the slowest 5% of visits (this is called ), the payment call takes 2.5 of those seconds, and here are three options."
That second version is something a team can act on. Handling ambiguity means closing that gap yourself. Ask who is affected, find the numbers, list the open questions, suggest options and decide what to try first.
Senior engineers are expected to do this without help. It is what lets someone hand you a problem instead of a , which is why it sits next to .
Common trapwaiting for someone else to break the work down, or jumping to a solution before the problem is clear.
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