Press enter or click to view image in full size

Data Analyst Resume

Data Analyst Interview

Resume Writing

Data Analysis

Dataquest

How to Write a Data Analyst Resume When You’ve Never Had the Job

Dataquest

9 min read

·

Oct 22, 2026

--

Listen

Share

Writing a resume for a job you haven’t had yet is its own problem. You have to make coursework, portfolio projects, and a job nobody called analytics read like analyst experience — on one page, for someone who reads resumes all day.

The raw material is usually already there. Most people underestimate how much of their existing work counts, and undersell the parts that do.

This guide covers three things: how to structure the page when you have no analyst job title, a formula for turning any of that work into a bullet a hiring manager believes, and a complete annotated example.

Every line on your resume is a question you’ve agreed to answer. Read your draft the way a reviewer would, and stop at anything you couldn’t defend out loud.

Jump to a section:

• What Hiring Teams Are Actually Looking For in 2026
• How to Structure the Page
• The Bullet Formula — and why most entry-level bullets fail
• Which Skills to List
• Using Projects as Your Work Experience
• Getting Past the ATS Without Gaming It
• Common Mistakes to Cut Before You Send

What Hiring Teams Are Actually Looking For in 2026

Hiring teams are working through more applications than they used to, and a growing share of those applications look polished in the same way. That changes which parts of a resume carry weight.

A Robert Half survey of more than 2,000 US hiring managers found that 67% of HR leaders say reviewing AI-generated applications has slowed their hiring process, and approximately 42% now spend more time reviewing each application as a result. Polish alone no longer distinguishes anything because everyone’s resume has it. Named datasets, named tools, a link that opens, and numbers that survive a follow-up question are what give a reviewer something to hold onto.

Your resume passes two filters before anyone calls. The applicant tracking system parses it for keywords, then a person scans what survived. Structure and content have to satisfy both.

How to Structure the Page

Most resume advice assumes you have relevant job history to lead with. If you don’t yet, the standard section order works against you.

Put your projects above your work experience. A reviewer reading top to bottom should reach evidence of analytical work before they reach three years of retail or teaching, because the first thing they’re looking for is proof you can do the job.

Four rules hold regardless of experience level:

1. One page, in reverse-chronological order within each section.
2. A single column. Two-column layouts scramble when parsed.
3. Standard headings like “Work Experience” rather than anything creative.
4. PDF, unless the posting asks for a Word document.

Write a summary, not an objective. An objective states what you want, which the reviewer already knows. A summary states what you bring, which is the thing they’re trying to find out. A workable entry-level summary names your skills, your evidence, and your target role in two or three lines:

Career changer with hands-on SQL and Python experience from five portfolio projects, including a 40M-row transit ridership analysis. Five years of retail operations experience using data to drive staffing and inventory decisions. Seeking an entry-level data analyst role.

The Bullet Formula (and Why Most Entry-Level Bullets Fail)

This is where most entry-level resumes lose ground. People tend to write what they did rather than what happened because of what they did.

Every strong bullet follows the same four-part pattern: start with an action verb, describe the specific work, name the tool, and close with a measurable or scoped outcome.

Press enter or click to view image in full size

Your verb is the first thing a reviewer reads, so it should show what kind of work you did and that you did it. By function:

Analysis: analyzed, segmented, forecasted, modeled, investigated

Data handling: queried, cleaned, joined, validated, aggregated

Building: built, automated, developed, designed

Communication: visualized, reported, presented, documented

Avoid “assisted with,” “helped,” “worked on,” and “responsible for.” They describe proximity to work rather than work.

Turning a guided project into a bullet

Weak: Completed a SQL course project analyzing a sales database.

Strong: Queried a 1.2M-row retail sales database in PostgreSQL to identify the three product categories driving 60% of seasonal revenue variance, using window functions to compare year-over-year performance by region.

Every point is specific: row count, database, the actual question, the technique, and a finding. Nothing here was invented.

Turning a portfolio project into a bullet

Weak: Built a Power BI dashboard for a public dataset.

Strong: Built a five-page Power BI dashboard on NYC 311 service requests from 2019 to 2024 (18M records), reducing the time to answer “which complaint types spike by borough and season” from a manual spreadsheet process to a filter click.

Time saved is a legitimate metric even without a business owner. You’re comparing your solution against the manual alternative, which is a real comparison you can describe.

Turning a non-analyst job into a bullet

Weak: Retail store manager responsible for scheduling and inventory.

Strong: Rebuilt weekly staffing schedules for a 22-person team using Excel pivot tables and two years of hourly foot-traffic data, cutting overtime hours by approximately 15% across two quarters.

Most jobs produce data work that nobody called data work. Scheduling, inventory, grading, patient throughput, and route planning all qualify. The bullet doesn’t change what you did; it changes which part you describe.

The honest-metrics rule

Generic resume advice says to quantify everything, which pushes people toward inventing percentages. A fabricated number is the fastest way to lose an interview, because the interviewer will ask how you calculated it.

When no business KPI is attached to your work, three kinds of quantification stay honest:

1. Scope. Dataset size, number of records, number of tables joined, time period covered.
2. Time comparison. How long the manual version took against how long yours takes. You can measure this yourself.
3. Stated technical results. Model accuracy, query runtime improvement, percentage of null values resolved.

If a bullet has none of these available, write it without a number rather than with a fake one. A specific, unquantified bullet outperforms a quantified lie every time.

Which Skills to List

Your skills section has one job: match the posting without reading as a keyword dump. Grouping by category does most of that work.

Mirror the exact wording from the posting. Some parsers match on exact strings, so “Power BI” and “PowerBI” are not always treated as the same term.

Apply one filter to everything on the list: could you answer questions about it for ten minutes without stalling? If not, it doesn’t go on the resume. A tool you touched once in a lesson creates an interview question you can’t answer.

Be specific about what you mean by a tool. “Excel” covers everything from basic formulas to pivot tables, lookups, and Power Query. An analyst posting usually means the second half of that range, so name the parts you use.

Skip star ratings, percentage bars, and proficiency graphics. They don’t parse into anything an ATS can read, and a reviewer has no idea what your four-out-of-five in Python means.

Leave soft skills out of the skills section. “Communication” as a label proves nothing, while “presented weekly inventory findings to a 12-person store team” proves it inside a bullet where it belongs.

Place the section near the top when you’re entry-level. It front-loads the terms the parser is matching against. Tailor it per application by reordering the list so the posting’s top three tools appear first.

Using Projects as Your Work Experience

Projects are your work experience until you have work experience. Format them that way.

Give each project a title, the tools used, a date, and two bullets — exactly like a job entry. Include three to five projects, not eight. A long list dilutes your strongest work.

Example:

NYC Transit Ridership Analysis | March 2026
Python (pandas, matplotlib), PostgreSQL, Tableau
github.com/yourusername/nyc-transit

• Analyzed approximately 40M rows of MTA Subway Hourly Ridership data (2023 to 2024) to identify the six stations with the steepest decline in weekday morning ridership
• Built an interactive Tableau dashboard mapping ridership patterns by line, hour, and borough, published with documented methodology and data sources

Link the work in the project heading, not buried at the bottom. Whatever you link must load, and the repository needs a README explaining the question, the data source, and what you found.

A project earns its place on your resume when it answers a real question someone might ask, uses a messy dataset that required cleaning decisions you can explain, and reaches a conclusion that supports a decision.

Pick three to five projects that show range rather than repetition. One exploratory analysis, one focused on data cleaning, and one SQL-heavy project cover more ground than three dashboards built the same way.

Leave off lesson follow-alongs you didn’t modify, and leave off the Titanic and Iris datasets. Reviewers have seen thousands of both, and neither demonstrates a choice you made.

Dates matter more than people expect. A project from this year signals current skills, so if everything on your list is eighteen months old, build one more before you apply.

Getting Past the ATS Without Gaming It

Applicant tracking systems get blamed for a lot of rejections they didn’t cause. Formatting is one ATS problem you can control.

Use a single column and standard section headings. Keep your contact details in the body of the document rather than in your word processor’s header or footer region, since some parsers skip those. Avoid text boxes and graphics carrying information that appears nowhere in the text.

Name your resume file the way a recruiter would want to find it later. “Jordan-Reyes-Data-Analyst.pdf” survives a crowded downloads folder in a way that “resume-final-v4.pdf” does not.

If your official title is something like “Insights Specialist” and the work was genuinely an analyst role, write “Insights Specialist (Data Analyst)” so the match happens. Only do this where the two titles describe the same job.

Kishawna Peck, CEO of Woven (formerly Womxn in Data Science), makes the heading point directly:

“Don’t get creative with the headings. Have something like ‘work experience’ instead of ‘my journey.’”

Keyword mirroring works when the keywords sit inside real bullets. Pull the terms from the posting and use them where they describe something you did. A keyword block at the bottom reads as gaming to a human reviewer, which is a worse outcome than a missed match.

On applying: you don’t need to hit every requirement. Kishawna Peck suggests treating the first two or three requirements as the real must-haves and aiming for roughly 60% to 70% match overall. Waiting for 100% mostly means not applying.

Common Mistakes to Cut Before You Send

Most rejected entry-level resumes fail on the same repeat offenders. Run your draft against this list:

Test your portfolio link in a private browser window before every application. A dead link on a resume that promises verifiable work does more damage than no link at all.

Read your draft the way a reviewer would, and stop at anything you couldn’t defend out loud.

Where to Go From Here

Your resume can only present work you’ve actually done. If your bullets feel thin after applying the formula, that’s useful information, and the fix is another project rather than better wording.

Start with the structure, write your bullets using the action verb, tool, and outcome pattern, and make sure every claim points at something a reviewer can open and check. Once the resume starts producing calls, the questions on it are the ones you’ll be asked in interviews — so that’s the natural next thing to prepare for.

Which bullet on your current resume are you least sure you could defend in an interview? That’s usually the one worth rewriting first. Drop it in the responses — a second pair of eyes catches things you can’t see in your own draft.

This article is a condensed version of a full resume guide originally published on Dataquest. For the complete resource, including an annotated resume example, a skills section walkthrough, and a full data analyst learning roadmap, visit the original post on the Dataquest blog.