Who this path is for
Choose this path if you want APIs, services, and data systems β including career changers who prefer server-side work over UI, and frontend developers adding a coherent backend track.
Career path
Build the systems that power products.
Pick a language, framework, and database. Add auth, APIs, and deployment. Substitutions are allowed β prerequisites stay visible.
9 skills Γ skill price (no separate path discount)
A backend developer builds the systems behind products: APIs, data models, authentication, business rules, and integrations. You make sure data is stored correctly, services stay reliable, and other apps (web or mobile) can consume what you expose.
Typical work includes designing endpoints, modeling tables or collections, writing validation and authorization, connecting to databases, logging and debugging failures, writing migrations, and deploying services. You use Git daily, read HTTP carefully, and document how teammates should call your APIs.
Choose this path if you want APIs, services, and data systems β including career changers who prefer server-side work over UI, and frontend developers adding a coherent backend track.
Basic programming concepts help; beginner language skills are included in the path.
Career roadmap
Destination: Backend developer Β· 9 courses in the default path Β· 5β8 months
Default track: Node.js / TypeScript Β· Express.js. Alternatives stay available when you customize.
Optional skills you can add β testing, deployment, auth, and related tooling.
Path projects, Experience Lab when you qualify, and portfolio evidence you can show.
Git, HTTP, and SQL come early because every backend stack depends on version control, the request/response model, and data. Language and framework come next so you build real services in Node, Python, or PHP. Database choice follows so persistence matches your stack. Auth, Docker, testing, and CI/CD are optional depth once a basic service runs end to end.
You learn to design routes, structure application code, handle errors, and keep secrets out of the repo. Frameworks accelerate delivery; foundations keep you from treating the framework as magic.
You practice schema design, queries, and ORM or query-layer patterns that match your language choice. APIs stay consistent: clear status codes, validation, and documentation so clients can integrate without guessing.
Toward the end of the path you run services outside your laptop β environment config, process management concepts, and optional containerization β so βit works on my machineβ is not the finish line.
Individual courses help you learn a technology. A Career Path gives those skills a sequence, connects them to a role, and shows what comes next β from foundations through practical work.
βI know JavaScript. What should I learn next?β
βHere is the sequence, why each skill matters, what comes next, and where I apply it.β
Core skills come first. Framework and ecosystem choices are customizable in the path builder. The roadmap above shows the same curriculum as a progression.
You should be able to design and ship APIs, persist data correctly, handle authentication basics, and deploy a service others can call β with GitHub history that shows how you got there.
Each skill is a focused course with tutor access. The path keeps prerequisites visible when you substitute stacks. Projects and code review matter more than collecting certificates.
API projects, data modeling exercises, and reviewed pull requests on path projects.
Documented APIs, schema decisions, and at least one deployed backend service with clear setup instructions.
Use path projects as portfolio evidence. Add frontend later via the Full-Stack path if you want end-to-end ownership, or move into Experience Lab supervised backend work when you qualify.
Supervised Experience Lab backend work, or add frontend via the full-stack path.