Reddit
Experience
·
2025 Q2
Neetcode 150 roadmap, but for System Design?
100 upvotes
4 replies
Interview Experience
I think everyone recognizes the value in the neetcode 150 roadmap but nothing like this exists for system design. I worked with some mentors from OpenAI, Amazon, Meta and Google to create something si
Full Details
I think everyone recognizes the value in the neetcode 150 roadmap but nothing like this exists for system design. I worked with some mentors from OpenAI, Amazon, Meta and Google to create something similar, a free open source **System Design Resource Tree**, organized so you can start at the root of the tree and go to the end to get familiar with all system design concepts in order and for free. The topics and the materials are based on system design interviews given at top tech companies. Since there are only 11 articles, it is only material I think is strictly required to pass a system design interview, no fluff or stuff I wouldn’t expect you to discuss in the actual interview. **Level 1 · Foundation** **About This Tree** \- how the map works and why it matters **Expectations by Level** – what interviewers really look for from junior through staff **Requirement Collection** – pulling out the key F‑/N‑FRs before you sketch a single box **Level 2 · Core Skills** **How to Be a Good Communicator** – narrate your thinking without rambling (yes, I put a behavioral article in the system design resource, it's that important) **Distributed System Communication** – async pub‑sub patterns that keep services loose and fast **API Design – Should You Do It or Skip It?** – when endpoints help (and when they burn time) **Entity Design** – lean, scalable data models that won’t bite you later **Database Overview** – SQL vs NoSQL, indexing, sharding, and the trade‑offs behind each call • **High‑Level Design** – the 10‑k‑foot blueprint that guides every deep dive **Level 3 · Mastery** **Microservice vs Monolith** – splitting vs staying whole, with real‑world cost/benefit math **Deep Dive** – moving from big picture to component contracts, one layer at a time **Workflow Engines** – orchestrating long‑running business flows without homemade cron chaos As always, shoot any feedback or questions my way. Happy designing! [https://easyclimb.tech/learning](https://easyclimb.tech/learning)
Free preview — Unlock all questions →
Topics
Trees
Sql
System Design
Networking