Backend Developer
You build the part users never see — the APIs, the data layer, and everything that has to stay up.
No degree needed Moderate. Harder to see your progress than frontend, because nothing is visual until it breaks.
Can I actually do this?
A real no-degree route, though usually a slower one than frontend because progress is less visible early on. Hiring is portfolio-and-interview led: expect to be asked how you would handle failure, not just whether the happy path works.
Who it suits. People who enjoy correctness and are bothered by edge cases — the ones who ask what happens if this is called twice.
Runway. Months to employable if you build and deploy; the depth keeps coming for years.
Coming from frontend, support or sysadmin work? All three transfer — you already know how systems fail in practice. Frontend Developer
Also advertised as
The route
Four stations, in order. Each one is a thing you finish before the next matters.
-
Station one
Learn it free
Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.
FastAPI — the tutorial
Free to learn · no certificate
Builds a real API step by step, with validation and docs generated as you go. Free and open source; substantial rather than a quickstart.
Verified 2026-07-27
Node.js — introduction and learn
Free to learn · no certificate
The other dominant backend runtime, documented free by the project itself. Worth knowing which of the two your target employers actually run before you pick.
Verified 2026-07-27
PostgreSQL — the official tutorial
Free to learn · no certificate
Backends are mostly databases with opinions attached. Learning SQL properly early is the highest-leverage thing on this list.
Verified 2026-07-27
-
Station two
Attest strategically
Nothing here is worth buying. Backend hiring runs on a code interview and what you have shipped; there is no certificate employers ask for. If you want a paid target, a cloud credential is more useful than a language one — see the cloud engineer route.
Nothing here is worth paying for
No credential needed
Nothing here is worth buying. Backend hiring runs on a code interview and what you have shipped; there is no certificate employers ask for. If you want a paid target, a cloud credential is more useful than a language one — see the cloud engineer route.
Checked 2026-07-27
-
Station three
Prove it
A certificate says you passed a test. These say you can do the job.
An API that survives being used wrong
Build one with validation, sensible errors and rate limiting, then document what it does when called badly. The failure behaviour is the interesting part.
A schema you would defend
Design the data model for something real, with constraints and indexes, and write down what you traded off.
A deployment with a rollback
Ship it somewhere public and roll a version back on purpose. Everyone can deploy; fewer have undone one.
-
Station four
Get hired
Search these exact titles
Who hires for this. Product companies, agencies, fintech, anything with an app — the largest employer base in software alongside frontend.
Being able to talk about how something you built failed carries further than a clean demo. That is our reading of how these interviews run, not a statistic we have verified.
On salaryWe don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.
Where this route continues
- Cloud Engineer — toward infrastructure
- Data Engineer (AI/ML) — toward data pipelines
- Frontend Developer — sideways move
This page last verified 2026-07-27 · How we verify
FastAPI, Node.js and PostgreSQL docs all fetched and READ 2026-07-27 (10,873 / 6,860 / 2,205 chars visible).