Rebuild the CV that stopped in 2016, don't patch it
Ten years at one employer is an asset. Told as a single job block on an old template, it reads like standing still.

Why appending to the old file quietly sinks you
Open the file. There's a career objective at the top asking for a challenging position, your full street address underneath, a Word template with a table holding the layout together, and "References available on request" at the bottom. All of that was normal in 2016. Today each line tells a recruiter the document has been sitting in a drawer, and it shapes how they read everything below it.
Then there's the bigger problem. Ten years at one employer usually means three or four different jobs: you took on a team, absorbed a second region, ran the migration nobody else wanted. On the page it shows up as one heading, one date range, and a list of duties that hasn't changed since your first month. A decade of growth reads as a decade of nothing happening.
Rebuilding doesn't mean inventing anything. The facts are yours and they're good. What changes is the container: internal moves broken out as separate entries with their own dates, bullets that lead with what changed instead of what you were responsible for, early history trimmed to a line, and a clean layout a parser can actually read. Same career, told the way it gets read now.
The old file
Six things your 2016 CV is still carrying
A career objective
It asks the employer for something. Lead instead with a summary of what you run and at what scale.
Your street address
Full address and postcode belong on utility bills. City, mobile and email cover everything a recruiter needs.
Tables and text boxes
The old template props up your layout with structures many parsers skip. What looks fine on screen can arrive empty.
References available on request
Nobody assumes otherwise. That line burns space you need for a promotion you never wrote down.
Duties instead of results
"Responsible for month-end reporting" says the job existed. "Cut month-end close from nine days to four" says you did it.
Software nobody runs anymore
A skills list built around retired tools dates you faster than your graduation year. Put this quarter's stack first.

Rebuild it in five moves
Split the decade into the jobs it actually was
One employer, several entries. Each title gets its own dates, so ten years of promotions are visible in a three-second scan.
Put scope on every entry
Team size, budget, region, systems owned. Growth shows up in how those numbers change from one role to the next.
Cut the pre-2010 detail
Roles older than fifteen years shrink to one line each: employer, title, years. The detail buys you nothing and ages the page.
Swap the objective for a positioning summary
Three lines: what you run, at what scale, and the move you're making now. Written for the job you want, not the one you had.
Rebuild in a format machines can read
Single column, standard section headings, PDF unless the posting says Word. Design that survives the parser and the recruiter.
Same career, two very different documents
| What a recruiter sees | Updated 2016 file | Rebuilt CV |
|---|---|---|
| Top of the page | Objective asking for a challenging role | Summary of what you run and at what scale |
| Ten years at one employer | One heading, one long date range | Three entries with titles, dates and scope |
| Bullets | Responsibilities copied from the old job description | Results with numbers, strongest first |
| Early career | Full detail back to the late nineties | One line per role under "Earlier career" |
| File and layout | Word template built on tables and text boxes | Single-column PDF a parser reads cleanly |
| Contact block | Street address, home phone, references line | City, mobile, email, LinkedIn |
Ten good years deserve a document that shows them
Upload the old file. HRLens splits your decade into real roles, rewrites the bullets as results, and hands back an ATS-ready CV.
Questions people ask after a decade in one place
Can't I just add my recent roles to the old CV?
You can, and it will hurt you. The objective, the street address, the references line and the table-based template all mark the document as a relic, and the recruiter reads everything else through that lens. Rebuilding takes about an hour and fixes the deeper problem at the same time: ten years of work showing up as one job.
How do I show ten years at one employer without looking static?
Break the block into separate entries under a single company heading, one for each title you held, each with its own dates. Then attach scope to every entry: team size, budget, region, systems owned. Progression becomes obvious the moment a reader sees three roles and three sets of numbers instead of one flat ten-year range.
How far back should my work history go?
Detail the last ten to fifteen years, then collapse the rest. Older jobs become a single line each with employer, title and years, or a short "Earlier career" section. Nothing before that earns its space, and full detail back to the nineties invites assumptions about your age before anyone reads what you delivered last year.
Do I still need a career objective or "references on request"?
No to both. The objective asks the employer for something, while a short positioning summary tells them what you deliver and at what scale, which is what they are actually screening for. References are taken for granted and nobody chases them before the offer stage. Delete both and give the space to a promotion you never wrote up.
Will an ATS read my old Word template?
Sometimes, and that is the trap. Parsers handle plain single-column layouts reliably, but text boxes, tables, headers and graphics are where content goes missing quietly. Your CV can land with the experience section blank and you will never hear about it. Rebuild in a simple structure and export to PDF unless the posting asks for Word.
What if I held the same title for ten years with no promotion?
Then split by phase instead of title. Group the decade into two or three chapters defined by what changed: a new system, a bigger region, a team you inherited, a product you took over. Give each chapter a date range and its own results. Same job, but the reader sees momentum rather than a straight line.