Executive Assistant Resume Guide: Level, Judgment, Confidentiality
The short answer: An EA resume is read for seniority and judgment. Name who you supported by title and the size of what they ran, then show the decisions you made on their behalf โ what you declined, rerouted, drafted in their voice, or chose not to escalate. Board work, complex travel, and budget authority are the proof points; the task list is not. And write about confidential work by category, never content: discretion is being assessed while the page is read.
If you're building your first admin resume, start with the administrative assistant guide โ scope, systems, and making invisible work measurable. This one picks up where that leaves off: what changes when the job is supporting people whose time is the company's scarcest resource.
Level and scale, in the first two lines
โ "Executive Assistant providing high-level administrative support to senior leadership in a fast-paced corporate environment."
โ "Executive Assistant to the CEO and CFO of a 900-person healthcare company (~$400M revenue) โ sole EA for both, supporting a 9-person leadership team and a 7-member board."
"Executive assistant" spans supporting a department head at a 40-person startup and supporting a public-company CEO. Those are different jobs, so say which: titles supported, how many executives, headcount or revenue of what they ran, and whether you were sole EA or part of a team. If you've supported a founder, a board chair, or a C-suite in a regulated industry, that context carries. Industry matters too โ legal, healthcare, finance, and nonprofit EAs deal with different compliance surfaces.
Judgment: what you decided, not what you scheduled
โ "Managed complex calendars, scheduled meetings, and coordinated travel arrangements for executives."
โ "Held final say on the CEO's calendar against 40+ weekly requests โ declined or rerouted roughly half without escalation, protected two deep-work blocks through quarter close, and rebuilt the leadership meeting cadence after a reorg cut standing meetings by a third."
This is the difference between an EA resume and an admin resume. At this level you're a filter with authority, so write the authority: correspondence drafted and sent in the executive's voice, requests you turned down, meetings you merged or killed, information you decided didn't need to reach them, decisions you made while they were unreachable. Every one of those is a judgment call an executive is trusting you with, and almost nobody puts them on paper.
Say what you were the gate for, too: who got access, how inbound requests were triaged, and how you handled the political reality of telling senior people no. That's the show-the-behavior rule in a role where "discreet and professional" is claimed by every applicant.
The high-stakes surfaces
Three areas separate senior EAs, and each deserves its own evidence.
Board and leadership meetings. Board packet preparation and distribution, agenda building with the chair or CEO, minutes, committee scheduling across external directors' calendars, governance deadlines, and offsite planning. Board cadence is a specific competence and hiring executives look for it directly.
Travel complexity. Not "coordinated travel" โ multi-leg international itineraries, visas and entry requirements, private and charter logistics, time-zone-aware scheduling across regions, and what you did when a trip broke mid-route at 2am. Rebooking a collapsed itinerary is the most concrete competence story an EA can tell.
Authority over money and people. Budget lines you managed, vendor selection and contract renewals you ran, expense approval thresholds, purchasing authority, and whether you managed or mentored other assistants. Supervising an admin team is a management line and should read like one, the way any trust marker does.
Confidentiality: category, never content
Describe the class of material and the stakes without the details: "supported a leadership team through an acquisition and a reduction in force โ board materials, offer and separation documents, and compensation data under NDA." That tells a hiring executive exactly what you can be trusted with and reveals nothing. Don't hint at events that were never public, don't name executives you supported unless their role was public and naming it is normal in your field, and never let a bullet turn into a story someone could reconstruct. How you write this section is the assessment.
Systems, and what to cut
Name the stack briefly โ calendar and email platforms, expense and travel systems, board portal, e-signature, project and communication tools, CRM if you touched it. It matters for onboarding speed, but at this level it's a supporting line, not the headline, and a wall of software reads junior.
Cut anything that reads like a task list: answering phones, filing, ordering supplies, greeting visitors, scheduling as a verb on its own. Cut "organized," "detail-oriented," and "proactive" โ the bullets above prove all three or nothing does. Keep it to one page unless you have fifteen-plus years, and if you're aiming at chief of staff or operations roles, lead with the project ownership and budget work rather than the support framing, because that's a deliberate reframe rather than the same resume with a different title on it.
Level up top, judgment in the bullets. PlainResume's reorderable sections make it easy to lead with who you supported and what you decided. Free, no sign-up, no paywall on the PDF โ everything stays in your browser.
Build your resume free โFrequently asked questions
What should an executive assistant resume include?
Titles supported and organization scale, judgment calls made on their behalf, board and travel complexity, budget and vendor authority, then systems.
How do you show judgment?
Write what you decided โ requests declined, meetings killed, correspondence sent in their voice, what you chose not to escalate โ not what you scheduled.
How do you write about confidential work?
By category and stakes, never content: "board materials, separation documents and compensation data under NDA." No names, no reconstructable details.