gradovioSign up

Programming

A programmer writes and maintains the code that makes software work — websites, mobile apps, internal business systems, games, databases, embedded devices and everything in between. In practice you spend your time turning a described need (from a product manager, a client, or a colleague in another department) into working, tested code, and then fixing and improving it once people start using it. Most programmers in the UK work inside a team of developers, testers and designers rather than alone.

Approximate graduate salary

Typically around £25,000-£35,000 to start, though this varies widely. Smaller employers and those outside the major cities tend to sit at the lower end; London, finance, and some specialist technology firms sit well above it, and a few pay considerably more than that range.

What you'd actually do

  • Picking up 'tickets' (small, defined pieces of work) from a shared board, writing code to deliver them, and marking them done — most teams work in short cycles of a week or two, often called sprints
  • Reading and understanding existing code written by other people, which usually takes up more time than writing new code from scratch
  • Writing automated tests so that future changes don't silently break things, and fixing the tests that break when you change something
  • Raising a 'pull request' — submitting your change for other developers to read and comment on before it goes live — and reviewing other people's changes in return
  • Debugging: reproducing a reported fault, tracing it through logs and code, and working out whether it's your code, someone else's, or the data
  • Short daily team catch-ups (often 10-15 minutes standing up) plus occasional sessions to estimate upcoming work or discuss how a feature should behave
  • Talking to non-technical colleagues to pin down what they actually want, which is frequently different from what they first asked for

How graduates get in

  • Graduate schemes at large employers — banks, insurers, retailers, consultancies, telecoms, defence firms, the NHS and the Civil Service all run technology graduate intakes. Common route, usually with online coding tests and an assessment centre.
  • Direct application to a 'junior developer' or 'graduate software engineer' vacancy at a small or mid-sized company. Very common, often faster and less formal than a scheme, and frequently the only option outside the big cities.
  • Converting from a placement year or summer internship into a full-time offer — this is one of the strongest routes in, because the employer has already seen you code.
  • Degree apprenticeships in software engineering or digital technology solutions — an alternative to the graduate route rather than a follow-on, where you work and study towards a degree at the same time.
  • Postgraduate conversion courses (MSc Computer Science or Software Development) for graduates of unrelated subjects. Workable, but you'll usually need a portfolio of your own projects alongside the qualification.
  • Self-taught and bootcamp routes. Genuinely used in the UK market, especially for web development, but harder going than a CS degree route — employers will judge you almost entirely on what you can demonstrably build.

What employers ask for

  • A degree in computer science, software engineering or a closely related subject is the most common starting point, but it is not universal — maths, physics, engineering and other numerate subjects are widely accepted, and some employers take any degree subject if you can code.
  • Many graduate schemes ask for a 2:1; a meaningful number ask for a 2:2 or use no degree filter at all and screen on a coding test instead. Some still ask for UCAS points or A-level grades. This varies a lot by employer size and sector.
  • Demonstrable code. A GitHub profile, a dissertation project, a university group project, a game, a website for a friend's business — employers want evidence you have actually finished something, not just passed exams.
  • Fluency in at least one mainstream language. Which one matters less than you'd think, but Python, Java, JavaScript/TypeScript, C# and C++ cover most UK vacancies.
  • Most employers accept that you will arrive knowing little about their stack and train you. Some specialist areas are stricter — defence and some government work requires UK nationality and security clearance, and certain embedded or scientific roles want specific prior experience.
  • Professional certifications (cloud platform certificates, for example) are nice to have and sometimes paid for after you join, but are rarely an entry requirement.

Skills that matter

Reading other people's code

Almost all commercial programming is modifying a large existing system, so the ability to work out how unfamiliar code behaves is more valuable day-to-day than writing elegant new code.

Systematic debugging

When something breaks in production you need to narrow the problem down methodically from logs and evidence rather than guessing and changing things at random.

Version control with Git

Every team uses it to merge work from multiple people, and getting into a tangle with branches and merges is one of the most common ways new starters lose a day.

Breaking a vague request into small, deliverable pieces

Requirements usually arrive as a sentence from a stakeholder, and estimating and sequencing the actual work is a large part of being trusted with bigger tasks.

Writing clearly for non-programmers

You will regularly have to explain why something will take three weeks, or what a bug means for a customer, to people who do not read code.

Comfort with not knowing

The tools and frameworks change constantly, so the ability to pick up an unfamiliar technology from documentation without being taught it is the difference between a junior and a mid-level developer.

Where it leads

  1. Graduate or junior developer: supervised work on small, well-defined tasks with your code reviewed closely. Typically the first year or two, though formal graduate schemes often run to a fixed length of around two years.

  2. Software engineer / developer: you own features end to end, review others' code and are trusted to estimate your own work. Most people reach this point within a few years, but timelines vary widely by employer and how much responsibility you're given.

  3. Senior engineer: you design how a system should be built, mentor juniors and are the person consulted when something complicated goes wrong.

  4. The path then usually forks. One branch is technical — lead engineer, principal engineer, software architect, or specialising in an area like data engineering, security, cloud infrastructure or machine learning. The other is managerial — engineering manager, then head of engineering or technology director.

  5. Sideways moves are common and well-regarded: into product management, technical consultancy, developer relations, solutions architecture, or contracting and freelance work. Some programmers also move into founding or joining very early-stage startups.

What people get wrong

“You spend your day writing code.”

Writing new code is often a minority of the working day. Reading existing code, testing, reviewing colleagues' work, debugging, and meetings to clarify what's actually wanted take up a great deal of it.

“You need to be brilliant at maths.”

Most commercial programming — business systems, web applications, internal tools — needs logical thinking and care, not advanced mathematics. Heavy maths matters in specific niches such as graphics, cryptography, machine learning and scientific computing.

“It's a solitary job for people who'd rather not talk to anyone.”

It's a team sport. You negotiate with product people, explain trade-offs to managers, pair up with colleagues on tricky problems, and have your work critiqued in writing every week.

“Without a computer science degree you're locked out.”

The UK market is relatively open to career changers and non-CS graduates compared with professions like law or medicine, because employers can test your ability directly with a coding exercise. It's harder without the degree, but far from closed.

Where this varies

"Programming" covers hugely different working lives. At a product-led technology company you may release changes to live users several times a day with a lot of autonomy. In banking, insurance, healthcare or government you'll work under far heavier change-control, documentation and compliance requirements, and releases may be weeks apart. Defence, aerospace and parts of government require security clearance and sometimes UK nationality, and may involve older languages and long-lived systems. Embedded programming (code running on physical devices) is closer to electronics engineering; data and machine learning work is closer to statistics; games programming is notorious for demanding hours and competitive entry. Geography matters too — London has the deepest market, but Manchester, Edinburgh, Bristol, Cambridge, Leeds, Belfast and Cardiff all have substantial tech employment, and remote or hybrid working is more common in this field than in most graduate careers, though several employers have pulled back towards office attendance.

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.