Systems Analyst

A systems analyst works out how an organisation's computer systems should work to support what the business actually needs, and translates that into something developers and suppliers can build or configure. They sit between the people who use a system (finance teams, clinicians, customer service staff, logistics planners) and the technical teams who build and maintain it, documenting requirements, mapping processes and testing that what gets delivered does the job. The role exists across banks, insurers, the NHS, central and local government, retailers, manufacturers and IT consultancies.

Starting salary: £25k–£35k
Live graduate jobs: 13 open now
Main way in: IT and technology graduate schemes at large employers
They usually ask for: A degree in any subject is accepted by many employers

Approximate graduate salary

Typically around £25,000–£35,000 to start, though this varies widely. Graduate schemes at large financial services firms and consultancies in London tend to sit at the upper end or above it; public sector, NHS and smaller regional employers tend to sit lower. Pay generally rises noticeably once you're working independently rather than under supervision.

What you'd actually do

Running workshops or interviews with staff who use a system, asking detailed questions about how they currently do a task and where it breaks down
Writing up requirements - plain-English statements of what a system must do - and getting the business users to confirm you've understood them correctly
Drawing process diagrams and data flows (often in tools like Visio, Lucidchart or Miro) showing how information moves between systems and people
Sitting with developers or a supplier's technical team to check whether a requirement is feasible, and rewriting it when it isn't

Show 3 more

Writing and running test scenarios, then logging defects and chasing them through to fix - this takes up far more time than most people expect
Investigating live problems: tracing why a figure on a report is wrong, which usually means querying data, reading system logs and comparing against what the process documentation says should happen
Attending stand-ups, sprint planning and refinement sessions if the team works in Agile, and keeping a backlog of work items up to date

How graduates get in

IT and technology graduate schemes at large employers - banks, insurers, retailers, utilities, the Civil Service and the NHS all run these, and systems or business analysis is a common rotation or stream. This is the most structured route.
Direct entry as a junior or trainee systems analyst, advertised straight as a permanent role. Common in mid-sized organisations and in the public sector, and very common outside London.
Moving across internally from a service desk, application support or testing role. A lot of systems analysts started by answering support tickets, learned the systems inside out, and moved sideways - this is probably the single most common route overall.
IT consultancies and systems integrators, who hire graduates in volume and place them on client projects. You'll be given a methodology and templates to follow and learn quickly on live work.

Show 2 more

Degree apprenticeships in digital and technology solutions, which produce people doing this work without a traditional graduate route - worth knowing about if you're deciding between university and an apprenticeship.
Conversion from a non-computing degree via a postgraduate IT or data conversion MSc. Possible, but unusual compared to simply applying directly - most employers care more about aptitude than subject.

What employers ask for

A degree in any subject is accepted by many employers; computing, information systems, maths, engineering and business are the most common, but humanities and social science graduates get in regularly, particularly where the employer values the writing and questioning side.
A 2:1 is the usual bar on structured graduate schemes; plenty of direct-entry roles accept a 2:2 or don't specify. Some employers have dropped degree classification filters altogether, so read each advert rather than assuming.
Evidence that you can handle data and detail - a dissertation involving analysis, a placement year, a part-time job where you fixed a messy process. Employers care about demonstrable examples more than the label on your degree.
Some SQL is increasingly expected, even at entry level, because so much of the job is checking what the data actually says. You can teach yourself enough to be credible.

Show 2 more

Professional qualifications are usually taken after you start, not before: the BCS (the Chartered Institute for IT) runs certificates in business analysis, requirements engineering and modelling, and many employers fund these. Agile certifications such as Scrum are also common.
A placement year or summer internship in IT, support or analysis is a genuine advantage for competitive graduate schemes, though far from essential for direct entry.

Skills that matter

Asking probing questions and not accepting the first answer

Users describe what they want rather than what they need, and the job is largely about digging past 'make it like the old system' to the underlying problem.

Precise written English

A requirement that can be read two ways will be built the wrong way, and you'll be the one explaining why in a meeting six months later.

SQL and basic data interrogation

When a report looks wrong, you need to query the underlying data yourself rather than waiting days for a developer to do it for you.

Process and data modelling

Being able to draw a clear process map or data flow forces hidden assumptions into the open and gives technical and non-technical people one shared picture to argue over.

Structured problem diagnosis

Faults rarely come with a cause attached - you work backwards from a symptom through the chain of systems until you find where the data went wrong.

Managing disagreement between stakeholders

Two departments often want incompatible things from the same system, and you have to surface the conflict, document the options and help someone senior decide rather than quietly picking a side.

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

Junior or graduate systems analyst: working on defined pieces of a larger project, writing requirements under review, doing a lot of testing and documentation. Typically the first couple of years, though graduate schemes often run to a fixed length such as two years.
Systems analyst / business systems analyst: owning a system or a workstream, running your own workshops, being the person the business comes to with questions about how a particular application behaves.
Senior analyst or lead analyst: shaping how requirements are gathered across a programme, mentoring juniors, and being involved earlier - in whether a project should happen at all, not just how to build it. Timing here varies a lot and depends on the size of the organisation.
A branch point rather than a single next step. Common destinations are business analyst and product owner (more business-facing), solution or enterprise architect and technical lead (more technical), and project or programme manager (delivery-focused). Some analysts move into the business function they've been supporting, because they end up understanding its processes better than most of the staff in it.
Beyond that: IT consultancy at senior level, contracting on a day rate, or management roles such as head of business systems or IT delivery manager. Contracting is common in this field once you have several years of experience and a track record with a specific system or sector.

What people get wrong

“It's a programming job with a different name.”

Most systems analysts write little or no production code. You need to read technical material, understand how systems fit together and often write SQL, but the output is documentation, decisions and tested systems - not software you've built yourself. If you want to code all day, look at software engineering instead.

“'Systems analyst' and 'business analyst' mean the same thing.”

The titles overlap heavily and some employers use them interchangeably, but where they're distinguished, a systems analyst leans towards how the technology should work and a business analyst towards what the business should do. Check the actual duties in the advert, because the title tells you less than you'd think.

“You spend your time quietly analysing things at a desk.”

It's a highly social job. Much of the week is meetings, workshops and chasing people for answers, and a large part of being good at it is persuading busy staff to give you an hour of their time and then getting them to commit to a decision.

“The work is mostly new, exciting systems.”

A great deal of systems analysis involves legacy systems - old, poorly documented software that the organisation depends on and can't easily replace. Working out how something built decades ago actually behaves is a core and genuinely valued skill.

Where this varies

The job differs a lot by sector and by employer size. In financial services and large consultancies it is often project-based, Agile, fast-moving and specialised - you may work on one system or one programme for a year. In the NHS, local government and smaller organisations the same title can be much broader, covering support, configuration, reporting, user training and procurement alongside analysis, and you may be the only person who understands a given system. In software vendors and systems integrators the role is more outward-facing, working with client organisations rather than colleagues. There's also variation in method: some teams still work to a fixed, documented, waterfall-style process with formal sign-off of a requirements document, while others work in Agile sprints where requirements evolve as user stories - the day-to-day feel of these is quite different, so it's worth asking at interview.

See all 13 live Systems Analyst 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.