Projects for Backend Developers
Backend projects are the capstone systems where separate skills are combined into working software. A URL shortener with analytics, an OAuth2 auth service, an event-driven order system, a multi-tenant SaaS API with rate limits and a RAG question-answering API each force real decisions about data models, security and failure handling.
Stage: Capstone and Career · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Projects
- Design a schema and API for a URL shortener with click analytics
- Implement OAuth2 login with refresh token rotation
- Process orders through queues with retries and idempotent consumers
- Isolate tenant data and apply per-tenant rate limits
- Write a README with architecture diagram and run instructions
Projects interview questions
How would you generate short codes in a URL shortener?
Common options are encoding an auto-increment id in base62, or generating random codes and checking for collisions. Base62 of a counter is compact and collision-free but guessable, while random codes are harder to enumerate. Distributed systems may reserve id ranges per node.
How do you separate data between tenants in a SaaS API?
Either keep a tenant id column on shared tables and always filter by it, use a schema per tenant, or a database per tenant. A shared schema is cheapest but needs strict enforcement, such as row-level security. Separate databases isolate more but cost more to operate.
Where Projects fits in the Backend Developer roadmap
Projects belongs to the Capstone and Career stage (intermediate level), which takes about 5 hours. Build real systems and prepare for interviews.
Other units in this stage
Back to the full Backend Developer roadmap