Application Support Developer

An Application Support Developer keeps the software that a business relies on running properly, and writes code to fix it when it doesn't. They sit between users who report problems and the systems those problems live in - investigating errors, patching bugs, running database queries and making small enhancements to live applications. Typical employers are banks, insurers, retailers, NHS trusts, universities, software vendors and IT managed-service providers.

Starting salary: £25k–£35k
Live graduate jobs: Search all jobs
Main way in: Technology graduate schemes at banks, insurers and large…
They usually ask for: A degree in computer science, software engineering, IT or a…

Approximate graduate salary

Typically around £25,000–£35,000 to start, though this varies widely - graduate schemes at large financial institutions and roles in London tend to sit at or above the top of that range, while smaller employers, public sector organisations and roles outside the South East often start lower. On-call or shift allowances can add meaningfully on top where they apply.

What you'd actually do

Working a queue of tickets raised by users or by automated monitoring - reading the error message, reproducing the fault, and deciding whether it is a data problem, a configuration problem or a genuine bug in the code
Writing and running SQL queries against production or test databases to check what the application actually did with a piece of data, and sometimes correcting bad data with a carefully reviewed script
Reading application logs and stack traces (the trail of error messages a program leaves when it crashes) to trace a failure back to the line of code or the integration that caused it
Making and testing small code fixes, putting them through version control and the normal release process, and writing up what changed

Show 3 more

Chasing overnight batch jobs and scheduled data feeds that failed - restarting them, patching the underlying issue, and telling the business when the data will be available
Talking to the people who reported the fault: confirming impact, agreeing priority, explaining in non-technical terms what went wrong and when it will be fixed
Updating the knowledge base and runbooks so the next person who sees the same fault can resolve it faster, and handing over open incidents at the end of a shift

How graduates get in

Technology graduate schemes at banks, insurers and large retailers - application support is a very common first rotation or first placement on these schemes, because it teaches you the estate quickly. This is a well-trodden route.
Direct entry as a junior/graduate application support analyst or developer, advertised year-round rather than in a fixed autumn cycle. Common at software vendors, IT service providers and public sector organisations, and often quicker to get into than a big scheme.
Moving across from a first-line IT service desk or infrastructure support role after picking up SQL and some scripting. This is a genuinely common internal route and employers take it seriously.
A summer internship or industrial placement year in IT, then converting to a graduate offer with the same employer - very common for sandwich-course computing students.

Show 2 more

Conversion routes for non-computing graduates: an MSc in computer science or software engineering, or a coding bootcamp plus demonstrable projects. Bootcamp entry works better for support-flavoured developer roles than for pure development roles, but it is not a guaranteed door.
Degree apprenticeships and school-leaver programmes exist in this space too, so you may find yourself working alongside colleagues who came in without a degree.

What employers ask for

A degree in computer science, software engineering, IT or a related technical subject is the most common ask - but plenty of employers accept any degree if you can show coding ability, and maths, physics and engineering graduates are frequently hired.
A 2:2 or 2:1 is the usual minimum, and this varies a lot: large graduate schemes often set 2:1 and sometimes UCAS points, while smaller employers and service providers frequently care more about a technical test than a classification.
Working SQL is close to universal for this role - more employers will test you on SQL than on anything else. Even a solid grasp of SELECT, JOIN and basic aggregation puts you ahead.
Familiarity with at least one programming language used in business systems - Java, C#/.NET, Python, JavaScript or PL/SQL are the common ones. The specific language is usually less important than showing you can read someone else's code.

Show 2 more

Some exposure to Linux/Unix command line, shell scripting or PowerShell, and to version control (Git). Not always mandatory at graduate level, but it comes up constantly on the job.
No professional exams are required. Some employers pay for ITIL Foundation (a widely used certification in how IT services and incidents are managed) or cloud certifications such as AWS or Azure fundamentals during your first year or two - useful but rarely needed to get hired.

Skills that matter

Structured debugging and root-cause analysis

The core of the job is narrowing a vague complaint like 'the report is wrong' down to a specific cause, and the people who do this methodically rather than by guesswork get promoted fastest.

SQL and data literacy

Most business applications are a front end over a database, so proving what actually happened almost always means writing a query against the data.

Reading unfamiliar code

You will spend far more time understanding code written years ago by people who have left than writing new code from scratch.

Explaining technical problems to non-technical people

You will regularly have to tell a frustrated finance or operations manager why their process is broken, what the workaround is and when it will be fixed - without jargon and without over-promising.

Working calmly under time pressure with clear prioritisation

When several things break at once you have to judge which is costing the business most, and hold your nerve on a major incident call while people are watching.

Writing things down properly

Incident write-ups, runbooks and handover notes are what stop the same fault burning a day of someone's time next month, and support teams are judged partly on this.

Putting these on a CV? We counted which skills 12,914 live graduate adverts ask for, and what to do with the answer — part of our application advice.

Where it leads

Graduate/junior application support developer: you shadow, take lower-severity tickets, and learn one or two applications deeply. Typically the first year or so.
Application support developer or analyst owning a system: you become the go-to person for a particular application or business area, take on-call rotations, and start making larger fixes and enhancements yourself. Commonly reached in roughly two to four years, but this depends heavily on how big the team is and how fast people leave.
A fork in the road. Many people move into full software development or DevOps/site reliability engineering, using the systems knowledge as the way in - this is a very common and well-regarded move. Others deepen into support and become a technical lead, production support manager or service delivery manager.
Senior technical routes: solutions architect, platform or SRE engineer, or a specialist in a particular vendor package (for example core banking, ERP or clinical systems), where deep knowledge of one product is genuinely valuable and well paid.
Management and adjacent routes: IT service management, incident and problem management, business analysis, or moving into the business function you have been supporting because you understand its processes better than most. Timelines here vary widely and depend far more on organisation size than on years served.

What people get wrong

“It's a help desk job - resetting passwords and telling people to turn it off and on again.”

That is first-line service desk work, which is a different role. Application support developers are usually second or third line: you get the problems the service desk could not solve, and you are expected to go into the code and the database.

“It's a dead end that stops you becoming a 'real' developer.”

It is one of the more reliable ways in. You learn the production estate, release processes and how systems fail in the real world, which many development graduates never see - and internal moves from support into development teams are common. The risk is staying too long in a team with no development work, so ask at interview how much of the job is coding versus triage.

“You'll be building new features.”

Most of your code output is small, defensive and carefully controlled - bug fixes, data-fix scripts, config changes and automation of your own repetitive tasks. Big new builds usually sit with a separate change or delivery team, though at smaller employers the same people do both.

“Support means unavoidable night shifts.”

It varies enormously. Some roles are strictly office hours with no on-call at all; others have a paid on-call rota, and a minority - typically trading systems, 24/7 retail or healthcare - run genuine shift patterns. This is one of the most important things to pin down before accepting an offer, along with whether on-call is paid.

Where this varies

The job differs a lot by employer type. In investment banks and trading firms it is fast, high-pressure, often early-start or shift-based, technically demanding and comparatively well paid. At a software vendor you support your own company's product for external customers, so there is a strong customer-service and SLA (service level agreement - a contractual promise about response times) element. In the NHS, universities and local government the pace is generally steadier, the pay lower, and the work often centred on configuring and supporting third-party packages rather than in-house code. At small companies the title may effectively mean 'the developer who also fixes things', with a genuine mix of new build and support. Job titles are inconsistent too - the same work is advertised as Application Support Analyst, Production Support Engineer, Technical Support Engineer or Systems Support Developer, so read the responsibilities rather than the title.

Search Application Support Developer jobsFrom employers' own careers sites, updated daily Tailor your CV for this roleFree with an account, 3 a month

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.