Data Analyst CV Example in 2026 [Free Checklist]

Before you write the first line, decide what kind of data analyst role you are targeting. A product analytics job, a finance reporting job, a BI analyst role and an operations analyst role can all use similar tools, but they look for different evidence.

Read the advert and mark the repeated signals. Look for words such as SQL, Power BI, Tableau, Looker, Python, Excel, forecasting, dashboards, data quality, reporting automation, customer behaviour, churn, pricing, KPI definitions, stakeholder management or experimentation. These words tell you what the recruiter will scan for first.

Your Data Analyst CV should then make the closest evidence visible in the first half-page. If the role is dashboard-led, lead with dashboard design, self-serve reporting and reporting adoption. If the role is forecasting-led, lead with planning packs, assumptions, variance analysis and scenario work. If the role is more commercial, show how your analysis shaped revenue, retention, pricing, cost, customer experience or operational decisions.

This first decision prevents a common problem: a CV that is technically accurate but badly positioned. You may have impressive experience, but if the right evidence is buried on page two, the recruiter may never reach it.

Your profile should be short, specific and easy to understand. A useful data analyst personal statement normally covers three things: your level of experience, the type of analysis you do and the business value you create.

A weak profile says that you are analytical, motivated and skilled with data. A stronger profile says what data you work with, which tools you use and what decisions your work supports. For example:

"Data analyst with four years of experience building SQL datasets, Power BI dashboards and weekly trading reports for ecommerce and subscription teams. Known for turning messy data into clear reporting that improves planning, reduces manual spreadsheet work and helps non-technical stakeholders act on the numbers."

That wording gives the recruiter more to work with. It names the tools, context and result. It also avoids a mistake many applicants make: trying to sound senior through vague adjectives. Your profile does not need to call you dynamic, detail-oriented or results-driven. It needs to show what kind of analysis you do and why it matters.

For a junior data analyst CV, keep the same structure but change the evidence. You might mention a degree project, apprenticeship, internship, SQL coursework, dashboard portfolio or placement. For a senior data analyst CV, add ownership. Mention reporting standards, KPI definitions, analytics roadmaps, mentoring, stakeholder influence or governance if those are genuinely part of your work.

The skills section should help a recruiter confirm that you match the role quickly. It should not become a dumping ground for every tool you have opened once.

Group your skills around the advert. A strong technical set might include SQL, Power BI, Excel, Tableau, Looker, Python, R, data modelling, data cleaning, forecasting, statistics, dashboarding, data visualisation, experiment analysis, ETL support and KPI reporting. You do not need every tool. You need the tools that fit the role and that you can defend.

Then include working strengths that matter in analysis roles. Stakeholder communication, data storytelling, documentation, commercial awareness, attention to detail, prioritisation and problem solving are all useful when backed by examples. Avoid listing soft skills that never appear elsewhere. If you write "stakeholder communication", the experience section should show a moment when you explained findings, clarified a definition or helped a team make a decision.

A good rule is to include fewer skills and make each one stronger. If your technical section has 20 tools, the reader may question which ones are core. If it has 8 to 12 well-matched skills and the bullets prove them, the CV feels sharper.

Most data analyst job descriptions include repeated duties: build dashboards, clean data, prepare reports, analyse trends, support stakeholders, maintain spreadsheets and present findings. These are useful starting points, but they are not enough on their own.

Each bullet should answer at least two of these questions:

• What data, tool or method did you use?
• Who used the analysis?
• What changed because of your work?
• How did you improve quality, speed, clarity, cost, revenue, retention or confidence?

Compare these two bullets:

• Responsible for weekly Power BI reporting.
• Redesigned weekly Power BI reporting for sales and operations teams, reducing manual preparation time by 8 hours per week and improving KPI consistency across regional reviews.

The second bullet is stronger because it gives tool, audience, result and business context. It also sounds like something an interviewer could ask about. That is the standard you want most bullets to reach.

When you do not have a precise number, use clear outcome language instead of inventing one. You can write that you standardised KPI definitions, reduced duplicate reporting, improved handover notes, supported pricing decisions or helped stakeholders self-serve routine questions. Honest, specific wording is better than a made-up percentage.

SQL, Power BI, Tableau, Looker and Excel are often searched for quickly on a data analyst CV. Put them where they are easy to find, but do not leave them as isolated keywords.

A SQL bullet should say what the query work did. Did you join customer and transaction tables? Rebuild a weekly dataset? Create reusable views? Clean inconsistent product tags? Add checks before a report went out? Support a dashboard refresh? These details show that you understand data beyond the tool name.

A BI bullet should show the dashboard purpose. A dashboard for executives, warehouse managers, product managers or customer support leads will have different measures of success. Mention the audience and the action. For example: "Built a Power BI retention dashboard for lifecycle and finance teams, combining cohort views, cancellation reasons and plan-level trends to support quarterly pricing discussions."

This level of context matters because many applicants list the same tools. The difference is whether your CV proves that you can use those tools in a business environment.

Projects are useful on a Data Analyst CV when they show skills that your employment history does not fully cover. They are especially helpful for junior candidates, career changers and people moving into a more technical analytics role.

A good project description should include the problem, data source, method and output. It should also say what the project taught or enabled. Avoid vague lines such as "created a dashboard project". Write something more concrete, such as: "Built a SQL and Power BI project using public transport data to identify peak delay patterns, clean incomplete records and present route-level trends in a self-serve dashboard."

Portfolio links can help, but do not rely on a link alone. Recruiters may not click it during the first scan. Summarise the strongest project in the CV itself so the value is visible even before the portfolio is opened.

For experienced analysts, projects can still work if they show cross-functional ownership, automation, data quality, forecasting or a reusable reporting asset. Keep them selective. If a project repeats the same evidence as your main job history, it may not need a separate section.

A junior data analyst CV does not need to pretend you have owned board-level reporting. It needs to prove that you can learn quickly, handle data carefully and explain your work clearly.

Use evidence from apprenticeships, placements, internships, university modules, bootcamps, volunteer projects, online portfolios, operational roles or admin roles where you used spreadsheets and reporting. If you supported a manager with weekly reports, cleaned customer lists, built Excel trackers, reconciled data or spotted errors, those examples can be relevant when written clearly.

The key is to show method. Explain how you checked the data, what tool you used, what output you created and who benefited. A junior bullet might say: "Built an Excel dashboard for a university retail dataset, using pivot tables and charts to compare weekly sales by product category and summarise findings for a group presentation." That is more useful than simply listing Excel as a skill.

Junior candidates should also be careful with language. Do not claim expert-level Python, advanced modelling or strategic ownership unless you can prove it. Confidence is good; overclaiming damages trust.

A senior data analyst CV should not just be a longer version of a junior CV. Recruiters expect stronger evidence of ownership, judgement and influence.

Show where you improved the reporting environment, not only where you produced reports. This might include setting KPI definitions, introducing dashboard QA, mentoring analysts, creating documentation, designing self-serve reporting, challenging weak assumptions, improving forecast reliability or aligning teams around a shared metric.

Senior bullets should often include the stakeholder group. Finance, product, operations, marketing, sales, customer success and leadership teams all use analysis differently. Naming the audience helps the reader understand your level of exposure.

A strong senior bullet might say: "Led a KPI definition review across finance, product and lifecycle teams, resolving conflicting funnel measures and creating reporting documentation used in monthly planning cycles." That shows stakeholder influence, data governance and practical value in one line.

If you manage people, mention it. If you do not manage people, you can still show leadership through standards, mentoring, project ownership and decision support. Be precise about the kind of leadership you provide.

Education matters on a Data Analyst CV, but it should not dominate unless you are early in your career. Include degrees, apprenticeships, A levels, professional training or certifications that support your target role.

Relevant subjects include statistics, economics, mathematics, computer science, data science, business analytics, finance, psychology, engineering and social sciences with quantitative methods. Short courses can also help when they prove practical tools such as SQL, Power BI, Tableau, Python or Excel.

For junior candidates, add one or two relevant modules or projects if they are genuinely useful. For example, econometrics, statistical modelling, database design, business intelligence or research methods can strengthen the application. For experienced candidates, keep education shorter and give more space to recent outcomes.

Certifications should be treated as supporting evidence. A Power BI or SQL course can help, but it will not replace a bullet showing how you used those skills. Pair training with a project or work example wherever possible.

Data analysis is technical work, but your CV should still be simple to read. Use standard headings such as Profile, Key Skills, Experience, Projects, Education and Certifications. Keep dates consistent, use reverse chronological order and avoid dense paragraphs.

Most UK data analyst CVs should be one or two pages. One page can work for junior candidates with limited experience. Two pages are normal if you have several roles, strong projects or relevant certifications. Three pages are rarely needed unless the role is unusually senior or academic.

Use short bullets rather than long paragraphs. Put the tool and outcome close together. Recruiters should not have to read six lines to find out that you used SQL to improve reporting accuracy.

Keep visual design restrained. A dashboard-style CV might look clever, but it can make the page harder to parse and less reliable for screening systems. Clear hierarchy, plain text, sensible spacing and consistent formatting usually work better.