Data Analyst resume

Name your analysis tools, the business area you work in and one decision or saving your analysis led to. Data analyst summaries often list tools only; adding business impact makes yours different.

Example (fictional): "Data analyst with three years in retail, using SQL, Python and Power BI to track sales and stock across 40 stores. Built a weekly margin dashboard that helped buyers cut slow-moving stock before the holiday season."

Another example (fictional), for a junior analyst: "Economics graduate and junior data analyst skilled in Excel, SQL and Tableau, with internship experience cleaning survey data and presenting findings to a marketing team."

Keep it to two or three sentences and adjust the sector words to match the job: finance, healthcare, e-commerce or operations.

List the query, analysis and visualisation tools you have used on real data, starting with the ones in the job advert. Most data analyst roles look for SQL, a spreadsheet tool and at least one BI tool.

Example skills section (fictional):

• Querying: SQL (PostgreSQL, SQL Server, BigQuery)
• Analysis: Excel (pivot tables, Power Query, XLOOKUP), Python (pandas, NumPy), R
• Visualisation: Power BI, Tableau, Looker Studio
• Data handling: data cleaning, ETL basics, data modelling, DAX
• Methods: A/B testing, regression, forecasting, cohort analysis

Put the most relevant group first. If a role is Excel-heavy, show advanced Excel features rather than just "Excel". Leave out tools you only saw in a course, or label them "familiar".

Strong data analyst bullets show the question you answered, the tool you used and the decision or result that followed. Analysis only matters when someone used it.

Examples (fictional, adapt to your work):

• "Wrote SQL queries joining sales, returns and web data to find the product lines driving most refunds; the category team changed two suppliers."
• "Automated a monthly KPI report in Power BI, cutting preparation from two days to two hours."
• "Built a customer churn model in Python that flagged at-risk accounts for the retention team each week."
• "Cleaned and merged five years of branch data in Excel and Power Query to support a store-closure review."

Avoid bullets that only say "analysed data" or "created reports". Say which data, for whom and what changed.

Build two or three portfolio projects on public data, list the tools clearly, and draw out any analysis you did in past jobs or studies. Employers hiring juniors look for evidence that you can query, clean, analyse and present data.

Plan:

• Projects: use open data (transport, health, sports, public finance) and answer a real question.
• For each project: question, data source, tools, finding, and a link to the dashboard or notebook.
• Past jobs: any spreadsheets, reports or tracking you did.
• Training: a degree module, a course or a certificate.

Example project line (fictional): "Analysed three years of city bike-share trips in SQL and Tableau to find peak demand by station; dashboard published on Tableau Public."

Keep the resume to one page.

Yes, if it contains finished, well-explained work. A dashboard or notebook lets employers see how you think, which a bullet cannot fully show.

Before you add the link:

• Make sure each dashboard has a title, a short question it answers and labelled charts.
• In notebooks, add markdown explanations, not only code.
• Remove unfinished or copied tutorial work.
• Check there is no confidential company data.

Put the link in your contact line or next to the relevant project, for example (fictional): "Retail sales dashboard – Power BI, published sample with synthetic data (link)."

If your best work was for an employer, recreate a similar analysis with public or synthetic data instead of sharing the real thing.

Find out what people did with your reports and describe that. Reports exist to support decisions, so connect your work to the meeting, team or change it informed.

Questions to ask yourself or your manager:

• Who read the report and how often?
• Did a team change targets, budgets, staffing or stock because of it?
• Did your report replace slower manual work?
• Did it catch an error or problem early?

Example bullets (fictional):

• "Produced the weekly operations dashboard reviewed by the regional director; it flagged a late-delivery trend that led to a courier contract review."
• "Replaced six manual spreadsheets with one Power BI report, freeing about a day a week for the finance team."

If you cannot trace an outcome, describe audience and frequency instead.

They can be useful, especially early in your career or when moving from another field, because they show structured training in common tools. Experience and projects still matter more.

Certifications data analysts often list (examples):

• Google Data Analytics Professional Certificate
• Microsoft Certified: Power BI Data Analyst Associate (PL-300)
• Tableau Desktop Specialist or Certified Data Analyst
• IBM Data Analyst Professional Certificate

Example (fictional): "Microsoft Certified: Power BI Data Analyst Associate, 2025."

Put them in a Certifications section with the year. If the certificate included a capstone project, list that project too, because it gives the reader something concrete to look at.

Recruiters usually search for tool names and analysis tasks from the job advert, so use the exact terms that apply to you. The most common are tool names, because they are easy to filter on.

Frequent data analyst keywords:

• SQL, Excel, Power BI, Tableau, Python, R
• Data cleaning, data visualisation, dashboards, KPI reporting
• ETL, data modelling, data warehouse
• A/B testing, forecasting, segmentation
• Stakeholder communication, requirements gathering

Use them in context: "Built KPI dashboards in Power BI using DAX measures" is stronger than a list. The job-description comparison in the builder shows which of the advert's most frequent terms already appear in your resume, so you can add the ones that honestly describe your skills.

The biggest weakness is listing tools without showing what you discovered or changed with them. Hiring managers want analysts who turn data into decisions.

Other common mistakes:

• Vague bullets such as "handled large datasets" with no size, source or purpose.
• Charts or skill graphics in the resume itself, which software may not read.
• Numbers with no context, such as "increased efficiency by a lot".
• Confidential figures from your employer.
• Claiming machine learning or advanced modelling you cannot explain in an interview.
• Errors in the resume itself, which is especially harmful for a detail-focused role.

Example fix (fictional): change "Worked with big data" to "Queried 30 million transaction rows in BigQuery to compare promotion performance by region."

Show ownership of metrics, data quality and how the business uses data, not only the reports you built. Senior analysts are expected to frame questions, guide stakeholders and improve the team's methods.

Highlight:

• Defining KPIs and getting teams to agree on them.
• Designing data models or a semantic layer.
• Leading analyses that changed strategy.
• Mentoring junior analysts and setting standards for code and dashboards.

Example bullets (fictional):

• "Defined a single 'active customer' metric with marketing and finance, ending three competing definitions in board reports."
• "Led a pricing analysis across 2,000 SKUs that informed the annual price review."

Keep a short tools line, but let leadership and influence fill most of the space.

Describe the problem the messy data caused and what your cleaning made possible. Cleaning is a large part of analyst work, and employers value people who do it carefully.

Include:

• The source and size of the data.
• The issues: duplicates, missing values, inconsistent codes, date formats.
• The method: SQL, Power Query, pandas, validation rules.
• The result: a trusted report, a faster process, fewer errors.

Example bullets (fictional):

• "Standardised 18,000 customer records from three CRMs, removing duplicates so the sales team had one accurate contact list."
• "Built validation checks in Python that caught missing branch codes before the monthly report ran."

This shows attention to detail with evidence instead of claiming it as a soft skill.

Present your current work as analysis, highlight advanced spreadsheet skills, and add one or two SQL or BI projects to show you can work beyond Excel. Many analysts start this way.

Steps:

• Headline: "Operations coordinator moving into data analysis (Excel, SQL, Power BI)".
• Rewrite bullets around analysis: reconciliations, trend reports, forecasting, dashboards.
• Show advanced Excel: Power Query, pivot tables, lookup functions, macros.
• Add a project in SQL and Power BI or Tableau.

Example bullet (fictional): "Built an Excel model tracking delivery times for 500 routes a week and presented monthly trends to the operations manager."

Keep your real job titles and let the bullets carry the analytical story.

List them separately, because employers often filter for each one and they show different abilities. SQL shows you can get data out of databases; Python or R shows you can analyse and automate beyond spreadsheets.

Example skills lines (fictional):

• "SQL: joins, window functions, CTEs, query optimisation (PostgreSQL, SQL Server)."
• "Python: pandas, NumPy, Matplotlib, Jupyter; scripting for automated reports."

Adding a few sub-skills, as above, shows depth without long explanations. Then prove each in at least one experience or project bullet. If your Python is basic, label it honestly, such as "Python (basic data cleaning and charts)".

Say who uses the dashboard, what it tracks, how often it is used and what it replaced or improved. The dashboard's purpose matters more than the number of charts on it.

A useful bullet pattern: "Built [dashboard] in [tool] tracking [metrics] for [audience], which [result]."

Examples (fictional):

• "Built a Power BI dashboard tracking call volumes and wait times for 60 contact centre agents, replacing a daily manual email."
• "Designed a Tableau executive dashboard covering revenue, margin and headcount, reviewed in each monthly leadership meeting."

If you can share a version with sample data, link it in your portfolio. Never put screenshots of real company dashboards in the resume.

For most data analysts: contact details with portfolio link, summary, skills, experience, projects, education, certifications. Put skills high because tool names are often the first thing readers check.

Variations:

• Graduates and career changers: put projects above experience if the projects show more analysis.
• Analysts with a quantitative degree, such as economics or mathematics, can keep education higher in their first two years.
• Experienced analysts can shorten projects or drop them.

Example skills heading (fictional): "Technical Skills: SQL, Power BI (DAX), Excel (Power Query), Python (pandas)".

Use a single-column layout with standard headings so applicant tracking systems read each section in the right order.

Describe what was tested, your part in design or analysis, and the decision taken. Experiment work shows strong analytical judgement, so make your role clear.

Include:

• The change tested: a page, price, email or process.
• Your part: sample size planning, tracking set-up, analysis, reporting.
• Tools: SQL, Python, an experimentation platform.
• The decision: rolled out, dropped or retested.

Example bullet (fictional): "Analysed a checkout-button test across 80,000 sessions in SQL and Python; the new design was rolled out after it showed a clear lift in completed orders."

Avoid stating precise lifts unless they are yours to share. "Clear lift" or "no meaningful difference" is fine if you can explain it in an interview.

Name the domain in your summary and use its terms in your bullets, because many employers prefer analysts who already understand their data. Domain knowledge can matter as much as tool skills.

Examples of domain terms:

• E-commerce: conversion funnel, basket size, returns rate, customer lifetime value.
• Banking: loan book, delinquency, transaction monitoring, customer segments.
• Healthcare: patient flow, bed occupancy, appointment no-shows, coding data.
• Telecom: churn, ARPU, network usage.

Example bullet (fictional): "Analysed appointment no-show patterns across six outpatient clinics to support a reminder-message trial."

Keep data privacy in mind. Never include patient, customer or account details, even anonymised examples from real work.

Show communication through outputs: presentations, written summaries, training sessions and how leaders used your findings. Analysts who can explain results clearly are in demand.

Evidence to include:

• Presenting findings to managers or executives.
• Writing short insight summaries with recommendations.
• Training colleagues to use dashboards.
• Gathering requirements from non-technical teams.

Example bullets (fictional):

• "Presented quarterly customer insights to the marketing leadership team, leading to a change in email frequency."
• "Ran Power BI training for 20 branch managers so they could filter their own data."

Mention the audience level, because explaining to a director is different from explaining to an analyst.

Yes, if you worked with real data and used analyst tools. Postgraduate research, theses and research assistant posts often involve cleaning, analysing and presenting data, which is the core of the job.

How to present it:

• List a research assistant post as a job with its dates.
• Put a thesis or dissertation under Projects or Research.
• Translate academic language into business terms: "survey of 1,200 respondents" rather than "primary data collection instrument".

Example bullet (fictional): "Cleaned and analysed a 1,200-response survey in R, running regression models and presenting results to the faculty research committee."

Focus on the methods and tools, and keep the academic topic short unless it matches the employer's sector.

Mention the practical steps you took to handle data responsibly, such as access controls, anonymising data for reports or following company data policies. Employers handling customer data value this.

Examples of what to include:

• Masking or aggregating personal data before sharing.
• Working within role-based access in a data warehouse.
• Documenting data definitions in a data dictionary.
• Following your organisation's retention or classification rules.

Example bullet (fictional): "Created an aggregated version of the customer dataset for marketing so they could analyse trends without access to personal details."

Do not claim legal expertise. Describe your practice and name the internal policy or framework only if it is not confidential.

Name the advanced features you use and show them solving a problem. "Advanced Excel" alone is too vague because people mean very different things by it.

Features worth naming if you use them:

• Power Query for importing and cleaning data
• Pivot tables and Power Pivot data models
• XLOOKUP, INDEX/MATCH, dynamic arrays
• Conditional formatting and data validation
• VBA macros or Office Scripts for automation

Example bullets (fictional):

• "Built a Power Query process that combined 12 branch files into one report each morning."
• "Wrote a VBA macro that formatted and emailed weekly stock reports to 15 managers."

Put "Excel (Power Query, pivot tables, XLOOKUP, VBA)" in your skills line so it can be found quickly.

Keep your official title in the job entry, but you can use "Data Analyst" in your headline if the work matches. Titles like MIS Executive, Reporting Officer or Business Intelligence Associate often cover analyst duties.

How to do it honestly:

• Job entry: "MIS Executive, Crestline Trading, 2022–2025".
• First bullet: explain that the role focused on data reporting and analysis.
• Headline: "Data analyst with three years of MIS reporting in SQL and Excel".

Example bullet (fictional): "Produced daily sales and collections MIS reports for 30 branches using SQL and Excel, and investigated variances with branch managers."

This lets your resume appear in searches for data analyst roles without misrepresenting your history.

One page is enough for most data analysts with under about five years of experience; two pages suit senior analysts with several roles and leadership work. Length should follow the evidence you have, not a fixed rule.

To keep one page:

• Combine tools into a grouped skills section.
• Limit each job to three to five results-focused bullets.
• Keep only your strongest one or two projects.

When two pages make sense:

• You have led teams or analytics programmes.
• You have several substantial projects, publications or certifications relevant to the role.

Example (fictional) one-line project to save space: "Bike-share demand analysis – SQL, Tableau Public (link)."

Check the country norm too: some regions expect longer CVs.

Say what you forecast, the method and tool, how accurate it proved in plain terms, and who relied on it. Forecasting is valued because it supports planning decisions such as staffing, stock and budgets.

Details to include:

• What: sales, demand, call volumes, cash flow, headcount.
• Method: moving averages, seasonal models, regression, Excel Forecast Sheet, Python libraries such as Prophet or statsmodels.
• Use: which team planned with it and how often.

Example bullets (fictional):

• "Built a weekly call-volume forecast in Excel that the contact centre used to plan agent rotas."
• "Created a seasonal sales forecast in Python for 300 products, reviewed monthly with the buying team and adjusted after each season."

Be modest about accuracy unless you tracked it. "Close enough to replace the manual estimate" is honest and still useful.

Yes, if you have queried or built reports on them, because many employers now keep their data in cloud warehouses and filter candidates on these names. Name the specific platform rather than "cloud".

Platforms analysts commonly list:

• Google BigQuery
• Snowflake
• Amazon Redshift
• Azure Synapse or Microsoft Fabric
• Databricks

Example bullet (fictional): "Wrote scheduled SQL queries in BigQuery that fed a Looker Studio dashboard for the growth team."

If you only used a platform briefly, add it under a "Familiar" label. If your work was on a traditional database such as SQL Server, list that instead; the SQL skills transfer and interviewers know it.