Executive assistant hiring is a trust decision, and resumes build trust through specifics: how many principals, at what level, across how many time zones, with what volume of travel and meetings. Vague loyalty language ("trusted right hand") does nothing; operational numbers plus tenure do everything. The reader wants to know, within ten seconds, whether you have operated at the altitude their principal flies at, and only concrete scope answers that.
The best EA bullets show judgment, not just logistics: meetings you re-prioritized when an acquisition call landed, problems you resolved before the executive ever saw them, operating rhythms you built that other leaders adopted. Logistics prove competence; judgment proves you can be left alone with the calendar, the inbox, and the board deck. The example below is written for a C-suite EA and scales down cleanly for director-level support.
Who reads your resume depends on the seniority of the seat. Director-level EA roles are usually screened by corporate recruiters running keyword searches through an applicant tracking system, which is why literal phrases like "calendar management", "travel coordination", and "board meeting preparation" have to appear on the page. C-suite and principal-EA searches often run through specialized EA recruiting agencies or the executive's current EA and chief of staff, who read for tenure, principal level, and discretion signals with a practiced eye. A strong EA resume works for both readers at once: searchable vocabulary on top of scope numbers.
Tenure is evidence in this profession in a way it is not for most jobs. An EA who supported one CEO for four years is presumed to have earned renewed trust roughly a thousand times; an EA with five one-year stints is presumed to have lost it, fairly or not. If your dates are long, make them prominent. If they are short for structural reasons (executive departures, acquisitions, layoffs), attach the reason in a brief clause, because an explained short stint reads completely differently from an unexplained one.
Writing the experience section. Open each role with the principal's level and count ("Executive Assistant to the CEO", "supported two VPs with combined orgs of 400+"), then build bullets on volume and outcome: meetings per week, time zones, trips per year, board and committee sessions, inbox share handled, offsites planned with headcounts and budgets. Add at least one judgment bullet per role: a calendar conflict you resolved during a critical week, a recurring-meeting audit that cut load, a process you built that outlived you. Avoid task lists ("answered phones, scheduled meetings"); every bullet should carry either a number or a decision. The quantification guide shows how to reconstruct volumes you never formally tracked.
Structuring the skills section. Split into executive-support skills and tools. Support skills should use the exact searched phrases: "complex calendar management", "international travel planning", "board and investor meeting logistics", "inbox management", "expense reporting". Tools matter more than EAs expect, because tool familiarity is a same-week-productivity screen: Google Workspace or Microsoft 365 (name whichever matches the posting), Concur or Navan for travel and expenses, Notion or comparable systems, Zoom and Slack administration. In 2026, add the AI tools you genuinely run (meeting-notes AI, drafting assistants) since executives increasingly expect their EA to operate that layer for them. See the skills section guide for placement.
Handling education and credentials. A bachelor's degree is commonly listed in EA postings and worth showing, but experience outranks it decisively; nobody hires a CEO's assistant off a GPA. If you lack a degree, do not compensate with filler, just let scope carry the page. Relevant extras that do help: a PACE certification or CAP (Certified Administrative Professional) for corporate screens, project management coursework for EAs edging toward chief-of-staff work, and language skills for principals with international footprints. Keep the education section to two or three lines and spend the space on experience.
Formatting for EA screens. Your resume is itself a work sample: executives judge an EA's materials the way they will judge the briefing documents you send under their name. That means flawless, restrained formatting: one page up to about ten years, single column, generous white space, zero typos, standard headings, PDF with real text. No photos, no graphics, no color experiments. It should look like something you would hand a board member. The 2026 format guide covers layouts that read as polished without reading as decorated.
Recurring mistakes on EA resumes. The most damaging: vague trust language with no evidence ("right hand to the CEO" is a claim, "zero leaks through two reorgs and one acquisition" is proof), missing volume markers so scope is invisible, naming confidential matters to demonstrate access (an instant red flag to EA recruiters), burying principal level below tool lists, unexplained short stints, and typos, which in this profession are disqualifying rather than merely sloppy since attention to detail is the product. Run the common mistakes checklist and then proofread twice more.
Use the top third for a summary that compresses the trust case: years, principal levels supported, headline volumes, and a discretion outcome, like the example below. Entry-level candidates and administrative assistants moving up should use a short objective naming the seniority they have touched and the level they are targeting instead of a thin summary. The summary guide has patterns for both, and career-changers should read the career change guide for the reframe.
Tailor per application, because EA seats differ more than the shared title suggests. A startup CEO wants scrappiness, tooling breadth, and comfort with ambiguity; a public-company CFO's office wants board hygiene, earnings-cycle awareness, and process rigor; a family office wants personal-logistics experience with explicit boundary protocols. Mirror the posting's emphasis in your first three bullets and your summary; the tailoring guide shows the ten-minute version.
The 2026 reality: AI scheduling and drafting tools have absorbed some of the mechanical layer of EA work, which has raised, not lowered, the bar for the human layer. Postings increasingly blend EA scope with chief-of-staff fragments: managing small projects, preparing decision memos, running leadership operating rhythms. Resumes that show judgment, discretion, and process-building on top of flawless logistics are matching those postings; resumes that read as pure scheduling are matching fewer. If you use AI tools to multiply your output, say so with an outcome attached, because principals want an EA who runs the tools rather than competes with them.
Use this page as a working file. Copy the structure, replace the volumes and principal levels with your own, borrow phrasing from the bullet bank below, then run the result through the resume checker to confirm the parsing and keyword coverage before it goes anywhere near a recruiter.