An executive assistant resume should make the support relationship clear: who you assisted, which decisions you could make, and how you kept work moving. Calendar management, correspondence, travel, and records can all be important. Explain their complexity instead of replacing ordinary verbs with grander ones.

This guide uses a fictional resume to show progression from department support to executive support. It also gives worked bullet examples, a keyword checklist, and ways to describe confidential work without revealing protected information.

Executive and administrative assistant titles overlap. O*NET describes executive administrative support as a combination of research, reporting, correspondence, scheduling, and other office responsibilities. A title alone does not establish decision authority or a pay band.

For an EA application, make three things visible:

• Who you supported: the CEO, two VPs, or a department leadership team, where you can disclose that relationship.
• Your authority: did you propose calendar priorities, apply agreed meeting rules, or make decisions within a delegated budget?
• Your output: a board pack, a reconciled expense report, a coordinated itinerary, or a documented improvement in turnaround time.

Administrative experience can demonstrate the same skills. Keep your actual titles and responsibilities, then select the evidence most relevant to the new posting.

This is a fictional September 2024 resume. Colleen, the employers, career history, credentials, and results are illustrative. The timeline shows about eight years in administrative work, including six in EA roles and three supporting a CEO and CFO. Use its structure; replace every claim with your own supported experience.

Use the posting to choose relevant terms. The list below is a practical starting point for executive support, not a measured ranking of job-market demand.

Add only the terms that describe work you have actually done, and put each one inside a line that shows the result. To check a specific posting rather than this general list, run it through the free resume keyword scanner, or see the full resume keywords by job title.

The example names the leaders supported and pairs responsibilities with deliverables: board packs, approved access lists, variance reports, and travel itineraries. A named output can be useful evidence even when you cannot substantiate a savings percentage.

The following pairs distinguish types of work, not classes of employee. Both sides can appear in either role. Use the wording in the posting when it accurately describes your experience; a broader term is not automatically a better keyword.

For example, submitting expense reports and controlling a travel budget involve different authority. Keep that distinction visible.

Calendar ownership can involve applying agreed priorities and recommending changes to the week. Scheduling may involve coordinating availability and resolving conflicts. Both are useful; only claim delegated decision authority if you had it.

Similarly, reconciling receipts does not mean you owned a budget. Describe the reports you produced, the approvals you handled, and who made spending decisions. Keywords work best when the accompanying bullet explains what you actually did.

Lead with relevant experience and the people or team you supported. Then name one or two strengths supported elsewhere in the resume. A useful formula is: relevant experience + support relationship + specific work + a substantiated result or deliverable.

Illustrative structure: “Executive assistant supporting two VPs, coordinating international travel and quarterly planning materials.” Add years and outcomes only where your history supports them. Avoid these common weaknesses:

If you have not supported C-suite executives, use your real scope: “supported a department head and a leadership team of five.” Connect it to the new role through work such as preparing briefings, coordinating schedules, or tracking follow-up. Keep the original job title.

Use records you can explain to find useful measures: calendars, approved budgets, expense reports, event plans, and service logs. If the evidence is unavailable or confidential, a precise description of scope and output is enough.

Start with facts, then improve clarity. Suppose you coordinated the CEO and CFO calendars across three time zones and introduced an agreed priority checklist:

• Vague: “Responsible for executive schedules.”
• Specific: “Coordinated CEO and CFO calendars across three time zones, using an agreed priority checklist to resolve meeting conflicts.”

The revision adds context from the stated facts; it does not invent hours saved. Choose roughly three to five strong bullets for a recent relevant role, adjusting for the experience you need to explain.

For confidential work, describe the permitted process, such as maintaining approved access lists and version control. Mentioning an undisclosed transaction, compensation discussion, or client can itself reveal confidential information. Check your obligations and approvals before using those details.

Two compact groups can help: responsibilities and tools. Put the most relevant work first, whether that is board coordination, travel, executive correspondence, or office operations. Back important skills with examples in your experience.

Name the tools you actually used: Microsoft 365, Google Workspace, Concur, Zoom, Teams, or a board portal. A short example such as “tracked travel commitments in Excel” is stronger than adding an unfamiliar platform because it appears in a posting.

Judgment, discretion, and anticipation may be relevant keywords, but give evidence rather than relying on the labels alone. List certifications with issuer and accurate status. IAAP CAP and PMI CAPM require ongoing maintenance. Microsoft 365 Fundamentals is retired; a historical award is not a currently available exam recommendation.

Your resume should be easy to review and easy to extract into an application form. The hiring process may involve a recruiter, hiring manager, and executive; avoid assuming every organization uses the same sequence.

Use these checks before submitting:

Follow the employer’s file instructions. A text-based PDF often preserves layout; use DOCX if requested. Check text selection and reading order after export. Greenhouse documents parsing problems with elements such as images, columns, and contact information in headers. Those risks do not establish that every ATS rejects such files.

Adapt the emphasis to your background:

• Senior EA: show delegated decision scope, leadership of other support staff, and substantial projects you actually owned.
• EA to the CEO: highlight relevant CEO support if you have it. If the posting emphasizes board logistics, show your contribution to that work; CEO support does not always include it.
• First EA role: draw on department support, office management, events, hospitality, or coordination. Show how you prioritized requests, prepared information, and completed follow-up without changing your previous title.

Read the posting for its emphasis: board preparation, travel, project coordination, or another support need. Keep a complete base resume, then select the most relevant evidence for each application.

In the Roleframe account app, you can keep a base resume and tailor a version for a job. Job-match feedback can help identify wording to review, while Remi can propose edits for you to assess. A Roleframe score is its own assessment, not the employer’s ATS score or a prediction of an interview. Check every suggested claim against your experience.