How Far Back Should a Resume Go?

The number most recruiters agree on is around 10 years of detailed work history, stretching to 15 when the older experience clearly maps to the job. This isn't a hard law. It's a default that keeps your resume focused on what a hiring manager can actually use.

Think of your resume as expensive real estate. A recruiter spends seconds on the first pass. Every line competes for attention. A job from 2008 that has nothing to do with the role you want is a line that could have shown a recent win instead.

The rule flexes in both directions. A senior executive with a long, relevant track record can justify more. A recent graduate might cover just two or three years plus school. Match the depth to your career, not to a fixed year count.

Skills, tools, and job titles from more than ten years ago are often stale. A marketer's 2011 experience predates most of the platforms and analytics tools that define the job now. An engineer's decade-old stack may be deprecated. Recruiters know this, so they weight recent work far more heavily.

There's a keyword side to this too. Applicant tracking systems (ATS) and recruiters scan for the specific terms in the current job posting. Those terms come from how the role is done today. The further back a job sits, the less its language overlaps with what employers search for now. We see this in the job descriptions our tailoring engine analyzes: the vocabulary of a role shifts steadily over time, and postings today reward the keywords that describe today's version of the work.

So an old job rarely earns its keep. It adds length, it dilutes your strongest material, and its terminology often no longer matches what filters look for. That's the practical case for cutting it, spelled out in how ATS keyword matching actually works.

Your career stage decides the right length more than any single rule. Here's how it breaks down.

Keep it to the last two to four years and lean on internships, part-time work, and coursework projects. Your education stays near the top while you have little work history. See the best resume section order for your experience level for where to place school versus work.

Ten to fifteen years is your window. Give the last decade full bullets with metrics. If a role from year 12 or 13 still matters, keep it short. If it doesn't, cut it without guilt.

Show your most recent leadership in full. For earlier roles, a compressed "Earlier Experience" section with title, company, and years is enough. You prove range without dragging the resume to four pages or exposing a 25-year timeline.

Recency matters less here than relevance. An older job that supports your new direction earns a spot even if it's outside the usual window. Keep it brief and tie it to the target role. Our career change resume guide walks through how to reframe older experience for a new field.

Don't delete valuable history. Compress it. When a job older than 15 years genuinely strengthens your case, keep it without letting it eat space.

The goal is to keep the signal and drop the clutter. A single line proving you once led a major initiative can matter; three stale bullets about it will not.

Cut a job when it no longer helps you get the specific interview you want. Concretely, remove it if it's older than 15 years and unrelated, if it used tools or methods that are now obsolete, or if it pushes your resume past two pages without adding anything.

Also cut short, unrelated stints, teen jobs, and roles that create confusing gaps or overlaps you'd rather not explain. One quiet exception: if a role is directly on-point for the job, keep it even when it's old. Relevance beats the calendar every time.

Age bias is real, and a long timeline hands screeners an easy way to guess your age before they read a single achievement. Trimming to 10-15 years keeps the focus on your work, not your birth year.

Two small moves reduce the signal further. Drop graduation dates from your education section when they're decades old. And cut the very oldest jobs so your first listed role doesn't broadcast a 30-year career start. You're not hiding experience. You're leading with what's relevant and current.

This also plays well with ATS parsing. A tighter, keyword-current resume matches today's postings better than one padded with roles from a different era. If you want the mechanics, read how to beat the ATS and how to make your resume ATS-friendly.

Deciding how far back to go isn't one answer, it's a different answer for every job you apply to. A role that values your older experience should surface it; a role that doesn't should never see it. Doing that by hand for every application is slow, which is why people either send one generic resume or apply too late.

Roleframe fixes that. You keep one base resume per target role, then spin off a tailored version for each posting. Multiple AI agents read the job, match its keywords against your history, and reorder or trim your experience so the relevant roles lead and stale ones step back, all with your approval before anything saves. You export a clean PDF where the file matches the editor exactly.