Data Analyst resume
Data Analyst Resume Examples
How to write a data analyst resume that proves you turn data into decisions.
A data analyst resume has to prove one thing above all: that you turn data into decisions, not just charts. Hiring managers are not impressed by the number of dashboards you built — they want to know which business question you answered and what changed because of it. The strongest analyst bullets always connect the analysis to the action it drove: a metric that moved, money saved, a launch informed, a process the team stopped doing. If your resume describes analysis without an outcome, it reads as activity, not impact.
For analyst roles the ATS filter is unusually predictable. SQL is non-negotiable and recruiters scan for it directly, so it must be unmissable. Visualization and BI tools — Tableau, Power BI, or Looker — are nearly always named, and Excel proficiency is still expected. Python or R show up for more technical postings. Name the exact tools the job description lists, in plain text, rather than the vague "data tools".
The trap unique to this role is sitting between two stools: claiming engineering scope you did not own, or underselling the judgment that makes a good analyst valuable. Keep the focus on insight, reporting, and decision support, and quantify everything — a numbers job with no numbers on the resume is a contradiction a hiring manager will notice immediately.
On structure: open with a skills section that puts SQL first, followed by your BI and analysis tools, because that block is what an ATS and a hiring manager scan before anything else. Keep it to one page early-career, list roles in reverse-chronological order, and reserve the top two bullets of each role for the analysis that changed a decision. If you have a portfolio of notebooks or dashboards, link it — but make sure every important result also appears in plain text on the resume, since the link is the first thing an ATS ignores.
Skills employers expect from a data analyst
Querying & data
Visualization & BI
Analysis
Business
Top ATS keywords for data analyst resumes
Applicant tracking systems and recruiters scan for the exact terms a posting names. Use the ones below that are genuinely true for you, in plain resume text — not only in a portfolio link.
Data Analyst resume bullet examples
These show the shape of a strong bullet for this role — outcome first, then the work and the scope. Replace the specifics with your own real evidence; never copy a metric you did not earn.
Driving decisions
- Identified a 22% drop-off in the mobile signup funnel through cohort analysis; the fix the team shipped recovered an estimated 1,800 signups/month.
- Built an executive KPI dashboard in Tableau that replaced a manual weekly deck, saving the analytics team roughly 6 hours/week.
- Segmented churned accounts by usage pattern and handed sales a prioritized save-list that recovered 11% of at-risk MRR in a quarter.
Analysis depth
- Wrote SQL models joining five source tables to attribute revenue by channel, revealing paid-social ROI was 40% below the previously reported figure.
- Designed and analyzed a pricing A/B test across 60K users; the resulting tiered plan lifted ARPU 9%.
- Built a weekly demand forecast in Python that brought planning error (MAPE) down from 19% to 11%.
Data quality & enablement
- Automated a daily data-quality check that caught three broken pipelines before stakeholders ever saw bad numbers.
- Built a self-serve Looker explore that cut ad-hoc data requests to the team by 30%.
- Authored the company first metric dictionary, ending months of conflicting "active user" definitions across teams.
Common data analyst resume mistakes
Saying "analyzed data" with no decision
The value is the action your analysis caused, not the analysis itself. End the bullet on what the business did differently.
Burying or omitting SQL
Recruiters for analyst roles scan specifically for SQL. Make it the first item in your skills section and show it inside a bullet.
No numbers in a numbers job
A data analyst resume with zero quantified outcomes signals you do not measure your own impact. Quantify the result, the scope, or the time saved.
Overclaiming engineering scope
Do not present yourself as owning production pipelines and infrastructure unless you did. Focus on insight, reporting, and decision support.
Chart-dumping
"Built 40 dashboards" is volume, not value. One dashboard that changed a decision beats forty nobody opened — lead with the one that mattered.