Entry-Level Data Analyst Resume Example

Updated · By Andrew Johnson, OneTwo Resume

In short: An entry-level data analyst resume has to show one thing: that you can take a messy table and return an answer somebody can act on. Without a prior analyst job, that proof comes from portfolio analyses on public datasets, coursework in statistics and databases, and any internship or campus role where you touched real numbers. Name SQL, Excel and one visualization tool inside those entries, and link the finished dashboards.

Other levels: Data Analyst resume example (all levels, with salary data) · Senior data analyst resume

What can stand in for experience on a junior data analyst resume?

Analyses that have a question, a dataset, a method and a finding. A hiring manager screening junior data analyst applicants is checking whether you have completed the whole cycle at least once — pulling data with a query, cleaning it, summarizing it and explaining the result to a person who does not write SQL. The sources below are listed from most to least persuasive.

Source of proofHow it should read on the page
Analytics or reporting internshipGoes under Experience. Say which report or dashboard you maintained, who used it, and one question you answered with it. "Refreshed weekly sales workbook for the regional team" is fine; add the query or formula work behind it.
Portfolio project on a public datasetTitle it with the question, not the dataset: "Which bike-share stations run empty by 8 a.m.?" Then the tools, the row count, the method and the finding, plus a link to the notebook or dashboard.
Statistics, database or econometrics courseworkOne line of course names under education, and a fuller entry only for a term project with real data — a regression study, a survey analysis, a database you designed.
Case or datathon competitionsGive the prompt, your part of the analysis and the placing. Judges are a stand-in for stakeholders, so mention that you presented the recommendation.
A non-analyst job where you worked with numbersPull out the spreadsheet you built for the shift schedule, the inventory count you reconciled, the survey you tallied. Those bullets are analyst bullets in disguise.
Certificates in SQL, Excel or a BI toolA supporting line, never the headline. Pair each certificate with a project that used the skill so it does not stand alone.

In what order should a first data analyst resume be laid out?

Lead with whatever contains your strongest analysis. For a current student or recent graduate that usually means education, then a Projects section, then work history. If you completed an analytics internship, place it right after education. Someone moving from another field — teaching, operations, customer support — should open with a short summary, then projects, then the earlier career condensed.

  1. Contact line with a link to a portfolio site, Tableau Public profile or GitHub folder that holds the finished analyses.
  2. Education with the degree, graduation date, and quantitative courses: statistics, regression, database systems, research methods.
  3. Internship or any role with a reporting component, written with tools and audiences named.
  4. Projects: two or three analyses, each framed as a question and ending with what you found.
  5. Skills split into querying, spreadsheets, visualization and statistics, so a recruiter sees the toolkit in a glance.
  6. Remaining jobs, one line apiece, keeping only bullets that involve counting, tracking or reporting.

How do you write a data analyst objective when you have not held the title yet?

State the tools you query and chart with, point to one completed analysis, and say which kind of data you want to work on — marketing, operations, product, healthcare. That third element matters because junior data analyst roles are hired by a business team, and a candidate who shows interest in the team's domain reads as easier to onboard than a generalist with the same SQL.

Example — Recent graduate, statistics major
Statistics graduate with a reporting internship at a regional retailer, where I rebuilt the weekly sell-through workbook in SQL and Excel and cut its refresh from half a day to 20 minutes. Portfolio includes a Tableau study of 1.1 million bike-share trips. Seeking a junior data analyst role on an operations or supply-chain team.
Example — Career changer from teaching
Former middle-school math teacher moving into analytics after completing a SQL and Tableau certificate and three portfolio projects. Spent six years tracking assessment results for 140 students a term and presenting them to parents and administrators; now applying the same habits to business data as an entry-level data analyst.
Example — Student, no internship
Economics senior with coursework in econometrics and database systems. Analyzed 300,000 public restaurant inspection records in Python and SQL to map repeat violations by neighborhood, and placed 2nd of 18 teams in a university datathon on hospital readmissions.

What skills do employers expect from an entry-level data analyst?

SQL that goes beyond SELECT star, spreadsheet fluency, one dashboard tool, and enough statistics to know when a difference is noise. Python or R is a plus for many junior data analyst postings, not a requirement. Employers also read for communication, since most of the job is explaining a number to someone who asked a vague question.

Querying

  • SQL
  • joins
  • window functions
  • CTEs
  • aggregations
  • PostgreSQL
  • BigQuery

Spreadsheets

  • Excel
  • pivot tables
  • XLOOKUP
  • Power Query
  • Google Sheets

Visualization

  • Tableau
  • Power BI
  • Looker Studio
  • dashboard design
  • chart selection

Statistics and scripting

  • descriptive statistics
  • hypothesis testing
  • linear regression
  • Python
  • pandas
  • R

Working habits

  • data cleaning
  • documentation
  • presenting findings
  • requirements gathering
  • data validation

Which bullet points work on a data analyst resume built from projects and internships?

Ones that follow the path of an analysis: the question, the data and tool, then the finding or the time saved. Row counts and dataset sizes are legitimate numbers when you have no revenue figure to cite. The six samples here come from internships, class projects and a campus job; treat them as patterns and substitute your own datasets and results.

  • Rebuilt a weekly sell-through report in SQL and Excel Power Query during a summer internship, replacing 14 manual copy-paste steps and shortening the refresh from four hours to 20 minutes.
  • Analyzed 1.1 million public bike-share trips in PostgreSQL and Tableau to identify 12 stations that ran empty before 8 a.m. on weekdays; published the dashboard and a one-page rebalancing recommendation.
  • Cleaned and merged 300,000 restaurant inspection records in pandas, resolving 9,000 duplicate business names, and mapped repeat violations by neighborhood for an econometrics term project.
  • Placed 2nd of 18 teams in a university datathon by modeling hospital readmission risk with logistic regression and presenting three intervention options to a panel of five judges.
  • Built a Google Sheets tracker for a campus tutoring center that logged 2,400 sessions a semester and showed demand by course and hour, which the director used to reschedule tutor shifts.
  • Designed and ran a 400-response student survey on dining-hall usage, tested differences between class years with chi-square tests in R, and summarized the results for the housing office.

Sample bullets for illustration — the figures are examples, not claims about a real person. Use your own numbers.

Why do entry-level data analyst resumes get passed over?

Usually because the page describes tools instead of findings. Listing "Tableau" proves nothing; a linked dashboard with a clear takeaway does. The other common problem is a portfolio made entirely of the same tutorial datasets every other applicant used, presented without a question of your own. The table pairs each frequent error with a repair.

What goes wrongHow to repair it
Projects described as "explored the dataset and created visualizations"Write the question you asked and the answer you got. If the analysis had no finding, it is not ready for the resume.
Only tutorial datasets such as passenger lists and flower measurementsPick a public dataset tied to the industry you are applying to — transit, retail, health inspections — and ask something a manager there would care about.
Dashboard links that require a login or no longer loadPublish to a public gallery, test the link in a private browser window, and add a screenshot to the repository as a fallback.
SQL listed with no sign of its depthMention joins, window functions or CTEs inside a bullet so the reader can gauge your level without a test.
Machine-learning buzzwords on an analyst applicationKeep modeling to what you actually did. Most junior analyst work is querying and reporting, and a resume aimed at data science reads as a flight risk.
Charts, skill meters or a two-column infographic layoutUse a plain single-column document. Save the design skill for the portfolio, where it can be judged properly.

What separates an entry-level data analyst resume from a mid-level or senior one?

Who asked the question, and what happened after you answered it. An entry-level data analyst resume shows self-directed analyses and tool fluency. A mid-level resume shows recurring reporting owned for a business team and analyses that changed a decision. A senior resume shows metric definitions, experimentation programs and analysts developed.

Entry-levelMid-levelSenior
Source of the questionsYou chose them, or a professor didA business team brings them to youYou decide which questions the team should be asking
Main evidencePortfolio projects, coursework, an internshipDashboards in daily use, ad hoc analyses tied to decisionsMetric frameworks, experiment programs, data-quality initiatives
Numbers in bulletsRows analyzed, hours saved, competition placingConversion, retention or cost moved by a recommendationRevenue or cost outcomes across a business unit, adoption of self-serve tools
Tool emphasisSQL, Excel, one BI toolSQL at depth, BI administration, some Python, dbt or similarModeling layers, experimentation platforms, governance; tools named sparingly
Page lengthOne pageOne pageUp to two pages
Portfolio linkEssentialHelpful if currentRarely needed; work is proprietary

Build your entry-level data analyst resume

Start from an ATS-readable layout and rewrite your own bullets in the editor.

Open the resume builder →

Entry-Level data analyst resume FAQ

How do I get a data analyst job with no experience on my resume?

Build the experience section out of analyses instead of jobs. Complete two or three projects on public data that each answer a business-style question, publish the dashboards, and write them up in the same verb-tool-finding shape as job bullets. Then mine your existing work history for anything involving spreadsheets, tracking or reporting and rewrite those duties as analyst tasks.

How long should an entry-level data analyst resume be?

A single page. Three projects, an education block, a grouped skills list and a condensed work history fit comfortably, and anything beyond that is usually course descriptions or a fourth project that repeats the first three. If space is tight, shorten the unrelated jobs first and keep the project findings intact.

Do I need Python on a junior data analyst resume?

Not always. Many junior postings center on SQL, Excel and a dashboard tool, and a candidate who is strong in those three will clear most screens. Add Python or R when you have used it on a real analysis — cleaning with pandas, a regression in R — and show it inside a project bullet so it is more than a keyword.

Which portfolio projects impress hiring managers for analyst roles?

Projects with a specific question, imperfect data and a recommendation at the end. Cleaning steps are worth mentioning because real data is dirty and managers know it. One project in the employer's domain is worth more than three generic ones, and a short written summary beside the dashboard shows you can communicate as well as chart.

Should I list online certificates on a data analyst resume?

Yes, in a short Certifications line, particularly if you lack a quantitative degree. They show initiative and give applicant tracking systems the tool names they scan for. They do not replace evidence, though, so place them below projects and make sure at least one project uses the skills the certificate covered.

More for data analysts: resume example · senior resume · cover letter example · interview questions

Entry-Level resumes for other roles: Software Engineer · Project Manager · Business Analyst · Product Manager · Financial Analyst

Guides: How to write a resume with no experience · Resume summary vs. objective · ATS resume keywords by industry