This Data Analyst CV template shows how to present SQL, Excel and Power BI experience alongside reporting improvements, data-quality work and business recommendations. The example follows a progression from Reporting Assistant to Data Analyst in retail.
Download the editable Word CV, explore the complete example below and use the guide to choose and present the strongest evidence from your own analytical work.
Filename: FreeCVDownload_Data_Analyst-1.docx
Content of this CV template
Alex Morgan | Data Analyst
a: Leeds, West Yorkshire e: [email protected]
t: 07700 900456 portfolio: example.com/alex-morgan
Profile
- Data Analyst with six years in retail reporting, progressing from reporting support to owning sales and fulfilment analysis for a homeware retailer.
- Use SQL, Excel and Power BI to turn order, stock and returns data into reporting that trading and operations teams can act on.
Work history
Data Analyst
Pennbeck Homeware Ltd, Leeds | June 2023 – present
- Own weekly sales, returns and fulfilment reporting for the trading and operations teams, covering an online shop and eight stores.
- Rebuilt the weekly trading pack using SQL Server views and Power BI, reducing preparation from four hours to 90 minutes per week, measured over eight reporting cycles.
- Agreed net sales and return-rate definitions with Finance; reconciled dashboard totals to order exports and documented exclusions before release.
- Analysed late dispatches by warehouse, product and order time. Recommended an earlier cut-off for bulky items; late dispatches fell from 8.4% to 6.9% during a six-week pilot at one warehouse.
- Added checks for duplicate order lines, missing product codes and unmatched returns. Worked with the systems team to fix an import that was duplicating refunded items.
- Use Python and pandas to compare supplier files with the product master, producing an exception list for buyers; keep scripts and SQL changes in Git for review.
- Present findings in fortnightly trading meetings, explaining seasonal effects and data gaps; trained six colleagues to use report filters and drill-through pages.
Reporting Assistant
Pennbeck Homeware Ltd, Leeds | September 2020 – May 2023
- Prepared Excel sales and stock reports using PivotTables and SUMIFS, checking store totals and investigating missing daily files.
- Combined eight store exports in Power Query, cutting the daily stock report from 45 to 20 minutes across a four-week check.
- Investigated stock exceptions with store managers and recorded corrections so repeat issues could be traced to their source.
- Learned SQL on the reporting database and took over standard extracts, with queries reviewed by the senior analyst.
Qualifications
Microsoft Certified: Power BI Data Analyst Associate
Microsoft | Awarded May 2024; renewed May 2026
BSc Mathematics and Statistics – 2:1
University of Leeds | September 2017 – July 2020
Skills
- SQL Server: joins, CTEs, aggregations and window functions for reporting and reconciliation.
- Excel: PivotTables, XLOOKUP, SUMIFS and Power Query for repeatable data preparation.
- Power BI: star-schema models, DAX measures, drill-through reports and scheduled refresh.
- Python: working knowledge of pandas for file checks and exploratory analysis.
- Data quality: duplicate and null checks, source reconciliation and documented validation rules.
- Analysis: trend and variance analysis, segmentation and comparisons that account for seasonality.
- Stakeholders: agreeing requirements, explaining limitations and recommending next steps.
- Git: versioning SQL and Python files and responding to peer-review comments.
Hobbies and interests
Enjoy walking in the Yorkshire Dales, volunteering at a local repair cafe and building small apps in my spare time.
How to write a data analyst CV
A strong Data Analyst CV makes it easy to see the kind of analytical work you can take on. Employers need to understand the data you work with, the questions you investigate and how colleagues use the results. Your choice of examples is what brings SQL, Excel and BI skills to life.
The most useful detail often sits between the software and the finished report: agreeing a measure with Finance, resolving a discrepancy between systems, building a repeatable reporting process or identifying a pattern that changes an operational decision. Give that work space on your CV.
Choose experience that fits the analytical role
Data Analyst roles can have quite different priorities. In operational reporting, the strongest evidence may be dependable management information, reconciled figures and improvements to recurring processes. A product analytics role may place greater emphasis on customer journeys, retention, experiments and recommendations to product teams. Finance roles may call for forecasting, variance analysis and an understanding of the commercial measures behind the reporting.
Use the responsibilities in the job description to decide which parts of your experience deserve the most space. If the team needs someone to improve its monthly reporting, foreground a reporting process you have developed or maintained. If it needs someone to investigate customer behaviour, lead with a relevant piece of analysis and the decision it informed.
Domain knowledge can make these examples considerably stronger. Sales and returns, service performance, energy consumption and subscription revenue each involve their own definitions and operating context. Naming the business area helps a recruiter understand the value of your experience, especially when several applicants use the same tools.
Use your profile to establish your level and focus
Your personal statement should introduce the analytical experience most relevant to the role. In a few sentences, establish your area of work, your principal tools and the contribution you can make. A profile built around retail reporting, SQL and Power BI gives the reader a much clearer starting point than a string of personal qualities.
For an experienced analyst, useful distinctions include owning a reporting area, working across several business functions, supporting commercial decisions or developing analysis for senior stakeholders. Choose the distinction that best reflects the next role you want.
For an entry-level application, draw on your strongest project, placement or analytical work within another job. A graduate who has investigated customer retention using SQL can introduce that project alongside their degree. A career changer may have a stronger opening in the reporting they already produce for an operations team.
Write the profile after selecting the evidence for the rest of the CV. That makes it easier to identify a clear theme and connect the opening to the examples that follow.
Build your employment history around analytical contributions
Begin each relevant role with a short description of its remit: the business area, the reporting or analysis you handled and the people you supported. In the example CV, the current role covers sales, returns and fulfilment reporting for an online shop and eight stores. That context makes the subsequent achievements easier to assess.
Use the remaining space for distinct contributions. A well-chosen set of bullets might cover a reporting improvement, an investigation, a data-quality issue and work with stakeholders. This gives a fuller picture of the role than several bullets describing similar dashboards.
A useful bullet connects your action with enough detail to explain its significance. For example, “Rebuilt the weekly trading pack using SQL Server views and Power BI, reducing preparation from four hours to 90 minutes per week” identifies the work, the tools and the outcome in one sentence. Other bullets can emphasise the decision supported or the reliability of the reporting.
Give recent, relevant work the most attention. Earlier roles can show how your responsibilities developed: preparing extracts, investigating exceptions, improving a process and eventually owning a reporting area. That progression is particularly valuable when your experience spans reporting support and a later analyst position.
Make your technical skills easy to assess
A compact skills section helps the reader locate the tools required for the vacancy. The employment and project sections then show the depth behind those entries. Grouping skills by their use can work well: querying, data preparation, BI and reporting, programming, and analytical methods.
Describe proficiency through the work you can do. “SQL Server: joins, CTEs and window functions for reporting and reconciliation” is more informative than a rating bar. A phrase such as “working knowledge of pandas for file checks” also gives a useful picture of your level. Place the tools most relevant to the application first.
SQL
Name the database or warehouse you have worked with, then select the SQL capabilities that matter for the role. Joins, aggregations, CTEs and window functions are useful terms where they describe your work. Their strongest support is a concrete example: combining order and returns data for reporting, producing cohort extracts, reconciling sources or improving a query used by a recurring report.
Your responsibilities help establish depth. Writing new queries, maintaining shared views, reviewing colleagues’ SQL and improving query performance each show something different. Include the relevant details in the job or project where you used them. A short explanation of what the query enabled is usually more useful on the CV than a code extract.
Excel and Power Query
Give Excel enough detail to show its analytical use. PivotTables, XLOOKUP, SUMIFS, Power Query and Power Pivot can support quite different work, from financial reconciliation to repeatable management reporting. Select the features that explain your strongest examples.
Power Query experience is especially worth making visible when you have replaced repeated manual preparation with a consistent process. In the example CV, combining eight store exports explains both the scale of the task and the improvement to the daily stock report. For a finance application, forecast models, scenario comparisons and reconciliation work may deserve more emphasis.
Python or R
Show what the language contributed to your analysis. That might be pandas for comparing supplier files, R for survey analysis, or a script that produces a regular exception report. Relevant libraries can sit alongside the task, giving a technical reader useful detail without overwhelming the description.
The setting also matters. An exploratory notebook, an academic project and a script used in a weekly reporting process demonstrate different kinds of experience. Naming that setting helps the reader assess your contribution. Where Python or R is central to the role, give the strongest example a prominent place in your employment history or projects.
Analytical methods
Choose methods that help explain the questions you have worked on. Trend and variance analysis, segmentation, forecasting, funnel analysis and experiments are more persuasive when attached to a relevant piece of work. For example, an investigation into late dispatches can demonstrate operational analysis, while a retention project can show how you examined customer behaviour over time.
Use the vocabulary of the role you are applying for. A statistical technique may deserve a named mention in a product analytics application; the same CV space may be better used for reconciliation and reporting controls in a management information role.
Explain what sits behind your dashboards
“Built Power BI dashboards” leaves much of an analyst’s contribution hidden. Show the parts of the work you handled: gathering requirements, preparing data, designing the model, defining measures, creating reports, arranging refreshes or helping users interpret the results.
For Power BI, details such as Power Query transformations, a star-schema model, DAX measures and scheduled refresh can establish technical depth. For Tableau, the relevant evidence might include data relationships, calculated fields, dashboard actions and publishing. With Looker, developing the LookML model and analysing data through an existing model are distinct contributions worth describing clearly.
Connect these details to the report’s purpose. A fulfilment dashboard used by warehouse managers to investigate late orders tells the reader more than its number of pages. An accompanying bullet could explain how you agreed a definition of an on-time dispatch, reconciled the totals or redesigned the filters following user feedback.
Reporting work also continues after launch. Maintaining a dependable refresh, responding to changing business requirements and improving how colleagues use a report are valuable responsibilities. Include evidence of that ongoing ownership where it is an important part of your role.
Give data quality and validation their own evidence
Data cleaning often takes substantial effort but disappears from a CV under “prepared data for analysis”. Bring out the problem you resolved and why it mattered to the reporting. Useful examples include reconciling figures across systems, investigating duplicate records, resolving missing reference data and checking that a new report agrees with established totals.
The example CV describes checks for duplicate order lines, missing product codes and unmatched returns, followed by work with the systems team to correct an import. This makes the candidate’s contribution visible: they identified an issue that affected the data and helped resolve its source.
For roles involving regular submissions, financial reporting or service performance, describe the controls you maintained. A validation report, an exception log or documented checking rules can show how you made a recurring process dependable. Mention collaboration with system owners or subject specialists when their involvement was part of the solution.
Show how your analysis reaches a decision
Stakeholder communication is strongest on a CV when the reader can see what you helped people understand or decide. Identify the audience and the work you did with them: agreeing a requirement with Finance, investigating a concern with operations managers, presenting findings to a product team or helping colleagues use a new report.
There are useful distinctions within that experience. Gathering requirements shows that you can turn a business question into analytical work. Agreeing metric definitions shows that you can resolve ambiguity across teams. Presenting a recommendation shows that you can explain the implications of the findings. Training users demonstrates that you can make a reporting tool useful in practice.
A concise example can bring several of these together: “Presented the causes of repeated stock exceptions to store managers and agreed changes to the weekly checking process.” The audience, finding and next step are all visible. Where your work led to a trial or an operational change, connect the analysis to that action.
For more senior roles, give space to how you shaped the work: deciding which questions to investigate, negotiating priorities, establishing shared measures, reviewing analysis or guiding colleagues. These responsibilities help demonstrate the level at which you operate.
Present achievements with useful context
Analytical impact can take several forms: quicker reporting, more dependable figures, a better decision, clearer priorities or a process that colleagues can use with less support. Choose measures that help explain the value of the work you are describing.
For a reporting improvement, the preparation time before and after the change is often a clear measure. Include the reporting frequency so the reader can understand its practical significance. The example’s reduction from four hours to 90 minutes for a weekly pack communicates the improvement without requiring an additional savings calculation.
For an operational investigation, a result is most useful alongside its scope. The example’s late-dispatch achievement identifies an earlier cut-off recommendation and reports the change during a six-week pilot at one warehouse. That is enough context to understand both the analytical contribution and the setting in which the result was observed.
Scope measures can strengthen a CV too. The number of stores covered, reporting cycles supported, teams using an output or colleagues trained helps the reader assess the responsibility involved. These details are particularly useful for dependable reporting work whose value is not captured by a revenue figure.
When a numerical outcome is unavailable, describe the practical result precisely. Establishing one agreed definition of a measure, resolving conflicting totals or giving a team its first consistent view of a process can all make convincing achievements. Explain what changed for the people using the analysis.
Select projects that strengthen the application
A project earns its place on a CV when it demonstrates a capability relevant to the vacancy. Choose work with a clear question, enough substance to discuss and an output that another person can understand. For a reporting role, a carefully developed report and its validation may be particularly useful. For a product role, an investigation into behaviour or retention may be more relevant.
Give each selected project a short title and a compact description covering:
- The question and context: what you investigated and the kind of data involved.
- Your contribution: the querying, preparation, modelling or analysis you carried out, including a significant checking step where relevant.
- The output: the finding, recommendation, report or tool that resulted.
A project entry might read:
Customer retention project — SQL and Power BI
Investigated how repeat purchasing varied between customer groups. Used SQL to prepare order histories and validate customer-level totals; built a Power BI report and recommended separate retention reporting for first-time and returning customers.
In a team project, a sentence about your part helps the employer see the skills you would bring to their team. An academic project can also demonstrate working with a substantial dataset, choosing an approach and explaining results to an audience beyond the project group.
For entry-level applicants, a Projects section can sit near the top of the CV, alongside education and technical skills. Employment outside analytics still adds evidence of business knowledge, problem-solving and communication. An analyst with an established work history will usually have stronger project evidence within their job entries; a separate section is useful when it adds a relevant capability that those roles do not show.
Use a portfolio to make selected work accessible
A portfolio is most useful when it gives an employer something worthwhile to inspect beyond the CV. It can be particularly valuable for a first analyst role, a career change or an application where a project demonstrates a tool you have had less opportunity to use at work.
Choose a small selection of work that supports the application. A project page should quickly explain the question, the data, your contribution and the principal finding. Then offer the appropriate detail: a report, dashboard, SQL files, notebook or repository. Put the clearest route to the work in the CV, either beside the project or with your contact details.
GitHub works well for SQL and programming projects when the repository is easy to navigate. A README can explain what the project does, where the key files are and how to reproduce the analysis. A screenshot or short results summary helps a recruiter understand the work before opening the code.
For a dashboard project, include context alongside the visual. Explain its intended users, the measures it presents and the decisions it supports. A concise project page can bring those elements together and provide both an interactive version and a readable preview.
Experienced applicants can make a strong case through commercial work described on the CV. Give a portfolio link prominence when it adds evidence that is useful to the particular application.
Position qualifications for your career stage
A relevant degree, apprenticeship or professional qualification helps establish your background. Include the award, institution and date, then add detail according to its value to the application. A recent graduate may benefit from a dissertation or modules involving statistics, databases or substantial analysis. After several years in relevant work, applied experience will usually deserve more space.
For an applicant from another discipline, an analytical dissertation or research project can be more useful than the degree title alone. Describe it through the same question, contribution and output used for other projects.
Technical certifications are easiest to assess when you give the full credential name, awarding organisation and award or renewal date. Position a relevant Power BI or other BI qualification near the skills and experience it supports. A course can be strengthened by a project showing how you applied the learning.
Let your strongest evidence determine the order of the CV. A graduate may lead with education and projects; a career changer may foreground reporting achievements from their current work; an experienced analyst can give priority to employment, analytical ownership and results. The graduate CV template offers another layout to consider when education and projects form the core of the application.
Data Analyst CV FAQs
Use the job title with a short description of its analytical remit, such as “MI Analyst — customer operations reporting”. The opening line can then identify the data, tools and teams involved. This helps a recruiter recognise relevant experience even when the title differs from the vacancy. Your profile can bring the connection into focus by describing the kind of analysis you specialise in and the role you are seeking.
A well-written CV entry can explain the business question, the type of data, your approach and the outcome without displaying the underlying material. Describe the client or business area at an appropriate level, such as a national retailer or a customer-service operation. Where a public work sample would help, a separate project using public or synthetic data can demonstrate a relevant technique. It can sit alongside the commercial experience as an additional example of your technical work.
If the assignments were delivered through one consultancy, use the consultancy as the main employment entry and identify selected assignments beneath it. Give each a brief sector or client description, dates where helpful, and its most relevant contribution. For separate contracts, individual entries can make the timeline easier to follow. Keep recurring details about the toolset in the skills section and use the assignment bullets to show the different questions, stakeholders and outcomes.
Yes, where the work demonstrates relevant analytical responsibility. Experience with tools such as SSRS or BusinessObjects can show SQL reporting, requirements gathering, scheduled outputs, reconciliation and support for business users. Name the platform and explain the work it enabled. If you also have experience with the employer’s BI tool, place that prominently so the reader can see both your established reporting background and your experience with their environment.
It can show relevant experience in preparing data, defining measures, designing reports and responding to user needs. Make those contributions clear in the project description. A Tableau project or recent Tableau training can then provide evidence of familiarity with the specific platform. The job description helps you judge the emphasis: a role requiring immediate responsibility for a Tableau environment will benefit from more detailed Tableau evidence than one welcoming experience across BI tools.
Describe the finding and the decision process it supported. Perhaps you identified the main causes of an operational problem, compared options for a planned change or gave a team evidence for setting priorities. A bullet can finish with “presented recommendations to the operations team” or “informed the decision to defer the rollout”, depending on the outcome. This gives the reader a useful account of the analytical work even when there was no subsequent implementation to measure.





