Which data analyst resume fits your evidence?
Choose Sofia’s structure when projects show your strongest analysis. Choose Miles’s when you have recurring responsibility for business questions, report definitions and stakeholder reviews. For a mid-level application, lead with relevant work and select the decisions you actually owned.
| What changes | Junior · SQL and portfolio | Experienced · Business decisions |
|---|---|---|
| Junior / recent graduate | Focused summary, education, projects, related work, skills | A defined question, SQL or spreadsheet method, validation and a finding with limitations. |
| Mid-level analyst | Recent relevant experience, selected skills, education; projects only when they add evidence | Independent analysis, maintained reports, stakeholder clarification and checks before delivery. |
| Experienced / senior individual contributor | Focused summary, experience, skills, education | Metric ownership, analytical tradeoffs, business interpretation, review practices and follow-through on recommendations. |
Example 1 of 2
Junior data analyst resume: SQL projects and related work
Sofia graduated in June 2026 and is applying for her first analyst job. Education and two clearly labeled projects show preparation. Her office work adds actual reconciliation and reporting responsibility without being renamed an analyst internship. The portfolio address is a placeholder for a public case-study landing page.
Recent information systems graduate targeting junior data analyst roles. Uses SQL, Excel and Power BI to turn a defined question into checked tables and readable reports. Portfolio work includes repeat-purchase analysis and appointment reporting, with query notes and limitations alongside each output.
- Relevant study: relational databases, business statistics and data visualization.
- Defined a second-purchase question by first-order month; excluded cancelled orders and kept recent cohorts separate when their observation window was incomplete.
- Used SQL CTEs and ROW_NUMBER to identify each customer’s first and second completed orders; checked tied timestamps with order IDs and reconciled customer counts to a separate aggregate query.
- Built a Power BI cohort report with a date table, documented denominators and a sample-order drill-through; published SQL, a data dictionary and a limitations note in the portfolio.
- Separated attended, cancelled and missed appointments in Power Query; flagged duplicate appointment IDs and retained unknown statuses in an exception table for review.
- Compared attendance by weekday and lead time with Excel PivotTables; proposed within-weekday checks in a brief before attributing differences to reminder messages.
- Reconciled weekly equipment sign-out sheets with the Excel return log; marked unresolved items for the supervisor rather than overwriting conflicting records.
- Prepared a monthly checkout summary using PivotTables and COUNTIFS; checked totals against source sheets and documented the reporting steps for the next student assistant.
Read Sofia Nguyen’s matching cover letter
Why this resume uses this section order
- State a focused starting point
The summary names SQL, Excel and Power BI, then points to the work below. It does not claim years of professional analytics experience. A junior title can express the target while the experience entry retains Sofia’s actual student office job title.
- Explain the query and the check
CTEs and ROW_NUMBER have a purpose: finding first and second completed orders. The tie-breaker and independent count check make that skill discussable. Excluding cancellations and separating incomplete cohorts also show why a technically valid query still needs an analytical definition.
- Give the second project a different job
This case adds Power Query exceptions, spreadsheet comparisons and a clear limitation. It does not repeat the SQL cohort report or pretend a course exercise changed a clinic’s attendance. Synthetic data is labeled in both project entries.
- Keep useful non-analyst experience
Source-sheet reconciliation, monthly totals and a handover are relevant analytical habits. Sofia describes the supervisor’s role in resolving discrepancies. The two bullets make this experience useful without pushing the more substantial projects down the page.
Resume bullet example: before and after
Before Analyzed customer orders with SQL and created a dashboard.
After Used SQL CTEs and ROW_NUMBER to identify each customer’s first and second completed orders; checked tied timestamps with order IDs and reconciled customer counts to a separate aggregate query.
The revision uses the same project facts to expose the method and verification. It gives the reader a specific SQL problem to discuss, without adding revenue gains or claiming that a portfolio dashboard was adopted by a business.
Example 2 of 2
Experienced data analyst resume: commercial reporting and decisions
Miles has worked in analysis since July 2019 and now holds a senior individual-contributor role. His strongest evidence is not a longer software list: it is the combination of metric agreement, technical checks and explanations for business reviewers. His earlier role shows the operational reporting foundation behind that responsibility.
Data analyst with seven years in commercial reporting and operations analysis. Turns sales and finance questions into agreed metric definitions, reconciled SQL outputs and Power BI reports. Explains changes in customer and product mix, documents limitations and works with business owners on the next question to investigate.
- Partner with sales and finance on monthly commercial reviews, translating questions about net sales, returns and customer mix into documented SQL analyses and decision briefs.
- Agreed a net-sales definition with finance that separates order-date sales from credit-date returns; documented the reconciliation bridge so reviewers could explain differences from the ledger.
- Investigated a regional margin change by separating product mix, discounting and freight allocations; presented account-level follow-up questions to sales leaders without attributing the change to a single cause.
- Maintain a Power BI sales model with order-line facts and customer, product and date dimensions; check join cardinality, unmatched keys and totals before releasing report changes.
- Compare repeat ordering across customer cohorts with equal follow-up periods; flag incomplete cohorts and record exclusions in the review brief before recommending accounts for sales follow-up.
- Review metric logic and SQL with two analysts, using sample records to test return handling and filters; maintain an issue log and coordinate source-field questions with the data engineering team.
- Produced weekly backorder reports in SQL Server and Excel, joining order lines with shipment records and aggregating shipments before the join to avoid duplicating ordered quantities.
- Built a Power Query exception workbook for missing promised dates and inconsistent item codes; reviewed unresolved records with purchasing before issuing the operations pack.
- Documented backlog aging bands and partial-shipment rules with the operations manager; walked planners through individual orders when report totals differed from their working lists.
Read Miles Turner’s matching cover letter
Why this resume uses this section order
- Connect technical work to the audience
Seven years is coherent with the dates at the November 2026 editorial date. Sales and finance questions give the summary a concrete setting. Miles does not claim to manage a department or make every commercial decision himself.
- Show what senior ownership means here
The net-sales definition and reconciliation bridge explain how Miles makes disagreement about numbers tractable. The margin investigation names competing explanations and produces follow-up questions. Neither bullet turns an analytical recommendation into an unsupported revenue outcome.
- Use an earlier role to show technical depth
Aggregating shipments before a join is a specific safeguard against duplicating ordered quantities. Exception handling and backlog definitions add operational context. These are different contributions from the recent commercial reviews rather than another list of dashboard duties.
- Keep the tool list tied to work
SQL Server appears in earlier reporting; Power BI modeling appears in the current role; Power Query appears in the exception workbook. Peer SQL review describes collaboration with two analysts, not a people-management role. Data engineering remains a partner team rather than a claimed infrastructure responsibility.
Resume bullet example: before and after
Before Worked with finance on sales reports and data accuracy.
After Agreed a net-sales definition with finance that separates order-date sales from credit-date returns; documented the reconciliation bridge so reviewers could explain differences from the ledger.
The revision identifies the definition, the timing difference and the handoff to reviewers. Those facts already belong to the example. It makes analytical judgment visible without inventing a time-saving percentage or asserting that the report and ledger must always show the same total.
What should a data analyst resume include?
Include contact details, relevant experience or projects, tools and methods, and education. Use a short summary when it clarifies your target. Recent graduates can put education and projects first; analysts with relevant employment should usually give that work the most space. Within each section, use recent-first dates and accurate role labels.
This guide focuses on reporting and business analysis. O*NET’s Business Intelligence Analysts profile describes querying repositories, producing reports, maintaining dashboards, testing outputs and supporting recommendations. Those tasks provide useful role context; job titles vary, so read the actual vacancy before deciding which evidence to emphasize.
A data engineering application needs evidence of the pipelines, platforms or operational data systems you built and maintained. A data science application may need statistical modeling, experimental design or model evaluation. Do not add either scope because you queried a warehouse. Miles models reporting data and raises source questions with engineers; he does not claim ownership of their platform.
For a career change, combine a focused project with the domain knowledge you actually used in your previous role. A purchasing specialist might explain stock exceptions; a support representative might analyze recurring request categories. Keep the former job title and distinguish later independent analysis from work completed for that employer.
For a focused opening, compare professional summary examples. Use the data analyst skills guide to select evidence you can explain.
Make a junior analyst portfolio useful beyond screenshots
Choose a project you can explain end to end. State the question, dataset origin, unit of analysis, date coverage and exclusions. Show your own SQL or transformation steps, a few checks and a readable result. Add a short interpretation: what the result suggests, what it cannot answer and what you would investigate next. One complete case can provide more useful evidence than several unexplained charts.
For Sofia’s repeat-purchase project, the case-study reader should be able to find the first-order cohort definition, handling of cancellations, tie-breaking rule and follow-up window. PostgreSQL’s documentation explains that window functions calculate across related rows while retaining row identity. Her example applies that capability to order sequencing; the resume need not become a SQL tutorial.
Use public data whose terms permit your use, or label synthetic data explicitly. Credit the dataset and disclose tutorial or team contributions. Do not suggest simulated observations describe actual customers. Link to a landing page with the question, output and methods; check access without signing in. A repository can hold supporting queries, but the reviewer should not need to run an environment to understand the case.
Write analyst bullets that connect method, checks and use
Draft from an evidence record: who asked what, which records you used, what you did, how you checked it and what you delivered. Select the most relevant detail for each bullet rather than forcing all five into every sentence. A paired set can explain the question in one bullet and verification in the next, as Sofia’s cohort entry does.
Show the failure you guarded against. A join can duplicate amounts when tables have different grains; missing keys can drop records; a changed date filter can alter a denominator. Miles’s shipment aggregation explains one concrete safeguard. Choose a check you actually performed, such as source reconciliation, duplicate-key review or sample-record tracing, instead of claiming ‘ensured 100% data accuracy.’
Distinguish a finding, a recommendation, an adopted action and a measured result. You may have recommended account follow-up without observing subsequent sales. If you have a permitted outcome measurement, explain its baseline, period and attribution. Otherwise describe the decision brief, agreed definition or validated report you delivered. These examples deliberately make no revenue, attendance or productivity gain claims.
For reporting models, explain the business grain as well as the product name. Microsoft’s Power BI guidance distinguishes facts used for summarization from dimensions used for filtering and grouping, and stresses consistent fact-table grain. Miles’s order-line model gives that context without claiming a warehouse redesign or a measured performance improvement.
Apply the resume bullet-writing method to your own responsibilities, checks and outcomes.
Choose technical skills and describe AI assistance honestly
Group tools separately from analytical practice. Select the SQL dialect, spreadsheet features and visualization platform you can use and explain. Then connect important methods to experience: cohort comparison needs a cohort definition; data quality needs checks; communication needs an audience and a deliverable. Python is useful in some vacancies, but a SQL and reporting resume does not become incomplete simply because the examples use other tools.
Include a certification only if you earned it, using the issuer’s actual title and your real status. Course attendance is not the same as a professional certification. Neither example needs an added credential to support its claims. Follow any explicit qualification requirements in the posting rather than presenting this guide as a universal eligibility rule.
If you used an AI assistant, describe the task and your verification. Microsoft documents Copilot for Power BI capabilities including DAX generation and warns that unprepared models can produce inaccurate responses. A defensible account explains how you checked suggested measures against sample records, filter behavior and agreed definitions. Name Copilot only when you actually used it; neither persona claims that experience. Keep restricted data within your employer’s approved tools and sharing rules.
Format the resume and protect confidential analysis
Use clear section headings, readable type and consistent dates. A focused page is a useful target for a junior application. An experienced analyst may need two pages when the additional work is relevant; first remove repeated reporting duties and tools without supporting examples. Do not squeeze a complex project into tiny type merely to retain a page count.
Keep charts in the portfolio and the resume’s main evidence in selectable text. Export the file type requested by the employer; when PDF is accepted, check reading order by copying text, open the links and review page breaks. Inspect fields populated after upload. Clear terminology and readable files help the application process, but no format or keyword score guarantees selection.
For private work, describe the business question, method, checks and permitted recommendation without exporting internal tables. Removing names alone may leave account or transaction records identifiable. Use an approved case description or a separate synthetic demonstration when necessary, and make clear that a reconstructed example is not the employer’s dataset. Public code and a portfolio are optional for an experienced analyst with confidential work.
Tailor an analyst resume to the business question
Suppose a commercial analyst posting asks for SQL, Power BI, finance reconciliation and recommendations for sales leaders. Miles can meet that intent by selecting existing evidence. The exercise below changes emphasis without adding a tool, achievement or responsibility.
- Separate requirements from the tool list
In the commercial posting, SQL and Power BI are methods. Finance reconciliation and sales recommendations describe the work. Match both: a dashboard bullet alone does not explain why its numbers can be trusted or what the audience should do with them.
- Move the closest evidence forward
Keep Miles’s finance definition and reconciliation bullet near the top. Place the margin investigation next, followed by the Power BI model. Retain his actual Senior Data Analyst title and dates; reorder bullets rather than relabeling him a finance manager.
- Revise the opening with existing facts
For this posting, Miles could write: ‘Commercial data analyst with seven years of reporting experience, using SQL and Power BI to reconcile sales measures and explain margin changes to sales and finance stakeholders.’ This selects existing facts; it does not add forecasting, Python or accounting qualifications.
- Handle gaps directly and check the final version
If the posting also requests Python, Miles should not add it to this resume. He can discuss a genuine learning project separately if one exists. Check that the opening, selected skills and first bullets tell the same story, and keep the distinction between recommendations and implemented business changes.
Choose supported capabilities from the data analyst skills guide and prioritize the work that matches this posting.
Common resume mistakes and how to fix them
Avoid ‘SQL, Python, R, Tableau, Power BI’ without evidence of use
Instead Select tools relevant to the posting and demonstrate the important ones in a query, report or analysis you can explain.
Avoid ‘Improved revenue’ after delivering a recommendation
Instead Name the finding and recommendation; add a business result only if it was measured and your contribution is clear.
Avoid A dashboard image with no question, definitions or checks
Instead Explain the audience, measure, data treatment and validation; use the portfolio for supporting visuals.
Avoid A course or synthetic-data project listed as client employment
Instead Label the project and dataset honestly, credit collaborators and show your own analytical contribution.
Avoid Calling all reporting work data engineering or data science
Instead Keep your actual title and describe the querying, modeling, analysis or infrastructure work you performed.
Build and review your resume
Build a resume around your experience
Data analyst resume FAQs
What should a data analyst resume with no experience include?
Use education, a focused skills section and substantial projects to show how you answer a question with data. Include related employment when it demonstrates checks, reporting or domain knowledge. Label projects accurately. Sofia’s structure works without an analyst internship; omit office experience if you have none and give the strongest project enough detail.
How should I describe SQL on a data analyst resume?
Name the dialect when relevant, then show a query purpose and a check. Sofia uses CTEs and ROW_NUMBER to sequence completed orders and reconciles customer counts. Miles aggregates shipments before joining to avoid duplicate quantities. You do not need to paste SQL into the resume; link to permitted supporting queries or explain them in an interview.
Does a data analyst resume need Python?
Follow the vacancy. If Python is required, show genuine analysis you performed with it. For roles centered on SQL, Excel and Power BI, demonstrate those tools well. Do not copy Python into your skills list because other analyst resumes include it. Related methods can support your application, but they do not establish experience with a tool you have not used.
What makes an experienced analyst resume different?
Show responsibility for definitions, analysis design, interpretation and review, alongside hands-on querying and reporting. Explain how you clarify questions with stakeholders and handle limitations. Miles’s finance reconciliation and margin investigation show that scope. Senior individual contributors can demonstrate it without claiming direct reports or final authority over business decisions.
Do all data analyst bullets need percentages?
No. A reliable definition, a reconciled report or a documented exception can be substantive evidence. Use numbers when they describe real scope or a measured result you can explain. Never attach an invented percentage to time saved, revenue or accuracy. Separate what your analysis found from what happened after a stakeholder acted.
Should I link a portfolio or GitHub account?
Include a relevant, accessible portfolio when it adds evidence, especially for a first role. Give each case a question, data origin, method, checks and interpretation. GitHub can hold supporting SQL, but it is optional. For confidential employment, use approved descriptions or an independently created synthetic demonstration rather than publishing company data.
Can I list AI tools on my analyst resume?
Yes, if you used them for relevant work and can explain your review. Name the tool, task and verification instead of listing ‘AI expertise.’ For a suggested DAX measure, explain how you tested it against known records and filter contexts. An AI-generated query or summary still needs your analytical judgment; do not add tools you have only seen demonstrated.
How do I make my data analyst resume ATS-friendly?
Use recognizable headings, actual job titles, clear dates and a text-based file the application accepts. Include the posting’s relevant terms naturally where your work supports them. Check that text copies in a sensible order and review imported application fields. Avoid turning the skills section into a list of every analytics keyword.
Can I open these resume examples in the builder?
The template action opens the Swiss design in AI ResumeGuru; it does not import Sofia’s or Miles’s example text. Add your own experience and project details, then check the wording, dates, links and relevance to the vacancy before exporting.
Resume checklist before you apply
- The opening identifies the analyst work you are targeting.
- Projects, courses and employment have accurate labels and dates.
- Each main analysis explains a question, method, check or useful deliverable.
- SQL dialects, spreadsheet features and BI tools match work you can discuss.
- Measures, populations and comparison periods are clear where they matter.
- Recommendations remain distinct from implemented actions and measured outcomes.
- Portfolio cases credit data sources and identify synthetic or tutorial material.
- No restricted data, unsupported metrics or unearned credentials appear.
- Links open, exported text is readable and the application follows employer instructions.