roadmap.sh: A Developer Roadmap Collection
/developer-roadmap
roadmap.sh is a community-driven collection of step-by-step guides mapping what to learn across dozens of tech roles, from frontend and backend to DevOps and AI engineering. Each roadmap is an interactive diagram, not a static list. It's a map, not a course. Reach for it for a structured learning order; skip it if you want built-in exercises and lessons.
What is roadmap.sh?
roadmap.sh is the GitHub repository (nilbuild/developer-roadmap) behind the roadmap.sh website, holding community guides for developers who want a structured path through a tech skill or role. Each roadmap is an interactive diagram whose nodes link to a short write-up. The collection spans frontend, backend, DevOps, AI engineering, and cybersecurity, plus best-practices guides and self-test questions.
Key Features and Content
- โRole-based roadmaps for frontend, backend, DevOps, DevSecOps, full stack, and specialized paths like AI engineer, data engineer, and software architect.
- โLanguage and framework roadmaps for JavaScript, TypeScript, Python, Go, Rust, Java, PHP, React, Vue, Angular, Node.js, and more, each as its own clickable diagram.
- โInteractive best-practices guides on narrower topics: backend performance, frontend performance, code review, API security, and AWS.
- โSelf-test question sets for JavaScript, Node.js, React, backend, and frontend, meant to check and rate what you already know.
- โNewer additions for AI-era work: an AI Engineer roadmap, a Prompt Engineering roadmap, an AI Agents roadmap, plus roadmaps for Claude Code, OpenClaw, and Vibe Coding.
- โA get-started page for picking which roadmap fits you, since the list itself doesn't rank or prioritize the paths for you.
Who Benefits from roadmap.sh?
roadmap.sh suits developers early in a specific track, like someone moving from tutorials into a first backend or DevOps role, who wants an ordered list of subjects instead of picking randomly from blog posts. It also works for self-taught programmers who want to see how deep a field like AI engineering or system design actually goes before committing time to it, and for mentors who want a shared reference to point junior developers toward. It's less useful once you already know the shape of your field and just need in-depth material on one narrow topic, since the roadmap format is built for breadth, not depth.
Navigating Your Tech Career
- โขPlanning a move into a new specialty, like going from frontend into full stack or from generalist dev into DevOps, by following the relevant roadmap in order.
- โขPrepping for a technical screen with the JavaScript, Node.js, React, backend, or frontend question sets.
- โขBenchmarking your own skill gaps against a role's roadmap before applying for a job titled AI engineer or software architect.
- โขPicking a next language or framework using the per-language roadmaps for Python, Go, Rust, Java, and others as a checklist rather than starting from scratch.
- โขTightening team practices with the best-practices guides on code review, API security, and performance, without writing internal docs from zero.
Strengths
- โCovers a wide span of roles and stacks in one place, from frontend and backend to AI engineering and cybersecurity, so you're not hunting across many separate repos for a starting map.
- โEach roadmap is a clickable diagram rather than a wall of links, which makes it easier to see how topics relate to and depend on each other.
- โIncludes practical add-ons beyond the maps themselves: best-practices guides and self-test question sets for a handful of core topics.
- โActively extended to newer tracks like AI Engineer, Prompt Engineering, and AI Agents, not just the traditional web-dev roles.
- โPredictable repo structure (roadmaps/<slug>/content/<topic>@<id>.md) makes it easy to find exactly which file backs which topic if you want to fix one.
Considerations for Using roadmap.sh
- โณThe README doesn't list a license type inline; it points to a separate license file for details, so check that file yourself before reusing content commercially.
- โณContent depth varies by design: a roadmap node is a short markdown write-up, not a full lesson, so you'll often end up outside the repo to actually learn a topic in depth.
- โณThere's no stated update cadence or version history in the README, so you can't tell from the repo alone how current a specific roadmap is.
- โณThe number of roadmaps and best-practices guides is large enough that picking the right one takes judgment; the README's own get-started page exists because the list alone doesn't tell you where to begin.
- โณAs a community-maintained collection, the accuracy of any single topic write-up depends on whoever last edited that markdown file, which the README doesn't independently verify.
Other Learning Resources
Frequently Asked Questions
roadmap.sh's roadmaps, guides, and question sets on GitHub are free and open to read; the README doesn't mention any paid tier, so pricing for extra features on the live site isn't confirmed here.
roadmap.sh doesn't publish a fixed update schedule in its README, but merged pull requests sync to the live site automatically, and new roadmaps are continually being added alongside the existing set.
roadmap.sh accepts contributions through its contributing.md guide, covering adding content to existing roadmaps, proposing new roadmaps, suggesting edits, and opening issues to discuss ideas before you build them.
roadmap.sh's roadmaps span role-based tracks (frontend, backend, DevOps, full stack, software architect), language and framework tracks (JavaScript, Python, Go, React, Vue, and others), and newer areas like AI engineering, prompt engineering, and AI agents.
roadmap.sh has beginner-tagged variants of some roadmaps, like Frontend Beginner and Backend Beginner, but most pages assume you already know roughly what the field involves and want order, not an introduction from zero.
The README points to a separate license file rather than naming the license inline, so the exact terms aren't stated in the facts available here โ check that file directly before reusing content.
Related repositories
Still deciding about developer-roadmap?
One click hands the question to an AI along with this page โ see what it says about developer-roadmap.