Data Analyst Resume: Examples, Skills, and Writing Guide

Hiring managers do not read a data analyst resume to find out whether you know SQL. They read it to find out whether your analysis ever changed anything. Most resumes stop at the tools ("Built dashboards in Tableau") and never get to the decision the dashboard drove, which is the part that gets interviews.

This guide shows you how to close that gap. You'll get a section order for each level, a skills table covering SQL, Python, BI tools and certifications, a metrics table for analysts, bullet examples from entry level to lead, a portfolio plan for career changers, and a full one-page sample resume.

You'll also find current pay and outlook figures from the U.S. Bureau of Labor Statistics, with a note on how to read them, since BLS does not publish a standalone "data analyst" category.

What a data analyst resume needs to prove#

Analyst work follows a loop: you get data, clean it, analyze it and communicate a finding that leads to a decision. A strong resume shows evidence for every stage. A weak one shows only the middle.

The four stages reviewers look for#

• Access: Can you pull data yourself? SQL queries, joins across systems, APIs, warehouse tools.
• Preparation: Can you clean and model messy data? Deduplication, handling missing values, building reusable tables.
• Analysis: Can you choose the right method? Segmentation, trend and cohort analysis, A/B test reads, regression.
• Influence: Did anyone act on it? A pricing change, a staffing decision, a budget shift, a process fix.

The last stage is where most resumes fall short. If you can show that a stakeholder made a different decision because of your work, you are ahead of most applicants.

Two readers, two different checks#

A recruiter usually screens first. They check the title, years of experience, required tools and location, often in under a minute. Then a hiring manager, usually a senior analyst or analytics lead, reads for judgment: did you pick sensible methods, did you check your data, and did your work change anything?

Write for both. Put tool names where the recruiter will see them (skills section and the first line of each role), and put the reasoning and results in your bullets for the hiring manager.

Data analyst titles vary more than you think#

The same work appears under many titles: data analyst, business intelligence analyst, reporting analyst, analytics specialist, product analyst, marketing analyst and operations analyst. O*NET's profile for business intelligence analysts lists titles such as BI analyst, BI specialist and market intelligence analyst as variants of the same occupation.

That matters for your resume in two ways. First, search for every variant, not just "data analyst." Second, match your headline and summary to the exact title in each posting, as long as it honestly describes your work.

Data analyst salary and job outlook#

The U.S. Bureau of Labor Statistics does not publish a separate occupation called "data analyst." Analysts are spread across several related categories, depending on the work they do. The table below shows the closest matches, using BLS data for May 2025 pay and 2025 to 2035 projections.

BLS reports that data scientists earned a median of $120,230 in May 2025, with the lowest 10 percent under $67,240 and the highest 10 percent above $199,130. Employment is projected to grow 35 percent from 2025 to 2035, with about 24,800 openings a year. O*NET groups business intelligence analysts under this same occupation code.

Operations research analysts earned a median of $88,940, with 12 percent projected growth. Market research analysts earned a median of $78,760 and are a much larger group, at about 952,700 jobs in 2025.

How pay compares across data-related math occupations#

Read these figures as ranges for the field, not a promise for any specific title. A "data analyst" job at a small nonprofit and a "product analyst" job at a large tech company may fall into different BLS categories and pay very differently.

What the data means for your resume#

The spread in pay mostly tracks the depth of methods and the size of the decisions involved. Analysts who can show statistical rigor, automation and influence over large budgets tend to move toward the higher-paid categories. If you want to move up, your resume should show those three things as clearly as your tool list.

Format, length and section order#

Use a reverse-chronological format in a single column. Keep it to one page unless you have a decade or more of relevant work. Change the order of sections based on where your strongest evidence lives.

Header and links#

Include your name, city and state, email, phone, LinkedIn and one portfolio link. The portfolio can be a GitHub profile, a personal site or a public dashboard gallery such as Tableau Public. One good link beats three thin ones.

Layout basics#

• One column with standard headings (Experience, Projects, Skills, Education)
• Dates right-aligned and in one consistent format
• No charts, icons or skill bars on the resume itself; save visuals for your portfolio
• PDF unless the posting asks for a Word file

Data analyst skills: SQL, Python, BI tools and more#

Your skills section is where recruiters check for keywords, and where hiring managers check whether your tools match their stack. Keep it grouped, honest and short enough to scan in five seconds.

How to group your skills#

Use labeled lines instead of one long list:

• Data and querying: SQL (PostgreSQL, BigQuery, Snowflake), Excel (pivot tables, Power Query, XLOOKUP)
• Programming: Python (pandas, NumPy, Matplotlib), R (tidyverse)
• BI and visualization: Power BI (DAX), Tableau, Looker
• Methods: A/B test analysis, cohort and funnel analysis, regression, forecasting
• Data tools: dbt, Airflow, Git, Google Analytics

Put SQL first unless the posting clearly emphasizes something else. Then mirror the BI tool and language the job post names.

Skills, tools and certifications table#

The table below maps the core analyst skill areas to hard skills, tools and recognized certifications. O*NET lists Microsoft Power BI, Excel, Snowflake and SAS among the in-demand technologies for business intelligence analysts.

A resume skills generator can give you a starting list for a specific title, and our guide to technical skills on a resume shows how to prove them.

Show proficiency without rating bars#

Rating bars and "expert" labels are subjective and invite skepticism. Instead, show depth through what you did:

• "Wrote window-function SQL to build a daily retention table used by 3 teams"
• "Automated a weekly 6-hour Excel report into a scheduled Python job"
• "Built a Power BI data model with 14 related tables and row-level security"

Excel still matters#

It is tempting to drop Excel in favor of SQL and Python, but most business stakeholders still live in spreadsheets, and many analyst postings still list it. Keep Excel on your resume and be specific about the advanced parts you use: pivot tables, Power Query, lookup functions, scenario models. "Excel" alone reads as basic; "Excel (Power Query, pivot tables, financial models)" reads as a working analyst's tool.

AI tools in analyst work#

Many analysts now use AI assistants to draft SQL, summarize survey text or speed up documentation. If you mention this, describe the outcome and your judgment, not just the tool name. For example: "Used an LLM to categorize 12,000 open-text survey responses, then validated a 500-row sample by hand to 94% agreement." That shows you know where AI output needs checking, which is the skill employers actually want.

Soft skills that matter for analysts#

Analysts are hired to help other people decide. Communication, stakeholder management, curiosity and judgment matter as much as tools. Don't list them as adjectives. Prove them in bullets: presenting findings to executives, translating vague requests into clear questions, or pushing back on a misleading metric.

Writing data analyst bullets that show impact#

Most analyst bullets describe an output: a report, a dashboard, a query. A strong bullet goes one step further and names the outcome: the decision made, the time saved, the money protected.

The question, method, result formula#

Use this structure: business question or problem + method and tools + decision or measurable result.

Each rewrite names the stakeholder, the method and what changed. An accomplishments generator can help you turn a plain task description into this shape, and our guide to quantifying achievements covers where to find numbers.

What to quantify as a data analyst#

Analysts often have more numbers than anyone else on the team, yet they forget to quantify their own work. Use this table to find yours.

Writing about dashboards#

Dashboards are the most common analyst output and the most commonly undersold. "Built 15 dashboards" tells a reviewer almost nothing. Instead, describe one or two dashboards by who used them, how often and what they replaced or enabled:

• Audience and cadence: "used in the Monday leadership meeting"
• What it replaced: "retired 5 manual spreadsheets"
• What it enabled: "let store managers reorder stock without waiting for a weekly report"
• What changed: "flagged stalled deals that reps then closed"

When the impact is indirect#

Sometimes you did the analysis and someone else made the call. You can still claim the influence honestly: "Analysis presented to the VP of Operations led to adding a second shift," or "Recommendation adopted in the 2026 pricing plan." State what you contributed and what the business did with it.

If you truly don't know the outcome, quantify scope instead: data volume, stakeholders served or the frequency of the report.

Data analyst bullets by seniority level#

As you grow, the scope of your work shifts from answering questions to choosing which questions get asked. Your bullets should reflect that.

Entry-level data analyst bullets#

Mid-level data analyst bullets#

Senior and lead data analyst bullets#

Projects and portfolio: the entry-level path#

If you are new to the field, projects are your experience. A good portfolio project looks like a real piece of analyst work: a business question, messy data, a clear method and a recommendation.

How to choose portfolio projects#

Pick two or three projects that cover different skills. A balanced set might include:

• A SQL-heavy analysis on a public relational dataset, answering a specific business question
• A dashboard in Power BI or Tableau that a manager could actually use weekly
• A Python analysis with cleaning, statistics and a written recommendation

Choose datasets with some mess in them: government open data, city services data, public company filings or survey data. Tutorial datasets that every course uses (such as the classic passenger-survival dataset) make you blend in.

How to write a project entry#

Treat each project like a job. Give it a title, a link, the tools and two bullets that show the finding and what someone could do with it.

Our guide to projects on a resume covers placement and formatting in more depth.

Where to host your portfolio#

You do not need a fancy website. Choose one home for your work and keep it tidy:

• GitHub: Best for SQL and Python projects. Each repository needs a README with the question, data source, method, key chart and recommendation.
• Tableau Public or a Power BI public report: Best for dashboards. Add a short description so a reviewer knows what decision the dashboard supports.
• A simple personal site: Useful if you want one link that collects everything, with a paragraph per project.

Whichever you choose, check that every link works from your PDF and that the first screen a reviewer sees explains what they are looking at.

Building a step-by-step entry-level plan#

1. Pick a target title and collect 10 job posts for it.
2. List the tools that appear in most of them; learn the top three well rather than ten badly.
3. Build one SQL project, one dashboard and one Python analysis on real data.
4. Write a one-paragraph summary for each project explaining the question, data, method and recommendation.
5. Earn one recognized certification if you have no formal training in the field.
6. Rewrite your past jobs to highlight any analytical work.
7. Tailor the resume for each application and run a resume to job description match before you send it.

Career changers: turning past work into analyst experience#

Many data analysts start in another field: finance, operations, marketing, teaching, healthcare or retail management. Your past job likely included analytical work. The goal is to name it in analyst language.

Finding the analyst work in your old job#

Look for any time you:

• Built or maintained a spreadsheet that others relied on
• Tracked KPIs, budgets, inventory, schedules or test scores
• Spotted a trend and recommended a change
• Pulled reports from a system (POS, CRM, EHR, LMS) and summarized them
• Ran a survey or compiled feedback and acted on it

Keep your old job titles. Recruiters need accurate titles and dates. Change the bullets underneath to focus on the analytical parts. Our career change resume guide covers the full repositioning, including how to write a summary that explains the switch.

Listing bootcamps and online courses#

A bootcamp or structured online program belongs in your education section with the provider, program name and completion year. If it included a capstone, move that capstone into your projects section and describe it like real work. Avoid listing every short course you have taken; one or two substantial programs and one certification are enough to show structured training.

Education and certifications for data analysts#

Most analyst roles ask for a bachelor's degree, but the field is open to people from many majors. Economics, statistics, mathematics, computer science, business and social sciences are all common backgrounds. When O*NET surveyed workers in business intelligence analyst roles about the education needed for new hires, most named a bachelor's degree.

How to list education#

Keep the entry short: degree, major, school and graduation year. Add a GPA only if it is strong and recent, and add relevant coursework (statistics, econometrics, databases) only if you are early in your career and it fills a gap. Experienced analysts can move education to the bottom of the page.

Which certifications help#

Certifications carry the most weight for career changers and entry-level candidates. Choose one that matches the stack in your target postings:

• Google Data Analytics Professional Certificate for a broad foundation in spreadsheets, SQL and visualization
• Microsoft Certified: Power BI Data Analyst Associate for Power BI-heavy roles
• Tableau Certified Data Analyst for Tableau-heavy roles
• Cloud data certifications (such as those from AWS, Google Cloud or Snowflake) for roles close to data engineering

List each with the issuer and year. Our guide to certifications on a resume covers placement and formatting.

Data analyst resume summary examples#

A summary is useful for analysts, because the title alone covers such a wide range of work. Use two or three lines: your focus, your main tools and one result.

For more patterns across fields, see our resume summary examples.

Full sample data analyst resume#

Here is a one-page resume for a mid-level analyst. The name, companies and figures are fictional; use the structure and adapt it to your own record.

Notice that every tool in the skills section also appears in a bullet, and every bullet ends with something the business did or gained.

Tailoring your resume by industry and title#

Analyst roles differ a lot by domain. Shift your keywords, metrics and examples to match the posting.

If a posting leans toward modeling and machine learning, see our data scientist resume guide. If it centers on requirements and process, the business analyst resume guide is a closer fit, and finance-heavy roles align with the financial analyst resume.

A quick tailoring routine#

For each application, pull the posting's tools, methods and domain terms. Our guide on how to find keywords in a job description shows a fast method. Then reorder your skills, swap in the most relevant bullets and adjust your summary's first line to the exact title.

ATS formatting and a final checklist#

Applicant tracking systems read text, not visuals. The charts that make your portfolio strong can make your resume unreadable if you embed them. Keep the resume plain and let your links carry the visuals.

Common mistakes to avoid#

• Embedding charts, logos or icons that parsers can't read
• Listing 25 tools with no proof of any of them
• Bullets that end at the output ("created a report") instead of the outcome
• Describing confidential data or client names you aren't allowed to share
• Using the same generic resume for marketing, finance and product roles

Resume Maker's AI assistant can rewrite a weak bullet directly in your resume, and every edit can be undone if you prefer your original wording. Whatever tool you use, check the final file with an ATS resume checker.

Make every number interview-proof#

Analyst interviewers love to probe numbers, because checking figures is the job. Before you send your resume, go through every metric and make sure you can answer three follow-up questions about it: how was it measured, over what time period, and what else might explain the change? If a lift came from a test, know the sample size and whether the result was significant. If a saving was an estimate, know how you estimated it.

If you can't defend a number, soften it to a range or replace it with scope. A slightly smaller, well-explained figure builds more trust than an impressive one that falls apart under one question.

File name and links#

Save your resume as a PDF named with your name and the role, such as "Jordan-Patel-Data-Analyst-Resume.pdf." Test every hyperlink in the exported file, since links sometimes break when a document is converted.

Final review checklist#

• SQL and the posting's BI tool appear in both skills and bullets
• Every bullet names a question, method and result or decision
• At least half your bullets include a number
• Portfolio link works and each project has a short write-up
• Old titles are accurate; analytical work is shown in bullets
• One page, single column, PDF
• No confidential figures or client names

Your next steps#

Start with your three most recent bullets. Rewrite each one with the question, method and result formula, and add the decision that followed. That alone separates your resume from most of the pile.

Next, regroup your skills section so SQL and the BI tool from your target postings lead. If you are entry level or switching fields, build or polish two portfolio projects on real data and link them in your header.

Finally, prepare for the next stage. Analyst interviews usually include a SQL screen and a case question, and our technical interview prep guide covers both. If you are still early in your search, the entry-level resume guide will help you present limited experience with confidence.