About

A map of what a senior engineer is expected to know, with the best thing to read about each of it.

573 topics74 subsections1,415 curated links208 hours of reading

What it is

Preparing for senior engineering interviews means holding a wide surface area in your head — the browser, React, backend design, databases, distributed systems, and increasingly how to actually build with models. The material exists, scattered across bookmarks, tabs and half-remembered blog posts. There was no single place saying here is the set of things a senior engineer is expected to have a real grasp of, and here is where to go learn each one.

So: 8 sections, 74 subsections, 573 topics. Four levels and it stops there — the topic page is terminal, and depth comes from the 1,415 links out rather than from more nesting.

How the topics were chosen

One rule, applied to every page: a topic earns a page if it can plausibly come up in a real interview round, or if you need it to answer something that does. A topic is skipped if it is real but never asked — deep browser-engine trivia, deprecated APIs, framework history for its own sake.

That is why there is no algorithms grind here and why the AI and LLM section is as large as it is. It is also why every page has to say what the thing is and why it matters: a definition you cannot motivate is a definition you will not hold under a follow-up question.

How it is built

Markdown files in a folder, read at build time. Every page in the map is prerendered as static HTML — there is no database behind the content, no CMS, and no admin UI. The whole tree is on GitHub, so the content reads as files there and renders as pages here.

A script checks every outbound link on a schedule, which is the only reason a map of 1,415 links stays worth trusting. Link rot is the failure mode a resource like this actually dies of.

What it knows about you

No accounts, no sign-up, no comments. Nothing you do here is stored against you.

Google Analytics is used to count visits, which is how I know whether any of this is read. It sets cookies and reports aggregate page views; it is not tied to anything you do on the site, and there is no advertising integration.

Support this work

This is free and it stays free. What it costs is the time to keep 1,415 hand-picked links from rotting — every one of them is re-checked on a schedule, and link rot is what a resource like this actually dies of. If the map saved you an afternoon, you can put something toward the next one. Pay what you think it was worth.

Support this work

Who made it

Built by Prateek Rawat, originally for my own interview preparation, which is why it is opinionated. Writing it for one reader is what let it take positions; opening it up cost nothing.

Start reading →