How long should a resume be with 10+ years of experience?

Two pages. With ten or more years of experience, two pages is the right length, and the reason is not that software counts them — no applicant tracking system publishes a page limit, and none of the vendor documentation treats length as a parsing problem at all. Two pages is what a person can hold in their head while scrolling a list of forty candidates.

The harder question is what goes on that second page and what comes off the document entirely. That answer changes with the job — an Operations Director and a Senior Software Engineer with the same decade behind them should not hand in the same two pages — and it rests on two things you can actually check: what the ATS vendors document about parsing, and what the Bureau of Labor Statistics reports about how long people stay in jobs.

Does any applicant tracking system have a page limit?

No.

Greenhouse publishes a list of the things that cause what it calls an unsuccessful resume parse, and it is worth reading for what is absent. The one hard number on the page is file size: Greenhouse Recruiting "can't parse resumes larger than 2.5MB." Everything else is structural — a resume with spaces between the letters, graphics or photos or word art, a document uploaded as an image, complex resumes with tables, headers and footers, contact information in a header or a text box, a columned layout, sections without clear structure. Page count is not on the list. Neither is word count.

Workday's administrator guide is thinner but points the same way. It says that "resume parsing results can vary based on resume format and order of words" and recommends resumes without images or image-based styles. It also names two fields it will not populate from a resume at all — Languages and Skills — which you have to type into the form yourself. For organizations using HiredScore, the supported attachments are DOC, DOCX, PDF, RTF and TXT. Not a page limit anywhere.

What the two biggest ATS vendors actually constrain

Drawn from Greenhouse's parsing help and Workday's admin and HiredScore documentation. A dash means the vendor does not state it. Both pages are listed in sources.

	Greenhouse	Workday
Stated page limit	None	None
Stated word limit	None	None
File size limit	2.5MB	Not stated
Accepted file types	Not stated on this page	DOC, DOCX, PDF, RTF, TXT (HiredScore)
Named parsing risk	Columned layouts, tables, headers and footers, images	Images or image-based styles; format and word order
Computed from your dates	Not stated	Employment gaps and time in position
Fields never auto-filled	Not stated	Languages, Skills

So a Senior Software Engineer with twelve years across three employers is not risking anything mechanical by running to a second page. The risk sits somewhere else, and it is not a machine.

Why two and not three

Because ten years is fewer jobs than most people think, and a third page usually means the same career told twice.

How long people stay, January 2024

4.8 yearsMedian tenure, management, professional and related occupations

3.9 yearsMedian tenure, all wage and salary workers

22%Wage and salary workers with 12 months or less at their current employer

28% / 24%Men / women with 10 years or more at their current employer

BLS put median tenure in management, professional and related occupations at 4.8 years as of January 2024, against 3.9 years for all wage and salary workers. Do the arithmetic on your own history: a decade at that rate is two employers, perhaps three, plus whatever promotions happened inside them. Two pages is not a squeeze for that. It is roomy.

The same release shows why readers of this post split into two very different shapes. BLS does not publish a single long-tenure figure for everyone, but it does publish the split: 28 percent of men and 24 percent of women had been with their current employer ten years or more, while 22 percent of all wage and salary workers had been in the job twelve months or less. If you are in the long-tenure group, your problem is that one employer's worth of history reads as one job unless you break out the titles. If you are in the other, your problem is the opposite: eight entries, and no signal about which three matter.

If you have ten years of experience, a one-page resume is a mistake. The one-page rule exists because a new graduate has one page of material, and it got repeated until it sounded like a standard. O*NET classifies both General and Operations Managers and Software Developers as Job Zone Four, "considerable preparation needed," where "a considerable amount of work-related skill, knowledge, or experience is needed" and people "usually need several years of work-related experience, on-the-job training, and/or vocational training." An employer hiring at that level is buying the years. Compressing them onto one page deletes the evidence for the thing being bought — and the candidate who does it reads as more junior than the one who did not, on identical experience.

What belongs where

Page one is the last five or six years and everything a recruiter will use to decide whether to keep reading. Page two is context. Nothing is on page three.

The line that does the most work here is the last one. Most three-page resumes are not long because the person did more; they are long because the 2013 role still has five bullets under it, and those bullets are describing a smaller version of what page one already claims.

One warning about compressing, because it is the step where people quietly break the parse. Greenhouse's list of failure causes includes abbreviated job titles — it gives "Sr. Account Exec" as the example — and company names written without an identifying word such as Inc., Co., LTD or LLC. Squeezing a 2011 role onto one line is exactly the moment you are tempted to write "Sr. Ops Mgr" and a bare company name instead of "Senior Operations Manager" and the employer's full registered name with its Inc. or LLC still attached. The compressed version saves a dozen characters and costs you a parsed employer and a parsed title. Write the line short by dropping the bullets, never by abbreviating the title or the company.

And if the reason you are cutting pages is file size, cutting pages will not fix it. A resume over Greenhouse's 2.5MB ceiling is almost never long — it is carrying an embedded photo, a logo, or a chart pasted in at print resolution. Delete the image and the two-page version comes in under a tenth of the limit.

Does page two need your name at the top of it?

In the body text, yes. In a running header, no — and that is the one piece of standard two-page advice that the vendor documentation contradicts outright.

The convention comes from paper. If you hand a recruiter two loose sheets, a running header carrying your name and "page 2 of 2" is what stops the stack getting shuffled on the way to the interview room. That is a real problem, and the header is a good answer to it, which is why the advice has outlived the paper. Greenhouse's parsing page names the same construct twice: complex resumes with tables, headers and footers, and separately, contact information placed in a header, footer or text box. Workday's guidance points the same way when it says parsing results "can vary based on resume format and order of words," because a repeated header is a block of words the extractor has to place somewhere in the sequence, and the place it picks is not necessarily where you put it.

Nobody shuffles a stack anymore. The file arrives as one document, stays one document, and gets read on a screen that scrolls. So take the name and the page number out of the header region entirely. If you want your name visible when a recruiter lands mid-document — a reasonable thing to want — type it as the first line of body text on page two, at body size, on the same left margin as everything else. It parses as text because it is text.

Two related habits worth dropping while you are in there. Do not split a two-page resume into two files; almost every application form takes one resume attachment, and the second upload either overwrites the first or lands in a field nobody opens. And do not put your phone number in the footer to save a line at the top — that is the exact failure Greenhouse names, and it costs you the contact fields rather than the line.

Here is what the recruiter sees

An Operations Director, fourteen years, three employers, everything given equal weight across three pages. What lands in the candidate list:

Current title: Operations Director Most recent evidence visible without scrolling: "Supervised shift scheduling for 40 staff" (2012)

The same person, two pages, oldest three roles compressed to a dated line each:

Current title: Operations Director Most recent evidence visible without scrolling: "Cut fulfilment cost per unit 18% across four sites"

Same career. The second version simply put the strongest sentence where the eye lands first.

If the whole decade is at one employer

Then your page-length problem is inverted, and the fix is not to add material but to break one block into several. BLS put median tenure for workers aged 55 to 64 at 9.6 years in January 2024, against 2.7 years for those aged 25 to 34 — long single-employer histories are common, and they parse badly when written as one entry with a ten-year date range.

Take an Operations Director who joined as a Shift Supervisor in 2015 and moved up twice. Written as one block, the resume shows a single title held for eleven years, and any system computing time in position gets one number that flatters nothing. Written as one company with three dated sub-entries — Operations Director 2022–present, Operations Manager 2018–2022, Shift Supervisor 2015–2018 — the same eleven years show a promotion rate, which is the actual argument for the next job. It also fills page one honestly, because the top entry now covers four years rather than eleven, and four years of results is what a recruiter is scanning for.

The 15-year cutoff is a convention, and nobody published it

You have read that a resume should go back fifteen years, or ten, or three roles. No public source says this. Not BLS, not O*NET, not Greenhouse's parsing documentation, not Workday's. It is an industry habit that hardened into a rule, and the honest version is that nobody has published a number for how far back a recruiter reads or what a fourth page costs you.

What the documentation does tell you is that your dates are inputs, not decoration. Workday's HiredScore "calculates employment gaps and time in position" from what you list, and presents parsed resumes "in the same format" so recruiters can compare candidates consistently. Delete a role to save space and you have not hidden it — you have created a gap in a field something is computing. Compress it to one dated line instead and the arithmetic stays intact while the page gets shorter.

This is also where the limits of the data are worth naming. None of these sources tell you what a recruiter prefers, how long they look, or whether two pages beats one in any measurable way. They tell you what breaks a parse and what gets calculated from your dates. The page-count answer is a judgement built on top of that, and I would rather say so than dress a convention up as a finding.

Two ten-year careers, two different page twos

Both example titles sit in the same job zone, and the resumes still should not look alike.

Wages and employment are BLS Occupational Outlook Handbook figures for May 2025 with 2025–35 projections; the education percentages are O*NET's own survey and a separate series, so read them side by side, not as one number.

That education row changes the layout. For a Senior Software Engineer, where 85 percent of respondents report a bachelor's degree as the requirement, the degree is table stakes: one line, page two, no coursework. For an Operations Director, where 29 percent report a high school diploma and 22 percent some college with no degree, the degree is not the qualifying credential — the years of supervisory scope are, which BLS lists as the entry requirement for the occupation. That candidate should spend the space on span of control, headcount and P&L, and treat education as a footer.

What to do this week

Print the resume you are sending right now and put the pages side by side on a table. If page two is more than half empty, cut to one page and move the survivors up; if there is a page three, every role older than ten years becomes a single dated line before you touch anything else.

Then find the oldest job on the document that still has bullets under it and delete them, keeping the title, company and dates. Read what is left. If the story of your decade still holds — and it almost always does — the bullets were repeating page one.

Last, check that your contact details are in the body text and not in the document header, because that is the one item on this page that Greenhouse names outright as a cause of a failed parse. Then stop redesigning and send it. If you would rather not retype the same experience section into every form afterwards, HeroApply fills the application from the resume you just finished.