UK

United Kingdom · Technology and data · Mid-Level (2-5 years)

Data Scientist

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Start my Data Scientist plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior Data Scientist
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Mid-Level Data Analyst · Machine Learning Engineer (Junior) · Quantitative Analyst (Technical Roles)

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

NOCN Level 4 certificate for Data Analysts NOCN · Level 4 · covers 8 of 14 standards
Qualifi Level 3 Extended Diploma in IT and Data Science Qualifi Ltd · Level 3 · covers 4 of 14 standards
Qualifi Level 3 Diploma in Data Science Qualifi Ltd · Level 3 · covers 3 of 14 standards
Pearson BTEC Level 4 Higher National Certificate in Computing for England Pearson Education Ltd · Level 4 · covers 3 of 14 standards
NOCN Level 3 VRQ in Data Science NOCN · Level 3 · covers 2 of 14 standards
BCS Level 4 Diploma - Digital Modular Programme for Data Analysts BCS, The Chartered Institute for IT · Level 4 · covers 2 of 14 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Practical Data Science NOCN Level 4 certificate for Data Analysts
Machine Learning Methods and Models in Data Science Qualifi Level 3 Extended Diploma in IT and Data Science
Data Analytics Pearson BTEC Level 4 Higher National Certificate in Computing for England
Introduction to Data Science NOCN Level 3 VRQ in Data Science
Data Analysis BCS Level 4 Diploma - Digital Modular Programme for Data Analysts

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
AI Governance Fluency using AI responsibly
Start my Data Scientist plan, free
Your Plan Illustration

Built for Data Scientist

5 units that map to this job, from the qualifications that cover it.

  1. Practical Data Science NOCN · covers 8 of 14 standards Level 4
  2. Machine Learning Methods and Models in Data Science Qualifi Ltd · covers 4 of 14 standards Level 3
  3. Data Analytics Pearson Education Ltd · covers 3 of 14 standards Level 4
  4. Introduction to Data Science NOCN · covers 2 of 14 standards Level 3
  5. Data Analysis BCS, The Chartered Institute for IT · covers 2 of 14 standards Level 4
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

2AI and this work

Will AI change your work as a Data Scientist?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • Prompt Engineering & LLM Integration
  • Responsible AI & Ethics
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Data Scientist plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Data Scientist plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A data scientist turns messy, real-world data into clear insights and working models. The job means figuring out what data actually shows, and building tools to prove it. It involves helping teams make decisions based on evidence. It means owning analytical projects from the first question to the final presentation.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Python (pandas, NumPy, scikit-learn) Intermediate

Writing and debugging scripts for data cleaning, exploratory data analysis, feature engineering, and building standard machine learning models from tutorials or established patterns.

SQL (PostgreSQL) Intermediate

Writing complex SELECT statements with joins, aggregations, and window functions to extract and manipulate data for analysis. Creating temporary tables to stage data.

Git / GitHub Basic

Cloning repositories, committing your changes, pushing/pulling updates, and creating branches for your project work. You'll follow our team's established workflow for version control.

Tableau Basic

Connecting to various data sources and building standard charts (bar, line, scatter) and simple interactive dashboards to visually present your findings from a specific analysis.

AWS (S3, SageMaker) Basic

Uploading and downloading datasets from S3 buckets using SDKs. Navigating the SageMaker UI to run pre-built Jupyter notebooks and training jobs using existing templates.

Jira / Confluence Intermediate

Managing your personal tickets through our sprint workflow (To Do, In Progress, Done). Documenting your analysis, findings, and model details clearly in Confluence for team knowledge sharing.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Model Algorithm Selection Propose options to supervisor, execute chosen algorithm under guidance. Independently choose and justify appropriate algorithm for well-defined problems, consult senior on novel approaches. Define and approve model algorithms for entire workstreams, mentor others on selection criteria.
Data Cleaning & Pre-processing Techniques Follow established procedures and templates for data cleaning. Independently select and apply appropriate techniques, identify and resolve new data quality issues. Design and implement new data cleaning methodologies, establish best practices for the team.
Project Timeline Adjustments Escalate any potential delays immediately to supervisor. Propose minor adjustments to your project timelines, discuss and get approval from Senior Data Scientist. Approve minor timeline adjustments for your workstreams, consult Director on significant shifts.
Tool/Library Selection for a Project Use pre-approved tools and libraries only. Recommend and justify new libraries or tools for specific project needs, get approval from Senior Data Scientist. Approve new tools/libraries for workstreams, contribute to defining team-wide tech stack standards.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Model Performance
The accuracy, precision, or recall of the models you build, depending on the problem.
Target · Achieve >90% accuracy/precision/recall on benchmark tasks, or meet specific project targets.

Your churn prediction model consistently achieves 92% precision in identifying at-risk customers, leading to a 5% improvement in retention efforts.

Task Completion Rate
How often you deliver your assigned analysis tasks and model builds by the agreed-upon deadline.
Target · Deliver 95% of assigned analysis tasks by the agreed-upon deadline.

You completed 19 out of 20 tasks in the last sprint, including a complex customer segmentation analysis that was delivered on time.

Code Quality & Maintainability
The cleanliness, readability, and bug-free nature of the code you write, as assessed by peer reviews.
Target · Fewer than 5 significant bugs or major refactoring requests per 1,000 lines of code discovered in peer review or post-deployment.

Your latest feature engineering script passed code review with only minor stylistic suggestions, and it's been running in production without issues for two months.

Data Extraction Efficiency
How quickly and accurately you can pull the necessary data for your projects.
Target · Reduce average data extraction time for routine requests by 10% through query optimisation or automation.

By optimising your SQL queries, you cut the time it takes to pull weekly marketing performance data from 3 hours to 2 hours 15 minutes.

Insight Clarity & Impact
How well you translate complex analytical findings into clear, understandable insights that business teams can actually use.
  • Stakeholders consistently say your presentations are easy to follow and directly inform their decisions. They'll come back to you for follow-up questions, not because they didn't understand, but because they want to go deeper. Your insights lead to tangible changes in strategy or product features.
Proactive Problem Identification
Your ability to spot potential data issues, model drift, or business problems before they become critical.
  • You flag an unusual trend in customer behaviour before the marketing team notices it. You point out a potential data quality issue in a new pipeline before it impacts a key report. You suggest a new analysis that no one had thought of, which then uncovers a valuable opportunity.
Collaboration & Peer Support
How effectively you work with your team and other departments, and how you help others grow.
  • You're known for helping out a junior analyst who's stuck on a tricky SQL query. Product Managers say you're easy to work with and always explain the 'why' behind your numbers. Your code reviews are constructive and helpful, not just critical.
Documentation Quality
The completeness, accuracy, and accessibility of your project documentation and code comments.
  • Another team member can pick up your project documentation and understand the model, data sources, and assumptions without needing to ask you a dozen questions. Your code is well-commented and easy to follow for future maintenance.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Solving Real-World Puzzles

You get a genuine kick out of taking a messy business problem, breaking it down with data, and finding a solution that actually works. The satisfaction comes from seeing your analysis directly inform a decision or improve a process.

Spending an afternoon figuring out why a certain customer segment has a higher churn rate, then seeing your recommendations lead to a new targeted marketing campaign.

Continuous Learning & Skill Development

You're always looking for new techniques, libraries, or ways to approach problems. You're motivated by the idea that you're constantly honing your craft and adding new tools to your belt.

Voluntarily spending an evening exploring a new feature engineering technique you read about, then trying to apply it to an ongoing project.

Tangible Impact & Contribution

You want your work to matter. You're driven by the knowledge that your models and insights are directly contributing to the company's success, whether that's saving money, increasing revenue, or improving customer experience.

Seeing a dashboard you built become the primary tool for a product team to monitor their feature's performance, knowing they rely on your numbers daily.

What frustrates people
  • The 80/20 Rule of Janitor Work: Spending most of your time on data cleaning, not modelling.
  • The 'Urgent' Ad-Hoc Request: Your sprint getting derailed by immediate, unplanned demands.
  • Vague Requirements, Specific Blame: Being given an unclear problem and then held solely accountable for the outcome.
  • The Black Hole of Legacy Data: Working with undocumented, historical data from defunct systems.
  • Explaining P-Values to Executives: The challenge of simplifying complex statistical concepts for non-technical audiences.
  • 'It Worked on My Machine': Models failing in production despite working perfectly in development.
  • Being the Human SQL Query Engine: Constantly pulling simple metrics instead of doing deeper analysis.
What this role does not give you
  • A perfectly clean, well-documented dataset waiting for you every day.
  • Complete control over your project priorities without occasional urgent shifts.
  • The guarantee that every model you build will make it to production and deliver massive impact.
  • A role where you only focus on cutting-edge research without any operational or maintenance tasks.

8Who you work with

Your work directly informs critical business decisions, from product feature prioritisation to operational efficiency. You're helping us understand 'why' things are happening, not just 'what', which means we can be proactive instead of reactive. Essentially, you're building the intelligence layer that helps the business run smarter.

Inside the business
  • Product Managers (they'll want to understand user behaviour)
  • Marketing Analysts (they'll need help optimising campaigns)
  • Engineering Teams (you'll work with them on data pipelines and model deployment)
  • Senior Data Scientists (your direct team, for collaboration and reviews)
  • Operations Leads (they'll need forecasts and efficiency insights)
Outside the business
  • External data providers (occasionally, for data quality checks)
  • Industry peers (at conferences or meetups, sharing knowledge)

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • A solid grasp of Python for data manipulation and statistical modelling (pandas, NumPy, scikit-learn).
  • Ability to write complex SQL queries for data extraction and transformation.
  • Experience with statistical analysis, hypothesis testing, and A/B testing methodologies.
  • Familiarity with at least one data visualisation tool (e.g., Tableau, Power BI, Matplotlib/Seaborn).
  • An understanding of core machine learning concepts (e.g., supervised vs. unsupervised learning, overfitting, bias-variance trade-off).
  • Experience working with version control systems like Git.
  • Demonstrable experience (2-5 years) in a data-centric role, ideally where you've owned projects from start to finish. This could be as a Data Analyst, Junior Data Scientist, or similar.

10What to practise next

Where the job is going, and what to do about it starting this week.

Advanced Cloud Data Services (AWS)

Critical within 12 months. Our data infrastructure is increasingly cloud-native. You'll need to move beyond just using S3 and SageMaker to understanding how to automate data pipelines using services like AWS Lambda, orchestrate workflows with Step Functions, and manage larger datasets efficiently within the AWS ecosystem.

AWS Lambda for Event-Driven Processing · AWS Step Functions for Workflow Orchestration · Data Lake Architectures (S3, Glue, Athena) · Cost Optimisation in AWS · Security Best Practices (IAM, VPC)

  • This month: Complete an online course on AWS Certified Developer – Associate or AWS Certified Data Analytics – Specialty.
  • Month 2: Work with a senior engineer to automate a small data ingestion task using AWS Lambda and S3 triggers.
  • Month 3: Take ownership of monitoring the costs associated with your AWS SageMaker instances and propose optimisations.
  • Month 4: Start exploring how to use AWS Step Functions to orchestrate a multi-stage data processing job.

Quick win: Set up cost alerts for your AWS account and review your SageMaker instance usage weekly to identify potential savings.

Advanced SQL & Database Optimisation

Important within 9 months. As our datasets grow, simply writing functional SQL isn't enough. You'll need to write highly optimised queries that don't bring down the database, and understand how to work with complex database structures efficiently. This means thinking about performance, not just correctness.

Query Plan Analysis · Indexing Strategies · Window Functions & CTEs (Advanced) · Database Design Principles (Basic) · Stored Procedures & Views

  • This month: Take an advanced SQL course focusing on performance tuning and complex queries.
  • Month 2: Review your most frequently used SQL queries and try to optimise them, comparing execution times.
  • Month 3: Work with a database administrator or senior engineer to understand our current indexing strategy and suggest improvements for your specific use cases.
  • Month 4: Document a complex SQL query you've written, explaining its logic and any performance considerations.

Quick win: Start using `EXPLAIN ANALYZE` on your SQL queries to understand their performance characteristics and look for obvious bottlenecks.

11Staying current once you are in

What people here do to keep up
  • Actively participate in online data science communities (e.g., Kaggle, Towards Data Science) to learn from peers and stay current with new techniques.
  • Attend relevant industry conferences or local meetups (virtual or in-person) to network and hear about real-world applications of data science.
  • Take advanced online courses or specialisations in areas like deep learning, natural language processing, or MLOps to expand your skillset.
  • Contribute to open-source data science projects if you're passionate about a particular area, it's a great way to learn and build a portfolio.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering & LLM Integration

Critical within 6 months—this isn't some far-off future, it's happening right now. Our competitors are already using tools like GPT to draft reports in 10 minutes that used to take 2 hours. Data scientists who figure this out will outproduce their peers by a significant margin. It's about working smarter, not harder.

  • Context Windows & Token Limits
  • Temperature Settings
  • RAG Architectures
  • Output Validation & Hallucination Detection
  • Prompt Chaining

Responsible AI & Ethics

Important within 12 months. As our models become more powerful and impact more areas of the business (and our customers' lives), ensuring they are fair, transparent, and unbiased isn't just a 'nice to have' – it's a legal and ethical imperative. Regulators are paying attention, and so should we.

  • Bias Detection & Mitigation
  • Model Interpretability (XAI)
  • Data Privacy & Anonymisation
  • Fairness Metrics
  • Ethical AI Frameworks

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Exploratory Data Analysis (EDA)
  • Statistical Modelling & Inference
  • Feature Engineering & Selection
  • Machine Learning Lifecycle Management (MLOps) Principles
  • Data Wrangling & ETL Design (Foundational)
  • Model Validation & Evaluation

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Associate Data Scientist (L1) Promotion

    1.5 - 2.5 years

    Skills to master

    • Mastering independent project execution, demonstrating strong problem-solving, and consistently delivering accurate, impactful insights.

    You're ready to move on when

    • Successfully owned and delivered 3-5 end-to-end analytical projects with minimal supervision.
    • Consistently received positive feedback on code quality and documentation from peers and seniors.
    • Proactively identified and resolved data quality issues without needing to be prompted.
    • Effectively communicated complex findings to non-technical stakeholders, leading to actionable decisions.
  2. 2

    Transition from Data Analyst or BI Analyst

    2 - 4 years

    Skills to master

    • Developing strong programming skills (Python/R), understanding statistical modelling, and gaining experience with machine learning algorithms.

    You're ready to move on when

    • Built a portfolio of personal projects demonstrating machine learning applications beyond basic reporting.
    • Completed relevant certifications (e.g., AWS ML Specialty) or advanced online courses in data science.
    • Demonstrated a deep understanding of statistical inference and hypothesis testing in previous roles.
    • Can clearly articulate the difference between descriptive, predictive, and prescriptive analytics.
  3. 3

    Transition from Software Engineer with Data Interest

    2 - 3 years

    Skills to master

    • Familiarity with data science specific libraries (scikit-learn, pandas), statistical concepts, and the nuances of data cleaning and feature engineering.

    You're ready to move on when

    • Has worked on projects involving large datasets and understands data warehousing concepts.
    • Developed a keen interest in applying statistical and machine learning techniques to business problems.
    • Comfortable with Python and has started exploring data science frameworks.
    • Understands the importance of model validation and evaluation metrics.

15Where this role leads

The long view: This work can lead to a deep technical specialism, or to leading a team of data scientists.

16Pay and demand

ONS's coding index maps “Data Scientist” to more than one occupation, so there is no one median to quote. Rather than pick, here is each one it could be, with its own figure:

  • IT business analysts, architects and systems designers £60,288 a year
  • Actuaries, economists and statisticians £53,342 a year

ONS Annual Survey of Hours and Earnings, from the April 2025 survey, about six months old when published, as ASHE always is, under the Open Government Licence.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Data Scientist is actually changing.

Where it leads

Roles this leads to

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Practical Data Science, worked against Data Scientist.

Practical Data Science Level 4

Applied to your work in Data Scientist

The objective of this unit is to enable learners to apply statistical and machine learning techniques to solve data science problems. Learners will gain practical skills in regression analysis, forecasting, model creation and tuning, natural language processing, and data mining to extract valuable insights from data.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Data Scientist plan, free
See Your Progress Grow Illustration
Data Scientist
  • Exploratory Data Analysis (EDA)
  • Statistical Modelling & Inference
  • Feature Engineering & Selection
  • Machine Learning Lifecycle Management (MLOps) Principles
  • Data Wrangling & ETL Design (Foundational)
  • Model Validation & Evaluation
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

17The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Data Scientist is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior Data Scientist (L3)

    2 - 3 years from Data Scientist

    You'll move from owning well-defined projects to tackling ambiguous, complex business problems. You'll lead major workstreams, mentor junior members, and start influencing technical decisions across the team.

    • Designing & Implementing Complex ML Solutions Moving beyond standard models to custom solutions for unique problems.
    • MLOps Leadership Leading the deployment and monitoring of models in production, ensuring scalability and reliability.
    • Technical Architecture Contribution Helping design the data and model infrastructure for new projects or capabilities.
    • Advanced Feature Engineering Developing novel features from diverse data sources to unlock new model performance.
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, the grunt work in data science can be a drag. But what if you could offload the tedious bits to an AI assistant? Imagine getting back hours every week to focus on the truly interesting, impactful problems. That's exactly what we're doing here.

As a Data Scientist, you'll be at the forefront of using AI to make your job easier and more effective. We're not talking about replacing you; we're talking about giving you a superpower. From writing boilerplate code to making sense of complex algorithms, AI is here to help you work smarter, not harder. Here's a peek at how you'll be using it day-to-day:

Boilerplate Code Generation

Forget typing out repetitive code for data loading, cleaning, or basic plotting. Tools like GitHub Copilot will instantly generate standard Python code snippets for you, letting you focus on the unique logic of your analysis. It's like having a coding partner who never sleeps.

Automated Exploratory Data Analysis (EDA)

Instead of manually writing dozens of lines of code to understand a new dataset, you'll use libraries like `ydata-profiling`. These tools automatically generate comprehensive EDA reports in seconds, highlighting missing values, correlations, and distributions. You'll get to the 'aha!' moments much faster.

Algorithm & Debugging Research

Stuck on a complex statistical concept? Need to compare different machine learning algorithms quickly? Use ChatGPT or other LLMs to get instant explanations, compare pros and cons, or even get suggestions for debugging those cryptic error messages. It's like having an expert on call 24/7.

Documentation & Summary Drafting

After a deep dive, feed your key findings and code snippets into an LLM to generate a first draft of your project documentation for Confluence or a non-technical summary for a stakeholder email. This saves you loads of time on the less exciting, but crucial, communication tasks.

Common questions

Common questions

How do you become a Data Scientist?

Common routes in include Associate Data Scientist Promotion (1.5 - 2.5 years), Transition from Data Analyst or BI Analyst (2 - 4 years) and Transition from Software Engineer with Data Interest (2 - 3 years). Times vary with prior experience.

Where can a Data Scientist progress to?

This role can lead on to Senior Data Scientist (2 - 3 years from Data Scientist), depending on the skills you build.

What new skills matter most for a Data Scientist?

Increasingly, Prompt Engineering & LLM Integration and Responsible AI & Ethics. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

18Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

 More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills involved are transferable. They can lead to machine learning engineering, product analytics, quantitative research, or management consulting. Data science is a foundational skill across most tech-driven industries.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my Data Scientist plan, free What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.