Technology
Data Scientist
Finds patterns in complex information to guide decisions
What does a data scientist do?
Every organisation collects data: what customers buy, where deliveries are delayed or how people use a product. A data scientist turns that raw information into a decision. They use statistics, code and knowledge of the business to explain what happened, predict what might happen next and test whether an idea actually works.
The fascination - and frequent annoyance - is that a dataset never arrives with a trustworthy explanation of itself. A column called “delivery date” may mean promised date in one system and actual date in another; a model can be mathematically sound while learning from a process that has just changed. Data science rewards people who will interrogate how the numbers were created as seriously as they tune an algorithm, then commit to an answer useful enough for somebody to act on.
Most graduates enter through a junior data scientist or data analyst role. A quantitative degree helps, but employers care a great deal about whether you can use Python or R, write SQL and explain a project clearly. A master’s can make the route easier, particularly for graduates changing subject or aiming at research-heavy machine learning, but it is not a universal entry ticket.
- Starting pay£33,000
- Ten years in£82,000
- IntensitySteady
- CompetitionFierce
- Postgraduate trainingNone needed
Data scientist salary in the UK
- A typical earner
- Bottom 10% up to top 10%
| When | Lowest 10% earn under | A typical earner | Top 10% earn over |
|---|---|---|---|
| On graduating | £25,000 | £33,000 | £46,000 |
| 1 year in | £27,000 | £36,000 | £52,000 |
| 2 years in | £30,000 | £42,000 | £60,000 |
| 3 years in | £33,000 | £48,000 | £68,000 |
| 4 years in | £36,000 | £54,000 | £78,000 |
| 5 years in | £38,000 | £60,000 | £90,000 |
| 6 years in | £41,000 | £65,000 | £100,000 |
| 7 years in | £44,000 | £70,000 | £108,000 |
| 8 years in | £46,000 | £74,000 | £114,000 |
| 9 years in | £48,000 | £78,000 | £120,000 |
| 10 years in | £50,000 | £82,000 | £125,000 |
The good and the bad of being a data scientist
The good
You learn how to tell whether something really works
Most workplaces are full of persuasive stories about why sales rose, customers left or a new policy succeeded. Data science gives you tools for testing those stories. You learn to separate coincidence from evidence, design fair comparisons and say how sure you actually are. That way of thinking is useful in almost any important decision, not just at work.
Your skills travel unusually well
The same basic toolkit can be used to detect fraud at a bank, improve hospital waiting times, forecast energy demand or understand why people stop using an app. You still need to learn each industry properly, but you are not locked into one sector. If the subject matter stops interesting you, the craft can move with you.
There is a real technical craft to master
Statistics, programming, experimentation and machine learning all reward depth. A problem that takes you two days as a graduate may take an hour after several years, and you can feel yourself becoming more precise. For people who like being a generalist but still want a hard skill they can practise, data science offers a satisfying middle ground.
The bad
Most of the job is less glamorous than the demonstrations
You may imagine spending the week training intelligent models. In reality, data is often missing, duplicated, badly labelled or spread across systems that were never designed to work together. A large part of the job is finding the right table, cleaning it and checking that the result has not quietly become nonsense. If you dislike painstaking detail, the interesting ten per cent will not compensate for the rest.
A correct analysis can still change nothing
Evidence does not make a decision by itself. A recommendation may be inconvenient, politically awkward or arrive after somebody senior has already chosen a direction. You have to understand what colleagues care about, explain the result without hiding behind technical language and sometimes accept that the business will ignore you. Being right is only half the job; making the answer usable is the other half.
The entry market can be confusing
Companies use data scientist, analyst, machine-learning engineer and applied scientist to mean different things. Some supposedly junior roles ask for a master’s, years of experience and a long list of tools. Others use an impressive title for fairly routine reporting. Graduates need to judge the actual work carefully and may find that starting as a data analyst is the quickest route into the profession rather than a consolation prize.
Data scientist career path
Junior Data Scientist / Data Analyst
Usually 0–2 years’ experience
You’ll normally work on well-defined questions with help from a more experienced colleague. Much of your time goes into learning where the organisation’s data lives, writing reliable queries and checking your work. The aim is to prove that someone can make a decision from your analysis without being misled by it.
Data Scientist
Usually 2–5 years’ experience
You’re expected to take a problem from a vague question to a useful answer yourself. You might design an experiment, build a forecast or prediction model and explain what the organisation should do next. You also start choosing the method rather than merely carrying out an approach somebody else selected.
Senior Data Scientist
Usually 5–8 years’ experience
The questions become more ambiguous and more important. You’ll guide other data scientists, challenge weak assumptions and decide how much analytical effort a problem deserves. Depending on the company, you may specialise in experimentation, forecasting, machine learning or a particular industry.
Lead / Principal Data Scientist
Usually 8–12 years’ experience
This is often the senior individual-contributor route. You set technical standards, shape large projects and become the person others consult when the obvious analysis is not good enough. Some principal data scientists stay deeply technical; leads may also coordinate a small team while still doing substantial hands-on work.
Head / Director of Data Science
Usually 12+ years’ experience
You’re now responsible for a team’s direction as much as its analysis. You decide which problems deserve data-science investment, hire and develop people and make sure the work is trusted and used across the organisation. The job shifts towards leadership, budgets and company strategy, although technical credibility still matters.
What degree do you need to be a data scientist?
Gives you the programming, databases and machine-learning foundations employers ask for most often. You may need to work harder on experimental design and on explaining uncertainty without technical shorthand.
Teaches you to reason from evidence and understand what a model is actually assuming. Graduates often have the strongest theoretical base, then need to turn classroom coding into software that other people can reliably use.
Trains you to model complicated systems and solve problems within real constraints. The combination of quantitative confidence and practical judgement transfers well, particularly in manufacturing, energy and technology.
Physics, chemistry and biology all involve noisy measurements, experiments and conclusions that must survive scrutiny. Scientists usually arrive comfortable with evidence; the main gap is often production-quality programming or commercial context.
Economics brings statistics, causal reasoning and an instinct for incentives. Psychology and other quantitative social sciences bring experimental design and an understanding of human behaviour, particularly useful in product and policy work.
People do move in from business, geography, the arts and many other subjects, usually by building quantitative evidence through a conversion master’s, a data-analyst role or a strong portfolio. The route is less direct, but subject knowledge can become an advantage in the right industry.
Hover a subject to see why it helpsTap a subject to see why it helps
A day in the life of a data scientist
08:45 – 09:30Check the overnight numbers
You look at the company’s main metrics and the health of a model that predicts which customers are likely to leave. Its predictions suddenly look less accurate. Nothing is obviously broken, so you write down three possible explanations before opening the code. Data science is easier when you resist falling in love with your first theory.
The data team quickly shares what it is doing and where it is stuck. An analyst needs help defining a customer as “active,” while an engineer warns that a useful data source will change next week. You agree who will investigate each issue. Even apparently mathematical work depends on people using the same definitions.
You query the raw data and discover that a recent app update changed when one event is recorded. The model has not suddenly become stupid; part of its input has changed meaning. You compare old and new records, speak to the engineer who shipped the update and create a clean version that can be used safely.
A product manager wants to know whether a new sign-up page performed better than the old one. The headline conversion rate increased, but more of the new users came from an unusually successful marketing campaign. You work through the comparison and explain what can be concluded now, what cannot and how to design a cleaner follow-up test.
Last night’s leftover pasta.
You return to a project forecasting weekly demand. You try a more complex method, test it against unseen data and find that it performs barely better than the simple baseline. You keep the simpler model. Good data science is not about using the cleverest technique; it is about using the least complex one that solves the problem reliably.
You show the forecast to a product manager. They do not want a tour of the mathematics; they want to know how many staff to schedule and what could make the estimate wrong. Their questions reveal a constraint you had missed, so you adjust the recommendation. Domain knowledge often improves a model more than another afternoon of tuning.
The analysis currently works only in your notebook. You tidy the code, add checks for missing data and ask a colleague to review it. This is the difference between an interesting answer and something the organisation can trust every week.
You show the corrected results to the delivery manager, who notices that one depot appears excellent only because failed orders are reassigned before the daily snapshot. Together you change the comparison and agree to run the model in shadow mode - making predictions without controlling decisions - for another week. The afternoon ends with no launch, but with a test capable of revealing whether the model helps in the real process.
What skills does a data scientist need?
How many hours does a data scientist work?
+1 hour compared with the average graduate profession