Newton Institute of Technology Logo
Newton Institute of Technology Building Your Dream Career

What Does a Backend Developer Do? Skills & Projects

ICT CAREER GUIDE BACKEND DEVELOPMENT

What Does a Backend Developer Do?

Build · Test · Fix · Improve

Explore what happens behind apps. Follow a developer fixing a real software problem, try a working beginner API, and discover the skills and career path.

BEHIND THE BUTTON

The screen shows the answer. The backend makes the decision.

FocusReal backend responsibilities

Practical exampleTicket check-in debugging

LevelBeginner-friendly

Updated9 Nov 2026

Quick answer

What does a backend developer actually do?

A backend developer builds and maintains the server-side software that processes requests, applies application rules, works with databases and connects services. They also test features, fix defects, enforce permissions and help keep applications dependable. Think of the code that checks a login, records an order or rejects a ticket that has already been used. [1]

  • Build features and APIs
  • Manage application data
  • Protect information
  • Test and fix problems

When someone buys a ticket online, the page may display a simple confirmation. Behind that message, software checks information, applies rules, records the result and returns a response. Backend developers design and maintain much of that work. You do not need any previous coding knowledge to understand the examples below.

Role focusServer-side behaviour
Core toolsCode · APIs · Data
Work evidenceProjects + Tests

How does the backend work?

Think of a shop where a customer orders two school bags. The screen receives the order, but server-side software must check the rules before confirming it.

Follow the request

Customer → Website → Backend → Database or other service → Backend response → Website. The frontend displays the interface; the backend decides how a request should be handled; the database stores and retrieves records.

Frontend

The page and controls a person sees, such as a product page and Place Order button.

Backend

Checks the requested quantity, availability, permissions and order rules.

Database

Stores products, inventory and confirmed orders so they can be retrieved later.

A backend is not the same as a database. It can also process scheduled tasks, integrate with external services and generate reports. Not every static website requires custom backend logic. For a deeper explanation of requests, see What Is an API in Web Development?. [1]

What does a backend developer do each day?

Daily tasks depend on the team and application. A working day usually combines investigation, programming, testing, documentation and collaboration.

Understand the request

Read the work ticket, ask questions and define what successful software behaviour means.

Investigate the system

Trace a request through the API and existing code; reproduce an error before guessing at its cause.

Develop a feature

Write application logic or update an API or database operation to meet the requirements.

Protect data

Validate requests and enforce who may see or change specific records.

Test and debug

Check normal behaviour, invalid input, repeated requests and other failure cases.

Review and maintain

Commit changes, discuss code reviews, prepare releases and investigate errors after deployment.

An important distinction

A professional developer may spend more time understanding and testing an existing application than writing brand-new code. The goal is correct software behaviour, not the number of lines typed.

Example 1: fix a ticket that can be checked in twice

Imagine a school sports event. A gate scanner occasionally accepts the same single-use ticket twice. You are the backend developer assigned to investigate and correct it.

The task: one valid ticket, one entry

Problem: Two gate staff might scan the same ticket at almost the same moment. Expected behaviour: Only one valid check-in succeeds, and the result remains saved.

Reproduce the bug

Use fictional test tickets and follow the scan request to see whether two submissions can both pass.

Define acceptance rules

Approve an unused valid ticket; reject a used, invalid or wrong-event ticket; require authorised staff.

Identify the data

A ticket has a unique code, event assignment and check-in status. The system must save status changes durably.

Implement safely

Make the check-and-update operation concurrency-safe at the database layer, not only in JavaScript memory.

Test failures

Try duplicate scans, concurrent requests, missing permissions and database failures.

Review and release

Document the change, request code review, run regression tests and monitor after release.

A sample check-in request

An authorised scanner might send POST /api/tickets/NIT-101/check-in. The backend checks permissions, event validity and whether the ticket has already been used. The frontend displays the outcome.

ScenarioExample responseMeaning
First valid scan200 OKEntry approved and stored
Already-used ticket409 ConflictDo not allow another entry
Unknown ticket404 Not FoundNo matching ticket
Unauthorised scanner403 ForbiddenSigned-in user lacks access

These are illustrative API decisions. HTTP status meanings are defined in standard HTTP references. [2]

The difficult part: two scans at the same time

If the application separately reads a ticket and then updates it, two requests might both see “unused” before either change is saved. This timing problem is called a race condition.

PostgreSQL · conditional check-in
— Simplified server-side database operationUPDATE ticketsSET checked_in_at = CURRENT_TIMESTAMPWHERE ticket_code = $1 AND event_id = $2 AND checked_in_at IS NULLRETURNING ticket_code;

Why this database update works

The application supplies the ticket and event identifiers as parameters, verifies the scanner’s authorisation, and confirms entry only when the permitted update returns a row. The ticket code needs an appropriate unique constraint. Real systems also need durable storage, appropriate transaction boundaries and failure handling. [3] [4]

TestExpected result
One valid check-inApprove once and save it
Same ticket againReject without changing its status
Two simultaneous scansAt most one approval
Ticket for another eventReject
Staff account without permissionReject
Database unavailableDo not falsely confirm entry
Application restartedPreviously saved status still exists

What the developer has achieved

This one job involved understanding a requirement, investigating a defect, designing an API, changing database logic, enforcing permissions, testing, reviewing and maintaining software.

Build a tiny backend in Node.js

This local exercise shows how a server receives requests, returns JSON and refuses a second scan. Follow the steps in order.

Step 1 · Prepare

Install a supported Node.js LTS release from the official Node.js website. In Windows PowerShell, type node --version to check the installation.

Step 2 · Create the project

Make a folder called ticket-backend. Inside it, create server.js and paste the following JavaScript.

server.js · beginner exercise
const { createServer } = require(“node:http”);const tickets = { “NIT-101”: “unused” }; createServer((req, res) => { const reply = (status, data) => { res.setHeader(“Content-Type”, “application/json”); res.writeHead(status); res.end(JSON.stringify(data)); };  if (req.method === “GET” && req.url === “/health”) { return reply(200, { status: “ok” }); } if ( req.method === “POST” && req.url === “/check-in/NIT-101” ) { if (tickets[“NIT-101”] === “used”) { return reply(409, { message: “Already checked in” }); } tickets[“NIT-101”] = “used”; return reply(200, { message: “Entry approved” }); } return reply(404, { message: “Not found” });}).listen(3000, “127.0.0.1”, () => { console.log(“Backend running on port 3000”);});

Step 3 · Run the server

In PowerShell, open the folder and run node server.js. You should see Backend running on port 3000.

Step 4 · Send three test requests

In a second PowerShell window, run the following commands one at a time.

PowerShell · test requests
curl.exe -i http://127.0.0.1:3000/healthcurl.exe -i -X POST http://127.0.0.1:3000/check-in/NIT-101curl.exe -i -X POST http://127.0.0.1:3000/check-in/NIT-101
RequestExpected HTTP statusExpected message
Health200{"status":"ok"}
First check-in200Entry approved
Repeated check-in409Already checked in

You can also try curl.exe -i http://127.0.0.1:3000/missing to see a 404 response. This exercise uses Node.js’s built-in HTTP module. [5]

What this exercise does not do

The ticket is stored only in memory. Restarting the program resets it. There is no login, database or multi-server coordination, so this is a local learning demonstration—not a real-world ticketing security system.

Two more real-life backend examples

The exact rules change between applications, but the developer still needs to plan, implement, test and protect the result.

Example 2 · Clinic appointments

A clinic must not allocate the same exclusive time slot to two patients. The backend checks staff schedules, applies a concurrency-safe booking rule, handles cancellations and prevents patients changing other people’s bookings.

Example 3 · Mobile-money order payment

A payment service may send the same notification more than once. The backend validates the provider message, checks the transaction reference, records the right order status and prevents accidental duplicate processing. It must never assume an unverified notification proves payment.

The lesson across all three examples

Backend work is not simply saving information. It is ensuring that an application makes correct decisions when people repeat actions, send invalid data, lose connectivity or use the system simultaneously.

Which skills does a backend developer need?

Learn a few essentials deeply before adding advanced tools. A beginner’s first goal is a complete, small API that can be tested and explained.

SkillWhat to understandPractical proof
ProgrammingVariables, functions, conditions, errorsA program that validates information
HTTP + APIsRoutes, methods, JSON, status codesTwo useful API endpoints
Databases + SQLTables, relationships, constraints, transactionsA record saved between restarts
SecurityAuthentication, authorisation, validationA rejected unauthorised action
Testing + debuggingNormal, failure and regression testsA documented defect and fix
Git + collaborationCommits, reviews, documentationReadable project history
DeploymentConfiguration, logs, maintenanceAn application another person can run

Which backend programming language should you learn first?

JavaScript + Node.js

Helpful if you want JavaScript on the frontend and backend.

Python

Used with frameworks such as Django and FastAPI.

C# / ASP.NET Core

A common option for APIs and organisational applications.

Java, PHP or Go

Also used for backend work, including frameworks such as Spring and Laravel.

No language is required for every job. Learn one well enough to build a database-backed API before trying several at once. Technologies such as Docker, cloud services and microservices can follow after you understand a simple application.

Three backend projects for beginners

Finish a useful, testable project and document it instead of collecting many unfinished tutorials.

Project 1 · School canteen menu API

Beginner: return menu items and prices, show one item by ID, and return a useful error for an unknown item. Start with sample data, then add a database.

Project 2 · Club membership backend

Intermediate: register fictional members, reject duplicate membership numbers, update statuses and enforce staff permissions. Show success and failure tests.

Project 3 · Shop order and stock API

Intermediate to advanced: receive stock, create orders, refuse insufficient quantities, handle repeated requests and test concurrent orders.

For each project, prepare a README explaining what it solves, how to run it, its API routes, database design, tests and known limitations. Use fictional data and never publish passwords or private customer records. GitHub provides useful guidance for presenting technical work. [6]

How do you become a backend developer?

Use checkpoints that show what you can do. There is no universal time limit or single educational route.

  1. Learn programming — Write a small program that accepts data, validates it and returns a result.
  2. Understand the web — Explain HTTP methods, JSON, URLs and API responses.
  3. Create your first API — Run a server and demonstrate at least two routes and one error response.
  4. Add persistent storage — Connect a database and confirm records survive a restart.
  5. Add security and tests — Demonstrate a rejected unauthorised action and repeatable failure tests.
  6. Finish and document a project — Make the repository understandable, runnable and clear about your contribution.
  7. Apply your abilities — Seek supervised experience, internships, attachments and suitable entry-level roles.

Know when you are progressing

A useful milestone is being able to explain why a feature works, what can make it fail, and how you tested it—not merely finishing a video course.

Backend developer career path and Kenyan jobs

Responsibilities generally grow from supervised changes to independently owned features and system design. Titles and promotion requirements vary between employers.

Career stageCommon focus
LearnerBasic programming, APIs, databases and small projects
Intern / traineeSupervised tasks, bugs and team workflows
Junior developerSmaller features, tests and reviews with guidance
Mid-level developerIndependent features, diagnosis and design choices
Senior developerComplex solutions, code reviews and mentoring
Technical lead / architectSystem design, larger decisions and coordination

What do Kenyan employers actually ask for?

A Nairobi backend role advertised by Savannah Informatics lists server-side code, APIs, relational databases, testing, debugging, documentation and collaboration. Its job description cites Go and Python among the preferred technologies. [7]

An October 2026 Saolix Group listing also specifies backend services and APIs, PostgreSQL and testing, although that full-stack role requires prior experience. These are examples of specific employers, not a universal national hiring rule. [8]

Prepare evidence for the vacancy

If the vacancy asks for APIs, show an API. If it asks for SQL, explain your tables and queries. If testing matters, show a failure you reproduced and fixed. Read the actual qualification and experience requirements.

What might an interviewer ask?

Be ready to explain what happens when a request reaches your application, where information is saved, how permissions are checked, what happens when a database fails, and which test proves a bug is fixed. Explain your own work rather than relying on a list of languages on your CV.

Frequently asked questions

Is backend development suitable for a complete beginner?

Yes. Start with programming fundamentals, HTTP and one small API. Add a database, access control and testing gradually.

Does every website need a backend?

No. A static information website may not require custom server-side application logic. Accounts, shared records and centrally managed rules often do.

Must I learn frontend development first?

You do not have to become a frontend specialist. Basic knowledge of web pages and browser requests helps you understand how users interact with your backend.

Is backend development just database development?

No. Database work is one responsibility; backend developers also create APIs, apply business rules, implement permissions and test or maintain systems.

Can I become a backend developer without a degree?

You can learn without a degree. Hiring requirements vary: some employers accept equivalent experience, while others require specified academic qualifications.

How long does it take to become employable?

It depends on your starting knowledge, consistent practice and job requirements. A course is one milestone; a tested project and the ability to explain it provide additional evidence.

Will artificial intelligence replace backend developers?

AI tools can assist with code and tests, but developers still need to verify requirements, correctness, security and behaviour. Do not expose confidential data or credentials to unauthorised tools.

References and further reading

  1. MDN Web Docs — Introduction to the Server Side. Server-side requests, processing and data.
  2. MDN Web Docs — HTTP Response Status Codes. HTTP response meanings.
  3. PostgreSQL 18 Documentation — UPDATE. Conditional updates and RETURNING.
  4. OWASP — Authorization Cheat Sheet. Permission checks and access control.
  5. Node.js — HTTP Module. Built-in Node.js HTTP server functions.
  6. GitHub Docs — Using Your GitHub Profile to Enhance Your Resume. Technical portfolio documentation.
  7. Savannah Informatics — Backend Developer. Kenyan employer description of backend responsibilities.
  8. Saolix Group — Full Stack Software Developer (29 October 2026). Recent Kenyan employer requirements for backend services and databases.
  9. Newton Institute of Technology — Full-Stack Software Development Course. Institutional training, attachment and tuition.
  10. Newton Institute of Technology — Admissions. Official programme application route.

Reviewed: 9 November 2026. The ticket, clinic, shop and project exercises are illustrative cases, not reports of confidential organisational operations.

Your next practical step

Learn to Build Backend Applications at Newton Institute of Technology

Study backend programming, APIs, databases, testing and deployment as part of NIT’s Full-Stack Software Development course. Our published programme includes eight months of training and at least three months of industrial attachment.

Institutional training8 months

Industrial attachment3+ months

Published tuitionKSh 90,000 [9]

Newton Institute of Technology · Migori Town, Kenya