HireDraftAI

HireDraftAI Blog

How Far Back Should a Resume Go: 10, 15, or 20+ Years?

Decide how far back a resume should go using relevance, career stage, evidence value, chronology, and explicit employer requirements—not a rigid year cutoff.

Resume length · Published October 28, 2026

Keep as much history as the target decision needs. Detail recent relevant work, compress older context, and preserve required records separately.

A long career timeline fades from detailed recent roles into compressed earlier experience
Editorial concept: evidence resolution changes with relevance and recency rather than one arbitrary cutoff.
A long career timeline fades from detailed recent roles into compressed earlier experience
Editorial concept: evidence resolution changes with relevance and recency rather than one arbitrary cutoff.

Many experienced candidates can focus detailed bullets on roughly the last 10–15 years, but that is an editorial starting point—not a rule. Go farther back when older work proves essential domain knowledge, a required credential, major progression, or the only relevant experience. Compress or omit older roles when they add little to the target decision. Follow any application that requests a complete history.

The question is not “How old is this job?” alone. Ask what evidence it contributes, whether recent work supersedes it, and whether removing it makes the career story misleading or incomplete.

Use three evidence layers

Assign each role to Detail, Compress, or Archive.

| Layer | Treatment | Use when | |---|---|---| | Detail | Full title, employer, dates, 2–5 focused bullets | Recent or decisive target evidence | | Compress | Title/employer/dates and perhaps one line | Context or progression matters, detail does not | | Archive | Keep in private master; omit from resume | No material relevance or chronology need |

Archive does not mean erase from your records. Government, regulated, security, and background forms may require complete history. A resume and a disclosure form perform different jobs.

Score evidence value rather than age alone

Keep older experience when it demonstrates a rare industry cycle, required technology or credential, high-stakes scope, geographic market, or origin of a specialization. Remove detail when later roles show the same capability at greater scale. A 17-year-old clinical license foundation may matter; a 17-year-old generic software duty may not.

Consider career stage. A candidate with six years of work should not arbitrarily discard the first year because a template says five. A 30-year executive should not spend half a page on an entry-level task unless it uniquely matters.

Use the live job and occupation profile to define relevance. Do not chase a formula intended for another field.

Worked example: a 24-year operations career

Helena's career began in warehouse supervision, moved through regional logistics, and now includes ten years of network operations leadership. She targets a role requiring automation, multi-site planning, and unionized-site experience.

Her last 12 years receive full detail. Two earlier regional roles are compressed into an “Earlier Operations Experience” block because they establish progression. A 2004 warehouse-supervisor role receives one line because it is Helena's only direct union-site experience and the target names that context. Routine duties disappear.

The resume reaches two focused pages. Helena keeps a complete private timeline for forms and checks. She did not cut at year 15; she changed evidence resolution according to value.

Avoid age-hiding tricks and date confusion

Do not remove graduation dates or early roles solely to guarantee that no one infers age; such decisions are personal and context-dependent, and discrimination cannot be solved by a formatting trick. Do not alter dates, combine employers, or make older experience look recent.

  • Use consistent month-year or year formats based on context.
  • Keep official titles or truthful descriptors.
  • Preserve career progression when it supports level.
  • Remove outdated contact details and technology inventories.
  • Avoid “20+ years” when target value comes from a narrower specialty.
  • Maintain a full master record.

The objective is relevance and clarity, not disguising the timeline.

Let older evidence earn its space repeatedly

For each application, ask what would be lost if an older entry vanished. If the answer is “nothing the reader needs,” compress it. If it closes a hard proof gap, retain a concise line or bullet. If the role requires a full CV, federal resume, publications, or project history, follow those conventions instead.

Review the archive annually. A recent project may replace old evidence; a new target may reactivate it. This is why a fact bank matters: omitted does not mean forgotten.

A resume is a high-resolution view of the evidence most relevant now, supported by lower-resolution career context. That architecture stays useful no matter how many years the career grows.

Sources and scope

History requirements differ across sectors and application types. Suggested time ranges are editorial heuristics, not employer rules; complete-history requests must be answered fully and accurately. Editorial review: September 6, 2026.

Take the next useful step

Place every role in Detail, Compress, or Archive for one target job, then restore any older evidence that uniquely closes a real requirement gap.

Questions readers usually ask

Is 15 years the maximum for a resume?

No. It is a common focus range for some experienced candidates, but older relevant evidence can belong.

Can I omit my first jobs?

Often from a selective resume when they add little, while keeping a complete private history and answering required forms fully.

Should I remove graduation dates?

It depends on relevance, conventions, and application requirements. Do not omit dates that are requested or needed to represent an in-progress qualification accurately.

How do I compress earlier experience?

Use a short section with title, employer, dates, and at most one relevance line instead of full duty lists.