Skip to content
JL JobLabs

CV Example · Tech · UK 2026

Data Analyst CV Example UK

Data analyst CVs in the UK fall into two camps: the dashboard-builder and the question-answerer. Hiring managers in 2026 want the second one. After placing analysts into retail, fintech and consultancies for over a decade, the pattern is clear: the CVs that get interviews show what business question you answered, what you found, and what changed because of it. SQL on every line is wasted space. The strongest analyst CVs read almost like product CVs: a problem, a piece of analysis, a recommendation, a measured impact. Tooling matters, but it sits underneath the work, not in front of it.

Alex By Alex · 12-year UK recruiter · Updated April 2026

Example header

Priya Sharma · Senior Data Analyst · 5 years · Bristol / Hybrid


Personal statement / Professional summary

Senior data analyst with five years embedded in commercial and growth teams at UK e-commerce and SaaS businesses. Strong on SQL, dbt and Looker, with a working comfort in Python for ad-hoc analysis. Best work happens when I'm sat next to a commercial owner trying to make a decision, not building dashboards no one opens. Last year, a basket-abandonment cohort analysis I ran led to a checkout change that recovered roughly £620k in annualised revenue across the UK store.

Bullet point examples

Strong bullets follow the same shape: action verb, specific scope, quantified outcome. Use these as patterns, not as copy-paste templates — the numbers must be your own.

Embedded analyst, commercial team at UK e-commerce retailer

  • Identified a basket-abandonment pattern in the checkout funnel that, once fixed, recovered roughly £620k of annualised UK revenue.
  • Built a churn-risk model in SQL and Python that flagged at-risk subscribers 30 days early; retention team's intervention recovered 18% of flagged customers.
  • Replaced a 40-tab Excel model with a dbt-powered Looker dashboard, cutting weekly trading-meeting prep from 6 hours to 25 minutes.

Data infrastructure and modelling

  • Migrated 80+ ad-hoc SQL queries into a structured dbt project with tests and documentation, reducing 'where does this number come from' Slack messages by an estimated 70%.
  • Defined the company's first set of certified metrics (revenue, active customer, gross margin) with finance, ending a long-running argument over whose number was right.

Stakeholder and exec analysis

  • Owned the weekly trading pack circulated to 30 commercial and exec readers, including the narrative summary the CFO presents to the board.
  • Ran a pricing-elasticity analysis across 1,200 SKUs that informed a 4% category-wide price increase, with no measurable volume drop in the following quarter.

Mentorship and process

  • Mentored two junior analysts on SQL and stakeholder management; both progressed to mid-level within 14 months.
  • Wrote the team's analysis-request intake template, cutting average turnaround on stakeholder requests from 9 days to 3.

Earlier role: analyst at SaaS startup

  • Built the first cohort retention model in SQL, replacing a finance estimate; the corrected number changed the company's CAC payback assumption from 14 to 22 months.
  • Set up the BI stack (Fivetran, dbt, Looker) for a 25-person company in 6 weeks, on a £40k annual budget.

Skills section — what to list

Mirror the skills exactly as they appear in target job ads. The ATS reads this section literally — synonyms hurt match scores.

SQL (advanced, including window functions and CTEs)dbtLookerTableauPython (pandas, numpy, scikit-learn basics)Excel and Google Sheets (advanced)BigQuery / Snowflake / RedshiftCohort and retention analysisA/B test design and read-outStatistical significance testingData modelling (Kimball)Git and version-controlled analysisStakeholder requirements gatheringCommercial and trading analysisForecasting (basic)

Data Analyst-specific CV mistakes that get you binned

  • × Listing tools as a wall (SQL, Python, R, SAS, Tableau, Power BI, Looker, Excel). It reads as junior. Pick the four or five you'd be tested on tomorrow.
  • × Bullet after bullet describing dashboards built. Hiring managers want the question the dashboard answered and whether anyone used it.
  • × No mention of stakeholders. If your bullets are all 'analysed X', I assume you sat in a corner. UK hiring managers in 2026 want analysts who can hold a room.
  • × Confusing a recommendation with an outcome. 'Recommended a 4% price rise' is half a bullet. 'Recommended a 4% price rise, implemented across 1,200 SKUs, no measurable volume drop' is the full one.
  • × Putting a 'Certifications' section that lists six week-long courses. One named, completed certification (e.g. dbt, Tableau Desktop Specialist) is worth more than five logos.

Common questions

How important is Python for a UK data analyst CV in 2026?
It's now expected at mid-level and above in most UK tech and fintech roles, and a clear differentiator at junior level. You don't need to be a software engineer; you need to be able to load a dataset, do a clean analysis, and produce a chart without having to ask. If your day job is SQL-only, build one or two real Python projects on public datasets and put them under a 'Selected analysis' heading. Hiring managers prefer one well-explained Python notebook over a generic 'Python (intermediate)' bar on a skills section.
Should I include a Tableau or Looker portfolio?
Only if you can show real work and not toy datasets. Most companies don't let you share work dashboards, so the cleaner option is one or two case-study pages on a personal site that walk through a question, the data you used, the analysis steps, and the recommendation. Use anonymised or synthetic data if necessary, and explain the choice. UK hiring managers in 2026 are far more interested in whether you can think than whether you can colour a bar chart correctly.
Do I need a degree in statistics or maths to be a data analyst?
No, and increasingly UK hiring managers don't filter on it. Half the strong analysts I've placed in the last three years came from economics, geography, business, or a non-graduate route through ops or finance. What matters is whether you can write clean SQL, structure an analysis, and explain it to a non-technical stakeholder. If your degree isn't quantitative, lean harder on the bullets: name the techniques (cohort analysis, A/B test read-outs, regression) and show the business outcome each one produced.