By mid-career the resume stops being a record and becomes an argument. Fifteen years of work will not fit on two pages, and it should not. The question is which parts support the specific case you are making for this specific role, and everything else is competing for space with them.
The second problem is subtler: a long history read chronologically can make you look like someone who has done many things rather than someone who has progressed. Fixing that is mostly a matter of emphasis and compression.
What to keep and what to compress
- Detail the last 10–15 years fully — three to five bullets per role
- Compress everything before that into an 'Earlier Career' block: title, company and dates only, in two or three lines total
- Drop roles older than about 20 years entirely unless one is genuinely load-bearing for this application
- Remove your graduation year if you are concerned about age screening — the degree stays, the year goes
- Cut every skill and technology you would not want to be interviewed on today
- Remove early-career certifications superseded by later ones
Making progression visible
When you have been promoted within one company, list the company once with the roles nested underneath and their own date ranges. Separate entries for the same employer make internal promotion look like job changes and waste space repeating the company description.
Across companies, progression should show in the bullets: scope growing, budget growing, team growing, decisions moving from execution to strategy. If your last three roles read at the same altitude, the reader concludes you plateaued — even if you did not.
Avoiding the dated signals
- No 'References available on request' — it has not been expected for twenty years
- No full postal address; city and country are enough
- No objective statement
- No 'Microsoft Office' as a skill unless you mean advanced Excel, in which case say advanced Excel
- No two-column layout with a photo, which reads as a 2015 template
- No decade-old technologies unless the role specifically wants legacy expertise — in which case lead with them
The summary carries more weight now
At entry level a summary is optional. At mid-career it is where you make your argument, because it is the only place you get to frame fifteen years before the reader starts forming their own view.
Four lines: what you are, how long, in what domain, and the two or three results that define your level. Then let the experience section evidence each claim.
Two pages, used well
Two pages is correct and expected at this level. Three is not, in any industry outside academia. If you are spilling, the fix is almost always cutting old roles to a compressed block rather than shrinking the font — an 8.5pt resume signals that you could not make a decision.
Frequently asked questions
- How far back should my resume go?
- Detail the last 10–15 years. Compress earlier roles into a two-line 'Earlier Career' block with titles, companies and dates, and drop anything beyond roughly 20 years unless it is directly relevant.
- Should I remove my graduation year?
- It is a reasonable precaution against age screening and costs you nothing — the degree itself stays. Some application forms will ask separately, and you should answer honestly there.
- How long should an experienced resume be?
- Two pages. One is possible and impressive if you can do it; three is a signal that you could not prioritise.
- How do I show promotions within one company?
- One company entry, with each role nested beneath it and its own dates. That makes internal progression legible at a glance instead of looking like three job changes.
- Should I include every job I have had?
- No. Include what supports the case for this role. Long-past irrelevant roles can sit in the compressed block; you are not obliged to detail a complete history on a resume, only to be accurate about what you do include.
- How do I explain a career break mid-career?
- One line with the dates and a plain reason — caregiving, health, study, redundancy, sabbatical. Concealment reads far worse than the break itself, and reviewers see them constantly.