Data analyst resume that turns queries into business decisions.

A data analyst resume is screened on two signals before anyone reads a full sentence. First, the tool stack: SQL is non-negotiable, and most postings also want at least one of Python or R, plus a BI tool (Tableau, Power BI, or Looker) and spreadsheets at a real level. Second, evidence that your analysis changed something a stakeholder did. A dashboard that nobody used is a maintenance task. A dashboard that cut weekly reporting from four hours to twenty minutes is a result.

The trap is describing your tools as a hobby instead of a job. 'Built dashboards in Tableau' tells a recruiter nothing about scale, audience, or impact. 'Built and maintained 6 executive Tableau dashboards tracking a 40M dollar revenue pipeline, adopted by 3 regional sales teams' tells them you operate at the level they are hiring for. Same tool, completely different read.

Keep SQL prominent and specific. Naming the dialect and the hard part (window functions, CTEs, query optimization on tables in the hundreds of millions of rows) separates you from the half of applicants who list 'SQL' as a single word and hope. Recruiters discount a bare keyword; they trust a sentence that proves depth.

Every strong analyst bullet has three parts: what you analyzed, the insight you surfaced, and the decision or dollar impact that followed. Weak bullets stop after part one. Strong bullets carry all three, and the number lives in part three because that is the part a hiring manager can defend in a review meeting.

Use this scaffold and fill it with your own work. The verbs that pull weight here are analyzed, modeled, segmented, forecasted, automated, and quantified, not 'responsible for' or 'helped with'.

• Analysis plus decisionAnalyzed 18 months of churn data in SQL and Python, identified 3 at-risk customer segments, and informed a retention campaign that cut monthly churn from 6.1% to 4.3%.
• Automation plus time savedAutomated a weekly KPI report with Python and the Tableau API, eliminating roughly 6 hours of manual work per week across the analytics team.
• Insight plus revenueBuilt a cohort model in Power BI that surfaced a pricing gap in the mid-market tier, supporting a packaging change that added 320K dollars in annual recurring revenue.
• What to avoid'Created dashboards and reports for stakeholders.' No tool, no scale, no outcome. It reads as a task description, not an achievement, and it is the most common line on a weak analyst resume.

A flat comma list of 30 tools helps nobody. Group your skills into named buckets so a recruiter scans them in two seconds and an applicant tracking system maps them cleanly to the job description. Four groups cover almost every data analyst posting: querying and languages, BI and visualization, statistics and methods, and data tooling. List the items in each group as plain text, never as skill bars or rating dots, which parsers cannot read.

Mirror the job description's exact wording. If the posting says 'Power BI' and you write 'PowerBI', or it says 'Microsoft SQL Server' and you only write 'SQL', you can lose the keyword match. Match the spelling the employer used, then keep the rest of the resume honest to what you can actually do in an interview.

• Querying and languagesSQL (PostgreSQL, BigQuery, Snowflake), Python (pandas, NumPy), R. Name the dialects you have actually used; they double as keyword matches.
• BI and visualizationTableau, Power BI, Looker, plus Excel and Google Sheets at an advanced level (pivot tables, XLOOKUP, Power Query). Spreadsheets still appear in most analyst JDs.
• Statistics and methodsA/B testing, regression, cohort and funnel analysis, forecasting, segmentation. These signal you analyze, not just visualize.
• Data toolingdbt, Airflow, Git, Jupyter, and the cloud warehouse you work in. Keep this list to tools you could discuss under questioning.

An entry level data analyst resume wins on projects and transferable analysis, not on a job title you do not have yet. Reorder the page so a Projects section sits near the top, right after a short summary, and treat each project like a job: a clear name, the tools used, and two or three quantified bullets. Pull data from a public source (a Kaggle dataset, a government open-data portal, an API), ask a real question, and report what you found and what it would mean for a decision-maker.

Transferable experience counts more than candidates think. Built reports in Excel for a previous retail or operations job? That is SQL-adjacent analytical work, so describe it with the same insight-to-decision pattern. A statistics or economics course where you ran regressions in R, a capstone, a bootcamp portfolio project: each is a legitimate proof point when you name the method and the result. The point is to show you can take a question, query the data, and produce an answer someone can act on.

Keep the layout ruthlessly ATS-clean: single column, standard section names (Summary, Skills, Projects, Education, Experience), no photo, no sidebar, no graphics. An entry-level resume that parses cleanly and shows three solid analytical projects beats a flashy one that scrambles in the parser and never reaches a human. If you are aiming higher up the ladder later, the data scientist resume guide shows how the same proof-of-impact discipline scales to deployed models.