The problem with analyst resumes
Analyst resumes tend to drift toward either of two failure modes. The first is a tools list dressed up as experience: "Used SQL and Python to build dashboards." The reader learns nothing about what the work achieved. The second is a business claim with no method: "Improved revenue by 12%." The reader cannot tell whether the candidate did that work or stumbled into it.
This example threads between the two. Every bullet names a specific method and a specific outcome, in that order. For example: "Identified an assortment gap worth €1.1m annual revenue through a basket-affinity analysis." Method first (basket-affinity analysis), outcome second (assortment gap worth a specific number). The reader can picture the work and can see the result.
The skills section
The skills section names the tools you would expect for this role (SQL, Python with two specific libraries, dbt, Power BI, Looker) and one category that is harder to prove but worth naming (stakeholder communication). Ten entries, no filler.
Note that "Excel" is not on the list. At the level of this resume, Excel is assumed. Listing it wastes a slot and makes the resume look less confident.
Education placement
The education section comes after skills, which is a small but deliberate choice. For a data analyst with five years of experience, the education is not the strongest evidence — the work is. Placing education below skills but above experience would be fine too; placing it above experience would over-emphasise the degree.
Bullet patterns to avoid
Three bullet patterns appear on many analyst resumes and should generally be avoided:
- "Responsible for dashboards." This describes a responsibility, not a result. Replace with what the dashboard did, how many people used it, or what decision it supported.
- "Wrote SQL queries." Every analyst writes SQL queries. If the query work is the story, describe the query's purpose: "Built a query layer that reduced report generation time from 45 minutes to 3 minutes."
- "Performed ad-hoc analysis for stakeholders." "Ad-hoc" and "stakeholders" are words that signal a task, not a result. Name the analysis, the audience, and what changed because of it.