How Far Back to Go, and What Cutting Old Roles Hides

Choosing a horizon — a point past which earlier work is summarised or dropped — is a reasonable editing decision, and it has two side effects people rarely account for. It removes context that sometimes explained your path, and it does not conceal what most people are hoping it conceals. Your qualification dates, the length of your career, and the shape of your progression remain visible from what is left. So the horizon is worth choosing on the basis of what a reader needs, not on the basis of what you would rather not show.

What the horizon is for

Early roles usually stop being informative before they stop being true. A first job that taught you a trade you no longer practise, in a company that no longer exists, described in the vocabulary of a decade ago, tells a reader almost nothing about whether to interview you now.

Cutting it back is not dishonesty. A resume is a case, not a complete record, and every line is there because it earns its space. The horizon is just the point where the earning stops.

The mistake is treating it as a fixed distance. It is not a number of years; it is the point where relevance runs out, and that point moves depending on the role you are applying for and on how much your field has changed.

What cutting old roles actually removes

The explanation for a change of direction. If your career pivoted, the earlier phase is sometimes the only thing that makes the pivot legible. Cut it and a reader sees an unexplained discontinuity instead of a coherent path.

Domain experience that has quietly become relevant again. You worked in a sector years ago; the role you are applying for is in that sector. The old entry is the strongest thing you have and the horizon would have deleted it.

Depth in a long-lived skill. Some capabilities are worth more the longer you have exercised them, and a truncated history flattens twenty years of practice into whatever fits inside the window.

Continuity. This is the practical one. Trimming early roles at an arbitrary point can leave a first date that starts mid-career with nothing before it, which reads as a question rather than as an edit.

What cutting old roles does not hide

This deserves saying plainly, because it is the unstated motive behind a lot of horizon advice.

It does not hide how long you have been working. Qualification dates, the number of roles, the seniority of the earliest one shown, and the vocabulary of your field all indicate it. A resume that starts mid-career with a senior title implies everything that came before it.

It does not hide a career length you would rather not state. If you would rather a reader did not form a view about your career length, deleting early roles does not achieve that; it just removes the detail while leaving the inference.

It does not remove those years from other records. Employment history exists in places you do not control, and application forms often ask for it in full.

It does not resolve a difficult episode. An early role you left badly is not made safer by absence, because the absence is itself visible if it breaks the timeline.

If the reason you want a horizon is any of these, the horizon is not the right tool. What is: writing the recent material well enough that it is what a reader spends their attention on.

Choosing where the line goes

Start from the role you are applying for. How far back does experience have to go before it stops bearing on this job? In a fast-moving technical field, quite recently. In a craft, a profession, or a regulated domain, much further.

Check whether your field’s tools have turned over. Work done with methods nobody uses is context, not evidence. Work done with methods still in use is evidence regardless of its date.

Look for the pivot. If your career has a turning point, the horizon usually belongs at or just before it, so the change is visible and explained rather than implied.

Then check the timeline for breaks. Wherever you put the line, the dates that remain should form a continuous sequence. If they do not, move the line or add a summarising block.

The summary block: how to keep old work without spending space

The tool most people miss. Rather than either detailing early roles or deleting them, collapse them.

A single block — “Earlier roles” or “Prior experience” — listing employer, title, and years for each, with no bullets. Two or three lines total. It preserves continuity, keeps the employers’ names visible, and costs almost nothing.

If a specific early role is genuinely relevant, lift that one out and give it a normal entry, leaving the rest in the collapsed block. There is no rule requiring chronological uniformity in how much detail each role receives.

If the old work supports a claim you are making now — a licence, a language, a domain — put the claim where a reader will see it and let the collapsed block carry the dates.

What still has no horizon

Qualifications you rely on. A degree or licence stays, whenever it was awarded. Whether to show the year is a separate question, and consistency matters: if you show years for some qualifications and not others, the omission is what gets noticed.

Credentials with a status. Anything that expires needs its status stated honestly rather than left ambiguous, which is the subject of certifications you let lapse.

Anything you would be asked about. If a reader is going to raise it, it is better present and framed than absent and inferred.

The trap when a tool does the trimming

Asking a builder or a chat tool to “condense my earlier experience” produces a summary of a summary, and the compression discards the specifics that made the old work worth keeping — the employer name, the domain, the actual dates. What comes back is a fluent paragraph about a general kind of career.

Worse, condensing across roles is where date and title errors get introduced, because the tool is merging entries and has no source to check against. If you use one for this, keep your original entries and compare, since the fields most likely to be silently altered are exactly the fixed ones and dates are the field most reliably checked against someone else’s records.

Two checks before you commit

Read the date column alone. Top to bottom, ignoring everything else. Is it continuous? Does the first date sit somewhere that makes sense, or does it start abruptly in the middle of a career?

Ask what the earliest entry is doing. If the answer is “explaining how I got here” or “supporting a claim I make later”, it belongs. If the answer is “completeness”, collapse it into the summary block. If the answer is “I could not decide”, it belongs in the block too.

Then confirm that everything remaining is something you could still discuss. Old entries are the ones you are least likely to remember well, and a line you cannot speak to is a liability wherever it sits on the page — which is the point of reading your resume as a sceptic before you send it. If an early claim has become unsupportable through sheer distance, narrowing or cutting it is the honest move.