The 12 Data Analyst Interview Questions You Will Actually Get in the UK (with Honest Answers)

Most online lists of Data Analyst interview questions are written for the US market and reused without thought. UK interviews look different: fewer riddles, more business framing, more SQL on the spot, and an explicit emphasis on stakeholder communication.

Below are the 12 questions that come up again and again across UK interviews in 2026, broken into the four rounds you will typically face.

If you are still preparing your portfolio for these interviews, our UK Data Analyst portfolio guide pairs well with this one.

Round 1: The Recruiter Screen (3 questions)

1. Walk me through your CV in two minutes.

This is not a chat - it is a filter. Strong answers follow a clean structure: starting point, what you built, why you moved into data, and the role you are targeting. Avoid listing every job and every tool. End with one sentence that connects you to this specific role.

2. Why a Data Analyst role, and why now?

UK recruiters listen for two things: a credible reason for the move, and evidence you understand the job. A weak answer is "I love data". A strong answer connects a real experience (you ran an internal report, fixed a process with a spreadsheet, got curious about why a number was wrong) to the responsibilities of the role you are applying for.

3. What is your salary expectation?

Always answer with a range, not a number. Anchor it to UK market data, not a personal wish. Our UK Data Analyst salary guide gives realistic ranges by region and experience.

Round 2: The Technical Interview (4 questions)

4. Write a SQL query to find the top 5 customers by revenue last quarter.

This is the most common live SQL question in UK interviews. The interviewer is watching three things: do you ask about the schema, do you handle the date range correctly, and do you sort and limit. Talk through your assumptions out loud - that is half the score.

5. What is the difference between INNER JOIN and LEFT JOIN, and when does it matter?

Beyond the textbook answer, give a concrete example: customers without orders, products without sales, campaigns without conversions. UK interviewers want to hear you connect the SQL concept to a real reporting risk - silently dropping rows that should have been counted.

6. Explain a window function you have used.

ROW_NUMBER, RANK, LAG, LEAD, and rolling sums all qualify. Pick one and walk through a real use case: ranking customers by spend, finding the previous order date, calculating a 7-day moving average. If you are not comfortable here yet, our SQL beginner guide covers exactly this.

7. We have a slow query. How would you start investigating?

This is a reasoning question, not a trivia question. A solid structure: look at the execution plan, check for missing indexes, look for unnecessary subqueries or joins, check whether filters are applied before joins, and confirm whether the slowness is consistent or intermittent. You do not need to be a DBA - you need to show you can think clearly under pressure.

Round 3: The Case Study or Take-Home (3 questions)

8. Sales dropped 12% last month. What would you investigate?

This is a structure test. A strong answer breaks the problem down: is the drop in volume or price, in which region, in which product, in which customer segment, is it real or a data issue? UK interviewers reward candidates who frame the question before reaching for a tool.

9. How would you define and measure customer churn for this business?

There is no single right answer - that is the point. The interviewer wants to see you ask: what is the business model (subscription, transactional), what counts as a customer, over what window do we measure inactivity, and how do we treat reactivations? Show you understand that metric definitions are decisions, not formulas.

10. Take this dataset home and present three findings on Tuesday.

Take-home tasks are evaluated on clarity, not complexity. Five rules to remember:

• start your write-up with the business question, not the data
• three findings is the right number - not seven
• each finding should have a number, a why, and a so-what
• at the end, state one thing you would investigate next
• include a short note on data limitations

Round 4: Behavioural and Stakeholder Fit (2 questions)

11. Tell me about a time you had to explain a complex finding to a non-technical stakeholder.

Use the STAR structure (Situation, Task, Action, Result), but do not recite it mechanically. The detail that lands in UK interviews is usually how you adapted - did you switch from a chart to a single number, did you reframe the metric in their language, did you check understanding by asking them to summarise back?

12. Tell me about a time a stakeholder disagreed with your numbers.

This is the most underrated question in UK Data Analyst interviews. The wrong answer is "I showed them I was right". The right answer is "I treated the disagreement as a signal that we did not share the same definition" - then you walked through how you reconciled, documented, and prevented it from recurring.

A Quick Pre-Interview Checklist

• refresh joins, group by, window functions, and CTEs in your preferred SQL dialect
• prepare two case-study stories from your portfolio you can talk through in five minutes each
• research the company's data stack - it is often listed in the job description
• have one thoughtful question ready about how the team measures success
• practise saying "I do not know" followed by how you would find out

The Honest Summary

UK Data Analyst interviews are less about clever puzzles and more about whether you can think clearly, write working SQL, communicate with a stakeholder, and hold a metric definition under pressure. Prepare for those four things and you will be ready for almost every question on the list.