bootdotdev/curriculum: The Open Roadmap Behind Boot.dev's Backend Courses

A Public Roadmap for a Private Curriculum

bootdotdev/curriculum is a repository that documents the learning paths on Boot.dev, an online backend development learning platform. The README describes it as a 'living roadmap' for the curriculum. Unlike most curriculum repositories, it does not contain course materials, code exercises, or lessons. It contains markdown files that describe the sequence of topics and technologies that Boot.dev's courses cover.

The distinction between the repository and the platform matters. The repository is open: anyone can read it, file issues, and suggest changes. The actual courses are on Boot.dev at www.boot.dev. The repository is the planning document; the platform delivers the content.

Publishing the roadmap openly serves a practical purpose. Prospective learners can review what is covered before committing to the platform. Existing students can see what courses are coming next. The Boot.dev team accepts feedback through GitHub issues and through Discord. The README states the team is most responsive on Discord but can also be reached on X at @bootdotdev.

Four Active Paths and Four Planned Additions

The README lists seven learning paths. Three are available now, one is available now, and four are marked as work in progress or planned.

Active paths:

- Backend Developer Roadmap, available in two technology tracks: Python with Go, and Python with TypeScript. - Data Analyst Roadmap, available in a Python and SQL track. - DevOps Roadmap, available in a Python with Go track.

Planned or work in progress:

- AI Engineer Roadmap (wip/planned), Python. - Data Engineer Roadmap (wip/planned), Python and Go. - Fullstack Developer Roadmap (wip/planned), Python and TypeScript. - Computer Science Roadmap (wip/planned), Python and Go.

The README notes that all learning paths are made up of a series of courses. The Backend Developer path is the most mature, with two technology track options. Go appears across all active paths, which reflects Boot.dev's technology emphasis. TypeScript appears as a secondary language option in the Backend and planned Fullstack paths. SQL appears in the Data Analyst path.

The four planned paths indicate the direction Boot.dev intends to expand: AI engineering, data engineering, full-stack development, and a broader computer science sequence. The ordering of these additions is not documented.

How to Read the Roadmap

The repository structure is minimal. The top-level directory contains README.md and a paths/ folder. Each learning path has its own markdown file inside paths/: backend.md, data-analyst.md, devops.md, ai-engineer.md, data-engineer.md, fullstack.md, and computer-science.md.

To read the full course sequence for a path, open the corresponding markdown file on GitHub. The README links directly to the Boot.dev versions of each path for the available tracks. For example, the Backend Developer path links to www.boot.dev/paths/backend?tech=python-golang and www.boot.dev/paths/backend?tech=python-typescript, which are the platform versions with the full course sequences.

The markdown files in paths/ describe the same sequences in a format that can be read without a Boot.dev account. This is the primary value of the open repository: the course sequence is readable and shareable without requiring access to the platform.

The repository has no build process, no install step, and no executable code. It is a plain markdown documentation repository. The last push was on 2026-09-10, indicating the roadmap is actively maintained.

Boot.dev's Learning Philosophy as Stated in the README

The README addresses a likely concern directly: whether to start learning even though several paths are not complete. The answer given is yes. The reasoning is that the curriculum will never be 'complete' in the same way that YouTube will never be complete, since new content is added continuously.

This framing positions incompleteness as a feature rather than a gap. A learner who starts the Backend Developer path today is beginning a curriculum that is actively being extended, not one that is stalled. The implication is that completing the currently listed courses in a path is a meaningful and sufficient goal, even while more courses are being added behind it.

The README links to www.boot.dev/about/ for a fuller explanation of Boot.dev's approach to learning. The repository itself does not elaborate on the pedagogical philosophy beyond this single note, deferring to the platform's own documentation.

The philosophy applies across all paths. Even the planned paths (AI Engineer, Data Engineer, Fullstack, Computer Science) are published in the roadmap before they are complete, showing what Boot.dev intends to build and inviting feedback before the courses are finished.

Languages Covered Across the Roadmap

The roadmap covers three languages across its active paths: Python, Go, and TypeScript. Python appears in every path as a primary or foundational language. Go appears in the Backend Developer and DevOps paths as a second language. TypeScript appears as an alternative to Go in the Backend Developer path.

The Backend Developer path is the most flexible: a learner can choose the Python and Go track or the Python and TypeScript track, depending on which second language they want to focus on. The DevOps path uses Python and Go without a TypeScript option. The Data Analyst path uses Python and SQL rather than a general-purpose second language.

The planned paths continue this pattern. Data Engineer uses Python and Go. Fullstack uses Python and TypeScript. Computer Science uses Python and Go. AI Engineer uses Python only.

This language focus reflects a deliberate curriculum design choice: Python as a consistent foundation across all paths, with Go and TypeScript serving different career objectives. Go is positioned toward backend services and systems tooling; TypeScript is positioned toward web development and full-stack work. The roadmap does not cover JavaScript frameworks directly in the active paths, though the planned Fullstack path would logically include frontend topics.

What the Repository Lacks

The repository has no license documentation. The README does not state a license, and no license file is visible in the top-level directory listing. Without a stated license, the default copyright law applies: reproducing or adapting the roadmap content would require permission from Boot.dev. For a reader who only wants to read and use the roadmap as a reference, the license absence is not a practical concern.

The repository contains no course materials. Lesson content, exercises, projects, and assessments exist on the Boot.dev platform, not in this repository. A learner who wants to follow the curriculum must access Boot.dev directly. The repository is a map, not the territory.

There are no GitHub releases or version tags. Updates to the roadmap are tracked through git commits on the main branch. The changelog is the git log rather than a structured release history.

The AI Engineer, Data Engineer, Fullstack, and Computer Science paths are marked as wip/planned. The README does not give timelines for when these paths will become available.

roadmap.sh as the Publicly Contributed Alternative

roadmap.sh (github.com/kamranahmedse/developer-roadmap) is the most widely known open-source collection of developer roadmaps. It covers backend, frontend, DevOps, full-stack, and dozens of other specializations as visual diagrams and structured paths. It is community-contributed and not tied to a specific learning platform.

The key difference from bootdotdev/curriculum is purpose and source. roadmap.sh presents a broad view of what a developer in a given specialty might learn, drawn from community input across many learning resources and career paths. bootdotdev/curriculum is specifically the sequence of courses that Boot.dev intends to build and sell, representing one opinionated set of choices about what to teach and in what order.

A developer using roadmap.sh as a reference is mapping the territory of a specialty and deciding which resources to use for each topic. A developer using bootdotdev/curriculum is specifically evaluating the Boot.dev platform and its course progression. The two documents serve different planning purposes and are not mutually exclusive.

Editorial conclusion

Developers researching a structured, sequential path into backend engineering, data analysis, or DevOps will find the roadmap useful as a planning reference, regardless of whether they use Boot.dev as the learning platform. The repository provides a clear view of what Boot.dev covers and what it plans to add. Four paths (AI Engineer, Data Engineer, Fullstack, CS) are still marked as work in progress or planned. No license is documented in the repository. Before following the roadmap, open the individual paths/*.md files on GitHub to read the full course sequences for each path, since the README only lists the path names.

Frequently asked questions

Official sources

1. bootdotdev/curriculum on GitHub
2. Issues
3. Project website
4. README