How to read this chief of staff resume example
The sample above is not a template to copy word for word - copied resumes read as copied. It is here to show the shape of a page that gets past a first screen: one column, standard headings, and bullets that end in an outcome rather than a duty. Decisions you shaped and programs that existed because you ran them.
- Every bullet opens with a verb and carries a number. That is the pattern, not a coincidence.
- The summary makes a claim and then supports it in the first bullet underneath.
- Skills are named tools, not adjectives, and each one appears again in the experience section.
- The earlier role is short. Recent work carries the weight of the page.
The numbers in a chief of staff resume
The most common thing missing from a chief of staff resume is a number. Not because the work had none, but because nobody wrote them down at the time. These are the measures a chief of staff can usually reach for, and the example uses them.
- Built the operating cadence - weekly metrics, monthly business review, quarterly planning - the company still runs on.
- Ran the integration workstream for a 90-person acquisition, from day-one plan to systems cutover.
- Unblocked three stalled cross-functional initiatives by naming owners and decision rights that did not exist before.
Before and after: rewriting a weak bullet
Most chief of staff resumes are one edit away from being much stronger, and the edit is the same every time: replace the description of the job with the result of doing it. The pairs below are the same work, written twice.
- Weak: "Responsible for strategic planning and related tasks." Strong: "Built the operating cadence - weekly metrics, monthly business review, quarterly planning - the company still runs on."
- Weak: "Worked on operating cadence projects across the team." Strong: "Ran the integration workstream for a 90-person acquisition, from day-one plan to systems cutover."
- Weak: "Helped improve processes and supported chief of staff initiatives." Strong: "Unblocked three stalled cross-functional initiatives by naming owners and decision rights that did not exist before."
Adapting the example to your own history
Work backwards from the posting. Find the two or three things it actually screens for, then make sure the top third of your page answers them. Everything below that is supporting evidence.
- Reorder your bullets so the one closest to the posting comes first in each role.
- Rewrite the summary for the specific job. It is the only part a human reliably reads.
- Cut any skill you would not want to be asked about for ten minutes.
- Keep Strategic planning, Operating cadence, Executive communication visible in context, not stranded in a list.