What a backend developer does
The frontend is what a user sees. The backend is everything that makes it true: the database that stores an order, the code that checks a password, the API that returns search results, the queue that sends the confirmation email. At GoDesign the backend work ranges from custom WordPress plugins to Laravel services and Supabase functions behind React apps like the S-Line tracking platform.
The roadmap
- 01How the internet works: HTTP, DNS, TLS, what a request and a response contain. Everything else sits on this.
- 02An operating system: Linux basics, the terminal, processes, permissions, SSH. Servers are Linux.
- 03One language, properly: PHP, JavaScript (Node), Python or Go. Pick by the jobs you want; PHP and Node cover most agency work.
- 04Git: branches, pull requests, resolving conflicts. Non-negotiable in any team.
- 05Relational databases: SQL, schema design, indexes, joins. PostgreSQL or MySQL.
- 06A NoSQL store: Redis for caching and queues, MongoDB or similar for document data. Learn when not to use them.
- 07APIs: REST first, then GraphQL. Status codes, authentication, versioning, pagination.
- 08Authentication and authorisation: sessions, JWTs, OAuth, role checks. Where most real-world bugs live.
- 09Caching: HTTP caching, application caching, CDN behaviour. The cheapest performance win available.
- 10Testing: unit and integration tests, and the discipline to write them before the bug report.
- 11Security fundamentals: OWASP top ten, input validation, secrets management, rate limiting.
- 12A framework: Laravel, Express or NestJS, Django, or Go's standard library. Learn one deeply.
- 13Containers: Docker for reproducible environments; enough Kubernetes to read a manifest.
- 14CI/CD: GitHub Actions or similar, running tests and deploying on merge.
- 15Observability: logs, metrics, error tracking. If you cannot see it in production you cannot fix it.
- 16Cloud and serverless: one provider well (AWS, Google Cloud or a simpler host), plus edge functions such as Supabase or Cloudflare Workers.
How long it takes
Items one to eight are the minimum for a junior role and take most people six to twelve months of consistent practice. Nine to twelve come from working on real systems for a year or two. Thirteen to sixteen are what make a developer senior. Build projects at every stage: a to-do API, then an ecommerce backend, then something with users you do not know.
Common questions
- Which backend language should I learn first in 2026?
- JavaScript with Node if you also want frontend work, PHP if you want the largest pool of agency and WordPress jobs, Python if you lean towards data and automation. Any of them teaches the concepts that transfer.
- Do I need a computer science degree to be a backend developer?
- No. A degree helps with fundamentals like data structures, but a portfolio of working, deployed projects with tests and documentation carries more weight in most hiring, including ours.
- Is backend development still worth learning with AI coding tools?
- Yes. AI tools write code faster; they do not decide schema design, security boundaries or what to build. Those judgements are the job, and the roadmap above is how you develop them.
