A senior resume has a different problem from an early-career one. The early-career resume struggles to fill a page. The senior resume struggles to fit on one. By staff, principal, director, or VP level, you've accumulated more verifiable claims than any single page can hold, and the failure mode is the opposite of inflation: it's overstuffing, listing every role, every project, every initiative, until the page reads as a CV instead of a resume and the weight of any single claim drops to nothing.
Senior selection rewards the cadence described in the weeks a real application is worth; a one-pager is not a one-evening exercise.
The move at this level is selection, not generation. You're not writing new bullets. You're choosing which of the bullets you've earned over twenty years to put on this page for this role.
The reader at this level changes
A senior reader (a hiring manager at director or VP level, or an exec recruiter) reads differently from an early-career reader. They scan for shape. They want to see the trajectory of decisions, not the volume of accomplishments. They register quickly whether the candidate has been operating at the level the role asks for, and they distrust resumes that try to convince them with quantity.
This means the page has to do less, not more. Five strong bullets on the most recent role, three on the one before, fewer on older roles. White space. Confident dates. The page reads as someone who has nothing to prove on the basics, they're past that, and is choosing what to surface.
If your current resume has eight bullets per role going back fifteen years, you're writing for the early-career reader, not the senior one. The page is too dense. Cut.
What to cut
The first cut is older roles by length. If you've been a director or above for ten years, the engineer role from twenty years ago is one line: title, company, dates. Maybe a single bullet if it points at the target. Often nothing. The reader doesn't need to be convinced you've been an engineer; they need to be convinced you've been operating at director level. Length signals weight; senior-era roles get the length, early roles get the dates.
The second cut is bullets that name a responsibility instead of a decision. Senior readers want decisions and consequences. Responsibilities are assumed at this level.
Responsibility
Managed a team of fifteen.
Decision
Restructured a team of fifteen across two locations to ship the platform migration on a six-month timeline against an original eighteen-month estimate.
The third cut is bullets that don't survive a single question of so what? If a senior reader could read the bullet and ask "and what came of that?" with no answer on the page, the bullet is incomplete. Either finish it or cut it.
Unfinished
Led the migration to AWS.
Finished
Led the migration of a 200-instance fleet to AWS, cutting operational cost by 38% and replacing four pager-rotation engineers with two.
What to keep, and where to put it
The bullets that stay are the ones that name a tradeoff or a magnitude. Tradeoffs read as senior work because senior work is mostly tradeoffs, choosing what to ship, what to cut, what to fund, what to defer. Chose to delay the v3 launch by a quarter to consolidate the v2 platform first, taking a short-term revenue hit to set up the next year of margin reads as a director-level decision. The reader can see you operating at the level the role is hiring for.
Magnitude bullets (numbers, scale, scope) are the other category that earns space. Owned a $40M annual budget across four teams is a scope claim. Grew the engineering organization from 28 to 95 across two years, retaining the original architecture review process while expanding it to three review boards is both a magnitude and a tradeoff.
Order these on the page by the role you're targeting. A protect-the-platform CTO role gets the platform stewardship bullets at the top; a build-something-new role gets the zero-to-one bullets at the top. The same record, two different orderings, two different pages.
The same record, ordered for a protect-the-platform role: reliability and incident bullets up top, hiring and team-build bullets later. Reordered for a build-something-new role, the migration and zero-to-one bullets would lead instead.
One page, with intent
There's a long argument in resume circles about whether a senior resume should be one page or two. For the general question across career stages, see how long should a resume be; the senior case is the most contested instance of that question.
One page forces the selection work this whole piece is about. It also signals composure. A senior candidate who fits twenty years onto one page has done the editorial work in advance and is asking for the reader's time deliberately, not exhaustively. That posture matches the level.
The page can be dense (narrow margins, smaller leading, careful spacing) but it stays one page. If you're at twelve or fifteen years and genuinely cannot fit, cut earlier roles to one-line entries and reclaim the space.
Don't update; rewrite
Senior records that haven't been touched in years tend to accrete. A bullet from 2018 stays in the file because no one took it out, even though the role it describes is two jobs ago and the framing reads dated. Refining a senior record means going through every line and asking: would I write this bullet today, for the role I'm targeting today? Most of the time, the answer is no, not because the work was bad, but because the framing is from a different audience and a different moment.
Rewrite the bullets that matter, even when the underlying facts haven't changed. Verbs date faster than facts. Optimized, spearheaded, leveraged (those age. Cut, traded, chose, closed, delivered) those hold.
Closing
The senior resume is a piece of editing, not a piece of writing.
The work has been done; the question is which work the page chooses to surface for this role, today. Trust the reader to recognize weight when you give them weight; don't try to overwhelm them with volume. One page, fewer bullets, more decisions, more magnitude, more tradeoff.
Take the time the page is worth. The same record, written for different roles, is different pages, and that's the work.
Read next