Data Analyst Resume: Show the Decisions Your Analysis Changed

A data analyst resume should show decisions your analysis changed. Everyone lists SQL, Excel and Python. What separates candidates is evidence that the work was used: a recommendation that was acted on, a report that people read, a process that changed. Lead each bullet with the question or problem, name the data and tools, and end with the result. Keep the skills section short and back it with projects. Hiring teams often discount tool lists because nearly everyone claims the same stack.

Analytics roles are a good example of why scope and impact matter more than keywords.

Structure

1. Name, contact, links to a portfolio or code.
2. Summary: years, domain, tools and one result.
3. Experience, with analysis-focused bullets.
4. Projects, if early in your career or changing field.
5. Skills.
6. Education and certifications.

Summary example

"Data analyst with four years in e-commerce, working in SQL, Python and Tableau. Built the weekly retention dashboard used by marketing and product, and an analysis of delivery delays that led to a change in carrier. Looking for an analyst role in a product team."

Bullets: from tasks to decisions

The stronger rows name the data, the tool and the outcome. Keep the figures honest and be ready to explain them. Hiring-side guidance for analytics roles makes the same point, that decisions influenced count more than tools listed. See screening data analytics candidates.

What reviewers look for

• Business question: what problem were you solving?
• Data: sources, size, quality problems you handled.
• Method: SQL, statistics, models, experiment design.
• Communication: who received the work and how.
• Impact: a decision, a change or a saving.
• Ownership: what you did and what the team did.

Include data volumes where possible; "analysed 2 million events" tells a reader more than "large datasets".

Skills

Group them:

• Querying: SQL (PostgreSQL, BigQuery)
• Analysis: Python (pandas, scikit-learn), R, Excel (Power Query)
• Visualisation: Tableau, Power BI, Looker
• Methods: A/B testing, regression, cohort analysis
• Data tools: dbt, Airflow, Git

Show depth: "SQL (window functions, CTEs, query optimisation)" says more than "SQL". See the skills section.

Projects for early-career or career-changing analysts

Use a template:

"Question: Why do customers cancel in the first 90 days? Data: 18,000 anonymised subscription records (public dataset). Method: cohort analysis in Python, logistic regression for drivers. Finding: customers who did not use feature X in week one were three times more likely to cancel. Link: GitHub write-up."

Choose a question a business might care about, finish it, and write it up in plain English. See projects on a resume. For people switching in from another field, career change resumes covers how to frame the move.

Portfolio

A short portfolio of three projects, each with a clear question, a chart or two and a conclusion, is worth more than ten notebooks of code. Reviewers may spend a minute on it, so make the first screen of each project tell the story.

Common mistakes

• Listing tools with no use cases.
• Describing the work as reports "provided" with no sign anyone used them.
• Overstating the models you built when you ran a standard function.
• Omitting the domain; an analyst who understands retail, health or finance is worth more than one who lists tools alone.
• Weak communication, shown by long, jargon-heavy bullets.

Preparing for the next step

Analyst interviews usually include a case or a take-home. Prepare for them with take-home assignments from the employer's side in mind, and practise explaining your work in two minutes with the STAR method. Keep your resume consistent with what you can discuss, and run the resume checklist before sending.

A sample experience entry

"Data Analyst, Northgate Retail (2022 to present)

• Built the weekly retention dashboard in Tableau, drawing on four data sources; marketing and product use it in their Monday planning.
• Analysed 14 months of order data to find why delivery times rose on two routes; the finding led to a change of carrier and a drop in late deliveries.
• Cleaned and joined customer data in SQL and Python, reducing monthly reporting time from two days to four hours.
• Designed six A/B tests on the checkout flow, two of which shipped."

Every bullet names the data, the tool and the outcome. The figures are examples, so use your own.

Statistical honesty

Reviewers with an analytics background notice overclaiming. If you ran a test, say how big the sample was and whether the result was significant. If you built a model, say how you evaluated it. A modest, accurate description of a simple method is more convincing than a grand claim about machine learning that you cannot explain. In an interview, expect to be asked how you handled missing data, bias in the sample and how you communicated uncertainty. Think of two examples before you apply.