Backend Development Practice
Build the server side of an app in the framework you use at work: routing, request validation, data access and dependency injection. Pick your stack (Spring Boot, Django, FastAPI, Flask, .NET, Node.js with TypeScript, Laravel or Ruby on Rails); each challenge opens a starter project in a browser IDE and is graded by its tests. Two paths that don’t depend on a framework, REST API Design and Backend System Design, cover the decisions behind the code.
Backend
10 pathsFrom the blog
6Frequently asked questions
7Which paths are in this category?
10 paths: Backend System Design (8 challenges), .NET (24 challenges), Django (72 challenges), FastAPI (28 challenges), Flask (4 challenges), Laravel (8 challenges), Node.js (TypeScript) (16 challenges), REST API Design (3 challenges), Ruby on Rails (4 challenges) and Spring Boot (48 challenges).
How many challenges are there?
215 challenges across 56 modules. More modules are on the way.
Do I need to install anything?
No. Every challenge runs in a browser-based IDE with everything already set up, and your code is graded automatically against a test suite.
Can I practice in the framework I use at work?
Yes. There are paths for Spring Boot, Django, FastAPI, Flask, .NET, Node.js (TypeScript), Laravel and Ruby on Rails, so you can practice in the stack you already use.
Do I need to know the language first?
Yes, the basics. Each framework path expects you to write simple code in its language, for example basic Python for Django or basic Java for Spring Boot. No earlier experience with the framework is needed.
Is there anything beyond framework code?
Yes. REST API Design covers designing endpoints, and Backend System Design covers how the parts of a backend fit together. Both work alongside any framework path.
Can I use AI while I solve a challenge?
Yes, if you want to. Each challenge lets you choose how to work: with AI agents, with AI chat only, or with no AI at all.
