Data Analyst Resume: Skills, Format & Examples (2026)

Data analyst resumes have a specific failure mode: they describe what tools the candidate used without showing what they actually figured out. "Built dashboards in Tableau" doesn't tell a hiring manager whether the dashboards mattered, who used them, or what changed because of them.

The hiring bar for data analysts in 2026 is whether you can do the work and work with stakeholders. Your resume needs to show both. This guide covers structure, what skills to highlight, and how to write bullets that read like an analyst, not a tool list. See the full data analyst resume example too.

Structure for a data analyst resume

1. Contact block
2. Professional Summary — 2–3 sentences. Specialty + concrete accomplishment + tooling.
3. Work Experience — reverse chronological.
4. Technical Skills — grouped (Languages, BI tools, Cloud/DB, Methods).
5. Education — degree, school, year. GPA if 3.5+ and within 3 years of graduating.
6. Projects (optional) — for new grads, career changers, or Kaggle/portfolio standouts.
7. Certifications (optional) — Google Data Analytics, IBM Data Analyst, Tableau, etc.

The skills section: what to include

Group skills into 4 categories. Pick the most relevant items in each. Don't list everything you've ever touched.

Languages: SQL (advanced), Python (pandas, NumPy, scikit-learn), R
BI & Visualization: Looker, Tableau, Mode, Hex, Metabase
Data & Cloud: Snowflake, BigQuery, Redshift, dbt, Airflow
Methods: A/B testing, cohort analysis, attribution modeling, statistical inference

Notes by category:

• SQL goes first. Every data analyst resume that doesn't lead with SQL gets discounted.
• Add proficiency only if it's meaningful — "Python (pandas, NumPy)" tells the reader you can wrangle data; "Python (TensorFlow, PyTorch)" tells them you can do ML work. The specific libraries matter.
• Skip Excel from your top-level skills unless the role is non-technical. Everyone has it; calling it out reads as junior.
• Include dbt if you've used it. It's one of the biggest keyword signals in data analyst hiring right now.

What hiring managers are looking for (and what they don't care about)

They care about:

• Whether you can write SQL beyond basic SELECT statements. Window functions, CTEs, query optimization.
• Whether you can translate a business question into an analysis. "The marketing team asked X; I framed it as Y; here's what I found."
• Whether you can communicate findings to non-technical people. Slack threads, executive readouts, written memos.
• Whether your work changed any decisions. "Dashboard built" is weak; "Analysis recommended killing channel X, saving $250K" is strong.
• Whether you can work with engineers on data infrastructure. dbt models, schema design, data quality.

They don't care about:

• Number of dashboards you've built. (Volume isn't impact.)
• The tools you used 5 years ago.
• Generic phrases like "data-driven decision making" — that's the job, not an achievement.
• Online courses unless they're top-tier (DataCamp generic certificates don't move the needle).

The bullet patterns that work

Three patterns for data analyst bullets. Mix them across your resume.

Pattern 1: Question → analysis → outcome

Investigated why mobile signup conversion dropped 18% week-over-week; isolated the issue to a broken iOS app version using funnel + cohort analysis, leading to a hotfix that recovered conversion within 48 hours.

Pattern 2: Built infrastructure → unlocked capability

Built the company's first attribution model in dbt and Snowflake, replacing 3 manual spreadsheets and enabling marketing to reallocate $1.2M of annual ad spend toward higher-converting channels.

Pattern 3: Stakeholder partnership → recurring impact

Partnered with the product team as the embedded analyst for the onboarding squad; designed and analyzed 14 A/B tests, with 4 launching company-wide changes that lifted D7 retention 6%.

Bullets that don't work:

• Built dashboards in Tableau and Looker. (Says nothing.)
• Performed data analysis to support business decisions. (Says less.)
• Maintained reporting and provided insights to stakeholders. (Says even less.)

For more on bullet structure: Resume Bullet Points: The XYZ Formula.

Metrics to lean on

Analysts often underestimate how many numbers they have. Use:

• Business outcomes: revenue moved, costs cut, retention or conversion lift, churn reduction.
• Scale: rows queried, models built, dashboards in active use, team size served.
• Time saved: hours of manual work eliminated, query latency reduced, report frequency increased.
• Quality: data accuracy improvements, schema migrations completed, A/B tests that read statistically significant.
• Adoption: stakeholders using your dashboards weekly, decisions made from your analyses.

If you have no numbers and can't get them, use named scope: "the only analyst on the growth team," "the analyst covering all of marketing for a 200-person company."

Resume by experience level

New grad / first analyst job

Lead with Education, then Projects (Kaggle, capstone, personal data work), then any internships. Skills section before Projects can work if you have strong tooling but light project depth. Keep to one page.

Strong projects look like: a real-world dataset, a defined question, a measurable conclusion. "Analyzed Citibike data to find the 5 stations with highest weather-dependent demand variability" beats "Used Python to explore a dataset."

Mid-level (2–5 years)

Order: Summary → Experience → Skills → Education. Bullets should show ownership growth: you started running A/B tests, you owned a domain (marketing, growth, product), you partnered directly with a function.

Senior (5+ years)

Same order, two pages OK. Bullets show breadth: working across domains, mentoring junior analysts, owning the methodology for measurement, partnering with executives. Specific technical leadership (built the experimentation framework, owned the metrics layer) carries weight.

Analytics engineer / data engineer track

If you've drifted toward the engineering side — dbt, Airflow, data modeling — explicitly include "analytics engineering" or "data engineering" language. The market for these roles is hotter than pure analyst roles and your resume should be discoverable for both.

Common data analyst resume mistakes

• Listing every dashboard tool ever touched. Tableau, Looker, Mode, Metabase, Power BI, Google Data Studio — pick the 2–3 you actually use and add the rest only if directly relevant.
• "Excel power user" as a top skill. Save for non-technical roles. For analyst roles, lead with SQL.
• Hiding the analyst work inside generic operations bullets. If you spent 30% of your last job doing analysis, that's your analyst experience — frame it that way.
• No domain mentioned. A "data analyst" without a stated domain (marketing, product, finance, ops) looks underspecified. Even just calling out the team you supported helps.
• Project work that's all online courses. Build one or two genuinely original projects on real data instead of listing 5 Coursera certificates.
• Listing certifications above experience. Past the first 6 months out of school, real work experience always leads.

FAQ

Should I include my SQL practice repo (LeetCode SQL, StrataScratch)?

Only if you have a long, public track record. A few solved problems is a worse signal than no link.

Do I need a portfolio?

For new grads and career changers, yes. For experienced analysts with clear work bullets, no. If you do have one, link it in the contact block.

How do I show stakeholder work on a resume?

Name the stakeholder (team, function, level) and the outcome. "Partnered with VP Marketing on Q3 budget reallocation" beats "Communicated with stakeholders."

What if I haven't used Python much?

Don't fake it. SQL-strong analysts are in demand. List Python only if you can defend it in an interview.