What an L8 principal engineer does
An L8 principal engineer is accountable for technical direction at the scale of an organisation rather than of a problem. The work is largely deciding what an entire area should be doing over years, and being the person whose read of a technology the company is willing to bet on.
There is very little useful written about L8, because very few people are one and most of what circulates is extrapolation from L7. The honest description is that the deliverable stops being a decision and becomes a position: what this organisation believes about a technology, why, and what it is therefore not going to do.
That makes being wrong expensive in a way it is not lower down. An L7 who mis-sizes a technology loses a project. An L8 who does it loses a roadmap, and the credibility that made the position worth anything in the first place.
It is not a level to plan for. People arrive at it by having been repeatedly and publicly right about things that mattered, which is why the only preparation that makes any sense is being genuinely able to size the technologies you are asked about.
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
- Inference EngineeringThe Generation LoopUnderstand how an LLM produces text token by token --- from the forward pass and logits through sampling and stopping to the serving stack that puts it all in production.11 lessons
- Inference EngineeringThe Hardware FloorMeasure and model GPU performance from first principles --- throughput vs latency, FLOPs and bytes, the memory hierarchy, arithmetic intensity, the roofline model, and why decode is memory bound. By the end you can read a profiler trace and name exactly which regime your bottleneck lands in.12 lessons
- Everything DataData Versioning & ML ReproducibilityMake datasets, features, experiments, and model outputs reproducible across time, teams, and environments.7 lessons
Common questions
- What is the difference between staff, senior staff and principal?
- Staff owns a problem across teams. Senior staff owns which problem is worth solving. Principal owns the technical direction of an organisation, which problems exist at all. Each step widens what is under judgement rather than adding more of the same work.
- Is L8 the top of the engineering ladder?
- No, but it is the top of the part most people encounter. Above it sit distinguished engineer and fellow bands, which at most companies are a handful of people and function closer to appointments than to promotions.
- Can I aim for principal engineer?
- 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.
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