Data analyst interview questions and answers (UK, 2026)
The SQL, stakeholder and data-quality questions UK data analyst interviews actually ask, and how to structure answers with real evidence.
What interviewers are really assessing
The interviewer's real question is: can I put this person in front of a stakeholder and trust the numbers that come back. Technical rounds test SQL (joins, aggregation, window functions) and Excel, but the deciding rounds are about judgement: how you handle ambiguous requests, dirty data, and discovering you were wrong. The usual UK format is an HR or recruiter screen, a technical test or take-home analysis, then an interview with the hiring manager, often with a business stakeholder sitting in to see whether you translate or jargon. Bring one analysis you can walk through end to end, because someone will ask for it.
Data Analyst interview questions and model answers
For each question: why it is asked, and the structure of a strong answer. Adapt the worked examples to your own experience; interviewers follow up, so never borrow a story.
1. Walk me through an analysis you did end to end, from request to result.
Why they ask it: It tests whether you can own the whole workflow or only execute steps someone else has framed.
Structure: the request as it arrived, how you clarified it, the data work, the finding, and what the business did about it. A worked sketch: asked vaguely "why is churn up", you reframed it as a cohort question, pulled twelve months of subscription data in SQL, and found 60 percent of churners had never activated the reporting feature; the onboarding email sequence was changed and 90-day churn fell two points. The business action at the end is what separates strong answers.
2. How comfortable are you with SQL? Describe the most complex query you have written.
Why they ask it: CVs say "advanced SQL" so often that interviewers calibrate the claim directly.
Be precise about constructs and honest about limits: for example, a multi-CTE query using ROW_NUMBER to deduplicate event data before joining it to a customers table, where the trap was a LEFT JOIN silently multiplying rows. Say how you validated it, such as reconciling the output total against a known monthly figure. Naming a validation habit earns more trust than naming another keyword.
3. Two data sources disagree on a key figure. What do you do?
Why they ask it: Reconciling conflicting sources is a weekly reality, and guessing wrong means wrong numbers reaching decision-makers.
Reconcile definitions before touching pipelines: is revenue inclusive of VAT, are refunds netted, which timezone bounds the day. Then trace lineage to where the figures diverge, quantify the gap, and agree one canonical source with the data owner, documenting the decision. A good sketch: finance reported 4 percent higher revenue than the dashboard because the warehouse excluded gift card redemptions; you documented the definition and added it to the metric dictionary.
4. Tell me about a time your analysis turned out to be wrong.
Why they ask it: Analysts who cannot admit error ship wrong numbers twice.
Name the actual error, how it was caught, and the correction speed: for example, a WHERE clause excluded one region, overstating growth, and a country manager spotted the gap. Cover telling stakeholders promptly with the corrected figure, and the guard you added afterwards, such as sanity-checking totals against finance before anything leaves your desk, or a peer review step for board-bound numbers. The recovery and the new check are the answer; the mistake is just the setup.
5. How would you explain a technical finding to someone non-technical?
Why they ask it: Analysis only creates value when a decision-maker understands it well enough to act.
Lead with the decision, not the method: instead of describing a regression, say "customers who contact support twice in their first month are three times as likely to leave, so we should intervene after the second contact". One chart, no jargon, uncertainty stated in plain words. If asked for a live example, pick a real finding and give the stakeholder version in two sentences, then the technical version, to show you hold both.
6. Three departments each want their request done first. How do you handle the week?
Why they ask it: Ad hoc overload is the role's daily failure mode, and silent triage breeds resentment.
Show a visible system, not heroics: a transparent request queue, triaged by effort against business impact, with recurring asks pushed to self-serve dashboards. Give an example of a conflict you escalated with a recommendation ("the pricing analysis affects a decision this Friday, the other two can wait a week") rather than quietly choosing. Interviewers are checking you will not become either a bottleneck or a doormat.
7. A dashboard you built is not being used. What do you do?
Why they ask it: Unused dashboards are the most common form of wasted analyst work, and the fix is diagnostic, not technical.
Treat it as a user research problem: talk to the intended users, find the question they actually ask each week, and rebuild around that. A worked sketch: a 20-tile sales dashboard was ignored until you cut it to the five numbers the Monday trading meeting runs on and put it on the meeting room screen; usage went from two views a week to daily. Mention measuring adoption, which most candidates never think to do.
8. Why analytics, and why this company?
Why they ask it: Motivation answers reveal whether you researched the company or are running a volume job search.
Connect something specific about their data to your interest: the kind of dataset (retail loyalty transactions, energy smart meter data), their stack if you know it, or a business question you would genuinely enjoy owning. Then anchor your analytics motivation in a real moment, such as the first time an analysis you did changed a decision. Specific beats enthusiastic, every time.
Questions to ask them
Asking nothing reads as low interest. These three work because they show you understand the role’s reality, and their answers tell you whether you want the job:
- What does the data stack look like, and who owns the pipelines: is there a data engineering team, or does that fall to analysts?
- Can you give me an example of a recent decision that changed because of analysis?
- What is the split between ad hoc requests and longer project work, and who protects that balance?
Practise out loud, not in your head
Reading model answers feels like preparation, but interviews are spoken: the first time you say an answer aloud should not be in the room. Rehearse each story out loud until it flows without sounding scripted. If you want a realistic run-through, Vouch’s AI coach Maya runs voice mock interviews built from a real job advert and your own CV, and gives feedback per question, which is the closest thing to the actual experience you can do from your sofa.
And since a strong interview starts with getting invited: the free cover letter generator writes a UK-format letter from your real experience, and the UK personal statement guide covers the 50-80 words at the top of your CV that decide whether it gets read.
Frequently asked questions
How should I prepare for a data analyst interview?
Prepare one or two analyses you can walk through end to end, with the business outcome attached. Practise SQL out loud: joins, GROUP BY with HAVING, and one window function, since narrating a query is harder than writing one. Look up the company's likely KPIs (conversion, churn, basket size) so your examples land in their language.
What format do UK data analyst interviews take?
Usually three stages over two to three weeks: a screen, a technical assessment (a live SQL or Excel exercise, or a take-home analysis of a sample dataset with a short presentation), then a competency interview with the hiring manager, often with a business stakeholder present. Some employers replace the take-home with a live case discussion.
How do I handle the salary question in a data analyst interview?
Give a researched range for your market and level rather than a single figure: analyst salaries vary sharply between London and the regions, and between sectors. Anchor it to evidence: "adverts for similar roles with this SQL and Power BI mix are listing thirty-two to thirty-eight, and I am targeting that range". Then ask about progression, because analyst-to-senior steps often move pay more than negotiation does.