Research Scientist

A research scientist designs and runs experiments or studies to answer questions that nobody has a settled answer to yet, then writes up what they found so others can use it. Depending on the employer, that might mean testing new drug compounds for a pharmaceutical company, developing better battery materials for an engineering firm, running modelling work for a government agency, or working on a university project funded by a research grant. Most of the work is done in small teams, and the "customer" is either an employer trying to develop a product, a funding body, or the wider scientific community.

Approximate graduate salary

Starting salaries for graduate-level research roles are typically somewhere around GBP 25,000-35,000, and this varies a lot - pharmaceutical, energy and defence employers and roles in London and the South East tend to sit at the higher end, while university research assistant posts, small companies and contract research organisations often sit lower. Roles requiring a PhD generally start higher, and academic posts follow published university pay scales rather than being individually negotiated. Treat all of this as a rough guide only.

What you'd actually do

Planning and running experiments - preparing samples, setting up equipment, following (and often adapting) protocols, and repeating runs so results can be trusted rather than being a one-off fluke
Recording everything in a lab notebook or electronic equivalent, in enough detail that a colleague could repeat the work exactly - this is far more of the job than most people expect
Analysing data: cleaning it up, running statistical tests, plotting it, and working out whether an apparently interesting result is real or noise
Reading recent published papers in the field to see what other groups have tried, and adapting methods from them
Presenting results at internal team meetings or group meetings, usually with slides, and defending the interpretation when someone challenges it
Writing up findings - internal technical reports and study documentation in industry, journal papers and conference abstracts in academia and some research institutes
Routine but essential lab upkeep: calibrating and maintaining instruments, ordering consumables, dealing with safety paperwork such as COSHH assessments (the UK regulations on handling hazardous substances)

How graduates get in

Direct entry straight from a BSc or MSc into a junior research role - common in industry, where titles like research assistant, research associate, scientist I or laboratory scientist are typical starting points. Employers here include pharmaceutical and biotech companies, contract research organisations (firms that run studies on behalf of other companies), materials and chemicals firms, food and consumer goods companies, and instrument manufacturers.
A PhD, then applying for research scientist roles. For academic research and for many senior industrial R&D positions this is effectively the standard route, and in some fields it is close to a hard requirement. UK PhDs typically take three to four years full-time and are usually funded through a studentship covering fees plus a tax-free stipend, so you are not normally paying to do one.
Graduate schemes at large science-based employers - pharmaceutical, energy, defence, food and consumer goods companies run these, though they are fewer in number than in finance or consulting and often rotate you through R&D alongside manufacturing or quality functions.
Government and public-sector research bodies, including the government science and research profession, national laboratories, public health and environmental agencies, and research institutes. These recruit both at graduate level and at postdoctoral level, sometimes through structured schemes.
Converting from a placement or summer internship - a year in industry as part of a sandwich degree, or a summer studentship funded by a research charity or learned society, is one of the strongest routes in because the employer already knows you can work in a lab.
Starting in a technician or laboratory analyst role and moving across into research. This is a real route, particularly in industry, but it usually takes longer and often works better if you pick up further study along the way.

What employers ask for

A degree in a relevant science, engineering, maths or computing subject - here the subject genuinely does matter, unlike in many graduate careers. Employers usually want a close match to the work: biochemistry or pharmacology for drug discovery, chemistry or materials science for formulation and materials work, physics or engineering for instrumentation, statistics or computer science for computational and data-heavy roles.
A 2:1 is the most commonly stated minimum, though some employers accept a 2:2 with a strong lab-based final-year project or relevant experience. Requirements vary and a few research-intensive employers effectively expect a first or a strong master's.
A PhD for many roles, especially anything titled 'senior research scientist', 'principal scientist' or 'postdoctoral researcher'. Whether a PhD is required varies enormously by field and employer - some industrial labs promote strong BSc/MSc scientists into research roles over time, while others reserve independent project leadership for PhD holders.
Hands-on laboratory or computational experience beyond taught practicals - a substantial final-year project, an industrial placement, a summer studentship, or a master's research project. Employers look at the specific techniques you have used, so list them.
Specific technical skills matched to the job advert: for example cell culture, PCR, chromatography, mass spectrometry, microscopy, or programming in Python, R or MATLAB. Adverts are usually explicit about this.
Professional registration is not usually required to start, but chartered status through a relevant professional body (for example Chartered Chemist, Chartered Biologist or Chartered Scientist) is available later and matters more in some sectors than others.

Skills that matter

Experimental design and the use of controls

Knowing what to compare your sample against, and what could confound the result, is the difference between a finding that survives scrutiny and weeks of wasted bench time.

Statistics and data analysis

You constantly have to judge whether a difference between two conditions is real, and increasingly you are expected to handle datasets large enough that spreadsheets alone will not do.

Programming, usually Python or R

Even in wet-lab roles, automating analysis and plotting saves enormous time, and in computational and bioinformatics roles it is the whole job.

Meticulous record-keeping

In regulated sectors such as pharmaceuticals your notebook can be audited, and in any setting a result you cannot reproduce or trace back is worthless.

Technical writing

Findings only count once they are written up clearly for a report, a regulatory submission or a journal, and clear writing is a large part of how you get noticed.

Persistence and troubleshooting

Most experiments fail the first several times, and the useful scientist is the one who systematically works out which step broke rather than repeating the whole thing hoping for a better outcome.

Reading scientific literature efficiently

You need to be able to skim a paper, extract the method, and judge how reliable the work is, without reading every word of everything published in your field.

Where it leads

Junior scientist / research assistant / research associate: you mostly run experiments that someone else has designed, and you build technical competence in a defined set of methods.
Scientist: you start designing your own experiments within a project, take responsibility for a workstream, and begin supervising placement students or new starters. Reaching this point commonly takes a few years, though it can be quicker with a PhD.
Senior scientist / postdoctoral researcher: you lead a project or a substantial part of one, choose the technical direction, and are the person others come to with problems. In academia the postdoctoral stage is usually a series of fixed-term contracts, which is a genuine drawback of that path.
Principal scientist, team leader or group leader in industry; lecturer or research fellow in academia. From here it splits into a technical track (staying deep in the science, becoming a recognised expert) or a management track (running teams, budgets and portfolios). Timelines vary very widely and depend heavily on sector, employer size and luck with funding.
Common sideways moves that many people make deliberately rather than as a fallback: regulatory affairs, medical writing, patent work, data science, clinical trials management, scientific sales and applications support, science policy, technology transfer, and product development. Research training is well regarded in all of these.

What people get wrong

“You need a PhD to be a research scientist.”

In academia and in some specialist industrial R&D, effectively yes. But a great deal of industrial research is done by people with a BSc or MSc who joined at graduate level and built expertise on the job. Whether a PhD is needed depends heavily on the sector and the specific employer - check job adverts in your field before assuming.

“It's mostly hands-on lab work with equipment.”

Bench time is often a minority of the week. A large share of the job is analysing data, reading, writing up, planning, meetings, safety and quality documentation, and in regulated industries, compliance paperwork. In computational fields there is no bench at all.

“You work alone on your own ideas, following your curiosity.”

Research is team-based and, in industry, tightly directed by commercial priorities - a project can be stopped mid-flow because the business changed direction. Even in academia the work is shaped by what a funder agreed to pay for. Independence over what you research usually arrives quite late, if at all.

“Success means discovering something.”

Most experiments produce negative or ambiguous results, and a good scientist is judged on rigour, reliability and speed of ruling things out as much as on breakthroughs. Being the person whose results other people trust is a stronger reputation than being the person with the exciting-but-shaky finding.

“Academic and industrial research are basically the same job in different buildings.”

They differ substantially. Academia offers more freedom in topic but comes with grant-writing, teaching duties, publication pressure and a run of fixed-term contracts. Industry generally offers better pay and job security, better-resourced facilities, and clearer progression, but the topic is chosen for you and you may not be able to publish.

Where this varies

"Research scientist" covers very different jobs. In pharmaceuticals and biotech the work is regulated, documentation-heavy and organised around long project pipelines. In contract research organisations you run studies to a client's specification, often to tight deadlines and across many short projects. In universities and research institutes you work on grant-funded projects, publish, and usually sit on fixed-term contracts. In government and public-sector science the emphasis is on evidence for policy, monitoring and standards rather than product development. And there is a growing split between wet-lab roles and computational or data-heavy roles - in the latter you may never touch a pipette, and the skill set looks much closer to data science. Geography matters too: clusters exist around Cambridge, Oxford, London, Manchester, Edinburgh, Dundee and the Cheshire and Teesside chemicals areas, and outside those clusters your options in a given specialism can be limited enough that relocating becomes part of the career.

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.