How far back should your CV go?

Ask ten career advisers how far back a CV should go and you will get ten different answers. Ten years. Fifteen years. Two pages maximum. Everything relevant. It depends. None of them are wrong exactly, but none of them are much use at eleven at night with an application form open either.

The reason the question feels hard is that it is really two fears wearing one question. The fear of looking old if you include everything, and the fear of losing credit for hard-won experience if you cut it. Both fears are legitimate, and both point to the same answer once you stop treating the CV as a biography. Go back as far as your evidence is still doing useful work for this application, and no further.

The 10 to 15 year default

For most experienced professionals, keeping the last 10 to 15 years in detail is a sensible starting point. That window covers the bulk of your relevant experience, reflects where your career actually is now, and sits roughly within what a hiring manager expects to see before their eyes glaze over.

The National Careers Service guidance on CV sections is useful here because it pushes in the same direction. Keep the structure clear and the content relevant, and stop treating the document like a full career archive.

There is also a blunt technical reason the older material fades. Skills decay in market value even when they do not decay in you. The engineer who was writing Java 15 years ago has not been writing that Java since, and the reader knows it. A detailed writeup of a 2011 role mostly tells the hiring manager how long ago 2011 was.

Treat 10 to 15 years as a filter rather than a law, though. The real question for every role on the page is the same one. Is this entry still earning its place?

When older experience earns its place

Some roles from further back genuinely matter, and cutting them would cost you real signal. That tends to be true when the old role proves something your recent history cannot:

• An early founding role or significant technical ownership that your later career has not replicated
• Domain experience in a specialist area the job requires, such as defence, healthcare, or embedded systems
• A qualification, certification, or project rare enough to be a differentiator
• A well-known company or landmark project that lends credibility to the rest of the story

The trick is that earning a place is not the same as earning a paragraph. A line or two naming the role, the company, and the relevant contribution usually does more for you than a full block that mostly reminds the reader how long ago it happened. You want the credibility without the carbon dating.

Compress instead of cutting

Between “full three-line entry” and “delete it” there is a middle move most people never use. Collapse the older positions into one short block near the bottom of the CV. Something like “Earlier experience includes technical lead and senior engineering roles at Company A and Company B, focused on distributed systems and data infrastructure.”

That single sentence quietly does a lot of work. It tells the reader your career has depth, answers the “what came before” question so it stops nagging, and spends almost none of the page doing it. Depth without noise is exactly the trade you want at the bottom of a CV.

It also deals with the gap problem. If cutting old roles would leave your timeline starting suspiciously mid-career, a compressed block closes the gap without inviting anyone to go digging through the details.

What to cut without hesitation

Some material is simply done. Old tech stacks with no relevance to where you are going. Junior roles your career has visibly moved past. Short contracts from years ago that add nothing to the current story. Any entry whose main justification is that you spent time on it rather than that it helps your case.

Cutting these is not dishonesty, and it is worth saying that plainly because the guilt is what keeps most bloated CVs bloated. A CV is not a legal record of your employment. It is evidence assembled for a specific argument. You choose the exhibits that support the case. The rest still happened, and it can still come up in an interview if it is genuinely useful. It just does not need to cost you attention on page one.

The answer changes with every job, which is the real problem

Here is why no fixed rule survives contact with an actual search. The same fifteen-year-old CTO experience is irrelevant noise for a hands-on engineering role and essential credibility for a principal position. The same early consulting work is filler in one application and a genuine differentiator in another. Even mainstream advice on tailoring your resume to the job description lands on the same point from a different angle. Relevance beats completeness, every time.

Which means the sustainable answer is to stop maintaining one CV that tries to answer the question for every job at once. Keep the full history somewhere safe, and make the how-far-back decision fresh each time you are tailoring for a specific role, when you can actually see what the role rewards.

That is how OutRung treats it. Your master profile holds everything, including the roles you would normally cut for space. When you generate a CV for a specific position, you decide what that application needs and pull forward only the experience that earns its place this time. Nothing is lost. Old detail just stops diluting strong recent evidence by default.

The honest answer

Default to 10 to 15 years in detail. Keep older roles when they prove something recent ones cannot, at a line or two rather than a paragraph. Compress the rest into a short block, cut what is genuinely past its usefulness, and stop trying to maintain one version that covers everything.

Your career does not get smaller when the CV does. The evidence just gets easier to see.