The company opens the role describing the best coder it ever had. The interview measures algorithm exercises and counts years of experience. Six months later the team has a well-paid senior who delivers inside their own scope, and the organization stays stuck on the same architecture decisions.
The scope that separates the role from a senior
Will Larson writes about the shift that comes with the level in Staff Engineer (O'Reilly, 2021): the engineer answers for decisions that affect several teams, for patterns other teams adopt, and for mentoring that shows up in other people's work. Pay follows that scope change. Most interviews keep evaluating one team's work.
A company that posts the role without writing down the scope hands the candidate an empty promise. The candidate joins expecting organizational impact. The company gets individual impact.
Four hiring mistakes
- Evaluating on a coding exercise. A Staff Engineer spends little of the day on algorithms. Ask for the last design decision that changed how three teams work, together with what that decision cost.
- Counting years instead of impact. "15 years of experience" measures career length and says little about reach. Ask which pattern the person defined and how many teams adopted it.
- Defining scope after the offer. Without an agreed target (architecture migration, technical leveling across teams, platform), the person arrives and builds their own agenda. Eight weeks go to intent.
- Hiring full-time for a six-month problem. Migrations, assessments and launches run 3 to 6 months. A consultant with a fixed scope covers them without a permanent headcount cost.
Three questions that sort the candidates
"Tell me about a technical decision you made that changed how three or more teams work." A good answer names the decision, the teams affected and what changed after. A weak answer describes the technology chosen.
"When did you choose the slower delivery because it was right in the long term, and how did you bring the team along?" That answer shows influence without authority, and whether the person can carry a trade-off to product and sales.
"Which seniors have you developed, and what do they do today?" Mentoring leaves a trail: bigger scope, a promotion, a decision taken without you in the room.
The profile that changes the organization
The right candidate measures their own work by what happens around them. The pattern that became practice. The senior who now runs design review. The review that saved two weeks of rework. He writes the same decision in engineering language and in commercial language, and he knows which of the two sides has to read it.
Evaluate on that evidence. Within two quarters, the architecture decisions that used to reach you start resolving inside the teams.
