Data, Analytics & AI

Skill areas

Data & Analytics

Data Analyst

A Data Analyst collects, cleans, and interprets structured and unstructured data to help organisations make better decisions. Core work includes writing SQL queries, building dashboards and reports in tools like Power BI or Tableau, conducting statistical analysis, and communicating findings clearly to non-technical stakeholders. Analysts work across departments — marketing, operations, finance, product — translating business questions into data queries and turning results into actionable insight.

Career information

Everything you need to know about this role

Salary, eligibility, background, qualifications, and where people typically work.

Expected salary range

P25 and P75 are the 25th and 75th percentiles for UK full-time pay (national benchmarks). UK median is the national full-time median salary.

P25UK medianP75

£29,000£39,000£54,000

Source: ONS Annual Survey of Hours and Earnings (ASHE), UK full-time gross annual earnings, April 2025 (released Oct 2025).

Entry

0–2 yrs

£28,000–£50,000

MidEst.

2–5 yrs

£46,000–£55,000

Senior

5+ yrs

£50,000–£70,000

Dot = average of the range; coloured bar shows min–max vs UK benchmarks above.

Eligibility limits

Right-to-work, checks, and role-specific requirements — tap to view.

Right to work in the UK required. No formal licence required. A degree is typically expected — data science, mathematics, statistics, computer science, or economics are preferred, though strong candidates from other disciplines are considered. Public sector roles may require BPSS. Roles working with sensitive personal data require understanding of GDPR obligations.

Understand eligibility rules →

How the role developed

The Data Analyst role has existed in various forms since the advent of business computing, but it was formalised and rapidly expanded by the explosion of digital data in the 2000s and 2010s. The rise of web analytics, CRM systems, and e-commerce created a demand for professionals who could extract insight from large, messy datasets without requiring a data science background.

Hadoop, then Spark, then cloud data warehouses democratised access to large-scale data processing, making the analyst role more powerful and more technical simultaneously.

The role today

Today, data analytics is one of the fastest-growing job categories globally — data roles occupied five of the top fifteen positions in the WEF Future of Jobs Report 2025. The field is evolving quickly: generative AI tools are automating routine reporting tasks, raising the bar for analysts who need to demonstrate judgement, domain expertise, and communication skills alongside technical proficiency.

Explore progression

See where this role can take you

Sample career paths, linked roles, and typical UK timelines for moving up or sideways.

Next step

Prepare for your interview

10 common questions with sample answers, structure tips, and what recruiters look for.

Interview prep10 questions

Practise the questions you'll actually get asked

Study the most common interview questions for this role, with structured guidance and strong sample answers.

Common interview questions

Answer guidance, sample responses, and tips for each question.

Ranked by how often this question appears across real interviews.

openingdata-analystintroduction
Why they ask
Data analyst interviews still open with your story to gauge communication and analytical journey.
What they want
Concise path into data, tools used, and business impact of your work or projects.
How to structure your answer
Current background and data focus
Project or work highlight with outcome
Why data analyst here
Ninety-second structure
Sample answer
I am a mathematics graduate who has completed a data analytics bootcamp and a university project analysing retail sales trends. I enjoy turning raw data into charts and recommendations non-specialists can use. My project used SQL and Python to identify seasonal products driving margin, which my tutor presented to a local shop owner. I also volunteer spreadsheet support for a charity tracking donor campaigns. I am detail-oriented, curious about data quality, and comfortable presenting findings. I want to grow as a data analyst here because your customer analytics team would let me apply those skills to real business decisions at scale.
Common mistakes
Listing tools without business context
No portfolio or project mentioned
Overly academic with no practical delivery
Bonus tips
Mention portfolio or GitHub if available
Lead with impact then tools
Align with domain in job advert
motivationanalyticscareer
Why they ask
They want lasting interest in insight and decision support, not only coding for its own sake.
What they want
Motivation linking data to business outcomes and continuous learning of tools.
How to structure your answer
What you enjoy about analysis
Example of insight that mattered
Career direction
Fit for this role
Sample answer
I want to work in data analytics because I like evidence-based decisions. Data removes guesswork when teams debate what customers do or which campaigns work. I enjoy cleaning messy datasets, finding patterns, and explaining results clearly. A charity dashboard I built helped coordinators focus on high-value donor segments. I am motivated to deepen SQL, BI, and statistics while partnering with stakeholders who act on insights. This role offers the volume and variety of data I need to grow from junior analyst to someone trusted for recommendations that move KPIs.
Common mistakes
Only mentioning high salaries or remote work
No stakeholder or business angle
Claiming data science and analytics are identical without nuance
Bonus tips
Name a KPI relevant to the employer
Show humility about learning domain knowledge
Mention ethical use of data briefly
sqlexceltools
Why they ask
Junior analysts must choose the right tool; this shows practical understanding of scale and workflow.
What they want
Excel for exploration and smaller sets; SQL for querying databases at scale; when to use each.
How to structure your answer
Primary purpose of each
Scale and collaboration differences
Strengths of Excel
Strengths of SQL
When to combine
Sample answer
Excel is excellent for quick exploration, charts, and smaller datasets on one machine, especially when stakeholders want interactive what-if analysis. SQL is a language for querying relational databases efficiently—filtering millions of rows, joining tables, and aggregating with repeatable scripts. SQL supports governed data sources and scheduled pipelines; Excel files can become fragile when shared. I often prototype in Excel or a BI tool, then productionise logic in SQL for consistency. Choosing depends on data size, refresh needs, and whether multiple people need the same defined metrics.
Common mistakes
Saying SQL replaces Excel entirely always
Unable to give a use case for either
Ignoring data governance
Bonus tips
Mention Power Query as bridge if you use it
Give an example row count where you switch tools
Note version control challenges in Excel
data-cleaningqualityetl
Why they ask
Most real-world data is dirty; cleaning approach reveals rigour and documentation habits.
What they want
Profile data, handle nulls and duplicates, standardise formats, validate, document transformations.
How to structure your answer
Profile and understand sources
Handle missing values and duplicates
Standardise types and categories
Validate against business rules
Document steps for reproducibility
Sample answer
I start by profiling: row counts, null rates, distinct values, and obvious outliers. I document the source system and extraction time. I fix structural issues—trim whitespace, standardise dates to ISO format, and map inconsistent category labels using a reference table. For missing values I choose imputation or exclusion based on business rules, never silently dropping without noting impact. I deduplicate using keys agreed with stakeholders. I validate totals against source reports where possible. In SQL or Python I keep transformation scripts in version control so analysis is reproducible and auditable.
Common mistakes
Deleting outliers without investigation
No validation or documentation
Assuming clean exports from source systems
Bonus tips
Mention great expectations or similar if used
Give a brief messy data example from a project
Discuss communicating data quality limits to stakeholders
dashboardpower-biproject
Why they ask
They need end-to-end evidence: problem, data, visuals, metrics, and how stakeholders used it.
What they want
Clear narrative with tools, design choices, and impact.
How to structure your answer
Business question
Data sources and cleaning
Metrics and visuals chosen
Outcome and feedback
Sample answer
For a bootcamp capstone I built a Power BI dashboard for fictional e-commerce leadership tracking conversion funnel, average order value, and return rate by channel. I joined web analytics and order tables in SQL, handled duplicate sessions, and defined consistent date filters. I used clear KPI cards, a funnel chart, and a slicer for campaign. I wrote a one-page guide explaining definitions so marketing and finance would interpret numbers the same way. Presenting to classmates acting as stakeholders, they said the returns spike by category prompted a hypothetical supplier review. I learned definitions matter as much as charts.
Common mistakes
Beautiful charts with no business question
Cannot explain metric definitions
No mention of audience
Bonus tips
Bring screenshots if interview allows
Explain one trade-off you made
Mention refresh schedule for production dashboards
data-qualitytroubleshootingstakeholders
Why they ask
Wrong data drives wrong decisions; they test troubleshooting and communication discipline.
What they want
Pause consumption, trace lineage, compare sources, fix upstream, document, notify stakeholders.
How to structure your answer
Stop sharing flawed outputs
Reproduce and isolate the issue
Check pipeline and source changes
Correct and communicate impact
Add monitoring if needed
Sample answer
If data looked incorrect I would pause publishing dashboards or reports that depend on it and note the time range affected. I would reproduce the issue with simple checks—row counts, sums against a trusted report, and recent deployments or ETL changes. I would compare staging versus production and speak with data engineering if pipelines broke. Once root cause is found I would fix or backfill, document the incident, and tell stakeholders what was wrong, what changed, and whether past decisions need revisiting. I would suggest a validation test to catch similar issues earlier.
Common mistakes
Silently adjusting numbers to match expectations
Blaming users without investigation
Not informing stakeholders of past impact
Bonus tips
Mention data contracts or SLAs if familiar
Give an example where you caught a bug
Show calm transparency under pressure
communicationstorytellingstakeholders
Why they ask
Analysis only matters if decision-makers understand and trust it.
What they want
Lead with insight and action, simple visuals, defined metrics, and caveats.
How to structure your answer
Start with headline insight
Use plain language and relevant KPIs
Show one clear visual
State limitations and recommended action
Sample answer
I would open with the answer they care about: returns rose fifteen percent last quarter, mainly in footwear online. I would avoid SQL jargon and define metrics once—what counts as a return. I would use one simple chart with labelled axes and traffic-light context against targets. I would explain likely drivers based on evidence, not speculation, and separate correlation from causation. I would recommend specific actions—review sizing guide, check warehouse pick errors—and note data gaps. I would send a short written summary after the meeting so finance and marketing align on definitions.
Common mistakes
Walking through every query step
Overloading slides with charts
No recommended next step
Bonus tips
Practice executive summary in three sentences
Anticipate questions on data freshness
Offer office hours for metric definitions
statisticscorrelationcausation
Why they ask
Misinterpreting relationships leads to bad business decisions; statistical literacy is essential.
What they want
Clear definitions, example, and how you would test or avoid causal claims incorrectly.
How to structure your answer
Define correlation
Define causation
Example where correlation misleads
How to investigate causality carefully
Sample answer
Correlation means two variables move together statistically—for example ice cream sales and sunburn incidents rise in summer. Causation means one variable directly produces change in another. Correlation does not prove causation because confounding variables or coincidence may explain the pattern. Ice cream does not cause sunburn; hot weather drives both. In business, higher app usage might correlate with revenue without causing it if marketing drove both. I would avoid causal language unless supported by experiments, time order, and domain theory, and I would suggest A/B tests or controlled analysis when decisions require proof.
Common mistakes
Using correlation and causation interchangeably
No example
Claiming analysts never need causation
Bonus tips
Mention spurious correlations humorously but briefly
Note regression does not alone prove causality
Show intellectual honesty with uncertain findings
toolssqlpython
Why they ask
Tooling fit speeds onboarding; they want honest proficiency levels.
What they want
SQL, Excel, Python or R, BI tools—with examples of deliverables.
How to structure your answer
Query and transformation tools
Visualisation tools
Collaboration or notebook tools
Learning goals
Sample answer
I use SQL in PostgreSQL and BigQuery-style environments for joins and aggregations. I use Excel and Google Sheets for ad hoc analysis and stakeholder-friendly tables. I analyse in Python with pandas and matplotlib for projects requiring scripting. I build dashboards in Power BI and have basic Tableau exposure from bootcamp. I version scripts on GitHub and document metrics in Confluence-style write-ups. I am keen to learn your warehouse, orchestration, and semantic layer tools during onboarding while delivering value with SQL and BI immediately.
Common mistakes
Tool list with no project linkage
Claiming expert in everything
Ignoring git or documentation practices
Bonus tips
Align to stack in job description
Mention dbt or Airflow only if true
Offer portfolio walkthrough
impactdecision-makingclosing
Why they ask
Closing with impact reinforces that you analyse to decide, not only to report.
What they want
Concrete decision, data used, outcome, and reflection.
How to structure your answer
Decision context
Data gathered and analysed
Choice made
Outcome and learning
Sample answer
Leading a university society event, we debated two ticket price points. I surveyed past attendance, modelled expected turnout at each price using last year's conversion, and estimated revenue minus costs in a simple spreadsheet. Data suggested a slightly lower price with higher volume would maximise revenue and inclusivity. We chose that option and sold out with record first-time attendees. The decision was not only intuitive—it was supported by assumptions we documented. That experience confirmed why I want a career where data guides fair, effective choices rather than gut feeling alone.
Common mistakes
Analysis with no actual decision
Fabricated metrics
Cannot explain limitations of your data
Bonus tips
Use business workplace example if you have one
Quantify outcome
End with enthusiasm for the role

Back to Data, Analytics & AI or all industries.

Data Analyst

Everything you need to know about this role

Expected salary range

Eligibility limits

How the role developed

The role today

Where this role can take you

Overview

Why this path matters now

Practise the questions you'll actually get asked

Everything you need to know about this role

Expected salary range

Eligibility limits

How the role developed

The role today

Where this role can take you

Overview

Why this path matters now

Practise the questions you'll actually get asked

Sample career paths

Related roles in this library

Career tips