Public Health Intelligence Analyst / Epidemiologist

The intelligence analyst's distinct contribution is making a population visible. That is why the primary gradient is Revelation: nobody can see a population directly, and the only way anyone knows that diabetes is rising in one ward, that childhood vaccination has fallen in a specific community, or that an unusual cluster of infections has appeared across three hospitals, is that someone found it in data that was not collected for that purpose. Discovery is the investigative half (framing the question, testing whether the signal is real or an artefact of how the data was recorded), Explanation is the delivery (an analysis nobody can act on is worthless), and Spread is what the analysis exists to serve, because the point of finding the gap is to direct resource at it.

The daily texture is data, code and interpretation. The analyst builds and maintains surveillance outputs, produces the health needs assessments that underpin commissioning decisions, evaluates whether a programme achieved anything, maps inequality across small geographies, and answers the specific analytical questions that consultants and councillors ask. Tools are typically R or Python, SQL, and geospatial software, working with routine NHS datasets, mortality and registry data, screening and immunisation systems, and survey data. Epidemiological training matters because the traps are specific to this discipline: confounding, ecological fallacy, small-number instability, changes in coding practice that look exactly like changes in disease.

The craft is knowing what a number cannot support. A great deal of the job is preventing a plausible but wrong conclusion from being acted on, and being the person who says the apparent rise is a change in how the data is recorded rather than a change in what is happening. That is not a popular contribution in a meeting, and it is the most valuable thing the role produces.

This is a data job, and people arrive expecting a health job. The week runs on statistics and code rather than on disease, and a fair number of entrants are surprised by how little of it is recognisably medical. That cuts both ways: it is a genuine route into public health that does not pass through a clinical career, and it is a long way from the patient.

The other thing is how much of the difficulty is administrative rather than analytical. Information governance, data sharing agreements, and secure environments consume a serious share of the job, because the datasets that would answer the question usually belong to someone else and moving them lawfully is slow. The technical analysis is often the fastest part of a project.

The usual entry is a public health analyst, intelligence officer, or information analyst post in a local authority, NHS body, or national agency, or an NHS graduate analytical scheme. Degrees in statistics, mathematics, data science, geography, epidemiology, biology, or economics are all common, and quantitative capability matters more than the subject. A Master of Public Health or a specialist MSc in epidemiology, medical statistics or public health data science is the standard route into more senior analytical work, and public health specialty training remains open to analysts as a route to consultant level. Demonstrable R, Python and SQL competence — a public portfolio of analysis is entirely acceptable evidence — carries substantial weight at entry [Faculty of Public Health 2026; from salary and job-posting data, Prospects 2026].