Data analyst resume examples: entry, mid and senior

Entry-level data analyst resume example

Junior data analyst · 0–2 years

Example bullets:

• Cleaned and merged three exports (about 90,000 rows) in Python and removed 6% duplicates before the analysis began.
• Built a weekly sales dashboard in Tableau for 8 regional managers, replacing a spreadsheet that took 3 hours to update.
• Wrote 20 SQL queries to clear a reporting backlog, each with a short note on its logic so the next analyst could reuse it.
• Analyzed survey answers from 1,200 customers and showed late delivery was the main reason for low scores; the team moved its carrier cut-off time.
• Published a city 311 service-request analysis in SQL and Python as a GitHub notebook with the question, method and findings.
• Automated a monthly Excel report with Power Query, cutting 4 hours of copy and paste to 20 minutes.

The numbers are examples of the shape a strong line takes, not benchmarks to match.

Mid-level data analyst resume example

Data analyst · 2–5 years

Example bullets:

• Replaced a 30-tab weekly report with one Tableau dashboard used by 45 managers; ad hoc data requests fell from 25 to 16 a month.
• Ran a pricing test with a matched control group across 24 stores; the result led to a price change on 60 products.
• Cut the sales model's query time from 25 minutes to 4 by rewriting joins and pre-aggregating in dbt.
• Built a churn model in Python that ranked at-risk customers; outreach to the top group raised repeat purchases by 5 points.
• Wrote a one-page data dictionary with finance and marketing, so both teams used the same metric names.
• Presented a quarterly findings review to eight directors, with one recommendation per slide.

Senior data analyst resume example

Senior data analyst · 5+ years

Example bullets:

• Owned 12 core metric definitions and the dbt models behind them, ending recurring disputes between finance and marketing over the numbers.
• Wrote the team's experiment standard, with sample-size checks, metrics fixed in advance and a review step; 18 tests followed it in a year.
• Showed a loyalty discount was cutting margin in 30 stores; the policy change was worth an estimated $520K a year.
• Redesigned the customer data model in Snowflake and cut dashboard load time from 45 seconds to under 5.
• Mentored four analysts and ran a monthly SQL review that caught logic errors before they reached dashboards.
• Advised the merchandising director on a range reset; 300 slow products were dropped with no measurable fall in category sales.

Skills and keywords data analyst postings commonly list

These are terms commonly listed in data analyst postings. Add a term only when a bullet or project shows you using it, and keep each tool's official spelling.

• Query and data: SQL, BigQuery, Snowflake, PostgreSQL, dbt, ETL, Data cleaning
• Analysis: Python, pandas, R, Statistics, A/B testing, Regression, Forecasting
• BI and reporting: Tableau, Power BI, Looker, Excel pivot tables, XLOOKUP, Power Query, KPI dashboards
• Working with people: Stakeholder communication, Requirements gathering, Data storytelling

The title line, contact block and portfolio link

Write the title the way postings write it. Data analyst, business analyst, reporting analyst and BI analyst are close relatives, and the best title is the one you held. If your title was something vaguer, such as operations associate, put the honest title in the experience entry and use "Data analyst" on the title line only if the work was truly analysis.

The contact block takes an email address, a phone number, a city and one or two links. For an analyst, the useful links are a LinkedIn profile and, if you have one, a portfolio: a GitHub repository with SQL and notebooks, or a Tableau Public profile. Lena has no portfolio link because her employers' work is her proof, but a junior analyst should add one.

Check every link in a private browser window before you send. A dashboard that asks the reader to log in, or a repository with no README, is worse than no link at all.

A summary that names your questions and your data

Analysts work in very different industries, so the summary should say where your data comes from. "Data analyst with six years turning retail and banking data into decisions" places Lena in two sectors at once, and the second sentence names how she works: SQL and Python daily, dashboards that managers open weekly.

Use two sentences. First: your title, years and the kind of data. Second: the way you add value, in plain words, such as explaining findings to people who do not read code. Keep tool names to the two or three you use every day.

If you are early in your career, lead with the project or the degree instead: "Statistics graduate with two internships and a published analysis of 90,000 city 311 requests" gives a reader something to open. See these skills to put on a resume for help picking the few that belong in the summary.

Bullets: lead with the decision the analysis changed

A weak analyst bullet starts with a tool: "Used SQL and Tableau to build reports." It tells the reader what was open on your screen. A stronger bullet starts with the decision or action the work changed, and then names the method.

Build each bullet in this order: the action or decision, the evidence behind it, and the method in a short clause. "Moved two weak promotions after analyzing results across 140 stores in SQL and Python, saving an estimated $310K a year" puts the outcome first and the tools last.

Estimates are acceptable when you label them. Savings from a decision are often modeled and not measured, so write "an estimated $310K a year" and be ready to explain the assumption. A precise-looking number you cannot defend is a liability.

Counting dashboards built is not an achievement. Ask what happened because a dashboard existed: who opened it, what they did differently and what changed in the numbers.

Data scale and statistics claims you can defend

State the scale of the data only when it helps a reader judge the work. Rows, sources and refresh cadence show difficulty: "merged three exports of about 400,000 rows" or "a nightly refresh across 14 models" tells the reader the data was not trivial. A bare "large datasets" tells them nothing.

Statistics words carry a promise, so use them carefully.

• Say A/B test or experiment only if you split users into groups, with a control, and compared outcomes. If you compared this month with last month, call it a before-and-after comparison.
• Say significant only if you ran a significance test. Otherwise write "the lift was 6%" and leave the adjective out.
• Name the model when you built one: logistic regression for churn, a time-series method for a forecast. "Predictive modeling" alone is vague.
• Report what the number meant for the business as well as its accuracy. A churn model with a good score changes nothing until someone acts on its list.

In an interview you may be asked how you chose a sample size or handled missing values. Put on the resume only what you could explain at a whiteboard.

Tools grouped by what they do

Tool soup is the analyst's version of keyword stuffing: twenty names in a row, none with evidence. Group your tools by the job they do so a reader sees the shape of your stack.

• Query: SQL, with the dialect or warehouse you used, such as PostgreSQL, SQL Server, Snowflake or BigQuery.
• Analysis: Python with pandas, R, and statistics methods such as regression or A/B testing.
• BI and reporting: Tableau, Power BI, Looker and Excel features such as pivot tables, XLOOKUP and Power Query.
• Data modeling: dbt, ETL pipelines and data cleaning work.

The builder's skills section is one comma-separated line, so choose the order. Lena puts SQL first, because it is the tool she uses all day. Add a bracketed library or feature when it makes a claim specific: "Python (pandas)" and "Excel (Power Query, XLOOKUP)" say more than "Python" and "Excel".

One tool per job is a good target for a junior analyst, and two or three per group suits a mid-level one. Every name should show up in a bullet or a project.

A portfolio for junior analysts

If you have no analyst job yet, a small portfolio is your experience section. Three projects are plenty if each reads clearly.

• Use public data. City open-data portals, government statistics sites and public sports or transit datasets are good sources. Avoid the practice datasets every learner uses, such as Titanic passengers or bike-share trips, which fill many tutorials and course capstones.
• Pick a real question. "Which neighborhoods wait longest for a pothole repair?" is a question. "Exploring the dataset" is not.
• Show the work. A GitHub repository holding SQL queries, a notebook and a README that states the question, the method and the finding.
• Show the product. A Tableau Public dashboard with a title that says what to look for.

Write one resume line per project: the question, the data size and the finding. "Analyzed 90,000 city 311 requests in SQL and Python to find the 10 neighborhoods with the longest pothole repair waits" works. Our post on the portfolio resume strategy explains how to present projects, and our career guide on breaking into tech in 2026 covers the wider path.

Education and certificates

A statistics, math, economics, computer science or business degree all read naturally for analysts. Lena's single line, BS Statistics, University of Illinois Chicago, 2020, is enough once she has a few years of work behind it. A recent graduate can add a short line of relevant coursework, such as regression or databases.

Two certificates are commonly mentioned for analysts. The Google Data Analytics Professional Certificate is a beginner-oriented program hosted on Coursera. The Microsoft Power BI Data Analyst Associate is earned by passing exam PL-300. Both help most for a junior or a career changer, and both supplement projects. Neither replaces a repository, a dashboard or a job. Check the issuer's site for the current exam details, fees and renewal rules before you commit.

Because the builder has only four sections, list a certificate as an Education entry, with the certificate name in the degree field and the issuer in the school field. A tool-specific certificate can also be named in your skills line, for example "Power BI (PL-300 certified)". Only list one you have passed.

Mistakes that weaken an analyst resume

"Proficient in Excel" with no proof. The phrase is easy to write and impossible to check. Name what you did in it: "cut a 12-hour monthly report to 2 with Power Query" is proof, and "advanced Excel" is a claim.

Tool soup. A skills line of twenty-five names, with half of them seen only in a course, makes the whole list doubtful. Cut it to what you could use tomorrow.

Dashboards as the achievement. "Built 40 dashboards" counts output. Report the use: the managers who opened it, and the decision it supported.

Vague data words. "Big data" and "advanced analytics" tell the reader nothing. Replace them with the size, the sources and the method.

Undefended statistics. A resume that says "statistically significant" invites a question. Be ready to name the test, or leave the phrase out.

Hiding the audience. Analysis is judged by what the audience did with it. Say who used your work: store managers, finance, a director group or a product team.

Tailoring to business, product and marketing analyst postings

The title data analyst covers several jobs, and the postings use different words for them. Keep one honest resume and shift the order of your evidence.

• Business and operations analyst: lead with cost, process, forecasting and reporting that managers act on. Put stakeholder communication and requirements gathering higher.
• Product analyst: lead with experiments, funnels, retention and event data, and show a test you designed with a control group.
• Marketing analyst: lead with campaign attribution, customer segments, lifetime value and the spend decisions your analysis changed.

Read the posting for the tools and the questions it names. If it asks for Looker and you built in Tableau, state the Tableau work truthfully and describe the outcome, because the skill transfers and the claim stays honest. Paste the posting into our ATS checker to compare keywords, and keep the matches you can back.

Record each application and the version you sent in the job application tracker. If you are weighing a move toward engineering, the software engineer resume examples show how the same SQL and Python experience reads there.

Frequently asked questions

How do I write a data analyst resume with no experience?
Lead with projects. Build two or three analyses from public data, each with a clear question, SQL or Python code in a GitHub repository, and a dashboard or write-up of the finding. Add internships, coursework, volunteer reporting work and a relevant degree. State what each project found and how large the data was, not only which tools you used.

Should I list Excel on a data analyst resume?
Yes, if you use it for real analysis, but be specific. Name the features, such as pivot tables, XLOOKUP or Power Query, and put a result in a bullet, like a report you automated. A plain claim of advanced Excel proves nothing, while one concrete example shows how you use it.

How many tools should a data analyst list?
List the ones you could use confidently tomorrow, grouped by purpose: query, analysis, BI and modeling. A junior analyst might list one in each group, and a more experienced analyst two or three. Every tool should appear in a bullet or portfolio project, so the skills line is backed by evidence.

Does a data analyst resume need a portfolio link?
It is not required for someone with a strong work history, but it helps a junior analyst or career changer a great deal. Link a GitHub repository with SQL and notebooks, or a Tableau Public profile, where each project states its question, method and finding. Make sure every link opens without a sign-in.