Data Analyst resume example
Also indexed as: business intelligence analyst · reporting analyst
Analyst resumes read like tool inventories: SQL, Python, Tableau, Looker, Excel. Every applicant has the same list, so the list decides nothing. What decides is evidence that a number you produced changed what somebody did: a pricing decision reversed, a churn cohort found, a report that replaced a weekly meeting.
Hiring managers for analytics roles are also screening for whether you understand the business you were analysing. A bullet about a cohort model that mentions retention, payback period and the decision it informed says more about your seniority than any certification.
A complete document in the Meridian family of layouts, rendered live, not a screenshot.
The screen
What a data analyst resume is actually judged on
A decision at the end of the analysis
"Built a dashboard" is a deliverable. "Found the 34% of trials that never activated and drove the onboarding change that lifted conversion 1.9 points" is an outcome.
Data volume and modelling depth
Row counts, number of sources joined, whether you owned the transformation layer or consumed someone else's tables.
Stakeholder range
Who read your work: a team lead, a VP, the board? Reporting altitude is a real seniority signal.
Bullets
5 bullets that would survive the screen
Copy the shape, not the words. Each one leads with the result, then names the mechanism, and carries the vocabulary of the field without listing it.
Built the attribution model in dbt that finance now uses for board reporting, replacing three conflicting spreadsheets.
Identified the 34% of trials that never reached activation; the onboarding change it drove lifted trial-to-paid conversion 1.9 points, worth $1.4M ARR.
Cut the weekly reporting cycle from eleven hours to forty minutes by modelling the source tables once instead of per-report.
Ran the pricing elasticity study across 240K accounts that supported a 12% list-price increase with no measurable churn effect.
Owned the definition layer for 60+ metrics, ending the recurring disagreement between sales and finance on what counted as a qualified lead.
The rewrite that matters most in this role
Created dashboards in Tableau for various stakeholders across the business.
Replaced eleven ad-hoc Tableau workbooks with one governed metrics layer, cutting the weekly close from eleven hours to forty minutes and ending the sales-versus-finance disagreement on lead definitions.
Why it works: Same tool, but the strong version shows judgement: consolidation, governance, time recovered, and a political problem solved. That is the difference between an analyst and someone who makes charts.
Skills
Skills worth listing as a data analyst
Only what you would be comfortable being interviewed on. A long list dilutes every real match.
Technical & role-specific
Worth proving, not claiming
These belong inside a bullet that demonstrates them, not in a list. A line that says “communication” is worth nothing; a bullet showing you ran the workshop is worth a lot.
Keywords
What the tracking system is indexing
These are the terms a requisition for this title typically matches on. Use the ones that are true of you, inside the sentences where you did the work.
Paste the actual posting into the builder and you get this list generated from that requisition instead of the general case, including which terms you are already carrying and which bullet is the right home for the rest.
How keyword targeting worksMistakes
Errors specific to data analyst resumes
Not the generic advice. These are the ones that cost people interviews in this particular field.
Listing every BI tool ever opened
Four tools you can defend beat nine you have seen. Reviewers ask about the ones on the page.
No numbers in an analytics resume
It is the one role where the absence is fatal. If you cannot share the figure, give the scale: rows, accounts, percentage moved.
Describing the request instead of the insight
"Provided ad-hoc analysis to the marketing team" describes a ticket queue. Name one analysis and what it changed.
Questions
Data Analyst resume questions
Should I include SQL queries or code samples?
Not in the document. A link to a portfolio repository or a written case study is fine; a query in a resume costs you a third of a page and answers nothing a screener asks.
I am moving from analyst to data scientist. What changes?
Lead with modelling and experimentation rather than reporting, and make sure each bullet names the method as well as the result. The rest of the document stays.
Do certifications matter here?
Cloud and warehouse certifications get scanned for at large companies and ignored at small ones. One line at the bottom, never a section above your experience.