How far back should a resume go

The short answer: most resumes should go back 10 to 15 years

If you are asking how far back should a resume go, the most useful default is usually 10 to 15 years of experience in detail. That range gives hiring teams enough recent, relevant history to understand your level without crowding the page with older roles that no longer help your case.

That does not mean everything older than 15 years must disappear. It means older experience needs to earn its space. If a role still supports the job you want now, keep it in a compressed form. If it does not, trimming it usually makes the resume stronger.

• Show the last 10 to 15 years in the most detail.
• Compress older but still relevant experience into shorter entries.
• Remove older jobs that no longer support the target role.
• Do not let early-career or student work dominate the first page once you have stronger recent proof.

Why going too far back can hurt the resume

Most resumes do not get weaker because an ATS rejects old jobs. They get weaker because older, lower-value history pushes your best evidence further down the page. Recruiters are usually trying to understand your current fit, recent scope, and likely next step. A long timeline can make that harder instead of easier.

Older roles can also introduce stale tools, outdated responsibilities, or a career story that feels less focused than it really is. The issue is not age itself. The issue is signal quality.

• Your strongest recent achievements get buried under older work.
• Low-relevance jobs take space from better evidence near the top of the page.
• Old tools and workflows can make your current profile feel less targeted.
• Extra history often pushes the resume to a second page without adding much value.

When older experience still belongs on the page

Older experience is worth keeping when it makes you more credible for the role you want now. That is especially true if it shows domain depth, a rare specialization, or a pattern of progression that newer roles alone do not fully explain.

For example, someone applying to healthcare operations, cybersecurity, accounting, government contracting, or compliance roles may benefit from older history if it proves long-term experience in that environment. The same is true when an early role contains a major achievement that still anchors your expertise.

• Keep older roles if they show direct industry or domain relevance.
• Keep them if they explain a leadership path, promotion arc, or technical specialization.
• Keep them if the employer or achievement still adds meaningful credibility.
• Keep them if removing them would make your experience level look artificially shallow.

When to cut, compress, or remove older jobs

If an older role does not help the reader believe you fit the next job, it should probably shrink or go. This is where many resumes become too historical. They read like a full career archive instead of a hiring document.

A simple rule works well: detailed bullets are for recent and relevant work. One-line entries are for older supporting history. Removed entries are for low-value roles that no longer change the hiring decision.

• Cut older jobs that are unrelated to your target role and add no useful transfer story.
• Compress roles that repeat skills already proven better in newer jobs.
• Remove early part-time, campus, or entry-level jobs once you have stronger professional experience.
• Trim anything that forces extra page length without improving fit, credibility, or context.

How to handle a long career without hiding important experience

If you have 15, 20, or 25 years of experience, the answer is not to give every role equal treatment. The better approach is to show recent years in detail, mid-career roles more selectively, and older roles in a compact supporting format.

You can also group older roles under an additional experience section if the exact bullet detail is no longer necessary. That keeps the page honest about your background while protecting the space needed for the work that matters most now.

• Use full bullet detail for recent roles that still define your level.
• Reduce older roles to one or two bullets when they are supportive but no longer central.
• Use an Additional Experience section for older roles that still deserve mention.
• If you held multiple titles at one company, emphasize the latest and strongest level instead of over-detailing every earlier step.

What career changers and returners should do differently

Career changers do not always follow the standard 10-to-15-year rule cleanly. Sometimes the most relevant experience for the next role is older than the current job history. In that case, it can make sense to keep an older role visible if it does more to prove fit than a recent but unrelated job.

The same applies if you are re-entering the workforce after time away. The goal is not to pretend the timeline is something else. The goal is to surface the experience that best supports the role you want now and explain the rest clearly and briefly.

• Keep older roles if they are the strongest proof for the new direction.
• Add recent coursework, certifications, freelance work, or projects if they help bridge the gap.
• Do not revive every old job just to fill space.
• Use the summary to explain the transition so the timeline feels intentional instead of confusing.

Examples: too much history vs the tighter version

These examples show how trimming older work can improve clarity without hiding real experience. The tighter version still tells the truth. It just makes the current fit easier to see.

• Before: Six separate entries from 2006 to 2015 with long bullets for help desk, desktop support, junior sysadmin, and operations support roles. After: Full detail for the last two infrastructure roles, plus one line for Additional early IT support and systems administration experience from 2006 to 2015.
• Before: A marketing resume still gives equal space to a 2010 retail supervisor role. After: Retail role removed, and the first page now focuses on recent lifecycle, campaign, and analytics work.
• Before: A project manager resume lists every coordinator title from the start of the career. After: The resume highlights current program ownership and summarizes earlier coordination roles in one compact progression line.

A final rule that works for most people

The best answer to how far back a resume should go is this: far enough to prove you, not so far that you distract from yourself. A resume is not meant to preserve every step of your work history. It is meant to help an employer understand why your background fits this opening.

If older experience strengthens that case, keep it. If it mainly adds length, noise, or outdated context, cut it back. The clearer your recent story becomes, the better the resume usually performs.

• Can a recruiter understand your current level in the first few seconds?
• Are older roles still doing useful work for the target job?
• Does each older entry add credibility, context, or relevant proof?
• Did trimming older history make the strongest recent experience easier to see?