What organizations hire Staff engineers to do
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
explain why an organization of 20 teams creates a role that belongs to no single team.
Planned topics
- Some problems sit between teams: nobody owns them, so nobody fixes them.
- A Staff engineer is paid to find, frame, and solve those problems, then hand the result back to the teams.
- Output is judged by outcomes for many teams, not by the amount of code you wrote.
- The title varies by company; the work (scope beyond one team) is what matters.
Draft outline details
Demonstration
a list of five Platform 2.0 symptoms (slow delivery, duplicated pipelines, repeat incidents, slow onboarding, three identity systems) with the column "which team owns this today?" mostly empty.
Check your understanding
Why is a problem that no team owns a Staff-level problem?
Show answer
Only someone with cross-team scope can frame it, and no team has the mandate or time.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.