“Built dashboards using SQL and Tableau” tells a recruiter which tools you used. It leaves the most useful part of the work unexplained: what you analyzed, whether the results were trustworthy, and who used them.
A strong data analyst resume makes those connections visible. That applies to customer behavior, staffing, inventory, financial reporting, service delivery, and plenty of other work outside a technology company.
What your data analyst resume needs to establish
Read the job description before choosing examples. “Data analyst” can describe a reporting role, a commercially focused analyst, an operations specialist, or work with a heavier statistical component. One tool list won't establish fit for all of them.
Analytical capability
Show the data, tools, and methods you used, with enough detail to make the work credible.
Business context
Explain the question, process, or decision the analysis served.
Ownership and use
Identify your contribution and what happened to the result after you delivered it.
For business-facing analytics, this connection is consistent with the work described in O*NET's Business Intelligence Analysts profile, which includes querying information, producing reports, and communicating findings. That profile is useful context, not a universal specification for every data analyst job.
Compare the posting's requirements with evidence in your recent work. If it asks for SQL, recurring reporting, and stakeholder communication, show where you used those capabilities. If it asks for experiment design or forecasting, a dashboard project alone may leave a substantive gap.
A complete data analyst resume example
This example is for an analyst targeting an operations analytics role. It emphasizes SQL, reporting reliability, and decision support across a distribution business. The simple structure keeps the work easy to inspect.
Jordan Lee
Chicago, IL · jordan.lee@example.com
Portfolio: add your own public case-study link
Summary
Data analyst with four years of experience in operations reporting and inventory analysis. Uses SQL, Excel, and Power BI to reconcile inconsistent reporting, investigate service issues, and support planning decisions across distribution teams.
Technical Skills
Tools: SQL, PostgreSQL, Excel, Power Query, Power BI
Methods: data reconciliation, trend analysis, metric definition, dashboard development, data-quality checks
Professional Experience
Data Analyst · Riverton Distribution
July 2022 to Present
- Built a weekly Power BI delivery-performance report covering six distribution sites, using SQL to combine shipment records with carrier updates.
- Resolved conflicting definitions of “on-time delivery” with operations and customer service leads, documenting a shared rule for the weekly review.
- Investigated recurring late deliveries by route and departure window; findings informed a pilot change to dispatch timing on two routes.
- Automated the weekly source-file reconciliation with SQL checks and Power Query, reducing hands-on preparation from four hours to one hour per reporting cycle.
- Documented report ownership, refresh steps, and exception handling so another analyst could maintain the workflow during absences.
Operations Coordinator · Riverton Distribution
August 2019 to June 2022
- Maintained shipment exception records and coordinated follow-up between warehouse staff and customer service.
- Created an Excel reconciliation sheet to flag missing delivery confirmations before the weekly reporting deadline.
Selected Project
Inventory replenishment analysis · Independent project
January 2022 to April 2022
- Used a synthetic retail dataset to compare stockout patterns by product category and reorder interval.
- Wrote SQL transformations and created a Power BI report showing where apparent demand changes could reflect missing records.
- Documented assumptions and proposed a replenishment pilot; no live inventory changes or business results are claimed.
Education
B.S. in Business Administration · Example State University
Why this example holds together: The summary matches the experience. The coordinator role explains the candidate's operational background. The analyst bullets show tools, judgment, stakeholder work, and a measured process improvement. The independent project is clearly separate from employment.
The example contains a project because it helps explain this candidate's move into analytics. For an established analyst with stronger professional work to show, that space may be better used for a relevant accomplishment from employment.
What a recruiter can establish from this resume
| Resume evidence | What it supports | What it doesn't establish |
|---|---|---|
| SQL joins, reconciliation, and recurring Power BI reporting | Practical experience preparing and reporting operational data | Advanced data engineering or every form of statistical analysis |
| Agreement on an on-time-delivery definition | Experience resolving a business measurement problem | Ownership of the company's entire data governance program |
| Findings informed a dispatch pilot | A clear connection between analysis and a business action | That the pilot succeeded or the analyst caused a delivery improvement |
| Preparation time reduced from four hours to one | A specific process result, if supported by the candidate's records | A revenue or headcount saving that hasn't been measured |
This is the level of precision to aim for. A resume can be persuasive while staying within what the evidence supports.
How to write data analyst resume bullets
Use this structure as a starting point: the question or problem, your analysis, and the resulting output or use. You don't need all three in every sentence, but the experience section should establish them across the role.
Before rewriting a bullet, collect the underlying facts. What data did you use? What did you check? What did you personally build or analyze? Who used the result? Which outcomes can you actually verify?
A rewriting rule
The stronger bullets below use additional facts stated in each example. They aren't details to infer from the weaker sentence. If you don't have the supporting facts, ask for them or keep the claim narrower.
Marketing analysis
Known facts: The analyst used SQL to combine campaign and CRM records, found that duplicate records inflated lead counts, and corrected the reporting logic with marketing operations.
Too vague
Analyzed marketing data and created reports.
Evidence visible
Joined campaign and CRM records in SQL, identified duplicate leads inflating campaign totals, and corrected reporting logic with marketing operations.
The revised bullet establishes a data-quality problem and the candidate's contribution. It doesn't claim that correcting the report increased sales.
Financial reporting
Known facts: The analyst reconciled billing records against a revenue report, isolated timing differences, and prepared a monthly exception summary for finance.
Too vague
Supported financial analysis using Excel.
Evidence visible
Reconciled billing records against the monthly revenue report in Excel, isolating timing differences and preparing an exception summary for the finance team.
The scope is useful even without a percentage. Adding “improved financial accuracy by 30%” would require a defined measure and evidence the candidate may not have.
Service operations
Known facts: The analyst grouped support cases by issue type and customer segment, identified repeat contacts after onboarding, and presented the findings to the service manager.
Too vague
Used data to improve the customer experience.
Evidence visible
Segmented support cases by issue type and customer group, identified repeat contacts after onboarding, and presented the pattern to the service manager for a process review.
If a process change later reduced repeat contacts, add that result only when you can substantiate it and describe your contribution accurately.
Show impact without manufacturing a business result
The distinction between doing the work and owning the result is part of what recruiters look for in a resume. Give the reader enough detail to understand your contribution before attaching a business outcome to it.
Analysts don't always own the decision that follows their work. You may deliver a recommendation that another team chooses not to implement. You may improve a recurring report without access to a revenue figure. Neither situation makes the work unusable on a resume.
| What you can verify | Useful evidence to describe |
|---|---|
| A measured change | Report preparation time, error counts, processing time, or another clearly defined result |
| A decision or action | A pilot, budget review, staffing adjustment, or investigation informed by your findings |
| Adoption of your work | A report incorporated into a recurring review, with a named audience and purpose |
| A quality improvement | A reconciled discrepancy, agreed metric definition, or documented validation process |
| A completed analysis with no implementation | The question, method, finding, and recommendation, with its status stated accurately |
“Recommended,” “informed,” and “identified” can be precise descriptions of valuable work. Choose stronger ownership verbs when you actually owned the activity. Don't use “drove revenue growth” to bridge a gap between an analysis and a business result you can't attribute.
Use scale when it helps explain complexity: reporting across six sites, combining three source systems, or analyzing a weekly process. A large row count by itself says little about the quality of your reasoning. Explain why the work required judgment.
For confidential work, use approved aggregate descriptions and non-sensitive measures. Don't include customer records, private dashboards, or employer data in a public portfolio.
Choose data analyst resume skills around the job
A skills section helps the reader locate specific capabilities. The experience and project sections show how you used them. Both should reflect the work the posting requires.
| Category | Examples, when relevant | Supporting evidence |
|---|---|---|
| Querying and preparation | SQL, Excel, Power Query, Python or R | Combining sources, transforming data, checking completeness, or reconciling records |
| Reporting and visualization | Power BI, Tableau, Looker | Who used the report, what it measured, and how it fit into a decision or workflow |
| Analytical methods | Cohort analysis, forecasting, regression, experiment analysis | A specific question, the method used, and its assumptions or limitations |
| Business collaboration | Requirements gathering, metric definition, presenting findings | An example of resolving ambiguity or helping a stakeholder use the analysis |
This is a menu of possibilities, not a checklist. Don't add Python because another analyst lists it, or claim experiment design when you only reported the results of an experiment someone else designed.
For a role centered on SQL and Power BI, make those capabilities easy to find if you have them. For a role requiring advanced statistical work, show the relevant method in context. If you haven't used a required tool, related experience may help explain a transition, but it doesn't make the missing skill present.
Use the terminology in the job description when it accurately describes your work. Repeating the same tool throughout every bullet won't resolve a missing example. HireKey's guide to high resume match scores without interviews explains why keyword coverage alone can leave important questions unanswered.
Writing a data analyst resume for a career change
Relevant analytical work can sit inside finance, marketing, operations, customer service, or administration. Keep your actual title and bring that work forward. Don't rename a position simply to match the one you're pursuing.
Summary
Operations coordinator with experience reconciling inventory records and preparing weekly exception reports. Uses Excel and Power Query in daily work; developed SQL skills through an independent inventory analysis project. Seeking a data analyst role focused on operational reporting.
Operations Coordinator · Maple Supply Cooperative
May 2022 to Present
- Reconcile warehouse stock records with order reports in Excel, escalating mismatches to purchasing and site leads.
- Built a Power Query workflow that combines weekly inventory files into a consistent exception report.
- Review recurring discrepancies with warehouse supervisors to distinguish timing differences from missing transactions.
Recruiter read: The candidate already handles relevant business data. The summary distinguishes workplace Excel and Power Query experience from project-based SQL practice. It doesn't claim years of professional SQL experience the candidate hasn't established.
That distinction helps you assess which roles are realistic. A reporting-focused opening may be a better match than a position requiring several years of production Python, statistical modeling, and independent experiment design.
Don't hide unrelated work so aggressively that your chronology disappears. Condense less relevant tasks, preserve the role and dates, and make room for the analytical evidence.
Data analyst resume projects: show what you investigated
A project is most useful when the reader can see your decisions. Naming a dataset and attaching a dashboard link leaves too much unexplained. Describe the question, your work, what you found, and the limits of the result.
Service Request Analysis · Independent Project
June 2026 to August 2026
- Analyzed an openly licensed city service-request dataset using SQL, comparing recorded resolution times across request categories.
- Checked for duplicate IDs, missing closure dates, and changes in category labels before calculating summaries.
- Built a Tableau dashboard and documented why unresolved requests were reported separately from completed cases.
- Presented findings in a short case study; noted that differences in case complexity prevented a simple ranking of team performance.
Recruiter read: The candidate can explain data quality and the limits of a comparison. The entry makes no claim that a city used the findings or that the project improved public services.
Use your actual dataset name and a working portfolio link when adapting this structure. If the project came from a course, label it as a course project and explain your contribution beyond the supplied instructions. If you followed a tutorial exactly, don't describe every design decision as your own.
For a newer analyst, one or two substantial relevant projects can be more informative than a long list of nearly identical dashboards. For an experienced analyst, prioritize workplace evidence unless the project demonstrates a capability your employment history doesn't show.
If earlier non-analyst roles are crowding out your strongest analytical work, use our guide to what to keep, condense, or remove from your work history to decide how much space they deserve.
Data analyst resume format and final checks
Use a straightforward structure: contact information, an optional focused summary, technical skills, professional experience, relevant projects, and education. Change the order when it helps surface your strongest evidence. A recent graduate may put education and projects higher; an experienced analyst should usually lead with relevant work.
Use a simple single-column document with standard headings and selectable text. Follow the employer's file instructions. Greenhouse documents parsing problems associated with complex formatting, including certain tables, headers, and text boxes. Systems vary, so review the imported application fields rather than assuming the upload was interpreted perfectly.
The comparison tables and annotations in this article explain the examples. They aren't resume formatting instructions. Keep your actual resume straightforward.
One or two pages can work, depending on relevant experience. Avoid shrinking text to fit a fixed page target. Remove repetitive responsibilities and unsupported skill claims before cutting a useful example.
- The opening establishes the kind of analytics work you do.
- Important tools appear in both the skills section and relevant evidence.
- Bullets distinguish your contribution from the team's work.
- Results are measured or described within what you can verify.
- Coursework and independent projects are labeled accurately.
- Portfolio links work and expose no confidential information.
- Your resume supports the requirements of this particular opening.
Frequently asked questions
What should a data analyst put on a resume?
Include relevant tools and methods, the business questions you've worked on, evidence of your individual contribution, and the use or outcome of your analysis. Add professional experience, relevant projects, and education in an order that makes your strongest qualifications easy to find.
Do I need Python on my data analyst resume?
Include Python if you can support the level of proficiency you claim and it is relevant to the work. Some postings emphasize SQL, spreadsheets, or business intelligence tools; others require Python or R. Use the actual job requirements rather than treating one language as mandatory for every analyst role.
How do I write a data analyst resume with no analyst job experience?
Show relevant analytical work under your real job titles, and add well-explained projects or coursework where needed. Distinguish employment from independent practice. Demonstrate the data you handled, the methods you used, and the conclusions you can defend.
How do I show impact without revenue numbers?
Describe a verified process improvement, a resolved data-quality issue, an adopted report, or a decision your findings informed. You can also explain the completed analysis and its recommendation without claiming implementation. Don't invent a financial result to make the bullet look stronger.
Should I include every analytics tool I've used?
Prioritize the tools relevant to the job that you can discuss credibly. A long inventory doesn't explain depth or recency. Put important tools in context through experience or project bullets, and be clear when your exposure is introductory.
Should an experienced data analyst include a portfolio?
A portfolio can help when it demonstrates relevant work that the resume can't explain fully, particularly a new specialization. It isn't a substitute for clear professional evidence. Share only material you have permission to make public, and label synthetic or public datasets accurately.
Make the work behind the tools visible
See what your resume communicates.
Use HireKey's free recruiter-informed resume review to examine whether your positioning, evidence, and level are clear before you send your next application.
Review your resume for free