What an L5 senior engineer actually does
An L5 (senior) engineer owns a service end to end - design, delivery and operation - and is judged on whether it works. It is the level at which supervision stops: the design is yours, and so is the outage.
L5 is where most engineers spend the longest, and it is a perfectly good place to stop. The step that follows is not about writing better code; the code is already fine. It is about the blast radius of the decision.
The most useful thing to do at this level is to get genuinely solid on the foundations that the next two rungs assume without ever teaching: how data is modelled and partitioned, how caches actually behave, and what happens when a dependency is slow rather than down.
What to actually study
Real modules from the curriculum, in the order they make sense. Every video each one points at is free.
- DeploymentThe Language of SystemsThe five behaviours every production system exhibits, stated as maths before they are stated as advice.6 lessons
- Everything DataData ModelingDesign data models that support analytics, feature engineering, training, and serving without leakage or excessive complexity.7 lessons
Common questions
- How long does it take to reach senior engineer?
- Commonly five to eight years, and it varies enormously by company and by how much scope was available to take. Time served is a poor predictor; evidence of owning something that mattered is the actual currency.
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