L5 vs L6: senior to staff, and what changes
L5 owns a service and is judged on whether it works. L6 owns a problem across services and is judged on what the solution costs the teams around it. The jump is not more code or bigger systems. It is that being locally right stops counting as being right.
The L5 to L6 gap is the one most engineers actually face, and it is described badly almost everywhere as "more impact". The sharper version: at L5 a clean design inside your service is a good design. At L6 a clean design inside your service that forces three neighbouring teams into a migration is a bad one, and noticing that before it ships is the level.
This changes what you have to be able to argue about. Partitioning, coordination, storage engine choice and failure behaviour stop being interview topics and become the vocabulary of the meetings you are now in. An L6 who cannot say why a design needs consensus, or why it does not, will not win those arguments however well they code.
The other half is unglamorous. At L6 you are expected to have an opinion about operations, because what the system does when a dependency is slow rather than down is a design question, and it is one L5 can often leave to somebody else.
What to actually study
Real modules from the curriculum, in the order they make sense. Every video each one points at is free.
- Everything DataData ModelingDesign data models that support analytics, feature engineering, training, and serving without leakage or excessive complexity.7 lessons
- DeploymentThe Language of SystemsThe five behaviours every production system exhibits, stated as maths before they are stated as advice.6 lessons
- Everything DataWarehouses & LakehousesUse modern warehouses and lakehouse technologies to store, query, optimize, and govern data for AI systems.7 lessons
- Everything DataStreaming & Real-TimeDesign and implement streaming data systems for low-latency features, real-time analytics, and event-driven ML applications.7 lessons
Common questions
- Is L6 hard to reach?
- At most large companies L5 is a terminal level and the majority of the individual-contributor ladder stops there, by choice or otherwise. L6 needs a problem worth owning across teams to actually exist on your surface, which is as much about where you sit as about how good you are.
- Do I need to become a manager to get past L5?
- No. The individual-contributor and management ladders run in parallel from L6 upward. What changes is the breadth of your technical influence, not whether anyone reports to you.
- What is the most common reason L5 to L6 stalls?
- Doing excellent work with no blast radius. Promotion at this step is evidenced by decisions that affected other teams, and an engineer who keeps being handed self-contained projects accumulates no such evidence no matter how well they execute them.
No course promotes anyone. Levels are awarded by employers against their own ladder, on evidence collected over months. What material like this can do is close a specific knowledge gap that is currently in the way.
Every level