← All articles

COVERPILOT FIELD NOTES · JULY 20, 2026 · 6 MIN READ

How far back should a resume go?

The rule of thumb is 10 to 15 years. But the rule of thumb is not the real answer, because a recruiter doesn't reject a job for being old — they lose interest in one for being irrelevant. Age is just the usual reason relevance runs out. Get the logic right and you'll know exactly which roles to keep, whatever the dates say.

Why 10-15 years is the default

The real test: relevance, not age

For each old role, ask one question: does this help me get the specific job I'm applying to? Usually the answer tracks with age, so 10-15 years works. But the exceptions matter:

How to keep older experience without eating the page

You don't have to choose between "list it in full" and "delete it". Split your history:

Relevant Experience — your recent, on-target roles, full detail, 2-4 bullets each with numbers.

Earlier Experience (or "Additional Experience") — older or less relevant roles compressed to one line each: title, employer, years. No bullets. You can even combine similar positions. It proves continuity without spending real estate.

And you can drop dates from the earlier section entirely — "Earlier roles in retail management" as a single summary line is completely acceptable when the specifics don't matter.

The special case: returning to an old field

This is the trickiest version, and a common one — you spent recent years in one line of work and now want back into a field you left a decade ago. Straight reverse-chronological order buries your relevant experience under the irrelevant recent stuff, and the recruiter never scrolls to it.

Two fixes, used together:

  1. Lead with a summary that states the pivot. Three lines up top: "Returning to [field] after [recent chapter], bringing [X years] of prior [field] experience plus [transferable skill from the recent work]." Now the reader knows the plot before they hit the timeline. (Summary formula and examples here.)
  2. Use the two-section split. Put the old-but-relevant field under "Relevant Experience" with real detail, and park the recent bridge jobs under "Additional Experience" as one-liners. Reverse-chronological order still holds within each section — you're just grouping by relevance first.

One honest note on the "overqualified / flight risk" fear when taking a bridge job: you can soften it by trimming the most senior old titles to plain descriptions and letting the cover letter say, in one line, that you want steady work in this area right now. Don't lie about your history — just don't lead with the parts that trigger the wrong assumption.

Quick rules by situation

The thread that ties it together

Every one of these calls is really the same call you make when you tailor a resume to a specific posting: keep what proves you can do this job, compress or cut the rest. A role's date is a shortcut for guessing relevance — but you can judge relevance directly. (That per-posting judgment is exactly what Coverpilot helps with: it reads the job you're applying to and shows which of your experience actually lines up.) Decide by relevance, and "how far back" stops being a rule you follow and becomes a choice you make.