The fastest way to lose an executive assistant role is to submit an administrative assistant resume with a different title on it. Recruiters hiring for the C-suite are screening for strategic language: board relations, executive communications, stakeholder management, confidential decision support. A resume built around "answered phones, scheduled meetings, ordered supplies" reads as tactical support, and tactical support is a different job at a different pay band.

This guide gives you a complete executive assistant resume example, then breaks down the keyword gap between EA and admin postings, section by section. The short version: EA job descriptions ask for judgment and ownership, admin job descriptions ask for tasks, and your resume needs to speak the first language even if your last title was the second.

The two roles share a surface, which is why so many EA resumes fail. Both manage calendars, both handle email, both book travel. What differs is scope, and scope is what the resume has to prove.

An administrative assistant supports an office or a team. An executive assistant supports one or a few senior leaders, which means they operate inside decisions: preparing board materials, gatekeeping the executive's time against competing priorities, handling information that would move markets or morale if it leaked, and often representing the executive to people more senior than the EA themselves. Hiring managers describe the strong EA as a force multiplier for the executive, and they screen resumes for evidence of exactly that.

Concretely, the resumes diverge in three places:

• The verbs. Admin resumes say scheduled, answered, filed, ordered. EA resumes say owned, gatekept, prepared, briefed, negotiated, anticipated. Same underlying activity in some cases, different level of agency.
• The audience. Admin resumes rarely name who was supported. EA resumes name the altitude: "supported the CEO and CFO," "primary point of contact for the board of directors." Altitude is the single clearest EA signal.
• The stakes. Admin bullets describe volume (calls handled, orders processed). EA bullets describe consequence: an offsite for the leadership team delivered under budget, a board meeting cycle that ran without a missed deadline, an executive's calendar restructured to recover hours per week.

If your current resume was written for an admin role, the fix is rarely inventing new experience. It is re-describing the experience you have at the level it actually operated. For a side-by-side reference, our administrative assistant resume guide shows what the tactical version of these sections looks like, which makes the contrast easy to see.

Here is what that looks like assembled into a real document. Notice how every section, from the summary to the individual bullets, keeps naming the executives supported, the strategic work owned, and the measurable result. The rest of this guide refers back to it.

Two things worth stealing from the example above even if your background looks different. First, the summary leads with who was supported and at what level before it lists a single skill. Second, almost every bullet carries either a number or a named deliverable, because "managed complex calendars" is a claim while "managed calendars across three time zones for two C-level executives" is evidence.

Roleframe's job-analysis engine reads real postings for both roles, and the pattern is consistent: executive assistant postings are loaded with strategic-scope keywords that barely appear in administrative assistant postings, while admin postings lean on task keywords that an EA resume should de-emphasize. Applicant tracking systems (ATS), the software that stores and filters applications, index against the posting's language, and recruiters run keyword searches on top of that. If your resume speaks admin while the posting speaks EA, you lose both filters at once.

Here is how the vocabulary splits:

Read the pairs in the last few rows carefully, because they describe the same activity at two levels. "Meeting scheduling" is putting an event on a calendar. "Calendar ownership" is deciding what deserves the executive's time, saying no on their behalf, and restructuring the week around what matters. "Expense report submission" is filing receipts. "Expense and budget management" is owning a departmental travel budget and reporting variance. When you rewrite an admin bullet for an EA application, you are usually moving it one row to the left.

A warning that applies to every role, not just this one: do not paste strategic keywords into a resume that has no evidence behind them. Recruiters interview against the resume, and "board relations" with no board story behind it collapses in the first ten minutes. Use the strategic term only where your experience genuinely supports it, then back it with a bullet. Our guide to ATS resume keywords covers how to match a posting's language without stuffing.

Your summary has one job on an EA resume: establish altitude in the first line. The recruiter needs to know, before reading anything else, what level of executive you supported and for how long. Everything else in the summary is secondary.

A working formula: years of experience, level supported, one or two strategic specialties, one quantified proof point. For example, the shape (not the exact words) of a strong one: seven years supporting C-suite executives, specialty in board coordination and international travel logistics, with a concrete result like a board cycle delivered without a missed deadline or measurable time recovered on an executive's calendar.

What kills EA summaries, in order of frequency:

If you are moving up from an admin role and lack C-suite support to name, lead with the highest altitude you honestly have ("supporting a department head and leadership team of five") and your strongest strategic specialty. Honest altitude beats inflated altitude every time, because the interview will find the truth. For more structures and worked examples, see how to write a professional summary.

EA impact is real but often invisible, because the whole job is making the executive's output look effortless. Your experience section has to make that invisible work measurable, and there are four reliable places to find numbers even in a role nobody ever gave you a dashboard for.

Then apply the standard structure, action verb plus specific task plus measurable result, but with EA-grade verbs. Compare the two versions of the same reality:

• Tactical: "Responsible for scheduling meetings and booking travel for executives."
• Strategic: "Owned complex calendars for the CEO and CFO across three time zones, restructuring recurring meetings to recover roughly five hours of executive time per week."

The second bullet is longer, and it earns the length: it names the altitude, the complexity, the action taken on the EA's own judgment, and the result. Three to five bullets of that quality per role beats eight bullets of duty-listing. If you are unsure how many to write, our answer on bullet points per job breaks it down by recency and relevance.

One more move that pays off for EAs specifically: include at least one bullet about handling something confidential or high-stakes, described at a level of abstraction that stays discreet. "Managed confidential materials for executive compensation and M&A discussions" proves discretion without breaching it, and discretion is a top screening criterion for this role.

The skills section on an EA resume does double duty. It is where recruiter keyword searches land, and it is the fastest scan of your scope. Build it in two visible groups: strategic competencies and tools.

List the specific tools you actually use, because recruiters search for them by name: Microsoft 365 or Google Workspace, an expense platform such as Concur, video conferencing (Zoom, Teams), and increasingly a project tool like Asana or Notion, since EAs at modern companies often run the leadership team's operating rhythm inside one. If you have used a board portal, name it. If you type or take minutes at speed, a concrete figure belongs here.

Keep soft skills out of the skills section entirely. Discretion, judgment, and anticipation matter enormously for this job, but as list items they are unfalsifiable. Prove them in bullets instead, where they come attached to a situation and a result. Our breakdown of resume skills section examples covers the keep-versus-cut logic in more depth.

Your resume for this role gets two very different readers, and the format has to serve both. The ATS and the recruiter read it first, keyword by keyword. Then, unusually often for any role, the executive themselves reads it, because executives choose their own EA the way they choose few other hires. The executive reader is scanning for polish, judgment, and whether the document itself reflects the standards they expect in their own materials.

That double audience points to specific choices:

Submit as PDF. A PDF locks your formatting on every machine it opens on, and the polish you built is part of the argument. The one page or two question has a fuller answer by experience level if your history sits on the borderline.

Three common variations on this resume, and what changes in each:

• Senior executive assistant. The differentiators are years at C-level, board exposure, and leadership of other admins. Lead the summary with the seniority of your principals and add any team you coordinated. Strategic project work (running the leadership team's operating cadence, owning an integration or office move) belongs in its own bullets.
• Executive assistant to the CEO. Mirror the posting's altitude exactly. If the job is CEO support, the words "CEO" or "chief executive" should appear in your summary and at least one recent bullet, assuming you can back them. Board relations moves to the front of your skills list, because CEO-support roles almost always include it.
• No direct EA experience. You are re-describing adjacent experience at its true altitude. Admin assistants, office managers, coordinators, hospitality supervisors, and paralegals all have translatable material: pick the moments where you exercised judgment on a senior person's behalf, handled confidential information, or delivered an event or process end to end, and write those as your leading bullets. A summary that names your target and your strongest transferable proof beats one that apologizes for the gap.

EA postings vary more than almost any other role, because the job is shaped by one person's working style. One posting is heavy on board coordination, the next on international travel, the next on managing a family office's personal logistics. A single generic EA resume will match none of them well, which is why tailoring matters more here than for most jobs. The mechanics of keeping a base resume with tailored versions per application solve this without rewriting from scratch every time.

Roleframe is built around exactly that workflow. You keep one master EA resume, duplicate it for each posting, and get a fit report: an ATS score against that specific job, the exact keywords the posting asks for that your resume is missing (this is where "board relations" versus "scheduling" surfaces concretely), and a prioritized plan of what to change. Then Remi, the career copilot inside the editor, helps you rewrite the bullets that need it, one proposal at a time, with you approving every word. Nothing gets written for you, which matters for this role more than most: an EA is hired on trust, and you should be able to defend every line in the interview.