UK

United Kingdom · Technology and data · Mid-Level (2-5 years)

Software Developer

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Start my Software Developer plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior Software Developer or Lead Developer
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Developer · Mid-Level Programmer · Backend Developer · Frontend Developer

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

ETCAL Level 3 NVQ Diploma in Engineering Technical Support ETC Awards Limited · Level 3 · covers 4 of 6 standards
EAL Level 3 NVQ Extended Diploma in Engineering Technical Support Excellence, Achievement & Learning Limited · Level 3 · covers 4 of 6 standards
EAL Level 3 Diploma in Advanced Manufacturing and Engineering - Technical Support Technician (Development Competence) Excellence, Achievement & Learning Limited · Level 3 · covers 4 of 6 standards
EAL Level 4 Diploma in Engineering and Advanced Manufacturing (Development Competence) Excellence, Achievement & Learning Limited · Level 4 · covers 2 of 6 standards
BCS Level 4 Diploma - Digital Modular Programme in Software Development BCS, The Chartered Institute for IT · Level 4 · covers 1 of 6 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Performing Low Level Programming for Engineering Software ETCAL Level 3 NVQ Diploma in Engineering Technical Support
Developing low level engineering software EAL Level 4 Diploma in Engineering and Advanced Manufacturing (Development Competence)
Software development Cambridge OCR Level 3 Alternative Academic Qualification Cambridge Advanced National in Computing: Application Development (Extended Certificate)
Software Developer BCS Level 4 Diploma - Digital Modular Programme in Software Development

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
Systems Fluency seeing the whole picture
Start my Software Developer plan, free
Your Plan Illustration

Built for Software Developer

4 units that map to this job, from the qualifications that cover it.

  1. Performing Low Level Programming for Engineering Software ETC Awards Limited · covers 4 of 6 standards Level 3
  2. Developing low level engineering software Excellence, Achievement & Learning Limited · covers 2 of 6 standards Level 4
  3. Software development Cambridge OCR · covers 1 of 6 standards Level 3
  4. Software Developer BCS, The Chartered Institute for IT · covers 1 of 6 standards Level 4
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

2AI and this work

Will AI change your work as a Software Developer?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • Prompt Engineering & LLM Integration
  • Observability & Distributed Tracing
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Software Developer plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Software Developer plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A software developer builds, tests and ships code for features, taking them from idea to working product. This role involves working mostly on your own, seeing how the code performs once people use it, and taking on feedback to improve it.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Version Control (Git & GitHub/GitLab) Intermediate

You'll use `git commit`, `push`, `pull`, `branch`, `merge` daily. You should be comfortable resolving simple to medium merge conflicts and understand basic branching strategies.

Python (Flask/Django) Intermediate

Writing and debugging functional backend code, building APIs, and integrating with databases. You'll be expected to follow existing patterns and contribute new features.

JavaScript/TypeScript (React/Node.js) Intermediate

Developing interactive frontend user interfaces with React, or building backend services with Node.js. You'll be working with existing components and building new ones.

Docker Intermediate

Running and interacting with existing Docker containers (`docker run`, `docker-compose up`) for local development. You should be able to write a basic Dockerfile for a simple application.

AWS (EC2, S3, CloudWatch) Basic

Deploying your code to existing EC2 instances, using S3 for basic file storage, and navigating the AWS console to check application logs in CloudWatch when debugging.

CI/CD Tools (Jenkins/GitHub Actions) Basic

Monitoring builds and troubleshooting basic pipeline failures. You'll understand the purpose of continuous integration and deployment, and how your code moves through the pipeline.

Databases (PostgreSQL/MySQL) Intermediate

Writing basic CRUD (Create, Read, Update, Delete) queries in SQL. You'll also use an ORM (Object-Relational Mapper) to interact with the database from your application code.

Project Management (Jira/Confluence) Intermediate

Working on tickets in Jira, updating status, logging time, and participating in sprint ceremonies. You'll also read and contribute to technical documentation in Confluence.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Technical Approach for a Feature Proposes options, but the Senior Developer decides. Decides on the approach for routine features within established patterns; consults Lead for novel problems or cross-cutting concerns. Defines the technical approach for complex features and major bug fixes, often influencing team standards.
Code Review Approval Cannot approve other developers' code. Focuses on learning from reviews. Can approve minor bug fixes or small, well-defined features from junior developers, under the guidance of a senior. Expected to provide constructive feedback. Full authority to approve code reviews for all team members, ensuring quality and adherence to standards.
Deployment Schedule Changes Escalates any potential delays to supervisor immediately. Can adjust minor deployment timings for their own features within a sprint, but must inform the team and Product Manager. Major changes require Lead approval. Has authority to adjust deployment schedules for team features, coordinating with Product and Operations.
Tool/Library Selection (Minor) Suggests tools, but the team decides. Can select minor libraries or tools for a specific task if they align with existing tech stack and pass security review, informing the team. Anything significant needs Lead approval. Evaluates and recommends new tools or libraries for team adoption, considering long-term impact and maintenance.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Cycle Time
The average time it takes for a task (like a bug fix or a small feature) to go from 'In Progress' to 'Done' in our project tracking system.
Target · Typically under 3 days

If you pick up a ticket on Monday and it's deployed by Wednesday, that's a good cycle time. We're looking for consistent, efficient delivery.

Pull Request Quality
The number of review comments on your Pull Requests (PRs) before they get approved and merged.
Target · Fewer than 10 comments on average

If your PR usually only gets 2-3 small suggestions, that shows your code is clear and well-structured. If it's getting 20+ comments, we'll need to work on clarity or understanding requirements.

Bug Rate
The number of major bugs (P1/P2) that are directly attributable to your code in a given sprint, discovered after deployment.
Target · Fewer than 1 major bug introduced per sprint

We all make mistakes, but consistently introducing critical bugs after your code goes live means we need to tighten up testing or review processes. Ideally, you're catching these before they hit production.

Test Coverage Contribution
The extent to which your new code or changes are accompanied by appropriate unit and integration tests.
Target · Maintain or improve test coverage for your areas of work

If you add a new feature, we expect to see new tests covering its functionality. If you fix a bug, we'd like to see a regression test added to prevent it from happening again.

Code Quality & Maintainability
How clean, readable, and well-structured your code is, making it easy for others (and future you) to understand and modify.
  • Positive feedback in code reviews about clarity and adherence to coding standards. Code is easy to debug and extend. You're not creating 'spaghetti code' that no one can follow.
Problem Solving & Independence
Your ability to tackle technical challenges, debug complex issues, and find solutions with minimal hand-holding.
  • You're asking smart questions after trying things yourself. You can articulate your thought process when debugging. You're not blocked for days on a single problem without seeking help.
Collaboration & Communication
How effectively you work with your team, share knowledge, and communicate technical concepts to non-technical colleagues.
  • You actively participate in sprint ceremonies. You give constructive feedback in code reviews. You can explain a technical problem to a Product Manager without using too much jargon. You're quick to offer help or ask for it when needed.
Proactive Learning & Growth
Your initiative in learning new technologies, improving your skills, and adapting to new tools or frameworks.
  • You're experimenting with new tech in your own time. You're suggesting improvements to our processes or tools. You're taking on tasks that challenge you and push your comfort zone.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Solving Interesting Technical Puzzles

You'll get a real kick out of figuring out why a complex system is behaving unexpectedly, or designing an elegant solution to a tricky data synchronisation problem. That 'aha!' moment is what you live for.

Spending an afternoon tracking down a subtle race condition in a multi-threaded application, then implementing a robust fix that prevents future issues.

Seeing Your Code Make a Real Impact

It's incredibly satisfying to know that a feature you built from scratch is now being used by hundreds or thousands of customers. You'll enjoy the direct feedback loop from users.

Shipping a new dashboard feature that helps our clients understand their data better, and then seeing positive comments in user feedback sessions.

Continuous Learning and Skill Development

You're always keen to pick up a new programming language feature, explore a different cloud service, or dive into a new design pattern. The idea of stagnation genuinely bothers you.

Volunteering to research and implement a new caching strategy using Redis, even if it means learning a new tool from scratch.

What frustrates people
  • The 'Works on My Machine' Problem: You'll spend hours debugging an issue that only appears in the staging or production environment, leading to frustrating dead ends. It's infuriating when it's fine on your laptop.
  • Vague Tickets & Scope Creep: You'll sometimes get a Jira ticket with a one-line description, which then balloons into a multi-week project after the Product Manager sees the first demo. Requirements can be a moving target.
  • Legacy Code Archeology: You'll be asked to fix a bug or add a feature to a 10-year-old codebase with no documentation, no tests, and the original author long gone. It's like being an archaeologist, but with code.
  • Waiting for Code Reviews: You'll finish a brilliant feature branch, only for it to sit for days waiting for a senior developer to approve your Pull Request, blocking your next task. It's a necessary evil, but annoying.
  • Tooling and Access Hell: Wasting half a day trying to get the right permissions, VPN access, or database credentials just to start working on a task. It's a common rite of passage, sadly.
  • The Urgent 'Quick Fix': Being pulled off your planned sprint work to handle an 'urgent' request from a stakeholder, which inevitably turns out to be more complex than described and completely derails your focus.
What this role does not give you
  • A perfectly structured, predictable work environment with no surprises. Expect some chaos.
  • The chance to always work on brand-new, 'greenfield' projects. You'll maintain existing systems too.
  • A role where you can avoid all meetings. You'll need to talk to people, honestly.
  • A place where you can just write code in isolation. Collaboration is key here.

8Who you work with

Your work directly impacts the stability, functionality, and user experience of our software. Every feature you build, every bug you fix, contributes to the overall quality of our product, which in turn affects customer satisfaction and retention. Essentially, you're building the engine that keeps the business moving.

Inside the business
  • Your immediate development team (other developers, QA engineers)
  • Product Managers (they'll give you the requirements)
  • Designers (they'll show you how it should look and feel)
  • Operations/DevOps (they'll help get your code into production)
Outside the business
  • Our customers (they're the ones using what you build, ultimately)

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • At least 2 years of hands-on experience in software development, building and deploying applications, or equivalent project experience.
  • Demonstrable proficiency in at least one modern programming language (Python, JavaScript/TypeScript, Java, C#, Go, etc.) and associated frameworks.
  • Experience with version control systems, specifically Git, and a good understanding of branching and merging.
  • A solid grasp of fundamental computer science concepts: data structures, algorithms, and object-oriented programming.
  • Experience working in an Agile development environment, participating in sprints and daily stand-ups.
  • The ability to write clear, concise, and well-tested code.

10What to practise next

Where the job is going, and what to do about it starting this week.

Advanced System Design & Architecture

As you gain experience, you won't just be building features; you'll be thinking about how those features fit into the larger system, how they scale, and how they interact with other services. This is a natural progression for a mid-level developer looking to move up.

Microservices vs. Monoliths · Event-Driven Architectures · Database Sharding & Replication · Caching Strategies · Fault Tolerance & Resilience Patterns

  • This week: Start reading 'Designing Data-Intensive Applications' by Martin Kleppmann (it's a classic for a reason).
  • This month: Take on a task that requires you to think about how a new feature will scale or interact with other services.
  • Month 2: Participate more actively in architectural discussions, even if it's just to ask clarifying questions.
  • Month 3: Propose a small architectural improvement for a service you work on, outlining the benefits and trade-offs.

Quick win: Whenever you build a new feature, ask yourself: 'What happens if this gets 100x more traffic? What if a dependency fails?'

DevOps & Infrastructure as Code (IaC)

The line between 'developer' and 'operations' is blurring. As a developer, you'll increasingly be responsible for the infrastructure your code runs on, using tools to define and manage it programmatically. This speeds up deployments and reduces errors.

Terraform / CloudFormation · Kubernetes Fundamentals · CI/CD Pipeline Authoring · Configuration Management (e.g., Ansible, Chef) · Cloud Security Best Practices

  • This week: Take an online course on Terraform or AWS CloudFormation basics.
  • This month: Volunteer to help the DevOps team with a small IaC task, even if it's just updating a configuration file.
  • Month 2: Try to containerise a personal project and deploy it to a basic Kubernetes cluster (e.g., Minikube).
  • Month 3: Work with your Lead to identify a part of our infrastructure that could be managed with IaC and start drafting a plan.

Quick win: Familiarise yourself with our existing Terraform or CloudFormation scripts. Ask a DevOps engineer to walk you through a deployment pipeline.

11Staying current once you are in

What people here do to keep up
  • Actively contribute to open-source projects or maintain a personal portfolio of coding projects on GitHub. It's a great way to showcase your skills and learn new ones.
  • Attend industry meetups, conferences (online or in-person), or webinars. Staying connected with the wider tech community is super important.
  • Dedicate time each week to learning new frameworks, libraries, or programming language features. We'll give you access to online learning platforms.
  • Seek out mentorship from senior developers, both within and outside our organisation. Learning from others' experience is invaluable.
  • Present on a technical topic to your team or a wider internal audience. It helps solidify your understanding and builds your communication skills.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering & LLM Integration

Competitors are already using Large Language Models (LLMs) to draft reports in minutes that used to take hours, or to generate code snippets. Developers who figure this out will outproduce their peers significantly. It's not future-tech; it's happening now.

  • Context Windows and Token Limits
  • Temperature Settings for Different Tasks
  • RAG (Retrieval Augmented Generation) Architectures
  • Output Validation and Hallucination Detection
  • Prompt Chaining for Complex Analysis

Observability & Distributed Tracing

As our systems become more complex and distributed (microservices, serverless), simply checking logs isn't enough. We need to understand the 'why' behind performance issues across multiple services, not just the 'what'. This is crucial for maintaining system health and debugging efficiently.

  • Metrics, Logs, and Traces (The Three Pillars)
  • OpenTelemetry
  • Service Mesh Concepts (e.g., Istio, Linkerd)
  • SLOs, SLAs, and SLIs
  • Chaos Engineering Fundamentals

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Agile Development (Scrum/Kanban)
  • Test-Driven Development (TDD) & BDD
  • SOLID Principles & Design Patterns
  • RESTful API Design & Consumption
  • Data Structures & Algorithmic Complexity
  • Secure Coding Practices

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Graduate Developer (Level 001)

    1-2 years

    Skills to master

    • Mastering the basics of our tech stack, understanding our codebase, writing well-tested code for small tasks, and actively participating in code reviews.

    You're ready to move on when

    • Consistently delivering assigned tasks with minimal supervision.
    • Proactively identifying and fixing minor bugs.
    • Contributing meaningfully to team discussions and ceremonies.
    • Demonstrating a strong grasp of core programming concepts and our chosen languages.
  2. 2

    Coding Bootcamp Graduate / Self-Taught Developer

    2-3 years of post-bootcamp/self-taught experience

    Skills to master

    • Building a strong portfolio of demonstrable projects, understanding best practices in a professional setting, and adapting to team-based development workflows.

    You're ready to move on when

    • A robust GitHub profile showcasing diverse projects and clean code.
    • Ability to articulate technical decisions and problem-solving approaches.
    • Experience collaborating on projects (even if open-source or personal team projects).
    • Familiarity with Agile methodologies and professional development tools.
  3. 3

    Developer from a Different Industry

    2-4 years of experience in a similar role in another sector

    Skills to master

    • Adapting to our specific tech stack and domain, understanding our business context, and translating existing skills to our environment.

    You're ready to move on when

    • Quickly picking up new technologies and tools specific to our company.
    • Demonstrating transferable skills in problem-solving and software design.
    • Successfully integrating into our team culture and development processes.
    • Proactively seeking to understand our industry and customer needs.

15Where this role leads

The long view: This work can lead to a lead developer role, shaping technical direction, or to engineering management, focused on people and delivery.

16Pay and demand

Pay & demand

Typical pay £56,914 a year Source: ONS Annual Survey of Hours and Earnings, 2025 (provisional), under the Open Government Licence v3.0

The figure is the median for full-time employees in the ONS occupation this job title codes to (Programmers and software development professionals), from the April 2025 survey, about six months old when published, as ASHE always is. It is that occupation's middle, not this role's. Half earn more.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Software Developer is actually changing.

Where it leads

Roles this leads to

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Performing Low Level Programming for Engineering Software, worked against Software Developer.

Performing Low Level Programming for Engineering Software Level 3

Applied to your work in Software Developer

This unit aims to equip learners with the ability to perform low level programming for engineering software applications, including developing, testing, and debugging code. Learners will demonstrate the ability to write efficient and optimised code and integrate it with higher-level components. Furthermore, they will understand the principles of low level programming languages and their applications in engineering.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Software Developer plan, free
See Your Progress Grow Illustration
Software Developer
  • Agile Development (Scrum/Kanban)
  • Test-Driven Development (TDD) & BDD
  • SOLID Principles & Design Patterns
  • RESTful API Design & Consumption
  • Data Structures & Algorithmic Complexity
  • Secure Coding Practices
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

17The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Software Developer is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior Software Developer (Level 003)

    3-5 years in this role

    You'll move from independently delivering features to leading complex workstreams, mentoring others, and making significant technical decisions.

    • System Design & Architecture Designing major components or services.
    • Performance Optimisation Deep understanding of profiling and optimising application performance.
    • Security Best Practices Leading the implementation of secure coding standards.
    • Advanced Debugging & Troubleshooting Resolving cross-service issues independently.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, as a developer, you spend a fair bit of time on repetitive tasks or sifting through documentation. Imagine getting that time back. AI isn't here to replace you; it's here to make you a far more efficient, impactful developer.

For a Software Developer, AI tools can become your personal pair programmer, your documentation assistant, and your test-writing buddy. They'll handle the grunt work, freeing you up to focus on the truly interesting, complex problem-solving that only a human can do. Frankly, if you're not using these, you'll be left behind.

Boilerplate Code Generation

Use tools like GitHub Copilot to instantly generate repetitive code snippets. Think functions for API calls, data transformation logic, or even entire configuration files. It's like having an autocomplete on steroids, saving you from typing out the same patterns over and over.

Code Explanation & Refactoring

Stuck trying to understand a confusing block of legacy code? Paste it into an AI tool (like Cursor or Copilot Chat) and ask it to explain what it does in plain English. Even better, ask it to suggest ways to refactor it for clarity and efficiency. It's a fantastic way to quickly get up to speed or improve existing code.

Unit Test Automation

After you've written a function, use an AI assistant to automatically generate a comprehensive suite of unit tests. This includes common cases, edge cases, and even tests you might not have considered. It dramatically speeds up your testing phase and improves code quality.

Documentation & Communication

Automatically generate documentation from your code comments (docstrings) or have AI write clear, concise Pull Request descriptions and commit messages based on your code changes. This saves you mental effort and ensures your communication is always spot-on, making life easier for your teammates.

Common questions

Common questions

How do you become a Software Developer?

Common routes in include Graduate Developer (1-2 years), Coding Bootcamp Graduate / Self-Taught Developer (2-3 years of post-bootcamp/self-taught experience) and Developer from a Different Industry (2-4 years of experience in a similar role in another sector). Times vary with prior experience.

Where can a Software Developer progress to?

This role can lead on to Senior Software Developer (3-5 years in this role), depending on the skills you build.

What new skills matter most for a Software Developer?

Increasingly, Prompt Engineering & LLM Integration and Observability & Distributed Tracing. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

18Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

 More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills involved apply across the tech industry. You could specialise further, in areas such as AI or site reliability engineering, move into a different product domain, or start your own venture. A solid foundation in software development opens many doors.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my Software Developer plan, free What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.