Administrative Assistant Resume Guide: Scope, Systems, and Trust

A practical guide from the team behind PlainResume, the free resume builder.

Admin assistant resumes face a structural unfairness: the better you were at the job, the less anyone noticed it happening. Smooth calendars, conflict-free travel, meetings that just worked — success leaves no visible trace, and resumes written from that experience default to invisible language too: "provided administrative support to the team." The fix is to make the machinery countable. The person screening — an office manager, an exec, an HR partner — is asking two questions: can this person run the operation without supervision, and can they be trusted with what crosses their desk?

State the scope: who, at what level, how many

Level matters as much as volume: supporting a C-suite exec, three VPs, or a walk-in office are different jobs, and the reader is matching you to theirs. Then the volumes — calendars, weekly meeting count, trips per quarter, events per year with headcounts, expense reports per month. None of this is padding; it's the verb-and-number rule applied to work that generates numbers constantly but rarely gets credit for them.

Name what you owned end-to-end

Beyond the daily machinery, admin roles accumulate whole systems with one owner — and those are your strongest bullets: "planned the 120-person annual offsite (venue, travel, $45K budget) three years running," "ran logistics for onboarding — 25 new hires last year, day-one ready," "managed 12 vendor relationships and the office's $8K/month supply budget." Software gets named when the posting names it — Google Workspace vs Outlook/Teams is a real screening line, and Concur, DocuSign, or an HRIS by name are ATS keywords worth matching honestly.

Trust is the differentiator — say what was routed through you

This is the admin equivalent of keyholder status: what management chose to route through you is a measurable form of trust. The phrasing rule keeps you safe — name the category (board materials, compensation paperwork, legal correspondence), never the contents. Done right, the bullet demonstrates discretion in the very act of describing it.

Show the save

The judgment part of the job — the intercepted disaster — deserves one or two bullets: "caught a double-booked board meeting three days out and rebuilt the day without either party knowing," "rebooked an exec's canceled red-eye overnight; she made the client meeting." These are the admin version of the decision bullet: they prove the thing every duty list fails to prove, which is that you notice problems before they land.

The ladder: EA, operations, chief of staff

Moving up to executive assistant leans on the trust section — exec-level gatekeeping, board cadence, travel complexity. Moving out — operations, chief of staff, project management — is a re-aiming exercise: the office move was a project with a budget, timeline, and vendors; the onboarding program is process design. The work already qualifies; the vocabulary decides which door it opens.

What to cut

"Organized, detail-oriented team player with strong multitasking skills" — the field's densest cliché cluster, and pure duty lists ("answered phones, filed documents, ordered supplies") that the title already implies. Your summary should read like the scope line in miniature: "Admin assistant, 6 years — sole support for 3 VPs and a 40-person org; runs calendars, travel, expenses, and the annual 120-person offsite."

Frequently asked questions