How to write a data analyst resume
Updated 2026-09-02
A data analyst resume is measured in decisions changed. SQL, Python, and dashboards are the entry ticket, and every applicant lists them. A hiring manager scans for something else. Which of your conclusions made someone change course, and which metric moved after that?
That sounds harsh if your week is mostly queries, reports, and ad-hoc requests. Usually the gap sits in the writing. “Did a churn analysis” is an activity. “The churn analysis led to a repricing that cut monthly churn by [N] points” is evidence. Every example on this page shows that shift.
One rule holds throughout: no invented numbers. Wherever a metric belongs, the examples show a [N] placeholder. Your real figures come from your own records. A template cannot supply them, and neither can an AI.
What a finished one looks like
Below is a complete sample for a fictional person, rendered as a real page by the product's own sheet and scored by the same rules engine the editor uses — the number is computed, not typed in. Every figure a bullet owes is left as [N], which is why the score stops under the cap. That is not a flaw in the example; it is the product's rule, demonstrated.
Priya Raman
Education
- Built the ridership model for [N] years of public transit data and presented it to the city transport office
- Won the institute analytics competition against [N] teams with a dining-hall demand forecast the hostel office then ran for two semesters
Experience
- Cut churn among new users by [N]% after showing that most of it came from accounts that never finished KYC, which drove a redesign of that step
- Designed and read out [N] A/B tests per quarter, including the pricing test that raised paid conversion by [N]%
- Recovered [N] million rupees of misattributed revenue by finding the channel bug that overstated one source
- Established the seller cohort model in SQL and Python that showed which onboarding step predicted [N]-day survival, changing the sales follow-up order
- Automated the weekly category report with dbt and Airflow, cutting preparation from [N] hours to [N] minutes
- Eliminated [N] thousand duplicate SKUs across [N] sellers through a fuzzy-matching pipeline, restoring search relevance in the affected categories
- Delivered the segmentation study on [N] thousand survey responses that the client used to decide which of its [N] product lines to keep
- Migrated [N] recurring client trackers from spreadsheets to SQL and Python, so the weekly refresh ran without anyone opening a file
- Standardized questionnaire coding across [N] studies, cutting final reconciliation from [N] days to one
Projects
- Scaled an open nightly collector of public food-price bulletins to [N] million observations across [N] cities
- Launched a sample-size calculator that ended the [N] rounds of scoping messages before each experiment
Additional Information
Layout: put a decision in the first ten seconds
One page by default. Two pages only past eight years of experience. Use the standard headings: Summary, Skills, Experience, Education. ATS parsers key on those exact words. Content under a creative heading may as well not exist.
Order sections by evidence density, strongest first. The first scan rarely covers more than the top half of the page. Your best proof has to sit there.
- 1Summary
Three lines: years and domain (product, marketing, or revenue analytics), plus your strongest decision-level result. This is the only section guaranteed a full read.
- 2Skills
Before Experience, so parsers and skimmers match keywords early. List only tools you can defend under follow-up questions.
- 3Experience
Reverse chronological. One decision or one moved metric per bullet; tool names play a supporting role.
- 4Projects
For entry-level candidates and career changers, place this above Experience. A full analysis on public data, with a link, is your one verifiable credential.
- 5Education
Degree plus statistics or quantitative coursework. Keep GPA only within a few years of graduation.
Summary examples by level
A summary previews your strongest evidence. Three lines: years and domain, one decision-level result, and the role you want next.
Statistics graduate with two analytics internships, focused on turning product data into decisions. Built the cohort analysis behind a [N]% cut in onboarding drop-off and automated [N] weekly reports in SQL and Python. Seeking a product analytics role with direct metric ownership.
With no tenure, cite verifiable internship output: one adopted analysis, one thing automated. The last sentence names the direction you want.
Data analyst with [N] years across e-commerce and SaaS, specialized in experimentation and revenue metrics. Designed the A/B testing process now used by [N] product teams, and led the churn analysis behind a repricing that cut monthly churn by [N] points. Comfortable presenting directly to executives.
Mid-career proof is adoption: a process teams still use, a decision that got made. Each [N] maps to one claim an interviewer can probe.
Analytics lead who builds metric systems rather than report queues: defined company-wide activation and retention metrics and the monthly review that runs on them. Manages [N] analysts and moved the team from ad-hoc queries to tested dbt models. Applies one filter to every request: which decision will this change.
Senior signal is a lever: metric systems, a team, a review cadence. The closing line is a working philosophy. Write it only if a whole interview can test you on it.
Bullet examples by competency
Interviewers look for five kinds of evidence on an analyst resume. Each example is a complete line: verb first, concrete scope, [N] where a metric belongs.
Decision impact
· Recommended shutting down an underperforming paid channel after cohort analysis; reallocating its budget lifted overall signup conversion by [N]%.
· Found [N]% of trial signups were duplicate accounts via a SQL audit, prompting finance to restate quarterly growth reporting.
· Led the churn analysis behind an entry-plan repricing, cutting monthly churn by [N] points within two quarters.
Experimentation and causal judgment
· Designed [N] A/B tests per quarter on onboarding flows, setting success metrics and minimum sample sizes before launch.
· Flagged a seasonality confounder in a rollout readout, stopping a launch that had shown a false [N]% lift.
· Introduced pre-registered metric plans for all experiments, cutting disputed readouts between product and marketing by [N]%.
Data quality and pipelines
· Migrated [N] recurring spreadsheet reports to tested dbt models, cutting weekly manual preparation from [N] hours to minutes.
· Rebuilt the revenue attribution query after finding double-counted refunds, correcting a [N]% overstatement in reported ARPU.
· Wrote data quality tests covering [N] core tables, so broken pipelines surface before stakeholders see wrong numbers.
Metric design and monitoring
· Defined a company-wide activation metric, replacing [N] conflicting definitions used across product and marketing dashboards.
· Built anomaly alerts on [N] core metrics, catching a payment-gateway failure the same day instead of at month-end close.
· Retired [N] unused dashboards after a usage audit, consolidating reporting into one weekly review used in the executive meeting.
Stakeholder translation
· Turned a pricing-elasticity analysis into a one-page recommendation; sales adopted the revised discount floor the following quarter.
· Ran monthly metric reviews with product and finance, converting ad-hoc data requests into a prioritized backlog.
· Wrote plain-language experiment readouts stating the decision each result supported and what remained uncertain.
Weak lines, rewritten
Each pair names the defect. The pattern behind all of them: weak lines describe activity, strong lines carry a decision and a moved metric.
Responsible for creating dashboards and reports for the marketing team.
Built [N] self-serve marketing dashboards that replaced weekly manual reports, saving [N] analyst-hours per month and answering campaign questions same-day.
Why it works · Defect: activity with no outcome, opened by the most passive duty phrase there is. A dashboard is only a medium. The rewrite says what it replaced, what it saved, and who got answers faster.
Analyzed user data to provide insights for product decisions.
Analyzed [N] months of churn data and recommended removing the forced tutorial; the change lifted week-one retention by [N] points.
Why it works · Defect: “insights” cannot be verified. The rewrite names the actual decision (removing the tutorial) and the metric that moved. Every word survives a follow-up.
Used SQL, Python, and Tableau on a daily basis.
Automated [N] recurring reports with Python and SQL, cutting the monthly close package from [N] days of manual work to one morning.
Why it works · Defect: a tool list is not an achievement. Tools belong on one line in Skills. A bullet has to say what the tools produced.
Helped improve the A/B testing process.
Introduced minimum sample-size checks and pre-registered metric plans for every experiment, cutting inconclusive readouts by [N]%.
Why it works · Defect: “Helped” hides the owner, so no one can tell which step was yours. The rewrite names two concrete mechanisms, and your contribution has nowhere to hide.
Worked with stakeholders to understand business requirements.
Ran a monthly metrics review with sales and finance, replacing [N] recurring ad-hoc requests with one agreed dashboard per team.
Why it works · Defect: anyone in any role can write this line, so it says nothing. The rewrite adds frequency, audience, and what got replaced. Now only you could write it.
Skills: what stays, what goes
List only what survives a follow-up question. Every tool named is both a keyword match and an invitation to be tested on the spot.
Worth the space
SQL (window functions, CTEs) · Python (pandas) · dbt · Excel (advanced formulas, pivot tables)
A/B testing and sample-size planning · Regression analysis · Hypothesis testing · Basic causal inference
Tableau · Looker · Power BI (list only what you have used)
BigQuery · Snowflake · Airflow (only with real scheduling experience)
Cut these
- Microsoft Office · Assumed for this role. Listing it dilutes real skills and suggests you had nothing stronger to say.
- Data-driven mindset · This is an adjective, and nobody can check it. If your bullets are written right, it is self-evident.
- Big Data · A label with no information. Name the platform and the scale (BigQuery, Spark, events per day), or leave it out.
- Familiar with machine learning · “Familiar” does not survive one follow-up. Which model, deployed where, with what result? If you cannot answer, delete the line.
ATS keywords that match how jobs are written
The words that recur in job descriptions are the words parsers match. Put the ones you have really done into bullets and Skills. Spell them the way the posting does.
Only use terms your experience can defend. Keyword stuffing does not move a parser, and a human reader hears noise. Every term you cannot back up in conversation is a landmine you planted yourself.
The evidence a reviewer can open
Almost nothing an analyst produces can be inspected by a stranger. The dashboards sit behind a company login, the queries live in a warehouse, and the memo that changed a price is on an internal drive. So the few things you can hand over carry more weight than they look like they should. This section covers what a reader actually opens, the line on the resume that points at it, and when the honest move is to point at nothing.
- The order they open things
The resume first, then usually LinkedIn — not to admire it, but to check that the dates and titles line up. The link in your header comes third, and only after a bullet made someone curious. With a few years of history behind you, plenty of readers stop at step two. Entry-level candidates and career changers get the reverse: the link is the screen, opened before anyone decides whether your bullets deserve a second read.
- The line on the resume that points at it
One line under Projects, with the conclusion inside it: “Open food-price tracker (Python, DuckDB) — nightly collector over public price bulletins; README opens with what the price series shows. github.com/you/price-tracker”. The link belongs in the header only when the whole profile is worth opening: “Portfolio: public.tableau.com/app/profile/you”. Never put the same thing in the header and under Projects. That reads as one project stretched to look like two.
- Open every link from a logged-out window
A Looker Studio report is private by default. A free-tier Streamlit app sleeps, so a stranger meets a wake-up screen. An .ipynb GitHub cannot render arrives as raw JSON, and a notebook whose outputs were cleared before the commit is a page of code with no charts in it. Each of those is a reader who tried and gave up, which lands worse than no link at all. Open every URL on the resume in a private window the week you send it, and look at what a stranger sees rather than what you remember putting there.
- Certifications a register can confirm
Tableau Desktop Specialist, Microsoft’s PL-300, the Google Data Analytics Certificate and dbt’s analytics engineering exam each issue a credential ID and a page that confirms it. Put the ID or the URL on the line; a certification with neither is a sentence, not a credential. Write the year you earned it. Some renew and some do not, so check yours before you send instead of letting the reader be the one who finds it lapsed. And keep two words apart: finishing a course is “Completed”, passing a proctored exam is “Certified”. The register knows which one you are, and so will anyone who looks.
- When the honest move is an empty field
A GitHub of forks with one Untitled.ipynb in it. A Tableau Public profile holding the sample-superstore workbook from the tutorial. A README still sitting on the default template. Whoever opens that learns you finished a course, which your certification line already said, and now also knows your judgment about what is worth showing. Delete the field. An empty one is a neutral signal; a bad link is a negative one. One finished analysis repairs it: one question, one public dataset, one recommendation, and a README a person can read without running anything.
- The work you are not allowed to show
Your strongest evidence is internal: the dashboard the executive meeting runs on, the query that caught the double-counted refunds. Do not screenshot it. Blurring an axis is not redaction, and the metric names alone will name the employer. What travels out is structure without values — the grain of the table, the join that was wrong, the decision that changed, and the movement written as a relative change. If you want something clickable, rebuild the same shape of analysis on a public dataset and say so in the README: same question, data anyone can download. That sentence is also your answer when an interviewer asks what you cannot share.
Common data analyst resume mistakes
- 1Counting dashboards as achievements
A dashboard is a medium, and a medium is not impact. Say which decision it served and who uses it weekly. Saying how many unused ones you retired works just as well.
- 2Making the tool list the main course
SQL, Excel, and Tableau are the entry ticket every competitor holds. Keep them to one line in Skills and spend the space on work only you did.
- 3Ending every bullet at “insights”
“Provided insights” and “supported decision-making” cannot be verified. Go one step further: who adopted it, what changed, which metric moved. If nothing was adopted, tell a different story.
- 4Using statistical vocabulary beyond your depth
Write “statistically significant” and you must state the sample size, the test, and how you chose the threshold. A misused term costs more than a missing one. It exposes your depth and your honesty at once.
- 5Claiming the team’s experiment as yours
Experiments are joint work across product, engineering, and analytics. The first follow-up is always which part you owned: the metric, the sample size, or the readout. Precision here makes you more credible.
- 6Leaving out data quality work
Correcting a miscalculated metric or stopping a wrong readout is strong evidence of judgment. Most people file it under chores and leave it out. That is exactly why it stands out.
The follow-ups your resume will trigger
An interviewer reads an analyst resume by picking one bullet and drilling three levels down. Every line you write should be ready for the exchange below.
The change lifted week-one retention by [N] points.
How was that number computed? Who is in the denominator, how long was the window, and what else shipped in the same period?
The exact metric definition, the sample composition, a list of concurrent changes, and how you ruled out confounders. If you cannot name the denominator, the bullet scores against you.
Designed A/B tests with minimum sample sizes set before launch.
How did you set the sample size? If the metric turns positive after one week and negative after two, what is your stopping rule?
The actual power-analysis steps, how you chose the minimum detectable effect, and one real case of an early stop or a reversed conclusion. This question separates doing from reading.
Defined the company-wide activation metric.
Why that definition? Which candidate definitions were rejected, and who pushed back?
The comparison of candidates, the objections and your answers, and one time the definition was challenged after launch. Metric definitions are half technique and half politics. Interviewers want to hear both.
Corrected a [N]% overstatement in reported ARPU.
How long did the error exist? Who caught it first? What did you change to prevent a repeat?
The timeline of discovery and fix, how you told finance and your manager, and the tests or monitoring you added. Half of this question is technique. The other half is whether you own mistakes.
Presented recommendations directly to executives.
Tell me about a recommendation of yours that was rejected. What was the reasoning, and who turned out to be right?
One real rejected case and how you verified the outcome later. Only people who have never presented to executives claim their recommendations always land.
FAQ
My job is mostly reports and ad-hoc requests. I never changed a decision. What do I write?
Trace one level upstream: who reads the report, and what they do after reading it. A process you automated, a wrong number you corrected, a bad readout you stopped. All of that is decision-level material you have been filing as routine.
If an honest inventory truly turns up nothing, that is useful information too: it tells you what kind of environment to pick next.
Should machine learning go on a data analyst resume?
Only if the job description asks for it and you have trained and delivered a model. The core of analyst roles is SQL, experimentation, and business judgment. An ML project that cannot survive follow-up questions is worse than none.
I come from Excel with no formal SQL work experience. Can I apply to multinational analyst roles?
Yes, but the evidence has to be checkable. Build one complete analysis on public data: queries, interpretation, recommendation. Put it on GitHub with a clear README. That beats a line saying familiar with SQL.
Advanced Excel (pivot tables, complex formulas) is a real skill. Keep it, and pair it with a bullet about what it produced.
My results are internal company data. Is it safe to put them on a resume?
Write relative changes rather than absolute values. Churn down [N] points is resume language; revenue figures are confidential. The [N] placeholders in these examples work the same way: you fill in what is safe to disclose.
Do analysts need a GitHub or portfolio link?
Only if it is curated. One project with a complete README and a clear conclusion beats ten empty repos. An interviewer spends a few minutes there at most, so design for those minutes. It is close to mandatory for entry-level candidates and career changers, and work history can stand in for it later.
Rewrite your analysis work into English at this level
Describe your analyses and the decisions they changed, in Chinese or English. The AI rewrites them into decision-first bullets in the syntax multinational recruiters expect, about ten seconds per draft. The four scores come from a rules engine, so the same draft always scores the same. Every missing metric stays a yellow [N] placeholder for you to fill. No invented numbers, ever.
Try 2 free drafts