Who This Course Is For

This course is for Senior engineers preparing for a Staff role, and for engineers who have recently become Staff. It teaches the work that separates the two levels. That work has three parts: judgment about which problems matter, scope beyond one team, and influence over people who do not report to you.

The course assumes that you know the basics of system design. You have shipped and operated production systems, and you have worked on a team. The course does not explain what a cache or a queue is. It does define every term that is not standard engineering vocabulary, where the term first appears. The rest of this page covers what the course teaches, what it leaves to other courses, and how to use it before an interview loop.

Two Rules the Course Follows

The course teaches Staff skills, not interview tricks. Most lessons describe how a Staff engineer actually does the work. Examples are turning a vague request into an agreed problem, writing a strategy, and disagreeing with another senior engineer. Staff interviewers look for evidence of exactly these skills. Learning the work is therefore the most reliable preparation for the interview.

Each skill lesson ends with how to use it in an interview. The body of the lesson teaches the skill and never mentions interviews. A short section near the end then shows what to say, often with a sample answer. It also gives the two follow-up questions you are most likely to hear. The last three chapters are different, because their subject is the interview itself.

What This Course Is Not

This course is not a collection of system design case studies. It uses one design at Staff depth to teach the decisions around architecture, such as non-goals, cost, and migration. For a broad set of worked case studies, Grokking the System Design Interview, Volume II covers twelve of them.

It is also not a general behavioral course. Grokking Modern Behavioral Interview teaches the STAR method and the common question families. This course adds only what a Staff answer must contain beyond them. Finally, it is not a salary course. It explains how to ask for the right level, and Grokking Tech Salary Negotiations covers pay.

What Each Chapter Teaches

Nine chapters follow this introduction. The first six teach skills, and the last three apply them to the interview.

How Each Lesson Is Built

A lesson opens with a concrete situation, a question, or a set of numbers. It then states the question it answers. Each section begins with a short definition or claim in bold. The mechanism follows, then a worked example with numbers, its costs and limits, and the cases where a simpler approach is better. Diagrams show processes, comparisons, and timelines.

Most lessons end with key takeaways and four practice questions. Try each question before you open its hidden answer. The three mock interviews end with a self-review checklist instead. Each chapter closes with a chapter assessment, and the course ends with a final exam.

One company appears throughout. It is an online marketplace with 400 engineers in 45 teams, about 180 services, and 12 million monthly buyers. Its central story concerns three job schedulers, built by three different teams, which together run 42,000 jobs a day. One of them ran a seller fee job twice. A Staff engineer in the platform group then led the work to replace all three with one. The same company and numbers return in many lessons. You can therefore see one problem from the angles of design, writing, influence, and judgment.

Using the Course Before a Loop

With several weeks before a loop, read the first chapter first. Every later lesson builds on its three differences between Senior and Staff. Then give most of your time to system design and the project deep dive. Those two rounds most often decide the level. The lesson The Staff Interview Loop suggests how to divide the hours.

While you read, choose one project of your own and apply each lesson to it. By the end, you should have a written problem statement and a decision record. You should also have one mistake you can describe precisely, and six to eight prepared stories. In the final week, take the three mock interviews under their time limits. Then check your answers against each mock's checklist.

Engineers who are already Staff can read the skill chapters in any order. Start with the one closest to a problem you face now.

Everything in the course rests on one comparison. The first lesson, Senior and Staff Engineers, shows how a Senior engineer and a Staff engineer handle the same incident.