Most data analyst CVs fail in the same way: they list SQL, Python and a stack of BI tools, but they never show the decision the analysis actually drove. A hiring manager reading 'proficient in SQL, Power BI and Excel' learns that you can operate the tools, not that your work changed anything. The difference between a shortlisted analyst and an ignored one is usually not the tech list. It is whether the CV proves you turn data into decisions people act on. This guide is specific to data analyst roles; for the wider picture across engineering, product and data, see our tech, product and data CV guide.
What employers want
Hiring managers for analyst roles are looking for three things. First, evidence that you turn data into decisions people act on, rather than producing reports that sit unread. Second, rigour: clean methodology, sensible assumptions, and results you can defend. Third, clear communication, because most of an analyst's value is lost if they cannot explain a finding to a non-technical stakeholder who has to act on it. Your CV should show all three, not just the first one implied by a tools list.
Lead with the decision, not the query
Frame each piece of work around the business question and what changed as a result. Start from why the analysis existed: someone needed to decide something. What was the question, what did you find, and what did the business do differently because of it? A bullet that reads 'analysed customer data in SQL' tells the reader nothing about impact. A bullet that names the decision, 'identified which onboarding step lost the most users, prompting a redesign that improved completion', shows you understand what analysis is for. The query is the means; the decision is the point.
Structure your tools sensibly
You do need a skills section, and it should be easy to scan. Group your tools rather than listing them in one long line: querying and databases (SQL, and the specific dialects you know), programming (Python or R, and the libraries you actually use), spreadsheets (Excel, including the functions that matter), and BI and visualisation (Power BI, Tableau, Looker). Match the grouping and emphasis to the advert. If a role leans on Tableau and dbt, those belong near the top. Avoid the tool-dump: a wall of forty technologies reads as padding and hides the ones that count.
Quantify impact
Analysts have an advantage here, because their work usually produces measurable change: time saved through automation, revenue or cost affected by a recommendation, accuracy or data quality improved, or manual reporting replaced by something self-serving. Reach for those numbers. Where exact figures are commercially confidential, use percentages, ranges or orders of magnitude, which prove the scale of the impact without disclosing anything sensitive. 'Cut a weekly report from a day to under an hour' is concrete and safe. Vague impact is the most common weakness in analyst CVs, and it is usually fixable. Our guide on duties vs outcomes walks through the rewrite in detail.
Show stakeholder communication
Technical ability gets you in the door; communication is often what separates candidates once inside. Show where you turned analysis into recommendations that a non-technical audience could act on, built dashboards that people actually use rather than ones that were requested and forgotten, or presented findings that changed a decision. These moments prove that your analysis lands with the people who own the outcome, which is exactly what employers are paying for.
Get past the ATS
Analyst CVs get filtered like any other. Keep the formatting plain: standard headings, no tables or text boxes for layout, and no key information trapped inside a graphic. Do not present your skills as a chart or an infographic; an ATS cannot read the image, and a human reviewer finds it harder, not easier. Use the real keywords from the advert, in your own true context. If the role asks for 'A/B testing' or 'data modelling' and you have done it, use those exact words rather than a synonym. Our honest guide to ATS-friendly CVs covers the formatting rules in full.
Tailor to the domain and seniority
'Data analyst' covers very different jobs. A marketing analyst living in campaign performance and attribution is not doing the same work as a finance analyst modelling forecasts, or a product analyst measuring feature adoption and retention. Read the advert for the domain and mirror it: bring forward the projects, metrics and vocabulary that match. Do the same for seniority. A junior CV can lead with solid, well-explained execution; a more senior one should show ownership, influence on strategy, and work that other people relied on.
A worked example
The numbers below are illustrative and generic, chosen to show the shape of a strong bullet rather than any real person's results.
Before: 'Built dashboards in Power BI.'
After: 'Built a churn dashboard in Power BI that flagged at-risk accounts, helping the team cut monthly churn by around 15%.'
The 'before' names a tool and a task. The 'after' names the same tool but adds the question (which accounts are at risk?), the audience (the team using it), and the outcome (churn fell). It is still one line, and it now proves impact rather than activity.
Common mistakes to avoid
- Listing tools and technologies with no decision or outcome attached
- Describing the query or method instead of what changed as a result
- Tool-dumping a huge skills list that buries the ones that matter
- Leaving impact vague when a percentage or range would prove it
- Presenting skills as charts or graphics an ATS cannot read
- Ignoring the domain and seniority the advert is actually hiring for
Common questions
What should a data analyst CV focus on?
The decisions your analysis led to, not just the tools you used. For each piece of work, name the business question, the analysis, and what changed as a result. Group your technical skills sensibly, quantify impact where you can, and show you can explain findings to non-technical stakeholders.
Do I need a portfolio for a data analyst role?
It helps but is rarely essential for a standard analyst role. A well-structured CV that proves the decisions your analysis drove usually carries more weight. If you include a portfolio or GitHub link, make sure it is tidy and relevant; a weak or abandoned one can do more harm than good.
How do I move from data analyst to a more senior data role on my CV?
Show scope and ownership, not just more tools. Emphasise work you led end to end, analysis that shaped strategy or was trusted by senior stakeholders, and any mentoring, standard-setting or modelling that goes beyond routine reporting. Frame the impact at team or business level rather than task level.