Ian Klosowicz
For entry-level data analyst roles, your resume should be one page. Two pages becomes reasonable once you have 5 or more years of relevant experience. Before that point, a second page almost always means there's content on the resume that shouldn't be there.
This question comes up constantly from people building their first analyst resume. They've got 3 jobs behind them, a couple of projects, some certifications, a skills list, and suddenly the resume is spilling onto page 2 and they're not sure whether to cut or to keep going.
The answer isn't about page count. It's about what earns its place on the page.
A recruiter spending 6 seconds on your resume doesn't have a better experience with 2 pages than with 1. They have a worse one. A second page doubles the surface area they need to cover in the same amount of time, and at the entry level, the additional content is almost never worth that cost.
The one-page rule isn't arbitrary. It exists because of what a longer resume signals at the early career stage. When someone with 2 years of non-analyst experience hands in a 2-page resume, the recruiter's first thought isn't "this person has a lot to offer." It's "this person doesn't know what matters." Editing is a skill. Knowing what to cut is a skill. A bloated resume is evidence that the candidate hasn't developed it yet.
For data analyst roles specifically, this matters more than in some other fields. Analysts are expected to distill large amounts of information into what's relevant. A resume that can't do that for itself is an early signal about how the candidate will handle actual analytical work.
One tight page beats two loose ones every time.
Two pages is appropriate when you genuinely can't fit your relevant experience into one without cutting things a recruiter would want to see. That threshold is roughly 5 years of relevant experience, meaning experience that connects to data work in some meaningful way.
Relevant experience includes:
If your 5+ years are all in unrelated fields and you're making a full career switch into data, you probably still want one page. The goal is to show relevance, and a second page of warehouse or retail job descriptions doesn't add relevance. It adds length.
The honest test: if you removed the weakest entry on page 2 and nothing important was lost, that page shouldn't exist.
Most entry-level resumes that run over a page do so for predictable reasons. Here's what to cut first.
Old jobs from more than 10 years ago that have no connection to analytics. A retail job from 2011 isn't strengthening your application. If there's something quantifiable and relevant from it, pull that 1 bullet into a more recent entry or drop it entirely.
Certifications beyond 2. A list of 8 Google certificates takes up space and signals that you spent months collecting credentials instead of building projects. Keep your 2 most relevant, cut the rest. No recruiter is counting them up and awarding points.
Coursework lists. "Relevant coursework: Statistics, Business Intelligence, Data Structures" is filler unless you're a recent grad with genuinely nothing else to fill the space. If you have projects, those replace coursework.
Bullet points that describe job duties rather than contributions. "Responsible for managing inventory" is a duty. "Maintained inventory accuracy at 99%+ across 4 product categories" is a contribution. The second one earns its place. The first doesn't. Cut duties, keep contributions.
The objective statement. "Seeking a data analyst role where I can leverage my skills to contribute to a data-driven organization" tells the recruiter nothing. Delete it. If you want a summary, write 2 tight sentences about your background and target role. If you can't do it in 2 sentences, skip it entirely.
References available upon request. Everyone knows. Nobody needs to read it. It's 4 words of wasted line.
Skills at the "familiar with" or "beginner" level. If you can't discuss a tool in an interview, it doesn't belong in the skills section. Listing it just to pad the section creates a risk when someone asks you about it in a screen.
Some people cut the wrong things in their rush to hit one page. Here's what stays regardless.
Every portfolio project you have, up to 3. Projects are your experience section when you don't have analyst titles on your resume. Cutting a project to save space is cutting the part of the resume that's doing the most work.
Quantified bullets. A bullet with a real number in it earns its line. If you're cutting bullets to reduce length, cut the qualitative ones first and keep the ones with metrics.
Your strongest tools. SQL, Excel, Tableau, Power BI. Whatever the posting specifically asked for. Those stay.
Contact information and LinkedIn. Obvious, but people in a cutting frenzy have removed things they shouldn't. Your name, email, city, and LinkedIn URL are not negotiable space.
I hear from a lot of people who cut their projects section down to 1 entry to save room for a long list of jobs. That's the wrong trade. A recruiter for an entry-level analyst role is more interested in 3 strong projects than in 6 jobs where you didn't use data. Cut the jobs down to their strongest bullets. Keep the projects.
Before you start cutting content, run through these formatting adjustments. Any one of them can recover a third of a page without removing a single bullet.
Margins. Standard Word margins are 1 inch. Drop them to 0.6 or 0.7 inches. That alone can recover 2 to 3 lines per page without affecting readability at all.
Font size. If you're at 12pt body text, dropping to 11pt or 10.5pt is barely noticeable to a reader and recovers significant space. Don't go below 10pt or it starts to feel cramped.
Line spacing. Single spacing with 4 to 6pt of space after paragraphs is tighter than 1.15 spacing and reads just as cleanly. Most resume templates have more whitespace than they need.
Section header size. Big bold section headers eat vertical space. Reducing them from 14pt to 12pt and keeping the bold is usually enough to distinguish them without the waste.
Bullet compression. Read every bullet and ask whether it could say the same thing in 1 fewer line. "Managed the weekly reporting process for the sales team, delivering summaries of KPIs to 4 stakeholders every Monday morning" can become "Delivered weekly KPI summaries to 4 sales stakeholders." Same information, half the lines.
Run these 5 passes before you cut any content. Most resumes hitting 1.1 or 1.2 pages drop to a clean single page without losing anything meaningful.
When I put together the resume module inside Analyst Hive, formatting was one of the pieces I had to build specific guidance around. The difference between a resume that parses cleanly, fits one page, and reads fast versus one that technically contains the same information but runs long and feels cluttered is almost entirely formatting discipline. The program walks through this at analysthive.io.
One-page resumes that are actually only half a page are their own issue. If your resume ends at the midpoint of the page, you haven't hit the content floor yet. A resume that's too short signals that you don't have enough to say, which at the entry level raises the same question as one that's too long: does this person understand what belongs here?
The target is a full single page. That means content runs to within an inch or so of the bottom. If you're well short of that, you haven't finished building the resume yet. Go back to your projects and make sure each one has 2 to 3 solid bullets. Go back to your work history and make sure you've pulled out every quantifiable contribution that exists. Add your education details if you haven't. Add certifications if they're relevant.
A resume that's genuinely thin on content has a resume problem, not a page count problem. The fix is more substance, not tighter margins.
Will a recruiter really reject me for a two-page resume if I'm entry-level?
Not automatically, but it creates friction. A recruiter who opens a 2-page entry-level resume has to decide whether to keep reading. Most will skim page 1 and make their call there, which means page 2 doesn't get read regardless. You've wasted the space and created the impression that you don't know how to edit. One tight page removes that friction entirely.
What if I have a lot of non-analyst work experience?
Summarize it rather than listing it fully. Keep your 2 most recent or most relevant non-analyst jobs, cut the bullets down to 2 per job maximum, and focus those bullets on anything quantifiable or adjacent to data work. The goal is to show you have a work history, not to document every duty from every job you've ever had.
Does the two-page rule apply to resumes submitted electronically?
Yes. The format of submission doesn't change the reading experience. A recruiter opening a PDF attachment still sees a second page as a second page. The same principle applies: one page until you've earned the second one with relevant experience volume.
My resume is 1.2 pages. Should I just let it run to 2?
No. A resume that ends a quarter of the way down page 2 is worse than both a clean single page and a full 2-page resume. It signals that you couldn't edit to one page and didn't have enough to justify two. Run the formatting adjustments in this post first. You can almost certainly compress that 1.2 to a tight single page without cutting content.
Is there a difference between what US and international employers expect?
Yes. The one-page preference is strongest in North American hiring. UK and Australian employers are generally comfortable with 2 pages even at the entry level. Continental European employers sometimes expect a CV format that's longer still. If you're applying internationally, research the norms for that specific market. The advice in this post is aimed at US and Canadian data analyst roles.
Should I submit a one-page resume even if the application says "CV"?
In the US, "resume" and "CV" are often used interchangeably in job postings, even though they're technically different documents. If a US employer asks for a CV, they usually mean a resume. Submit one page. If you're applying to an academic, medical, or research role where a true CV is expected, that's a different format entirely with different length norms.
If you're building your resume from scratch for a data analyst role, Analyst Hive walks through the full resume process as part of a structured 90-day program. The resume module covers format, length, content, ATS optimization, and tailoring. Join at skool.com/analysthive/about.
