Roadmaps, so you learn things in an order that works.

A free overview of how to plan a preparation timeline, what to study in what order and how the rounds fit together. Read it before deciding what to buy or who to book.

A sequenced path through the engineering management loop, covering people scenarios, project execution, technical depth and the coding round that many managers are still asked to pass. A very different loop from an engineering one.

The full path through system design preparation, from the building blocks up through advanced designs and practice. Follow it in order instead of assembling a curriculum from scattered blog posts.

The ordered path through coding interview preparation, from data structure fundamentals to patterns to company-specific practice. Use it when you have the material but no idea what to do first.

A preparation track aimed specifically at the large tech company loop, where the bar on problem difficulty, communication and time pressure is higher than most. It sets the standard you are being measured against before you walk in.

A curated set of articles, talks and books about the part of the job that is not writing code: scope, influence, communication and ownership. Useful when you are technically solid, keep getting good reviews, and still cannot work out what is missing for the next level.

The multi month self study plan one engineer used to go from web developer to a large technology company, published as a checklist covering the whole computer science foundation. Enormous, free, and honest about how long it takes.

A short, opinionated guide naming the nine subjects that matter and exactly one book and one course for each. Its value is in everything it leaves out.

A complete undergraduate computer science curriculum assembled entirely from free online courses, sequenced with prerequisites and maintained by a community. A degree's worth of material at no cost, minus the accountability.

A visual map of the operations side, covering Linux, networking, containers, orchestration, infrastructure as code, continuous integration and observability. Useful for seeing how large the territory is before you commit.

A free map of what engineering management involves, covering people, process, delivery, technical judgement and the business side. Useful mainly for finding out whether you actually want the job.

A visual map of front end skills with the essentials marked separately from the optional branches, which is what stops it becoming an anxiety generator. Use it as an audit, not a syllabus.

The backend counterpart, covering languages, databases, caching, APIs, authentication, testing and deployment, with the required parts marked. A useful map of the territory between writing endpoints and running a service.

A free dependency graph of coding interview topics, showing which subjects unlock which and giving each one a small problem set. It answers what to study next better than any list, and costs nothing.

A free visual map of what an AI engineer is expected to know, separating the model training path from the far more common path of building products on existing models. Useful for working out which skills your target role actually wants.

A free visual dependency map of system design topics, showing what to learn and in what order, with progress you can tick off. Useful mostly as a checklist to find the gaps in what you already know.