Developer Roadmaps is the repo behind roadmap.sh, Kamran Ahmed’s community-driven collection of around 250 visual learning paths for developer roles and individual technologies. Each roadmap is a directed graph: nodes are skills, edges are “learn this before that.” Click a node, get a curated resource.
View Developer Roadmaps on GitHub
- 362,679 stars
- 44,669 forks
- TypeScript
- Custom license
Developer Roadmaps: The visual graph is the product
Every roadmap is a clickable SVG graph. Boxes are skills (“HTTP,” “CSS Grid,” “Docker,” “Kafka”). Lines between them show dependencies (“learn DNS before SSL,” “learn PostgreSQL before NoSQL”). Color coding tells you what is essential, what is nice-to-have, and what is optional. It’s the format every “learning path” should have been in for the last decade and most still aren’t.
Click any node and a side panel opens with curated links: official docs first, then the best free tutorials, then a good book or video. The curation is the value, not just the topology.
Role-based and skill-based, separate
Two families of roadmaps. Role-based covers “Frontend Developer,” “Backend Developer,” “DevOps Roadmap,” “AI Engineer,” “Prompt Engineer,” “Blockchain Developer,” “QA Engineer” (about 25 roles). Skill-based covers “JavaScript,” “Go,” “Python,” “SQL,” “System Design,” “Data Structures & Algorithms” (about 30 individual topics). Pick a role to learn the whole stack, or pick a skill to go deep on one thing.
The role maps are updated quarterly; skill maps are updated as the tech itself shifts (the Go roadmap now covers generics, the AI roadmap covers agents as of 2025).
The repo vs the site
The GitHub repo is the source of truth: every roadmap lives as a structured JSON spec plus an SVG/MDX render. The user-facing surface is roadmap.sh, which renders the same data with better navigation. You don’t need to clone the repo to use the roadmaps; you bookmark the site. The repo matters for contributing, requesting a new roadmap, or running the platform locally.
Best used with a deadline
The roadmaps are comprehensive to the point of being intimidating: “Backend Developer” has 80+ nodes. They work best when paired with a real target (a job interview in 4 months, a project you want to ship, a course that imposes a timeline). Without that, the roadmap becomes a procrastination surface: “I should learn Kubernetes next” forever. Pick one path, work it for three months, then re-evaluate.
Developer Roadmaps is the visual learning-path index. Use it to plan a track, then leave the site and do the actual work: the roadmap shows you the territory, it doesn’t walk it for you.