Reviewed:
Data Analyst resume example
A data analyst is hired to turn messy operational data into answers someone can act on. In an engineering organisation that usually means writing SQL against warehouse tables, building dashboards that on-call engineers and product managers actually open, and doing the ad hoc digging when a metric moves and nobody knows why. The job is judged on whether the numbers are right and whether anyone changed a decision because of them.
A screener reads a data analyst resume looking for three things fast: which databases and dialects you have written against, which BI tool you own end to end, and evidence that you can define a metric and defend it. Listing tools is not enough. Each role should show the question you were asked, the query or model you built, and what the business did next.
Mid-level means you are trusted alone with a dataset. Show that you have cleaned data no one wanted to touch, caught a bad number before it reached a report, written documentation other people use, and taught a stakeholder to read a dashboard instead of asking you for a screenshot. Keep it to one page and put numbers on the outcomes.
The example
Jordan Avery is a placeholder, and every employer on this page is fictional. The numbers are illustrative.
What makes it work
The same bullets as people usually write them, and what changed.
Before
Responsible for building and maintaining dashboards for various stakeholders.
After
Rebuilt the fulfilment dashboard in Tableau around four agreed metrics, cutting weekly ad hoc report requests from about 15 to 4.
Replaces a duty with a specific artefact and a volume change the manager can picture.
Before
Wrote complex SQL queries to pull data from multiple sources.
After
Wrote a dbt model joining order, carrier and scan events so late-delivery reporting ran from one table instead of three hand-run queries.
"Complex" tells the reader nothing; the rewrite names the data and what it replaced.
Before
Worked closely with engineering and product teams on data needs.
After
Ran a 30-minute intake call for each analysis request and turned vague asks into a written question and success metric before starting.
Shows the actual practice behind collaboration instead of asserting it.
Before
Improved data quality across reporting.
After
Added 22 dbt tests for null keys and duplicate order IDs, which caught a broken upstream feed a day before month-end reporting.
Names the checks and gives one concrete save, which is more convincing than a claim of improvement.
Before
Analyzed A/B test results for new product features.
After
Analysed a checkout experiment across 40,000 sessions and recommended against launch after the lift fell inside the confidence interval.
Includes scale, the statistical reasoning, and a decision the analysis actually changed.
Before
Trained team members on using BI tools and reports.
After
Taught two support leads to filter and export from the queue dashboard, ending roughly six screenshot requests a week.
Small, specific and measurable, which reads as true where a training claim does not.
Keywords a data analyst resume needs
| Keyword | Why it matters | Where to put it |
|---|---|---|
| SQL | Nearly every data analyst screen filters on SQL, and hiring managers expect window functions and CTEs at this level, not just SELECT. | skills list and at least two experience bullets |
| Snowflake | Names the warehouse you worked in, which tells the reader your queries ran at real scale. | skills list under databases |
| dbt | Shows you build modelled, tested tables rather than one-off queries, which is standard in analytics engineering-adjacent roles. | skills list and a bullet about data models |
| Tableau | BI tool ownership is a hard requirement in most postings; recruiters match the specific tool. | skills list and a dashboard bullet |
| Python (pandas) | Signals you can handle work that outgrows SQL, such as cohort analysis or file cleanup. | skills list |
| A/B testing | Engineering and product teams ask analysts to read experiment results and say whether a difference is real. | a bullet under your most recent role |
| data quality | Analysts are trusted when they catch bad data; postings name accuracy and validation explicitly. | summary and a bullet about testing or checks |
| ETL pipelines | Shows you understand where your data comes from and can debug it upstream. | skills list and an experience bullet |
| stakeholder requirements | Half the job is turning a vague request into a answerable question; this phrase maps to that. | summary or a bullet about intake |
| KPI definition | Teams need one agreed definition per metric; owning that is a mid-level signal. | a bullet under your most recent role |
| data visualization | Common screening term and covers chart choice, not just tool operation. | skills list |
| Git | Analysts who version their SQL fit engineering workflows; many teams require pull requests for model changes. | skills list |
| cohort analysis | A concrete analytical method that proves you go beyond counts and averages. | an experience bullet |
| self-service reporting | Reducing ad hoc request volume is a measurable outcome managers care about. | a bullet about dashboards or documentation |
Common mistakes
- Listing SQL, Python and Tableau with no bullet showing what you built in any of them.
- Describing dashboards without saying who used them or what changed after they shipped.
- Claiming huge percentage gains, like cutting query time 99%, which makes every other number suspect.
- Writing bullets about data pulls and extracts, which reads as a report runner rather than an analyst.
- Skipping the warehouse and BI tool names, so recruiter keyword searches miss you entirely.
- Padding with machine learning coursework when the role is reporting and experimentation.
- Explaining methods at length but never naming a decision, launch or process the analysis affected.
- Using a two-page resume where the second page is a list of every tool you have ever opened.
Questions people ask
- How much SQL detail should I put on a data analyst resume?
- Name the dialects and warehouses you have worked in, then prove depth in a bullet. Mentioning window functions, CTEs or an incremental model is more useful than writing "advanced SQL". One or two bullets that describe a real query or model do the job.
- Do I need Python if the job is mostly SQL and dashboards?
- It helps but it is rarely the deciding factor at mid-level. Listing pandas and one bullet where a script did something SQL could not is enough. Do not invent machine learning work you have not done.
- Should I include a portfolio or GitHub link?
- Yes, if it contains something a stranger can read in two minutes. A repo with clean SQL, a short README and a dashboard screenshot beats a long notebook nobody opens. Put the link in the header, not in a separate section.
- How do I show business impact when I only produced reports?
- Track what happened after the report. Did a team change a threshold, stop a launch, reallocate staff, or stop asking you for numbers? Even "replaced a weekly manual spreadsheet" is an outcome, and time saved counts.
- Is a data analyst resume different for an engineering team?
- Somewhat. Engineering-adjacent teams care about version control, data modelling, pipeline debugging and instrumentation quality, so put Git, dbt and ETL work forward. Marketing or finance teams weight attribution and forecasting instead.
- How many bullets per role?
- Three to five. Give the current role four or five and older roles three. Cut anything that repeats a tool you have already proved.
- Do certifications matter for data analysts?
- They matter most early on or when you are switching fields. A warehouse or BI certification shows current tool knowledge, but a mid-level analyst with strong bullets does not need one. List them in one short line near the bottom.
- What should the summary say?
- Two or three sentences naming your years of experience, your main stack, and the kind of questions you answer. Skip adjectives about yourself and skip career goals. A screener should know within five seconds whether your tools match theirs.
More resume examples
Now do it with your own resume
Paste your resume and a job description to tailor your experience to the role. Review every suggestion before using it.
Start from this example