Business Analyst

A business analyst works out what a business actually needs from a change — usually a new IT system, a process redesign or a regulatory requirement — and translates that into something developers, testers and managers can act on. They sit between the people who do the work (claims handlers, finance teams, clinicians, customer service staff) and the people building or delivering the solution, making sure what gets built solves the real problem. Most graduate BAs work in-house at large organisations such as banks, insurers, retailers, utilities, government departments and the NHS, or in consultancies delivering change for client organisations.

Approximate graduate salary

Starting salaries for graduate business analysts in the UK are typically around GBP 26,000–35,000, though this varies widely. London roles at large financial services firms and consultancies sit at the higher end and sometimes above it, while public sector, NHS and regional roles outside major cities tend to start lower. Consultancies and banks often add a bonus; public sector roles rarely do but usually offer stronger pension terms.

What you'd actually do

Running workshops and interviews with staff to map how a process currently works, then drawing it up as a process map or 'as-is / to-be' diagram showing the current and intended future state
Writing requirements — user stories, acceptance criteria or more formal requirement documents — that describe what a system needs to do and how you'll know it's working
Digging through spreadsheets, system exports and reports to check whether what people say happens actually matches what the data shows
Sitting in agile ceremonies (stand-ups, sprint planning, refinements) with developers and testers, answering questions about why a requirement is worded a certain way and clarifying edge cases
Chasing decisions: emailing and calling stakeholders who owe you an answer, escalating when two departments want incompatible things, and keeping a log of open questions
Supporting testing — writing or reviewing test scenarios, helping business users through user acceptance testing (UAT), and triaging defects to work out whether something is a bug or a misunderstood requirement
Producing slides and short written updates for project boards or steering groups explaining progress, risks and what decisions are needed

How graduates get in

Graduate schemes — very common. Large banks, insurers, retailers, telecoms firms and consultancies run technology, change or 'business transformation' graduate programmes that rotate you through BA-type roles. Many won't use the words 'business analyst' in the advert, so look for 'change', 'transformation', 'digital', 'technology consulting' or 'operations'.
The Civil Service Fast Stream and departmental/NHS graduate schemes, which include digital and project delivery routes with substantial BA content. Note the Civil Service and NHS have their own competency and values-based application processes.
Direct entry as a junior or trainee business analyst, advertised individually rather than as a scheme. Common at mid-sized firms, software companies and public sector bodies, and often more open to non-standard backgrounds than graduate schemes.
Sideways moves from an operational role — starting in customer service, claims, underwriting, finance or back-office operations and moving into the change team because you already understand the process. This is one of the most common routes into BA work in the UK, though it takes a year or two in the first role.
Consulting graduate schemes, where you'll do BA-style work under a title like 'analyst' or 'technology consultant' across multiple client projects.
Placement years and summer internships in technology, operations or consulting — a strong route because many employers convert interns directly onto graduate schemes.
Apprenticeship-style or conversion routes exist (business analyst apprenticeships, digital bootcamps) but these are less commonly the graduate route into large employers.

What employers ask for

A degree in almost any subject. Business, management, economics, computer science, information systems and maths are common, but humanities and science graduates are widely hired — this is genuinely a subject-agnostic role at most employers.
Degree classification requirements vary a lot. Many large graduate schemes ask for a 2:1; a fair number ask for a 2:2 or have dropped classification requirements entirely, particularly outside the biggest financial services employers. Some still screen on UCAS points or A-level grades, others explicitly do not.
Evidence you can handle structured problems and communicate about them — usually assessed through online tests (numerical, logical, situational judgement), a video interview and an assessment centre with a group exercise and a case study or presentation.
No professional qualification is required to enter. The main industry certifications are the BCS (Chartered Institute for IT) Business Analysis qualifications, including the International Diploma in Business Analysis, and agile certifications such as Scrum or SAFe. Employers typically fund these once you're in post rather than expecting them beforehand.
Technical requirements vary sharply by sector. Some BA roles expect you to write SQL queries and work with data tools; others involve no coding at all and are purely process and stakeholder work. Read the job description carefully rather than assuming.
Relevant experience helps but need not be formal — running a society, a placement year, part-time work where you saw a clunky process up close, or a dissertation involving interviewing people and analysing findings all count in applications.

Skills that matter

Asking precise questions

Stakeholders describe what they want in vague terms, and the job is largely working out what they actually mean before someone spends months building the wrong thing.

Writing clearly and unambiguously

A requirement that can be read two ways will be built the wrong way, so BAs spend a lot of time making written statements tight enough that a developer who's never met the business can't misinterpret them.

Process mapping and modelling

Being able to turn a messy verbal description into a clear diagram (flowcharts, BPMN, swimlane diagrams) is the core technique for exposing where a process breaks down.

Working with spreadsheets and data

You'll routinely need to size a problem — how many cases go down this route, how often does this exception occur — using Excel and, in many roles, basic SQL to query databases directly.

Handling disagreement between stakeholders

Two departments often want contradictory things and neither outranks the other, so the BA has to surface the conflict, lay out the trade-offs and get a decision made rather than quietly picking a side.

Comfort with ambiguity and unfinished information

Projects start before anyone knows the answer, and BAs have to make progress with partial information while flagging clearly what's still unknown.

Where it leads

Junior/graduate business analyst — supporting a more senior BA on part of a project, doing the documentation, note-taking, data pulls and testing support. Typically one to two years, though on structured graduate schemes this is often a fixed two-year programme with rotations.
Business analyst — owning your own workstream or small project end to end: running the workshops, writing the requirements, and being the person the development team comes to with questions.
Senior or lead business analyst — responsible for the analysis approach across a large programme, often managing or mentoring other BAs and dealing with senior stakeholders directly. Time to reach this varies widely, from around four or five years to considerably longer depending on employer size and how much change work is going on.
From there the role branches, and which branch you take matters more than seniority. Common directions: product owner or product manager (owning what gets built and why), project or programme manager (owning delivery, budget and timelines), data analyst (if you leaned technical), or consulting.
Longer-term destinations include head of business analysis or change, product director, or moving into the operational business you've been analysing — BAs often end up running the department whose processes they redesigned. Timelines here vary enormously and depend heavily on sector and organisation size.

What people get wrong

“It's a finance or accountancy job because of the word 'business'.”

Most BA roles are technology and change roles. You're far more likely to be sitting with software developers discussing how a system should behave than looking at a balance sheet. The confusion is real enough that some employers now advertise the role as 'change analyst' or 'product analyst' instead.

“You need to be able to code, or at least have a computer science degree.”

Many BAs never write a line of code. What you need is enough technical literacy to hold a sensible conversation with developers — understanding what a database, an API or a system integration roughly is — not the ability to build things yourself. That said, SQL and data skills genuinely open doors in some sectors, so it's worth learning the basics.

“It's mostly solitary analysis work — reading documents and producing reports.”

It's one of the more socially demanding roles in a technology function. A large share of the week is meetings, workshops, and persuading people who don't report to you and are busy with their day jobs to give you their time and make decisions. If you dislike chasing people, you'll find it draining.

“The BA decides what gets built.”

BAs usually have influence rather than authority. You surface options, evidence and consequences, but a product owner, sponsor or steering group makes the call — and sometimes they'll choose the option you argued against. Learning to disagree well, document the risk and then get behind the decision is part of the job.

Where this varies

The job title covers quite different jobs. In financial services and large corporates, a BA is usually embedded in a change or transformation programme, works to formal governance, and may spend months on regulatory-driven work with heavy documentation. In software companies and digital teams, the role is much closer to a product role — lighter documentation, user stories, close daily contact with developers, and sometimes merged with the product owner job entirely. In consultancies, you move between clients every few months, travel more, and are expected to be presentable in front of senior client staff early on. In the public sector and NHS, the pace is often slower, procurement and policy constraints shape what's possible, and job titles may follow the Government Digital Service role framework. Some employers also use 'business analyst' for what is really a data or MI (management information) analyst role producing reports and dashboards — check whether the advert talks about requirements and stakeholders or about SQL, dashboards and reporting, because these lead to different careers.

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.