Data Analyst Resume Skills (What to List and How to Prove It)

Hard skills for a Data Analyst resume

• SQL — The single most-requested skill on Data Analyst posts. Prove it with scope: "wrote SQL joins and window functions across 8 tables to build a churn cohort report used by the retention team weekly."
• Data cleaning and wrangling — Show you can handle real, dirty data: "cleaned and deduplicated a 1.2M-row sales export, fixing date formats and null handling so revenue figures matched finance to within 0.3 percent."
• Data visualization and dashboards — Name the tool and the audience: "built 4 Tableau dashboards that replaced manual weekly decks and gave 30 sales reps self-serve pipeline numbers."
• Spreadsheet analysis (Excel or Google Sheets) — Go past basic formulas: "modeled a pricing scenario in Excel using pivot tables, VLOOKUP, and what-if analysis that informed a 12 percent margin change."
• Descriptive and inferential statistics — Tie stats to a decision: "ran significance testing on a landing-page experiment and flagged a 7 percent lift that was within noise, saving a premature rollout."
• A/B testing and experimentation — Show the full loop: "designed and analyzed an A/B test on checkout flow, sized the sample for 80 percent power, and recommended the variant that raised conversion 4 percent."
• Python or R for analysis — Only claim it if you have used it: "used Python with pandas to automate a monthly cohort analysis that previously took a full day in spreadsheets."
• Data modeling and metric definition — Prove you can define the question: "standardized the definition of active user across 3 teams, ending a recurring dispute over conflicting numbers in leadership reviews."
• KPI and reporting design — Show ownership: "owned the weekly KPI report for a 200-person org and added a leading indicator that predicted churn 2 weeks earlier."
• ETL and data pipelines — Quantify the time saved: "built an automated ETL job in SQL and dbt that refreshed marketing data nightly, replacing a 3-hour manual pull."
• Forecasting and trend analysis — Anchor it to accuracy or impact: "produced a 6-month demand forecast that came within 5 percent of actuals and shaped inventory planning."
• Stakeholder reporting and data storytelling — Show the outcome, not the chart: "turned a 40-page export into a one-page narrative that led the product team to cut a feature with low engagement."

Technical skills and tools

• SQL databases (PostgreSQL, MySQL, BigQuery, Snowflake) — List the specific warehouse you queried. "Wrote analytical queries against a Snowflake warehouse used company-wide" beats a vague "databases."
• BI and visualization tools (Tableau, Power BI, Looker) — Name the one on the job post. Show you published, not just viewed: "published and maintained 6 Power BI dashboards refreshed daily."
• Spreadsheets (Excel, Google Sheets) — Mention advanced features by name: pivot tables, Power Query, array formulas, INDEX-MATCH, and any macros you built.
• Python data stack (pandas, NumPy, Jupyter) — Pair the library with a task: "used pandas and Jupyter to clean and join survey data from 3 sources for a monthly report."
• Version control and collaboration (Git, dbt) — Shows you work like an engineer: "managed analytics SQL in Git and modeled metrics in dbt so logic was reviewed and reusable."
• Cloud and ticketing tools (GCP, AWS, Jira) — Reference the environment you operated in so the resume matches the company stack on the posting.

Soft skills (with evidence)

• Translating business questions into analysis — Prove it: "reframed a vague leadership ask about declining sales into 3 testable hypotheses, then answered the one that mattered with a cohort breakdown."
• Communicating findings to non-technical audiences — Show the result: "presented analysis to the marketing VP and recommended pausing a campaign, which redirected 15K of monthly spend."
• Attention to detail and data accuracy — Make it concrete: "caught a join error that double-counted orders before a board report shipped, correcting a 9 percent revenue overstatement."
• Curiosity and problem framing — Show you dig past the first answer: "noticed a metric spike was a tracking bug, not real growth, after investigating a sudden 20 percent jump."
• Prioritization under competing requests — Demonstrate judgment: "triaged 12 weekly ad-hoc data requests and pushed self-serve dashboards that cut repeat asks by half."
• Cross-functional collaboration — Name the partners: "worked with engineering and product to fix event tracking, improving data quality for every downstream report."

ATS keywords to mirror from the job post

SQL, data analysis, data visualization, Tableau, Power BI, Excel, Python, dashboards, A/B testing, ETL, KPI reporting, data cleaning.

Where to put your skills on a Data Analyst resume

Use a short skills section near the top, grouped so a screener finds the must-haves fast: one line for languages and tools (SQL, Python, Tableau, Excel), one line for techniques (A/B testing, forecasting, ETL). Keep it to the tools you can defend in an interview, because anything listed is fair game for a question. Put the exact tool names from the job post here, spelled the way they spell them, so the ATS match is clean.

The skills section is the index, but the proof lives in your experience bullets. Every strong skill should appear at least once in a bullet attached to a result, not just floating in the list. A recruiter trusts "reduced reporting time 80 percent with an automated SQL pipeline" far more than the word "SQL" sitting in a comma-separated row, so spread your top skills across your work history where they earned a number.

How to show a skill instead of just listing it

Convert each skill into a sentence with a tool, an action, and an outcome with a number. Instead of "data visualization," write "built a Power BI dashboard that gave 30 reps self-serve pipeline data and ended weekly manual reporting." The pattern is tool plus what you did plus what changed for the business. If you do not have an employer example, use a project: a Kaggle analysis, a capstone, or a dataset you scraped and modeled all count when written with the same structure.

Quantify even when the data feels small. Rows processed, hours saved, percent change, number of stakeholders served, and dollars influenced are all credible numbers. If you genuinely cannot measure the outcome, name the decision your analysis drove: "analysis led the team to drop a low-engagement feature." A concrete decision beats a vanity adjective like "results-driven" every time, because it shows your work actually moved something.

Which skills to cut

Cut filler that every applicant writes and no one verifies: "hard-working," "team player," "passionate about data," and "proficient in Microsoft Office." They take space and signal nothing. Also drop tools you have only clicked through once. If you cannot answer a basic interview question about a tool, leaving it on the resume is a liability, not a plus, because a single weak answer can sink the screen.

Trim outdated or off-target items too. Listing "Microsoft Word" or generic "computer skills" on a Data Analyst resume reads as padding. Keep the section tight and tilted toward what the specific posting asks for, then move the saved space into experience bullets where your real skills earn their proof. When in doubt, ask whether a skill helps you answer a data question faster; if not, it can go.