{"id":3737,"date":"2026-11-09T11:19:32","date_gmt":"2026-11-09T08:19:32","guid":{"rendered":"https:\/\/niteducation.com\/resources\/?p=3737"},"modified":"2026-11-09T11:19:41","modified_gmt":"2026-11-09T08:19:41","slug":"what-does-a-backend-developer-do","status":"publish","type":"post","link":"https:\/\/niteducation.com\/resources\/what-does-a-backend-developer-do\/","title":{"rendered":"What Does a Backend Developer Do? Skills &amp; Projects"},"content":{"rendered":"\n<article aria-labelledby=\"nit222-title\" class=\"nit-article nit-article--software nit-article--pathway-guide\" itemscope=\"\" itemtype=\"https:\/\/schema.org\/Article\">\n<meta content=\"en-KE\" itemprop=\"inLanguage\"\/><meta content=\"2026-11-09\" itemprop=\"dateModified\"\/><meta content=\"2026-11-09\" itemprop=\"datePublished\"\/><div aria-labelledby=\"nit222-title\" class=\"nit-pg-hero\">\n<div>\n<p class=\"nit-pg-kicker\">ICT CAREER GUIDE <span>BACKEND DEVELOPMENT<\/span><\/p>\n<p class=\"nit-hero__title\" id=\"nit222-title\" itemprop=\"headline\">What Does a Backend Developer Do?<\/p>\n<p class=\"nit-pg-hero__line\">Build <i>\u00b7<\/i> Test <i>\u00b7<\/i> Fix <i>\u00b7<\/i> Improve<\/p>\n<p class=\"nit-pg-hero__summary\" itemprop=\"description\">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.<\/p>\n<div class=\"nit-pg-hero__actions\"><a class=\"nit-pg-button nit-pg-button--gold\" href=\"#nit222-workflow\">Explore the developer&#8217;s task<\/a><a class=\"nit-pg-button nit-pg-button--outline\" href=\"#nit222-exercise\">Try the code exercise<\/a><\/div>\n<\/div>\n<div aria-label=\"A backend receives a request, applies server-side logic, and sends a response\" class=\"nit-pg-hero__art\">\n<p>BEHIND THE BUTTON<\/p>\n<div aria-hidden=\"true\" class=\"nit-pg-signpost\"><span class=\"nit-pg-signpost__top\">Request<\/span><span class=\"nit-pg-signpost__centre\">API<\/span><span class=\"nit-pg-signpost__bottom\">Response<\/span><\/div>\n<strong>The screen shows the answer. The backend makes the decision.<\/strong>\n<\/div>\n<div aria-label=\"Article overview\" class=\"nit-pg-hero__meta\">\n<p><span>Focus<\/span>Real backend responsibilities<\/p>\n<p><span>Practical example<\/span>Ticket check-in debugging<\/p>\n<p><span>Level<\/span>Beginner-friendly<\/p>\n<p><span>Updated<\/span>9 Nov 2026<\/p>\n<\/div>\n<\/div>\n\n<div class=\"nit-article__body\">\n<section aria-labelledby=\"nit222-answer-title\" class=\"nit-quick-answer\" id=\"nit222-answer\"><div class=\"nit-quick-answer__head\"><span aria-hidden=\"true\" class=\"nit-quick-answer__mark\">\u2713<\/span><div><p class=\"nit-quick-answer__label\">Quick answer<\/p><p class=\"nit-quick-answer__kicker\" id=\"nit222-answer-title\">What does a backend developer actually do?<\/p><\/div><\/div><div class=\"nit-quick-answer__body\"><p class=\"nit-quick-answer__text\">A <strong>backend developer<\/strong> 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. <a aria-label=\"Reference 1\" href=\"#nit222-ref1\">[1]<\/a><\/p><ul class=\"nit-quick-answer__signals\"><li>Build features and APIs<\/li><li>Manage application data<\/li><li>Protect information<\/li><li>Test and fix problems<\/li><\/ul><\/div><\/section>\n<p>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.<\/p>\n<div class=\"nit-facts-grid\"><div class=\"nit-fact-card\"><span>Role focus<\/span><strong>Server-side behaviour<\/strong><\/div><div class=\"nit-fact-card\"><span>Core tools<\/span><strong>Code \u00b7 APIs \u00b7 Data<\/strong><\/div><div class=\"nit-fact-card\"><span>Work evidence<\/span><strong>Projects + Tests<\/strong><\/div><\/div>\n<nav aria-label=\"Article contents\" class=\"nit-toc\"><h2>In this guide<\/h2><ol><li><a href=\"#nit222-day\">What a developer does at work<\/a><\/li><li><a href=\"#nit222-workflow\">Solve a real backend problem<\/a><\/li><li><a href=\"#nit222-exercise\">Try the small working API<\/a><\/li><li><a href=\"#nit222-examples\">More real-life examples<\/a><\/li><li><a href=\"#nit222-skills\">Skills and languages<\/a><\/li><li><a href=\"#nit222-projects\">Projects for your portfolio<\/a><\/li><li><a href=\"#nit222-roadmap\">Step-by-step learning route<\/a><\/li><li><a href=\"#nit222-career\">Careers and jobs in Kenya<\/a><\/li><\/ol><\/nav>\n<section aria-labelledby=\"nit222-fundamentals-title\" id=\"nit222-fundamentals\"><h2 id=\"nit222-fundamentals-title\">How does the backend work?<\/h2><p class=\"nit-section__lead\">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.<\/p><div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">Follow the request<\/p><p>Customer \u2192 Website \u2192 Backend \u2192 Database or other service \u2192 Backend response \u2192 Website. The frontend displays the interface; the backend decides how a request should be handled; the database stores and retrieves records.<\/p><\/div><div class=\"nit-concept-grid\">\n<div class=\"nit-concept-card\"><h3>Frontend<\/h3><p>The page and controls a person sees, such as a product page and Place Order button.<\/p><\/div>\n<div class=\"nit-concept-card\"><h3>Backend<\/h3><p>Checks the requested quantity, availability, permissions and order rules.<\/p><\/div>\n<div class=\"nit-concept-card\"><h3>Database<\/h3><p>Stores products, inventory and confirmed orders so they can be retrieved later.<\/p><\/div>\n<\/div><p>A backend is <strong>not<\/strong> 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 <a href=\"https:\/\/niteducation.com\/resources\/what-is-an-api-in-web-development\/\">What Is an API in Web Development?<\/a>. <a aria-label=\"Reference 1\" href=\"#nit222-ref1\">[1]<\/a><\/p><\/section>\n<section aria-labelledby=\"nit222-day-title\" id=\"nit222-day\"><h2 id=\"nit222-day-title\">What does a backend developer do each day?<\/h2><p class=\"nit-section__lead\">Daily tasks depend on the team and application. A working day usually combines investigation, programming, testing, documentation and collaboration.<\/p><div class=\"nit-career-grid\">\n<div class=\"nit-career-card\"><h3>Understand the request<\/h3><p>Read the work ticket, ask questions and define what successful software behaviour means.<\/p><\/div>\n<div class=\"nit-career-card\"><h3>Investigate the system<\/h3><p>Trace a request through the API and existing code; reproduce an error before guessing at its cause.<\/p><\/div>\n<div class=\"nit-career-card\"><h3>Develop a feature<\/h3><p>Write application logic or update an API or database operation to meet the requirements.<\/p><\/div>\n<div class=\"nit-career-card\"><h3>Protect data<\/h3><p>Validate requests and enforce who may see or change specific records.<\/p><\/div>\n<div class=\"nit-career-card\"><h3>Test and debug<\/h3><p>Check normal behaviour, invalid input, repeated requests and other failure cases.<\/p><\/div>\n<div class=\"nit-career-card\"><h3>Review and maintain<\/h3><p>Commit changes, discuss code reviews, prepare releases and investigate errors after deployment.<\/p><\/div>\n<\/div><div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">An important distinction<\/p><p>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.<\/p><\/div><\/section>\n<section aria-labelledby=\"nit222-workflow-title\" id=\"nit222-workflow\"><h2 id=\"nit222-workflow-title\">Example 1: fix a ticket that can be checked in twice<\/h2><p class=\"nit-section__lead\">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.<\/p><div class=\"nit-section-panel\"><h3>The task: one valid ticket, one entry<\/h3><p><strong>Problem:<\/strong> Two gate staff might scan the same ticket at almost the same moment. <strong>Expected behaviour:<\/strong> Only one valid check-in succeeds, and the result remains saved.<\/p><\/div><div class=\"nit-project-grid\">\n<div class=\"nit-project-card\" data-project=\"01\"><h3>Reproduce the bug<\/h3><p>Use fictional test tickets and follow the scan request to see whether two submissions can both pass.<\/p><\/div>\n<div class=\"nit-project-card\" data-project=\"02\"><h3>Define acceptance rules<\/h3><p>Approve an unused valid ticket; reject a used, invalid or wrong-event ticket; require authorised staff.<\/p><\/div>\n<div class=\"nit-project-card\" data-project=\"03\"><h3>Identify the data<\/h3><p>A ticket has a unique code, event assignment and check-in status. The system must save status changes durably.<\/p><\/div>\n<div class=\"nit-project-card\" data-project=\"04\"><h3>Implement safely<\/h3><p>Make the check-and-update operation concurrency-safe at the database layer, not only in JavaScript memory.<\/p><\/div>\n<div class=\"nit-project-card\" data-project=\"05\"><h3>Test failures<\/h3><p>Try duplicate scans, concurrent requests, missing permissions and database failures.<\/p><\/div>\n<div class=\"nit-project-card\" data-project=\"06\"><h3>Review and release<\/h3><p>Document the change, request code review, run regression tests and monitor after release.<\/p><\/div>\n<\/div><h3>A sample check-in request<\/h3><p>An authorised scanner might send <code>POST \/api\/tickets\/NIT-101\/check-in<\/code>. The backend checks permissions, event validity and whether the ticket has already been used. The frontend displays the outcome.<\/p><div aria-label=\"Scrollable comparison table\" class=\"nit-table-wrap\" role=\"region\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Scenario<\/th><th scope=\"col\">Example response<\/th><th scope=\"col\">Meaning<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">First valid scan<\/th><td><code>200 OK<\/code><\/td><td>Entry approved and stored<\/td><\/tr><tr><th scope=\"row\">Already-used ticket<\/th><td><code>409 Conflict<\/code><\/td><td>Do not allow another entry<\/td><\/tr><tr><th scope=\"row\">Unknown ticket<\/th><td><code>404 Not Found<\/code><\/td><td>No matching ticket<\/td><\/tr><tr><th scope=\"row\">Unauthorised scanner<\/th><td><code>403 Forbidden<\/code><\/td><td>Signed-in user lacks access<\/td><\/tr><\/tbody><\/table><\/div><p>These are illustrative API decisions. HTTP status meanings are defined in standard HTTP references. <a aria-label=\"Reference 2\" href=\"#nit222-ref2\">[2]<\/a><\/p><h3>The difficult part: two scans at the same time<\/h3><p>If the application separately reads a ticket and then updates it, two requests might both see \u201cunused\u201d before either change is saved. This timing problem is called a <strong>race condition<\/strong>.<\/p><div aria-label=\"Code example: PostgreSQL \u00b7 conditional check-in\" class=\"nit-code-window\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">PostgreSQL \u00b7 conditional check-in<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\"><span class=\"nit-code-comment\">&#8212; Simplified server-side database operation<\/span><\/span><span class=\"nit-code-line\">UPDATE tickets<\/span><span class=\"nit-code-line\">SET checked_in_at = CURRENT_TIMESTAMP<\/span><span class=\"nit-code-line\">WHERE ticket_code = $1<\/span><span class=\"nit-code-line\">  AND event_id = $2<\/span><span class=\"nit-code-line\">  AND checked_in_at IS NULL<\/span><span class=\"nit-code-line\">RETURNING ticket_code;<\/span><\/div><\/div><h3>Why this database update works<\/h3><p>The application supplies the ticket and event identifiers as parameters, verifies the scanner\u2019s 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. <a aria-label=\"Reference 3\" href=\"#nit222-ref3\">[3]<\/a> <a aria-label=\"Reference 4\" href=\"#nit222-ref4\">[4]<\/a><\/p><div aria-label=\"Scrollable comparison table\" class=\"nit-table-wrap\" role=\"region\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Test<\/th><th scope=\"col\">Expected result<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">One valid check-in<\/th><td>Approve once and save it<\/td><\/tr><tr><th scope=\"row\">Same ticket again<\/th><td>Reject without changing its status<\/td><\/tr><tr><th scope=\"row\">Two simultaneous scans<\/th><td>At most one approval<\/td><\/tr><tr><th scope=\"row\">Ticket for another event<\/th><td>Reject<\/td><\/tr><tr><th scope=\"row\">Staff account without permission<\/th><td>Reject<\/td><\/tr><tr><th scope=\"row\">Database unavailable<\/th><td>Do not falsely confirm entry<\/td><\/tr><tr><th scope=\"row\">Application restarted<\/th><td>Previously saved status still exists<\/td><\/tr><\/tbody><\/table><\/div><div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">What the developer has achieved<\/p><p>This one job involved understanding a requirement, investigating a defect, designing an API, changing database logic, enforcing permissions, testing, reviewing and maintaining software.<\/p><\/div><\/section>\n<section aria-labelledby=\"nit222-exercise-title\" id=\"nit222-exercise\"><h2 id=\"nit222-exercise-title\">Build a tiny backend in Node.js<\/h2><p class=\"nit-section__lead\">This local exercise shows how a server receives requests, returns JSON and refuses a second scan. Follow the steps in order.<\/p><div class=\"nit-section-panel\"><h3>Step 1 \u00b7 Prepare<\/h3><p>Install a supported Node.js LTS release from the <a href=\"https:\/\/nodejs.org\/en\/download\" target=\"_blank\" rel=\"noopener\">official Node.js website<\/a>. In Windows PowerShell, type <code>node --version<\/code> to check the installation.<\/p><\/div><div class=\"nit-section-panel\"><h3>Step 2 \u00b7 Create the project<\/h3><p>Make a folder called <code>ticket-backend<\/code>. Inside it, create <code>server.js<\/code> and paste the following JavaScript.<\/p><\/div><div aria-label=\"Code example: server.js \u00b7 beginner exercise\" class=\"nit-code-window\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">server.js \u00b7 beginner exercise<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\">const { createServer } = require(&#8220;node:http&#8221;);<\/span><span class=\"nit-code-line\">const tickets = { &#8220;NIT-101&#8221;: &#8220;unused&#8221; };<\/span><span class=\"nit-code-line\">\u00a0<\/span><span class=\"nit-code-line\">createServer((req, res) =&gt; {<\/span><span class=\"nit-code-line\">  const reply = (status, data) =&gt; {<\/span><span class=\"nit-code-line\">    res.setHeader(&#8220;Content-Type&#8221;, &#8220;application\/json&#8221;);<\/span><span class=\"nit-code-line\">    res.writeHead(status);<\/span><span class=\"nit-code-line\">    res.end(JSON.stringify(data));<\/span><span class=\"nit-code-line\">  };<\/span><span class=\"nit-code-line\">\u00a0<\/span><span class=\"nit-code-line\">  if (req.method === &#8220;GET&#8221; &amp;&amp; req.url === &#8220;\/health&#8221;) {<\/span><span class=\"nit-code-line\">    return reply(200, { status: &#8220;ok&#8221; });<\/span><span class=\"nit-code-line\">  }<\/span><span class=\"nit-code-line\">  if (<\/span><span class=\"nit-code-line\">    req.method === &#8220;POST&#8221; &amp;&amp;<\/span><span class=\"nit-code-line\">    req.url === &#8220;\/check-in\/NIT-101&#8221;<\/span><span class=\"nit-code-line\">  ) {<\/span><span class=\"nit-code-line\">    if (tickets[&#8220;NIT-101&#8221;] === &#8220;used&#8221;) {<\/span><span class=\"nit-code-line\">      return reply(409, {<\/span><span class=\"nit-code-line\">        message: &#8220;Already checked in&#8221;<\/span><span class=\"nit-code-line\">      });<\/span><span class=\"nit-code-line\">    }<\/span><span class=\"nit-code-line\">    tickets[&#8220;NIT-101&#8221;] = &#8220;used&#8221;;<\/span><span class=\"nit-code-line\">    return reply(200, {<\/span><span class=\"nit-code-line\">      message: &#8220;Entry approved&#8221;<\/span><span class=\"nit-code-line\">    });<\/span><span class=\"nit-code-line\">  }<\/span><span class=\"nit-code-line\">  return reply(404, {<\/span><span class=\"nit-code-line\">    message: &#8220;Not found&#8221;<\/span><span class=\"nit-code-line\">  });<\/span><span class=\"nit-code-line\">}).listen(3000, &#8220;127.0.0.1&#8221;, () =&gt; {<\/span><span class=\"nit-code-line\">  console.log(&#8220;Backend running on port 3000&#8221;);<\/span><span class=\"nit-code-line\">});<\/span><\/div><\/div><div class=\"nit-section-panel\"><h3>Step 3 \u00b7 Run the server<\/h3><p>In PowerShell, open the folder and run <code>node server.js<\/code>. You should see <code>Backend running on port 3000<\/code>.<\/p><\/div><div class=\"nit-section-panel\"><h3>Step 4 \u00b7 Send three test requests<\/h3><p>In a second PowerShell window, run the following commands <strong>one at a time<\/strong>.<\/p><\/div><div aria-label=\"Code example: PowerShell \u00b7 test requests\" class=\"nit-code-window\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">PowerShell \u00b7 test requests<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\">curl.exe -i http:\/\/127.0.0.1:3000\/health<\/span><span class=\"nit-code-line\">curl.exe -i -X POST http:\/\/127.0.0.1:3000\/check-in\/NIT-101<\/span><span class=\"nit-code-line\">curl.exe -i -X POST http:\/\/127.0.0.1:3000\/check-in\/NIT-101<\/span><\/div><\/div><div aria-label=\"Scrollable comparison table\" class=\"nit-table-wrap\" role=\"region\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Request<\/th><th scope=\"col\">Expected HTTP status<\/th><th scope=\"col\">Expected message<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Health<\/th><td><code>200<\/code><\/td><td><code>{\"status\":\"ok\"}<\/code><\/td><\/tr><tr><th scope=\"row\">First check-in<\/th><td><code>200<\/code><\/td><td><code>Entry approved<\/code><\/td><\/tr><tr><th scope=\"row\">Repeated check-in<\/th><td><code>409<\/code><\/td><td><code>Already checked in<\/code><\/td><\/tr><\/tbody><\/table><\/div><p>You can also try <code>curl.exe -i http:\/\/127.0.0.1:3000\/missing<\/code> to see a <code>404<\/code> response. This exercise uses Node.js\u2019s built-in HTTP module. <a aria-label=\"Reference 5\" href=\"#nit222-ref5\">[5]<\/a><\/p><div class=\"nit-callout nit-callout--warning\"><p class=\"nit-callout__title\">What this exercise does not do<\/p><p>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\u2014not a real-world ticketing security system.<\/p><\/div><\/section>\n<section aria-labelledby=\"nit222-examples-title\" id=\"nit222-examples\"><h2 id=\"nit222-examples-title\">Two more real-life backend examples<\/h2><p class=\"nit-section__lead\">The exact rules change between applications, but the developer still needs to plan, implement, test and protect the result.<\/p><div class=\"nit-concept-grid\">\n<div class=\"nit-concept-card\"><h3>Example 2 \u00b7 Clinic appointments<\/h3><p>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\u2019s bookings.<\/p><\/div>\n<div class=\"nit-concept-card\"><h3>Example 3 \u00b7 Mobile-money order payment<\/h3><p>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.<\/p><\/div>\n<\/div><div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">The lesson across all three examples<\/p><p>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.<\/p><\/div><\/section>\n<section aria-labelledby=\"nit222-skills-title\" id=\"nit222-skills\"><h2 id=\"nit222-skills-title\">Which skills does a backend developer need?<\/h2><p class=\"nit-section__lead\">Learn a few essentials deeply before adding advanced tools. A beginner\u2019s first goal is a complete, small API that can be tested and explained.<\/p><div aria-label=\"Scrollable comparison table\" class=\"nit-table-wrap\" role=\"region\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Skill<\/th><th scope=\"col\">What to understand<\/th><th scope=\"col\">Practical proof<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Programming<\/th><td>Variables, functions, conditions, errors<\/td><td>A program that validates information<\/td><\/tr><tr><th scope=\"row\">HTTP + APIs<\/th><td>Routes, methods, JSON, status codes<\/td><td>Two useful API endpoints<\/td><\/tr><tr><th scope=\"row\">Databases + SQL<\/th><td>Tables, relationships, constraints, transactions<\/td><td>A record saved between restarts<\/td><\/tr><tr><th scope=\"row\">Security<\/th><td>Authentication, authorisation, validation<\/td><td>A rejected unauthorised action<\/td><\/tr><tr><th scope=\"row\">Testing + debugging<\/th><td>Normal, failure and regression tests<\/td><td>A documented defect and fix<\/td><\/tr><tr><th scope=\"row\">Git + collaboration<\/th><td>Commits, reviews, documentation<\/td><td>Readable project history<\/td><\/tr><tr><th scope=\"row\">Deployment<\/th><td>Configuration, logs, maintenance<\/td><td>An application another person can run<\/td><\/tr><\/tbody><\/table><\/div><h3>Which backend programming language should you learn first?<\/h3><div class=\"nit-concept-grid\">\n<div class=\"nit-concept-card\"><h3>JavaScript + Node.js<\/h3><p>Helpful if you want JavaScript on the frontend and backend.<\/p><\/div>\n<div class=\"nit-concept-card\"><h3>Python<\/h3><p>Used with frameworks such as Django and FastAPI.<\/p><\/div>\n<div class=\"nit-concept-card\"><h3>C# \/ ASP.NET Core<\/h3><p>A common option for APIs and organisational applications.<\/p><\/div>\n<div class=\"nit-concept-card\"><h3>Java, PHP or Go<\/h3><p>Also used for backend work, including frameworks such as Spring and Laravel.<\/p><\/div>\n<\/div><p>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.<\/p><\/section>\n<section aria-labelledby=\"nit222-projects-title\" id=\"nit222-projects\"><h2 id=\"nit222-projects-title\">Three backend projects for beginners<\/h2><p class=\"nit-section__lead\">Finish a useful, testable project and document it instead of collecting many unfinished tutorials.<\/p><div class=\"nit-project-grid\">\n<div class=\"nit-project-card\" data-project=\"01\"><h3>Project 1 \u00b7 School canteen menu API<\/h3><p>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.<\/p><\/div>\n<div class=\"nit-project-card\" data-project=\"02\"><h3>Project 2 \u00b7 Club membership backend<\/h3><p>Intermediate: register fictional members, reject duplicate membership numbers, update statuses and enforce staff permissions. Show success and failure tests.<\/p><\/div>\n<div class=\"nit-project-card\" data-project=\"03\"><h3>Project 3 \u00b7 Shop order and stock API<\/h3><p>Intermediate to advanced: receive stock, create orders, refuse insufficient quantities, handle repeated requests and test concurrent orders.<\/p><\/div>\n<\/div><p>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. <a aria-label=\"Reference 6\" href=\"#nit222-ref6\">[6]<\/a><\/p><\/section>\n<section aria-labelledby=\"nit222-roadmap-title\" id=\"nit222-roadmap\"><h2 id=\"nit222-roadmap-title\">How do you become a backend developer?<\/h2><p class=\"nit-section__lead\">Use checkpoints that show what you can do. There is no universal time limit or single educational route.<\/p><ol class=\"nit-list\"><li><strong>Learn programming<\/strong> \u2014 Write a small program that accepts data, validates it and returns a result.<\/li><li><strong>Understand the web<\/strong> \u2014 Explain HTTP methods, JSON, URLs and API responses.<\/li><li><strong>Create your first API<\/strong> \u2014 Run a server and demonstrate at least two routes and one error response.<\/li><li><strong>Add persistent storage<\/strong> \u2014 Connect a database and confirm records survive a restart.<\/li><li><strong>Add security and tests<\/strong> \u2014 Demonstrate a rejected unauthorised action and repeatable failure tests.<\/li><li><strong>Finish and document a project<\/strong> \u2014 Make the repository understandable, runnable and clear about your contribution.<\/li><li><strong>Apply your abilities<\/strong> \u2014 Seek supervised experience, internships, attachments and suitable entry-level roles.<\/li><\/ol><div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">Know when you are progressing<\/p><p>A useful milestone is being able to explain why a feature works, what can make it fail, and how you tested it\u2014not merely finishing a video course.<\/p><\/div><\/section>\n<section aria-labelledby=\"nit222-career-title\" id=\"nit222-career\"><h2 id=\"nit222-career-title\">Backend developer career path and Kenyan jobs<\/h2><p class=\"nit-section__lead\">Responsibilities generally grow from supervised changes to independently owned features and system design. Titles and promotion requirements vary between employers.<\/p><div aria-label=\"Scrollable comparison table\" class=\"nit-table-wrap\" role=\"region\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Career stage<\/th><th scope=\"col\">Common focus<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Learner<\/th><td>Basic programming, APIs, databases and small projects<\/td><\/tr><tr><th scope=\"row\">Intern \/ trainee<\/th><td>Supervised tasks, bugs and team workflows<\/td><\/tr><tr><th scope=\"row\">Junior developer<\/th><td>Smaller features, tests and reviews with guidance<\/td><\/tr><tr><th scope=\"row\">Mid-level developer<\/th><td>Independent features, diagnosis and design choices<\/td><\/tr><tr><th scope=\"row\">Senior developer<\/th><td>Complex solutions, code reviews and mentoring<\/td><\/tr><tr><th scope=\"row\">Technical lead \/ architect<\/th><td>System design, larger decisions and coordination<\/td><\/tr><\/tbody><\/table><\/div><h3>What do Kenyan employers actually ask for?<\/h3><p>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. <a aria-label=\"Reference 7\" href=\"#nit222-ref7\">[7]<\/a><\/p><p>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. <a aria-label=\"Reference 8\" href=\"#nit222-ref8\">[8]<\/a><\/p><div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">Prepare evidence for the vacancy<\/p><p>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.<\/p><\/div><h3>What might an interviewer ask?<\/h3><p>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.<\/p><\/section>\n<section aria-labelledby=\"nit222-faq-title\" id=\"nit222-faq\"><h2 id=\"nit222-faq-title\">Frequently asked questions<\/h2><div class=\"nit-faq\"><details class=\"nit-faq__item\"><summary>Is backend development suitable for a complete beginner?<\/summary><div class=\"nit-faq__answer\"><p>Yes. Start with programming fundamentals, HTTP and one small API. Add a database, access control and testing gradually.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Does every website need a backend?<\/summary><div class=\"nit-faq__answer\"><p>No. A static information website may not require custom server-side application logic. Accounts, shared records and centrally managed rules often do.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Must I learn frontend development first?<\/summary><div class=\"nit-faq__answer\"><p>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.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Is backend development just database development?<\/summary><div class=\"nit-faq__answer\"><p>No. Database work is one responsibility; backend developers also create APIs, apply business rules, implement permissions and test or maintain systems.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Can I become a backend developer without a degree?<\/summary><div class=\"nit-faq__answer\"><p>You can learn without a degree. Hiring requirements vary: some employers accept equivalent experience, while others require specified academic qualifications.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>How long does it take to become employable?<\/summary><div class=\"nit-faq__answer\"><p>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.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Will artificial intelligence replace backend developers?<\/summary><div class=\"nit-faq__answer\"><p>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.<\/p><\/div><\/details><\/div><\/section>\n<section aria-labelledby=\"nit222-related-title\" id=\"nit222-related\"><h2 id=\"nit222-related-title\">Related NIT learning guides<\/h2><ul class=\"nit-list\"><li><a href=\"https:\/\/niteducation.com\/resources\/what-is-an-api-in-web-development\/\">What Is an API in Web Development?<\/a> \u2014 understand requests and responses.<\/li><li><a href=\"https:\/\/niteducation.com\/resources\/what-is-a-database\/\">What Is a Database?<\/a> \u2014 learn how records are organised.<\/li><li><a href=\"https:\/\/niteducation.com\/resources\/front-end-vs-back-end-vs-full-stack-in-kenya\/\">Front-End vs Back-End vs Full-Stack in Kenya<\/a> \u2014 compare specialisations.<\/li><li><a href=\"https:\/\/niteducation.com\/resources\/how-to-become-a-software-developer-in-kenya\/\">How to Become a Software Developer in Kenya<\/a> \u2014 explore the wider career route.<\/li><li><a href=\"https:\/\/niteducation.com\/admissions\/\">NIT Admissions and Intakes<\/a> \u2014 registration and application guidance. <a aria-label=\"Reference 10\" href=\"#nit222-ref10\">[10]<\/a><\/li><\/ul><\/section>\n<section aria-labelledby=\"nit222-sources-title\" class=\"nit-sources\" id=\"nit222-sources\"><h2 id=\"nit222-sources-title\">References and further reading<\/h2><ol><li id=\"nit222-ref1\"><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Learn_web_development\/Extensions\/Server-side\/First_steps\/Introduction\" target=\"_blank\" rel=\"noopener\">MDN Web Docs \u2014 Introduction to the Server Side<\/a>. Server-side requests, processing and data.<\/li><li id=\"nit222-ref2\"><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Reference\/Status\" target=\"_blank\" rel=\"noopener\">MDN Web Docs \u2014 HTTP Response Status Codes<\/a>. HTTP response meanings.<\/li><li id=\"nit222-ref3\"><a href=\"https:\/\/www.postgresql.org\/docs\/18\/sql-update.html\" target=\"_blank\" rel=\"noopener\">PostgreSQL 18 Documentation \u2014 UPDATE<\/a>. Conditional updates and RETURNING.<\/li><li id=\"nit222-ref4\"><a href=\"https:\/\/cheatsheetseries.owasp.org\/cheatsheets\/Authorization_Cheat_Sheet.html\" target=\"_blank\" rel=\"noopener\">OWASP \u2014 Authorization Cheat Sheet<\/a>. Permission checks and access control.<\/li><li id=\"nit222-ref5\"><a href=\"https:\/\/nodejs.org\/api\/http.html\" target=\"_blank\" rel=\"noopener\">Node.js \u2014 HTTP Module<\/a>. Built-in Node.js HTTP server functions.<\/li><li id=\"nit222-ref6\"><a href=\"https:\/\/docs.github.com\/en\/account-and-profile\/tutorials\/using-your-github-profile-to-enhance-your-resume\" target=\"_blank\" rel=\"noopener\">GitHub Docs \u2014 Using Your GitHub Profile to Enhance Your Resume<\/a>. Technical portfolio documentation.<\/li><li id=\"nit222-ref7\"><a href=\"https:\/\/www.savannahinformatics.com\/careers\/openroles\/backend-developer\" target=\"_blank\" rel=\"noopener\">Savannah Informatics \u2014 Backend Developer<\/a>. Kenyan employer description of backend responsibilities.<\/li><li id=\"nit222-ref8\"><a href=\"https:\/\/saolixgroup.com\/careers\/full-stack-software-developer\/\" target=\"_blank\" rel=\"noopener\">Saolix Group \u2014 Full Stack Software Developer (29 October 2026)<\/a>. Recent Kenyan employer requirements for backend services and databases.<\/li><li id=\"nit222-ref9\"><a href=\"https:\/\/niteducation.com\/resources\/full-stack-software-development-course\/\">Newton Institute of Technology \u2014 Full-Stack Software Development Course<\/a>. Institutional training, attachment and tuition.<\/li><li id=\"nit222-ref10\"><a href=\"https:\/\/niteducation.com\/admissions\/\">Newton Institute of Technology \u2014 Admissions<\/a>. Official programme application route.<\/li><\/ol><p><strong>Reviewed:<\/strong> 9 November 2026. The ticket, clinic, shop and project exercises are illustrative cases, not reports of confidential organisational operations.<\/p><\/section>\n<section aria-labelledby=\"nit222-register-title\" class=\"nit-pg-enrol\" id=\"nit222-register\">\n<div class=\"nit-pg-enrol__copy\"><p class=\"nit-pg-eyebrow\">Your next practical step<\/p>\n<h2 id=\"nit222-register-title\">Learn to Build Backend Applications at Newton Institute of Technology<\/h2>\n<p>Study backend programming, APIs, databases, testing and deployment as part of NIT&#8217;s Full-Stack Software Development course. Our published programme includes eight months of training and at least three months of industrial attachment.<\/p>\n<\/div>\n<div class=\"nit-pg-enrol__details\"><p><span>Institutional training<\/span><strong>8 months<\/strong><\/p><p><span>Industrial attachment<\/span><strong>3+ months<\/strong><\/p><p><span>Published tuition<\/span><strong>KSh 90,000 <a aria-label=\"Reference 9\" href=\"#nit222-ref9\">[9]<\/a><\/strong><\/p><\/div>\n<div class=\"nit-pg-enrol__actions\"><a class=\"nit-pg-button nit-pg-button--gold\" href=\"https:\/\/niteducation.com\/admissions\/\">Register \/ Apply Now<\/a><a class=\"nit-pg-button nit-pg-button--outline\" href=\"https:\/\/niteducation.com\/resources\/full-stack-software-development-course\/\">Explore the Full-Stack Course<\/a><\/div>\n<p>Newton Institute of Technology \u00b7 Migori Town, Kenya<\/p>\n<\/section>\n<div class=\"nit-article__footer\"><p>Newton Institute of Technology \u00b7 ICT learning and careers \u00b7 Migori Town, Kenya \u00b7 9 November 2026<\/p><\/div>\n<\/div><\/article>\n","protected":false},"excerpt":{"rendered":"<p>ICT CAREER GUIDE BACKEND DEVELOPMENT What Does a Backend Developer Do? Build \u00b7 Test \u00b7 Fix \u00b7 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. Explore the developer&#8217;s taskTry the code exercise BEHIND THE BUTTON RequestAPIResponse The [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[30],"tags":[789,790,788],"class_list":["post-3737","post","type-post","status-publish","format-standard","hentry","category-ict","tag-backend-developer-responsibilities","tag-backend-developer-skills","tag-what-does-a-backend-developer-do"],"_links":{"self":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3737","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/comments?post=3737"}],"version-history":[{"count":1,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3737\/revisions"}],"predecessor-version":[{"id":3738,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3737\/revisions\/3738"}],"wp:attachment":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/media?parent=3737"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/categories?post=3737"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/tags?post=3737"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}