Most data analyst resumes read like a tool inventory: SQL, Excel, Tableau, Python, listed in a block and repeated in every bullet. Recruiters screening analyst roles see that list on nearly every application, so it stops telling them anything. What separates a shortlisted resume is evidence that your analysis led somewhere: a decision made, a cost found, a metric moved, a report someone stopped building by hand.
This guide covers the keywords applicant tracking systems look for, how to write bullets that show business impact, and how the resume changes between entry-level and experienced analysts.
What Hiring Managers Screen For
An analyst job posting usually asks for three things, whatever the industry:
- Getting the data: writing SQL against real databases, joining messy sources, cleaning and validating.
- Making it readable: dashboards, reports and charts that non-technical people use.
- Changing a decision: turning numbers into a recommendation and seeing it acted on.
Most resumes prove the first, some prove the second, and few prove the third. The third is what moves you from "qualified" to "interview".
Keywords by Category
Group your skills so a recruiter can scan them in seconds, and mirror the exact names from the posting. ATS matching is literal: "Power BI" and "PowerBI" may not be treated as the same term.
- Querying and data: SQL, PostgreSQL, MySQL, SQL Server, BigQuery, Snowflake, data cleaning, data validation, ETL
- Analysis: Excel (pivot tables, Power Query, XLOOKUP), Python (pandas, NumPy), R, statistics, A/B testing, cohort analysis, forecasting, regression
- Visualization and BI: Tableau, Power BI, Looker, Looker Studio, dashboard design, KPI reporting
- Business context: stakeholder management, requirements gathering, financial analysis, marketing analytics, product analytics, supply chain metrics
Only list what you can be tested on. Analyst interviews often include a live SQL exercise or a take-home case, and a skill you cannot demonstrate will cost more than its absence.
Bullets That Show Impact
A strong analyst bullet has four parts: the question, the method, the output, and what changed because of it.
Before: Created dashboards in Tableau for the sales team.
After: Built a Tableau pipeline dashboard used by 40 account executives weekly, replacing a manual Excel report and cutting forecast prep from two days to two hours.
Before: Analyzed customer data using SQL.
After: Identified through SQL cohort analysis that customers onboarded by phone churned 30% less; the finding funded a phone onboarding pilot for all enterprise accounts.
Before: Responsible for monthly reporting.
After: Automated 12 monthly finance reports with Python and SQL, removing roughly 25 hours of manual work per month and eliminating copy-paste errors flagged in the prior audit.
If you do not know the exact outcome, use what you do know: who used the output, how often, and what it replaced. "Used by the leadership team in quarterly planning" is honest and still shows reach.
Structure for a Data Analyst Resume
- Header: name, city and state, phone, email, LinkedIn, and a portfolio or GitHub link if it contains real work.
- Summary: two or three lines. Title, years, domain, one result. The summary examples guide has the formula.
- Skills: grouped as above, four lines at most.
- Experience: reverse chronological, three to five bullets for recent roles.
- Projects: essential for entry-level candidates, optional later.
- Education and certifications: degree, school, year. Certifications such as the Google Data Analytics certificate or Microsoft's Power BI certification belong here; they help with keyword matching but do not replace evidence.
One page is the standard for analysts with under ten years of experience. The one-page resume guide covers what to cut.
Entry-Level: Projects Do the Work Experience Cannot
If you are a graduate, a bootcamp finisher or moving from another field, projects carry your resume. A good analyst project:
- Uses a real, messy public dataset rather than a cleaned tutorial file.
- Asks a business question, not "exploring the Titanic dataset".
- Ends with a recommendation and a chart someone could act on.
- Links to code or a published dashboard.
Analyzed three years of city 311 complaint data (1.2M rows) in SQL and Tableau; found that 18% of noise complaints came from five blocks and proposed targeted enforcement hours. Dashboard published on Tableau Public.
Two strong projects beat five tutorial copies. If you are switching careers, frame past work in analyst terms: an operations coordinator who built Excel trackers and reported weekly numbers already did analyst work. The career change resume guide shows how to reframe it.
Experienced Analysts: Show Scope and Ownership
After three or four years, recruiters look for signs you are ready for senior or lead roles:
- Ownership: you defined the metrics, not only reported them.
- Scale: data volumes, number of stakeholders, number of teams relying on your work.
- Influence: recommendations adopted, budgets moved, experiments designed.
- Enablement: self-serve dashboards that reduced ad hoc requests, documentation, mentoring junior analysts.
If you are moving toward machine learning or modeling, the data scientist resume guide explains how expectations change. If you are moving toward pipelines and infrastructure, see the data engineer resume guide.
Common Mistakes
- Tool lists with no outcomes. Every bullet says "using SQL" and none says what was learned.
- Skill bars and star ratings. "SQL: 4/5" means nothing to a recruiter and confuses parsers.
- Two-column layouts with skills in a sidebar. Some ATS parsers read columns out of order and lose the sidebar. A single column is safer.
- Listing every library. Matplotlib, Seaborn and Plotly in one line is noise. Name the stack the posting asks for.
- No link to work. For analysts, a portfolio is often the tiebreaker between two similar resumes.
Templates That Parse Cleanly
Harvard Resume Template — the single-column academic-standard layout and the most downloaded template on CVEdge. Set it to Letter and it is the safest US default.
Classic Resume Template — standard headings, no graphics, parses cleanly in Greenhouse, Workday, Lever and iCIMS.
Executive Resume Template — for senior candidates who need the summary and leadership scope to land before the role history.
Related Guides
- Data Scientist Resume Guide 2026
- Business Analyst Resume Guide 2026
- Resume Keywords That Get You Hired
- How to Write Resume Bullet Points That Show Impact
Frequently asked questions
What skills should a data analyst put on a resume?
SQL first, then the analysis tool the posting names (Excel, Python or R), then the BI tool (Tableau, Power BI or Looker). Add business skills such as stakeholder reporting or A/B testing when the role mentions them. Match the posting's exact spelling.
Do I need a portfolio as a data analyst?
For entry-level and career-change candidates, yes: it is the main evidence you can do the work. For experienced analysts it is optional, because your experience bullets carry the proof, but a published dashboard still helps.
Are data analytics certificates worth listing?
List them in an education or certifications section. They help with keyword matching and show initiative, but recruiters weigh projects and work results more heavily than certificates alone.
How long should a data analyst resume be?
One page for under ten years of experience. Senior and lead analysts with broad scope can use two, as long as the second page holds results rather than older duties.
How do I show impact if I do not know the business result?
Describe the reach of your work instead: who used it, how often, what it replaced and how much time it saved. Those facts are verifiable and still show value.
Next Step
Upload your resume to the free ATS resume checker to see what an employer's system extracts from it, then fix the gaps before you apply.
