Data Analyst Resume Guide: Stack Match First, Then the Decisions You Changed

A practical guide from the team behind PlainResume, the free resume builder.

The default analyst resume is a tool list wearing a job: "SQL, Python, Tableau" up top, "built dashboards and analyzed data to support business decisions" below. The problem is that both halves describe every analyst alive. The manager reading it has one real question — did anything change because this person analyzed it? — because they've seen the alternative: dashboards nobody opens, decks nobody acts on. Your resume's job is to answer that question with specifics.

The stack line: SQL first, tiers, posting names

SQL is the gate skill — nearly every posting filters on it, so it leads. After that, the same rules as engineering resumes: 8–12 tools in honesty tiers, because every listed tool is an interview invitation. One analyst-specific wrinkle: Tableau, Power BI, and Looker are different keywords to an ATS, and shops are loyal to theirs — mirror the posting's tool when you genuinely know it, and say so plainly when you know its sibling ("Tableau daily; delivered two projects in Power BI").

The decision bullet: question → analysis → what changed

The formula has three parts: the business question, what you did analytically, and the decision that followed. The third part is the one most analyst resumes omit and the only one managers are screening for. Scope it honestly — you rarely make the decision, so say what's true: "flagged," "recommended," "leadership acted on." An honest "my analysis was one input to the pricing rollback" still beats "built dashboards," because it places you in the room where something changed.

The numbers that count (and the ones that don't)

Row counts and pipeline sizes impress other analysts, not hiring managers — use them sparingly. The numbers that carry weight are about consumption and consequence: cadence ("reviewed weekly by the exec team"), adoption ("self-serve dashboard used by 12 sales pods; replaced ad-hoc requests"), automation ("replaced a 6-hour weekly manual report"), and outcome direction with honest magnitude ("churn fell from roughly 1.8% to 1.2% monthly after the fix"). When employer confidentiality bites, relative figures and adoption evidence carry the signal without disclosing the books — the same ratios-not-books principle sales resumes use.

Early career: the portfolio is the experience section

Without work history, one or two finished projects on real public data are your strongest evidence (the first-resume problem, analyst edition). The differentiating move is the writeup: frame each project as a decision memo — what you asked, what you found, what you'd recommend — not a tutorial notebook. One reasoned analysis with a clean README beats five Titanic notebooks, for the same reason deployed beats tutorial for engineers. Course certificates follow the usual rule: the skill and the project carry the claim; the certificate is a footnote.

What to cut

• "Data-driven storyteller," "passionate about insights" — the field's cliché pair; your decision bullets are the storytelling evidence.
• Inflated method claims — a linear regression in a notebook is not "machine learning," and the interviewer who asks about your "ML models" will find out in one question. Name the actual method; competence with the right tool reads better than borrowed vocabulary.
• The tool wall — compressed into tiers, above.

Your summary should read like your best bullet generalized: "Data analyst, 4 years in e-commerce — SQL/Tableau daily; built the retention reporting the exec team reviews weekly, and the churn analysis behind last year's pricing fix."

Frequently asked questions