There is no official rule, which is exactly why this trips people up
Ask ten career advisers how far back a CV should go and you will get ten different answers. Ten years. Fifteen years. Two pages max. Everything relevant. It depends.
None of them are wrong exactly, but none of them are very useful either.
The actual answer is simpler than the debate makes it sound: go back as far as your evidence is still doing useful work, 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.
Anything older than that tends to start losing relevance fast. Technologies change. Methodologies shift. A senior engineer who was writing Java 15 years ago has not been writing the same Java since.
The 10 to 15 year range is not a hard rule, though. It is a filter. The real question is always whether a role is earning its place on the page.
When older experience is still worth including
Some roles from further back genuinely matter and cutting them would actually hurt you.
That might include:
- 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 that is rare enough to be a differentiator
- A well-known company or landmark project that lends credibility to the rest of your story
In those cases, a short entry is usually enough. You do not need to write it up in full. A line or two that names the role, the company, and the relevant contribution is often more effective than a detailed block that reminds the reader how long ago it was.
Compressing rather than cutting
There is a middle path that most people miss: compression.
Instead of either including a full three-line entry for each early role or cutting them entirely, you can collapse several older positions into a single short section near the bottom. Something like “Earlier experience includes technical lead and senior engineering roles at Company A and Company B, focused on distributed systems and data infrastructure.”
This keeps the signal without the noise. It tells the reader that your career has depth without making them wade through decades of history to find it.
What to cut without hesitation
Some things are just not earning their place and need to go.
Old tech stacks that are no longer relevant. Junior roles that your career has visibly moved past. Short contracts from years ago that do not add anything to the current story. Any entry where the main reason it is there is that you spent time on it, not that it helps your case for this job.
Cutting these is not dishonesty. A CV is not a legal record of your employment. It is evidence. You choose the evidence that supports the argument you are making for a specific role. The rest can wait.
The problem with one CV for everything
The reason this question is hard to answer cleanly is that the right answer changes depending on the job.
The same fifteen-year-old CTO experience might be irrelevant for a hands-on engineering role and essential for a principal or staff-level position where leadership credibility matters. The same early consulting work might be noise in one application and a genuine differentiator in another.
That is why the most sensible approach is to stop maintaining a single CV that tries to work everywhere. Keep your full career history somewhere safe, and then make deliberate decisions about what to include when you are tailoring for a specific role.
That is exactly how OutRung approaches it. Your master profile holds everything, including roles you might normally cut for brevity. When you generate a CV for a specific position, you can decide what that application needs and pull forward only the experience that earns its place for that role.
Nothing gets lost. You just stop letting old detail dilute strong recent evidence every time you apply.
The honest answer
Go back as far as your experience is still relevant and credible for the specific role.
Default to 10 to 15 years in detail. Compress what is older but still useful. Cut what is genuinely past its usefulness. And stop trying to maintain one version that covers everything.
Related questions
-
A practical default is 10 to 15 years of detailed experience. Beyond that, compress or cut unless older roles directly support the case you are making for a specific job.
Written by
Tian - Founder of OutRung
Tian is an AI professional, builder, and the founder of OutRung. Holding a PhD in deeptech, Tian navigated the frustrating modern job market first-hand before transitioning into the AI space. OutRung was built to share the exact strategies that made that transition successful. Tian's goal is to help everyday job seekers use AI to find their ideal roles efficiently, without needing to be computer experts themselves.
More to read
-
How to add volunteer work to your CV (and when not to) Volunteer work sits in an awkward spot on a CV. Most people either over-explain it because they are proud of it, or leave it out entirely because they are not sure it counts. -
How to respond to an interview email without sounding stiff or unclear Getting an interview email should feel like good news, but somehow it often turns into a tiny writing crisis. You do not need to sound impressive. You need to be clear. -
Resume vs cover letter and why mixing them up hurts your application A CV and a cover letter are meant to do different jobs. When you make them say the same thing, you waste the little attention your application gets. -
What technical skills to put on a resume when your real value is more than a keyword list A skills section can help you get noticed, but it can also make a serious technical career look weirdly thin. The trick is knowing what belongs in the list and what needs proof.