If you are an experienced EA eyeing chief of staff, business operations, or program roles, you are closer than your resume shows. Most EA resumes focus on support. CoS screens look for operating cadence, cross-functional delivery, decision support, and discretion. The work often overlaps. The gap is in how an executive assistant to chief of staff resume names it.
One thing most career advice skips: plenty of these hires never touch a job board. They come from an internal promotion, or from someone the executive trusts vouching for the candidate. Do the resume work, and in parallel go get the access: an internal sponsor, a former exec who landed somewhere new. The resume converts that access. It rarely creates it.
One piece of market context. O*NET counts 502,800 executive secretaries and executive administrative assistants employed in 2024, projects a decline of 1 percent or lower for 2024 to 2034, and puts total projected openings across that decade at 50,000, against a median wage of $76,590 in 2025 (O*NET OnLine, 43-6011.00). Those figures describe the job you are leaving. Flat demand in your current lane is a fair argument for pushing on the title now.
Why EA resumes undersell CoS readiness
EA resumes undersell CoS readiness because they name the activity and drop the decision behind it. Calendar, travel, expenses, meeting logistics. A reviewer reads a support function and moves on.
What the reviewer wants is the operating system you ran for the executive and the org: how you set the cadence, decided at the right altitude, drove cross-functional follow-through, and protected sensitive work.
The recognition problem shows up here. You have done the work. It just sits under keywords that do not carry your impact. What you need is a rewrite, and a rewrite is cheap.
Two moves do most of the lifting. Name what you owned end to end, so that "owned the executive operating cadence" replaces "managed calendar." Then put the result at the front of the bullet and the mechanics behind it, and tie board prep, leadership meetings, and planning weeks to the governance they served instead of the logistics they required.
A third move separates a credible bullet from an inflated one, and rewrite guides skip it: scale. "Ran leadership forums" tells a screener nothing. "Ran weekly leadership forums for a nine-person exec team at a 400-person company" tells them whether your experience is sized to the job they are filling. Use your own real numbers. Every number in the example bullets below is invented to show the shape.
Do not try to fix the whole resume tonight. Rewrite the top three bullets under your current role, outcome first, and stop there.
From calendar to operating cadence: reframing exec support
Running a calendar sounds tactical. In practice, senior EAs set how the organization makes decisions. When you set agendas tied to quarterly priorities, enforce pre-reads and decision memos, gate who gets time with the executive, and chase action items until they close across teams, you are running the decision system. Name it that way.
Language you can adapt, with example numbers to swap for your own:
- "Established the executive operating cadence for a CEO and a nine-person leadership team: agenda standards by priority, enforced pre-read deadlines, decisions tracked to close."
- "Resequenced leadership forums to match the planning cycle so commitments stopped colliding."
Scan the last quarter of your exec's calendar. List the recurring forums you created or improved, what each one decides, and one piece of friction you removed. Every line on that list is a bullet.
Projects you already ran: finding the program evidence
CoS roles are program roles with a different title. They stand up initiatives and push cross-functional work until it finishes. Plenty of EAs already do that, filed under "special projects."
Where to mine evidence:
- Company-wide meetings and offsites you scoped and delivered. That is internal program management and vendor orchestration. Write it that way.
- A policy or system change you pushed through: an expense overhaul, a new travel workflow, a contract template that needed legal, finance, and ops to agree before anything could move.
- Whatever you quarterbacked during the weeks your exec was unreachable and you owned the timeline.
Write each one outcome first, then scope, then the control surface you held: "Delivered the first integrated QBR week on schedule. Aligned finance, sales, and product on inputs, owners, and go/no-go criteria. Owned the timeline, the risk register, and stakeholder comms."
Skim your sent mail, pull three programs you shepherded, and write them up that way.
Confidentiality as a qualification, described safely
You have probably handled highly sensitive work. CoS hiring managers assume they will need that from you, and they want to see it claimed. The trick is claiming it without disclosing anything.
Standard advice gets this wrong in one way. Naming the type of transaction can itself be the confidential fact. A bullet mentioning diligence for an acquisition tells a reader a deal happened, roughly when, and that you were inside it. If that deal is still sensitive, the line can produce a phone call from your former employer's counsel, and a hiring manager who has watched that happen reads it as a judgment problem rather than a signal of trust.
Default to language that names your control points and nothing else:
- "Supported the CEO through a confidential executive initiative. Ran the forums, the comms calendar, and stakeholder sequencing under NDA."
- "Owned board-meeting operations: pre-read deadlines, briefing packets, minute approvals, materials controlled end to end."
Keep names out. If you want to name a deal category at all, confirm it with your employer or your own counsel first, and only where the activity is already public. Nobody will hold generic phrasing against you. A leak they will remember.
Write one bullet that starts "Under NDA," then names the category and your ownership.
The judgment signal: decisions you made without escalating
CoS hiring managers listen for judgment. Where did you decide rather than route the question upward? Your resume needs two or three crisp examples.
Look for the moments. You resequenced inbound requests to protect a strategic priority. You took schedule risk to hold a launch window and ran the mitigation yourself. You rewrote somebody's decision memo so it framed a real tradeoff instead of a foregone conclusion. That last one, written up: "Advanced a stalled review by drafting the decision memo, framing the options against real constraints, and driving a documented choice."
The related gap is people. Most CoS postings mention leading a team or owning a budget, most EAs have done neither on paper, and that is usually the thing making you hesitate. Do not paper over it. Write up the authority you did hold: vendors you managed and replaced, contractors you directed, cross-functional owners who took deadlines from you without reporting to you. Dotted-line leadership counts, and it reads better plainly stated than dressed up as management. In a screen, say the true thing, that you have not carried direct reports and you have run programs where half a dozen people owed you work and delivered it. Then ask what this role's people scope is. Some CoS jobs have none.
Pick one decision you owned and write the risk, the call, and the result in one sentence.
An executive assistant to chief of staff resume: before and after
Target role: Chief of Staff, Business Operations. Every number below is invented for the example.
Targeted summary:
- EA stepping into CoS. Built and ran the executive operating cadence, board governance, and cross-functional programs. Trusted with confidential work.
Before: task-first bullets
- Managed complex calendar and travel for CEO. Coordinated meetings and logistics. Prepared agendas and took notes.
- Scheduled board meetings and coordinated materials. Helped with special projects as needed.
After: outcomes-first bullets
- Established the executive operating cadence for a CEO and a nine-person leadership team. Set agenda standards by priority, enforced pre-reads, and tracked decisions to close, which cut last-minute fire drills.
- Ran board operations as governance for a board of eight: pre-read deadlines, briefing packets, minute approvals.
- Owned delivery for a confidential initiative under NDA, sequencing stakeholders and surfacing risk early enough that it could still be fixed.
- Converted leadership requests into decision-ready packets so finance, product, and legal could settle a choice in one sitting.
How to use this pattern: your headline names the bridge in plain words, something like executive assistant targeting chief of staff and business operations roles, without misstating the title you hold. Group the bullets by the system you run: cadence, governance, programs, decision support. Keep the logistics too, since expense workflows and travel show scale and trust. They just belong inside an outcome bullet.
Title-bridge strategy: EA to business operations to CoS
Whether the direct jump is realistic depends less on your bullets than on who is hiring. Startups, smaller companies, and nonprofits hire EA to CoS directly with some regularity, because the role there goes to whoever can run the place. Large enterprises lean on consulting or MBA pedigree, or they promote from inside. If a big name is your target, take the bridge: an executive assistant promotion into a business operations title is the faster yes, and it has you writing CoS bullets a year sooner. For plenty of people the EA career path reaches chief of staff through an ops job.
Either way, this runs over months. Reframing bullets takes an evening. Building the programs that make the reframing true takes considerably longer.
Three things help with the mechanics. The HiringCoachAI resume builder spins targeted versions off a master resume, so a CoS version and an operations version can sit side by side. A job fit analysis shows where your bullets match a target posting and where they miss, and you close those gaps with real experience, never with filler. For a human read, the directory of independent coaches on HiringCoachAI is worth a look; pick someone whose background matches your target sector.
Final checklist
Four things before you send it.
- Your headline names the target without misstating the title you actually hold.
- At least one bullet under every role shows a decision you made rather than a task you completed.
- A reader can tell how big the thing was that you ran: team size, company size, board size.
- The confidential work is claimed by category and control points, with nothing in it that should not be public.
A resume this specific gets you a screen, and the screen tests the same claims: which call you made, why, and what you would do differently. Hiring managers know this jump is unusual, so they push on it. Practice those stories out loud.
Pick one bullet tonight and rewrite it. That is the whole exercise, and the fastest way to find out whether a reviewer would stop on your resume.