Data analyst job postings list tools — SQL, Python, Tableau, dbt. Every candidate's resume lists the same tools. What differentiates them is evidence of analytical thinking: how they framed the question, what they measured, what they found, and what the organisation did as a result.
The strongest analyst resumes read like case studies, condensed to bullets.
The shape of a strong analyst bullet
The bullet should answer four questions in one sentence:
- What was the question? The business problem or investigation.
- What did you do? The analysis, the model, or the query.
- What did you find? The insight or the number.
- What changed? The decision or the outcome.
Example: "Built a cohort retention model in SQL and Python to investigate the drop in 30-day retention in Q3. Found that new users who completed onboarding step 3 retained 2.3x better. The insight shaped the redesign of the onboarding funnel, which improved 30-day retention from 22% to 34%."
That one bullet contains a question, a method, a finding, and an outcome. It reads like a mini case study. A hiring manager reading it learns more about you than from three generic tool-listing bullets.
Skills — where most resumes lose
Do not list tools as if the tools are the skill. The tool is a means. Group your skills by analytical capability rather than by category of software:
- Data manipulation: SQL (advanced), Python (pandas, numpy), dbt
- Statistical analysis: A/B testing, regression, cohort analysis, survival analysis
- Visualisation: Tableau, Looker, matplotlib
- Data modelling: dimensional modelling, star schemas, slowly changing dimensions
- Business domains: subscription metrics, funnel analysis, pricing, experimentation
The "business domains" line is optional but powerful. It tells the reader that you understand what the numbers mean, not just how to query them.
Quantified impact is essential
Analysts often have an advantage over other candidates because their work naturally produces numbers. Use them.
Types of quantification to look for:
- Scale: Number of rows, users, transactions, or events analysed.
- Speed: Reduction in query time, report refresh time, or time-to-insight.
- Impact: Improvement in a business metric linked to the analysis.
- Adoption: Number of stakeholders or teams using your work.
If you cannot find a number, describe the decision the analysis influenced. "The insight informed the redesign of the onboarding funnel" is a strong outcome even without a number.
Analyst projects
Projects can be strong evidence, but only if they demonstrate analytical depth. A Tableau dashboard of public data is weak. A project that produces a specific insight from messy data is strong.
Example: "Analysed 5 years of UK housing data to identify regional affordability trends. Built an interactive dashboard using Python (pandas, Plotly) that was viewed by 4,000+ users and cited in a policy discussion thread on a major UK forum."
The evidence is not the tool — it is that someone paid attention to the result.
What does not work
Common weaknesses in analyst resumes:
- Tool laundry lists. "SQL, Python, R, SAS, Tableau, Power BI, Excel, Looker, dbt" — this reads as untrustworthy. Nobody is deeply fluent in all of these.
- Report production framed as analysis. "Produced weekly sales reports" is not analysis — it is reporting. If that is what you did, reframe it: "Designed and automated the weekly sales report, cutting production time from 4 hours to 15 minutes and freeing the team to focus on ad-hoc analysis."
- No business context. An analyst who cannot connect to business outcomes is a report builder.
- Certificate padding. Listing every Coursera certificate is a signal that you do not have real projects to talk about.
The test for every analyst bullet: does it explain what decision it changed? If not, it reads as a report, not an analysis. Reports are cheap; analyses that change decisions are rare.
Start with an analyst template
Skills-forward layouts for data and analytics roles.