Operations Analyst
An operations analyst looks at how a business actually runs day to day - how orders get fulfilled, how trades get settled, how patients move through a clinic, how a delivery network is staffed - and uses data and process work to make it run better or spot when it's going wrong. The work is a mix of pulling and analysing numbers, sitting with the people who do the process, and writing up what should change. The job title is used across very different sectors (banking, logistics, retail, healthcare, tech, energy, consultancies), so the substance depends heavily on the employer.
Approximate graduate salary
Typically around GBP 25,000-35,000 to start, though this varies widely. Roles in financial services operations in London and in some tech firms sit at the upper end or above it; public sector, charity and smaller regional employers often start lower. Graduate schemes at large corporates tend to cluster in the middle of that range, sometimes with a bonus or relocation element.
What you'd actually do
- Pulling data out of internal systems - usually via SQL queries against a database, or exporting from an operational system - and cleaning it up so it can actually be analysed
- Building and updating dashboards or recurring reports that track operational measures like processing times, error rates, backlogs, stock levels or service levels, and chasing down why a number moved
- Investigating exceptions: a batch that failed overnight, a shipment that missed its window, a set of trades that didn't settle, a spike in customer complaints - working out the root cause and who needs to fix it
- Sitting with or shadowing the people who run the process (warehouse staff, contact centre agents, settlements teams, clinical admin) to understand what really happens versus what the process document says
- Modelling scenarios in Excel or Python - what happens to staffing if volumes rise, what a change to a shift pattern does to throughput, what a new supplier lead time means for stock
- Writing short summaries and slide packs for managers, and presenting findings in operational review meetings where the audience wants the recommendation first, not the methodology
- Supporting or running a small improvement project - documenting the current process, agreeing the change, testing it, and checking afterwards whether the numbers actually moved
How graduates get in
- Graduate schemes are the most common structured route. Many large banks, insurers, retailers, logistics firms, utilities and manufacturers run an 'operations' or 'business operations' graduate programme with rotations across different operational teams. These typically open in autumn for the following September.
- Direct entry to an advertised analyst or junior analyst vacancy. This is very common outside the big graduate-scheme employers - smaller companies, scale-ups and public sector bodies hire analysts one at a time rather than in cohorts, and often advertise year-round.
- Internal moves from a frontline operational role. A lot of operations analysts started in a contact centre, warehouse, branch, back-office processing team or clinical admin role and moved sideways once they'd shown they could handle data. This route is more common than graduate careers advice usually suggests, and the operational knowledge is genuinely valued.
- A summer internship or placement year with the same employer, converting to a graduate offer. Placement years are especially common in logistics, manufacturing, retail and financial services operations.
- Via consultancy or an outsourced service provider. Some graduates join an operational consultancy or a business process outsourcing firm and then move client-side into an in-house analyst role.
- Apprenticeship-style or degree apprenticeship routes exist in some large employers, and a small number of graduates enter through the NHS Graduate Management Training Scheme or Civil Service Fast Stream and end up doing recognisably similar operational analysis work in the public sector.
What employers ask for
- A degree is usually expected but the subject often doesn't matter much. Numerate subjects (economics, maths, statistics, engineering, business, geography, sciences) are common and sometimes preferred, but plenty of employers hire from any discipline if you can evidence comfort with numbers.
- A 2:1 is the most commonly stated bar, particularly on structured graduate schemes. A good many employers accept a 2:2, especially for directly advertised roles at smaller organisations, and some have dropped degree classification filters entirely - it varies a lot.
- Some employers still apply UCAS points or A-level grade filters, often including maths at A-level or GCSE. This is more common in banking and large corporate schemes than elsewhere.
- Demonstrable comfort with Excel is close to universal. SQL is increasingly asked for and is sometimes tested at interview; Python or R appear in more data-heavy roles but are not usually a hard requirement at entry level.
- No mandatory professional qualification to enter. Depending on sector, employers may later fund things like Lean Six Sigma belts (a process improvement methodology), APM or PRINCE2 project management qualifications, CIPS for procurement-facing work, or CFA/IMC for investment operations. Chartered status via the Chartered Institute of Logistics and Transport or CIPS is relevant in supply chain paths.
- Selection usually involves online numerical and situational judgement tests, then a case exercise or data task, then interview. Some employers use an assessment centre; smaller employers often just do two interviews and a practical task.
Skills that matter
SQL and spreadsheet fluency
Most operational data lives in databases or system exports, and being able to get at it yourself rather than waiting on a data team is what makes you useful in the first few months.
Process thinking - mapping how work actually flows
The core of the job is spotting where handoffs, approvals and rework create delay or error, which requires you to think in steps and dependencies rather than just in numbers.
Scepticism about your own data
Operational data is messy - duplicate records, missing timestamps, people using free-text fields wrongly - and an analyst who reports a dramatic finding that turns out to be a data quirk loses credibility fast.
Explaining an analysis to non-analytical people
Your recommendations usually land with a warehouse shift manager, a team leader or an operations director who needs 'here's what's happening and here's what I should do' in a couple of sentences, not a methodology walkthrough.
Persuading people who don't report to you
You almost never have authority over the teams whose process you're changing, so getting a change adopted depends on involving them early and making the fix easier than the status quo.
Working calmly under an operational incident
When a system fails or a backlog builds, you may be asked for numbers on the state of play within the hour, and being able to produce something defensible quickly matters more than being perfect.
Where it leads
First one to three years: analyst. You are given defined questions and recurring reporting, with someone reviewing your work. The focus is on learning the systems, the data and how the operation genuinely functions.
Senior analyst: you scope your own questions, own a process area or a set of metrics end to end, and are trusted to take findings straight to operational managers. Timing varies widely - two to four years is common but it depends far more on the employer's structure than on any fixed rule.
From there the path forks. Some move into operations management, taking responsibility for a team and its performance rather than analysing it. Others go deeper technical - data analyst, business intelligence, data science - if they've built strong coding skills. Others move into project or change management, running the improvement work rather than sizing it.
Mid-career destinations include operations manager, head of operational performance or continuous improvement lead, business partner roles supporting a specific function, or product or programme roles in tech-driven businesses.
Longer term, the operations route is one of the more common feeders into senior general management - COO-type roles, supply chain directorships, or heading a service function - because you accumulate a detailed picture of how the business actually makes money and where it leaks. This takes many years and is not a given.
What people get wrong
“It's a data science job in disguise, and you'll spend your time building models.”
Most of the work is descriptive and diagnostic - what happened, why, and what should change - using SQL and spreadsheets. A large share of your time goes on understanding the process and talking to the people running it, not on modelling. Roles that are genuinely model-heavy are usually advertised as data scientist or optimisation analyst.
“'Operations' means back-office admin and it's a lower-status role than front-office or strategy jobs.”
In many businesses operations is where the cost base and the customer experience actually sit, so operational analysts get unusually early exposure to senior decision-makers and to how the organisation makes money. It is a well-trodden route to general management.
“The analysis is the deliverable - find the insight, present it, job done.”
A finding nobody acts on is worth nothing. A significant part of the role is the unglamorous follow-through: convincing an operational team the problem is real, agreeing a change with people who are busy, and checking afterwards whether the numbers moved. Analysts who only produce reports tend to plateau.
“It's an office-based desk job.”
Depending on sector, you may spend real time on a warehouse floor, in a depot, on a contact centre floor or in a hospital department. You cannot diagnose a process you have never watched, and many employers expect analysts to go and see the operation.
Where this varies
This title covers genuinely different jobs. In investment banking or asset management, an operations analyst usually works in trade settlement, reconciliations, collateral or client onboarding - highly regulated, deadline-driven, with a strong controls focus and a real chance of early-morning or late cut-off pressure. In retail, logistics and manufacturing it leans towards supply chain, demand forecasting, warehouse and network performance, often with site visits and shift-adjacent hours. In tech and scale-ups it often means business operations - a broad, loosely defined role covering whatever the company needs measured this quarter, with more SQL and more autonomy but less structure. In the NHS and wider public sector it typically involves patient flow, capacity planning and waiting-list analysis. The daily tools overlap; the subject matter, hours and culture do not. It is worth reading the actual job description carefully rather than assuming the title tells you much.
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.