The Data Analyst resume: every KPI, formula, and pattern
The 7 numbers that carry this resume
Every data analyst bullet gets stronger with one of these. The benchmark tells you what's worth claiming; the question helps you dig your real number out.
Name one decision that changed because of your analysis. What did it save or earn?
What was the money attached — savings found, revenue unlocked, spend reallocated?
Who uses your dashboards, how often, and what meeting or process runs on them?
What manual reporting did you kill? How many hours a week, for how many people?
How many experiments did you design or read out? Which one changed the product?
Did you make a slow report fast or a flaky pipeline reliable? From what to what?
How large were the datasets — rows, events per day, number of sources joined?
Bullet formulas
Structure first, wording second. Fill the brackets with your own numbers.
Strong verb + analysis or artifact + tool + the decision/outcome it drove, with the number.Weak: "Created dashboards in Tableau." Strong: "Built the retention dashboard (Tableau + BigQuery) that surfaced a 23% drop-off at onboarding step 3; the redesign it triggered lifted D30 retention 4 points."No money numbers? Use adoption, time saved, or scale: "used weekly by 40 sellers", "killed 6 hrs/week of manual reporting", "across 200M events/day".
Verbs that read like ownership
Weak phrase → stronger pattern
A dashboard nobody opens is a chart. Adoption is the metric of a dashboard.
Analysis is the verb of the job title — the finding and the decision are the achievement.
Name the stakeholder, the recommendation, and whether it was acted on.
Recurring manual reporting is a cost center; automating or eliminating it is the win.
Tools belong inside an achievement, not as one.
"Insights" is filler until you name one and what it changed.
Keywords screens look for
Use the ones that are true for you — keyword stuffing reads as noise to a human on the other side. The studio tracks your coverage live.
Before you send it
- Every bullet ends in a number: money, hours saved, adoption, accuracy, or scale
- One line that proves SQL depth — window functions, multi-source joins, or the event volume you queried
- Dashboards described by who uses them and for what, never by how many you made
- A named experiment win with the metric it moved
- Metric definitions/data-quality work mentioned once — it signals seniority and trust
- Portfolio link if early-career: a public analysis with real data beats certifications
- Tools list matched to the JD's stack synonyms (Power BI vs Tableau, BigQuery vs Snowflake)
See how your resume scores against this guide
Free instant check — the same engine, no sign-up, nothing stored.
Check my resume →