How Far Back Should Your Resume Go? (2026 Data-Backed)

The ten-to-fifteen-year rule is real, but it’s an output, not an input. It’s the rough overlap of three forces that all push in the same direction: how long people actually stay at jobs, how recruiters decode age from a resume, and how ATS keyword scoring weighs older roles versus recent ones. When those three forces align — which is most of the time, for most candidates — the rule holds. When they don’t, you need a different answer.

This guide unpacks the rule against the data, gives you an industry-by-industry decision matrix, and shows what compressing a twenty-five-year career actually looks like on the page. The aim is to replace “ten to fifteen years” with a defensible decision you can make for your specific situation.

The rule isn’t arbitrary. It’s the rough intersection of three independent forces that all happen to converge around the same decade-and-a-half window. Understanding which force matters most in your situation tells you whether the rule fits your case or whether you need a different answer.

The first force sets the floor: with median tenure under four years for younger workers, fifteen years still gives you four or five roles — plenty to show trajectory. The second force sets the ceiling: every additional year past fifteen adds age signal without adding evidence of recent capability. The third force explains why simply adding more pages doesn’t solve the problem: it actively hurts the keyword math the parser uses to rank you.

When all three forces point the same direction — which is true for most corporate roles — the ten-to-fifteen-year window is correct. When one of them flips, the answer flips with it. A federal hiring portal cares about complete employment history regardless of age signaling. An academic search committee weighs depth of record over recency. A tech recruiter scoring against last-decade tooling cares less about your two-decade career and more about whether you’ve shipped anything modern in the last three years. The rule bends in those cases — predictably, by industry.

The same candidate, the same career, the same résumé content can be too long for one industry and too short for another. The two cards below split the world into the two camps that matter — the standard rule applies to one, the full-history rule applies to the other — and lay out who falls where.

One asymmetry matters: when in doubt, default to the standard rule. Corporate-style résumés can be expanded easily if a recruiter asks for more depth; full-history résumés submitted in error to a corporate role read as too long, dated, or unfocused, and you don’t usually get a second look. The standard rule is the safer mistake to make.

The rule isn’t “cut everything before 2010.” It’s “make sure nothing on the page is hurting the case for the role you want next.”

Cutting older roles entirely creates two problems. The first is the gap: if your detailed work history starts in 2014 but your career started in 1998, the missing sixteen years either looks like an unexplained absence or invites the assumption that you padded your tenure. The second is signal loss: name-brand early employers, formative roles, or relevant industry exposure may matter even when the responsibilities don’t. The fix is to compress, not delete. There are three formats that work, and the right one depends on what the older roles are doing for the story.

Whichever format you pick, the rule is consistency: don’t mix them in the same résumé. A résumé with “Earlier Experience (2003–2014)” at the bottom should not also have a separate “Selected Earlier Roles” block — the two formats answer different questions and stacking them looks like padding. Pick the one that serves the case for the role you’re applying to and use it cleanly.

Below is a working example. Beatriz Stenmark is fictional but the situation is real: a senior marketing director with twenty-five years of experience applying to a Senior Director role at a mid-cap company. The “before” version lists everything in equal detail. The “after” version applies the standard rule and the one-line summary technique. Both are honest. Only one fits on two pages.

WORK EXPERIENCE25 years listed in equal detail; recent roles compete with 1999–2003 entries for spaceSenior Marketing Director · Cardinal Brook Software · 2019–Present
- Five bullets, recent role, full detail

Director of Marketing · Northbridge Analytics · 2014–2019
- Five bullets, recent role, full detail

Senior Marketing Manager · Helio Pay Systems · 2010–2014
- Four bullets, mid-career role

Marketing Manager · Highland Mercer · 2008–2010
- Four bullets

Marketing Manager · Ardent Signals · 2005–2008
- Four bullets

Senior Marketing Coordinator · Foster & Reed · 2003–2005
- Three bullets

Marketing Coordinator · Foster & Reed · 2001–2003
- Three bullets

Marketing Assistant · Pellingham Industries · 1999–2001
- Two bullets, first job out of college

WORK EXPERIENCELast 12 years detailed; pre-2014 compressed into one labeled blockSenior Marketing Director · Cardinal Brook Software · 2019–Present
- Led marketing for $180M ARR B2B SaaS company; rebuilt demand-gen function and lifted pipeline from $42M to $98M annually
- Built ABM program with 8-person team across enterprise and mid-market segments; lifted enterprise win rate from 22% to 31%
- Owned $14M annual marketing budget; reduced CAC by 28% over three years through channel-mix optimization
- Hired and developed 4 directors; promoted 2 internally to senior leadership

Director of Marketing · Northbridge Analytics · 2014–2019
- Built marketing function from 2 to 14 people during Series B through Series D growth
- Launched product marketing program supporting four product launches; aggregate $34M ARR contribution
- Owned brand refresh and rebrand following $90M Series D; led agency selection and rollout

Senior Marketing Manager · Helio Pay Systems · 2010–2014
- Owned demand generation for fintech vertical at $40M ARR; lifted SQL volume 4x in 18 months

EARLIER EXPERIENCE (1999–2010): Marketing Manager → Marketing Coordinator at Highland Mercer, Ardent Signals, Foster & Reed, and Pellingham Industries. Brand campaigns, channel marketing, and team leadership across B2B and consumer goods.

The “after” version cuts six explicit role entries down to one summary line — without losing the fact that those years happened, and without hiding company names that may matter to a reader who recognizes them. The recent twelve years now have the room they need to make the case for the next role. Both versions cover the same career. Only one fits the rule.

The standard rule is the right answer in the majority of corporate situations. But a small number of cases justify going further back in detail. Each one has a clean test: if the older role doesn’t pass it, compress the role anyway.

The honest framing for these cases is “an older role earns its place when it does work the recent record can’t do.” If the older role just adds tenure without adding evidence, it’s costing you space and signaling age without paying for either. Cut it.

The decision to compress is usually right. The execution is where it goes wrong. These are the six failure modes that produce a résumé that’s both too long and unconvincing — the worst possible outcome of a truncation pass.

The ten-to-fifteen-year rule is right for most candidates because tenure data, age signaling, and ATS keyword density all push in the same direction within that window. When one of those forces points elsewhere — a federal application that requires complete history, an academic CV that rewards depth, an early-career role that proves a specialization the recent record doesn’t — the rule bends. The skill is recognizing which case you’re in.

If the question is “should I keep my 2003 marketing coordinator job in the same detail as my 2024 director role,” the answer is no — compress it into an “Earlier Experience” line that closes the gap without spending the space. If the question is “should I drop my 1999 graduation year from the degree section,” the answer is also probably no longer no — drop it. The résumé you submit should make the case for the role you want next, not document everything that came before.