The skills backend engineers use on the job, from picking a language through databases, APIs, caching, infrastructure, scaling, reliability, and AI-assisted development. Start at the top and work down, basics first. Free to read, no signup required.
How to use this: tap a step on the map to open its details, skill pills, and guidance in a side panel. Work down the spine in order. Each stage assumes the ones above it. You don’t need to master every topic before moving on, and you never fully “finish”, since the field keeps moving. Aim for working competence, build things as you go, and come back to the harder topics when a real project or role calls for them.
Build a project: this is the part that sticks
Reading roadmaps doesn’t make you a backend engineer. Shipping does. Every topic above only becomes real knowledge once you’ve used it to build and run something. Projects are also what interviews and portfolios are built on: one thing you can explain in depth beats a stack of half-finished tutorials.
A URL shortener. It is small enough to finish, yet it touches routing, databases, caching, and rate limiting all at once.
A REST API for a to-do or blog app with real auth, then layer on pagination, tests, and a Docker setup.
A background job queue or worker that processes tasks asynchronously off the request path.
A thin end-to-end clone of a product you use, like a link-in-bio API or a bookmarking service, from database to deployed endpoint.
Deploy it somewhere public, put it on GitHub with a real README, and write down the trade-offs you made and why. One deployed, documented project you can talk through beats ten tutorials you followed along with.
Frequently asked questions
Consistency and real projects matter more than any schedule. From zero programming to job-ready is commonly 9 to 18 months of steady effort; if you already program, focused backend study can get you interview-ready in a few months. The people who make it are the ones who keep shipping, not the ones who pick the perfect schedule.
No. Foundations, web fundamentals, Git, databases, and APIs are the non-negotiable core. Caching, containers, orchestration, and advanced architecture you pick up as real roles and projects call for them. Nobody knows all of it equally, and senior engineers still look things up every day.
It varies enormously by country, city, company size, and seniority. Entry-level and senior at a large tech firm can differ several-fold, and the same title pays very differently across markets. Rather than quote a single number that’s wrong for most readers, check current listings for your specific location and level, and use Job Match to see how your profile stacks up against a real posting.
No. A degree helps with fundamentals and passes some hiring filters, but plenty of working backend engineers are self-taught or came through bootcamps. A portfolio of real, deployed projects plus solid fundamentals is what interviews test.
Any of the mainstream backend languages (see Foundations). Python or Node/TypeScript are the gentlest starting points; Go and Java are excellent and highly employable. The specific choice matters far less than getting good at one, because the concepts transfer.
A little helps you build complete projects and work well with frontend teams, and "full-stack" roles want both. But you can go deep on backend without becoming a frontend expert. Enough HTML, CSS, and JS to build and test your own APIs is plenty to start.
Get a personalized plan for real interviews
This page covers what to learn. When you’re ready to get hired, Interview Ready turns it into a personalized 30-day plan built around your resume and a specific target role: real practice in the right order (DSA, system design, behavioural), a guided Build-a-Project track alongside it, and progress tracking the whole way. Start free.
