Administrative Assistant CV Example
An administrative assistant CV is usually read by an office manager, an HR coordinator, or the executive you would support, and they are screening for one thing above all: can this person keep an office, a calendar, and a dozen competing requests running without dropping anything. Administrative hiring rewards proof of reliability, not adjectives. The software you can actually use is checked literally - Microsoft Office, Outlook, Google Workspace, and increasingly tools like Slack, Asana, or a named CRM - so list the exact systems the role mentions, because fluency means you are useful from day one. Volume is screened too: most administrative roles attract hundreds of applicants and are filtered by an ATS before a human sees them, so a clean, standard structure beats a decorative template every time. The summary has to open with scope - how many people you have supported, how large the calendars and budgets were, how many systems you ran - not with the word 'organized'. And the bullets that win quantify: 'answered phones and filed documents' loses to 'managed calendars for 4 executives, processed 60+ expense reports a month, and cut supply costs 18% by renegotiating two vendor contracts'. This example covers the structure that surfaces those signals in the order an office manager looks for them, the summary and software sections that prove you can do the job, the skills block, the experience bullets that win shortlists, and the common mistakes that drop strong candidates below the cut. Everything is editable in the Cvida builder - use it as a starting point and tailor it for your software stack, the size of the office, and the seniority of the role you are targeting.
Why an administrative assistant CV is different from a generic CV
Administrative hiring runs on signals generic CV advice tends to skip. Start with what makes it different:
- Reliability is the product: an office manager is hiring someone to make sure nothing slips, so every line should signal that you are organized, accurate, and unflappable under a heavy, interrupt-driven workload - not just that you held the title.
- Software is checked literally: Outlook, Excel, Word, Google Workspace, scheduling and travel tools, and any CRM or ERP the role names. List the exact systems you can use, because 'proficient in office software' tells a screener nothing they can act on.
- Volume and the ATS come first: administrative roles draw huge applicant pools and are almost always filtered by an applicant tracking system before a person reads them, so a clean, standard, single-column layout beats anything decorative.
- Scope is the differentiator: 'supported the team' could mean two people or two hundred. State how many executives or staff you supported, how many calendars and inboxes you ran, and the size of the budgets or expense volumes you handled.
- Discretion matters: admins handle confidential information, payroll, and executive calendars, so signals of trustworthiness and professional judgement carry real weight - name them where you can show them, not as empty adjectives.
Treat your CV as evidence that an office runs smoothly because you are in it. An office manager should be able to confirm your software, your scope, and a reason to trust you with their calendar inside two minutes - and if they cannot, you do not make the shortlist no matter how capable you actually are.
The CV structure that works for administrative roles
Administrative reviewers scan in a fixed order and an ATS parses top to bottom, so use a clean, predictable structure rather than a creative one:
- Header: name, target title ('Administrative Assistant' or 'Executive Assistant'), phone, a professional email, city, and a LinkedIn URL. Skip the photo, date of birth, and full home address - they add ATS risk and no value.
- Professional summary: three or four lines stating your years of experience, the software you run, the scope you have supported, and one quantified win. It is the first thing read, so make it earn the rest of the page.
- Key skills: a compact block of the software and competencies the job posting names, so both the ATS and a human can match you in seconds.
- Experience: reverse-chronological, most recent first, each role with three to six quantified bullets - not a copy of the job description.
- Education and certifications: kept brief, with any administrative, software, or bookkeeping certificates that strengthen the application.
- Optional extras: languages, a short technical-tools line, or volunteer coordination - only if they support the target role.
- Length and format: one page for under ten years of experience, two at most, saved as a PDF with a standard font and no tables, text boxes, or columns that an ATS can misread.
The order matters as much as the content: an office manager reading top to bottom should reach your software and scope before anything else. A clean structure is not a missed chance to stand out - for administrative roles it is exactly the professionalism the job is screening for.
The fundamentals of CV structure and length this example builds onThe professional summary: scope, software, and the reliability signal
Your summary is the one paragraph guaranteed to be read. For an administrative assistant it should prove scope and software in the first line, not announce that you are organized:
- Open with scope and years: 'Administrative assistant with 6 years supporting C-level executives in a 200-person office', not 'hard-working and detail-oriented professional'.
- Name the software immediately: the systems you run - Outlook, advanced Excel, Google Workspace, a named CRM - belong in the first two lines, because that is what the screener and the ATS are matching against.
- Include one quantified win: a cost saving, a process you streamlined, or the volume you handled, so the summary carries proof and not just claims.
- Match the target title: echo the exact role name from the posting ('Executive Assistant', 'Office Administrator') so the reader and the ATS see an immediate fit.
- Keep it to three or four lines: a summary that runs longer stops being a summary and pushes your experience below the fold.
A strong administrative summary reads like a one-sentence reference: this person ran this scope, on these systems, with this measurable result. Lead with adjectives instead and you sound like every other applicant in a pool of hundreds.
How to write a CV summary that opens with proof, not adjectivesSoftware and tools: the section that gets you past the filter
For administrative roles, software is often the single biggest filter - list it explicitly and accurately rather than burying it in prose:
- Office suite: name the specific applications and your real level - 'advanced Excel (pivot tables, VLOOKUP, macros)' says far more than 'Microsoft Office'.
- Communication and scheduling: Outlook, Gmail, calendar management, Zoom, Teams, and any travel-booking tool you have used to coordinate executives.
- Project and task tools: Asana, Trello, Monday, or Slack - increasingly expected even in traditional admin roles, so include the ones you actually know.
- Business systems: any CRM, ERP, HRIS, or accounting tool (Salesforce, SAP, QuickBooks, an HR portal) named in the posting, listed with honest proficiency.
- Be truthful about level: distinguish 'proficient' from 'familiar', because software claims are the easiest thing for an interviewer to test on the spot.
Mirror the exact tools the job posting lists, in the posting's own words, so the ATS scores a clean match and a human sees instant fit. A precise software section is often what moves an administrative CV from the rejected pile to the interview pile.
The skills block: software, organization, and communication
Administrative work blends hard tools with the soft skills that keep an office running. Show both, but anchor each in something concrete:
- Hard skills: the software stack, data-entry accuracy and speed, calendar and travel management, minute-taking, expense processing, and document control.
- Organizational skills: prioritization across competing requests, deadline management, and the ability to keep multiple executives' workflows running at once.
- Communication: professional written and verbal communication, since admins are often the first point of contact for clients, vendors, and staff.
- Discretion and judgement: handling confidential information, payroll, and executive schedules without supervision - a core trust signal for the role.
- Avoid empty adjectives: 'hard-working' and 'team player' are unprovable filler; replace them with skills a reader can picture you doing on day one.
Pick the skills the specific posting emphasizes rather than listing everything you can do. A focused block that mirrors the job's language reads as a candidate who fits the role, not one applying to every office job in the city.
How to choose and present the skills that actually move a CVExperience bullets: from 'answered phones' to measurable impact
This is where most administrative CVs fall flat - listing duties instead of impact. Every bullet should show scope, action, and a result a reader can measure:
- Quantify the scope: 'managed calendars and travel for 4 senior executives' beats 'responsible for scheduling', because numbers turn a duty into a measure of capacity.
- Show cost and efficiency: 'cut office-supply costs 18% by renegotiating two vendor contracts' or 'reduced invoice processing time from 5 days to 2' proves business value, not just activity.
- Lead with strong verbs: coordinated, streamlined, implemented, processed, negotiated - not 'responsible for' or 'duties included', which read as passive.
- Show volume: 'processed 60+ expense reports and 200+ invoices monthly with 99% accuracy' signals you can handle a real workload without errors.
- Tie work to outcomes: connect what you did to a result - a smoother onboarding, an event delivered on budget, a manager freed to focus on higher-value work.
A reviewer should be able to read any single bullet and know both what you ran and how well it went. 'Answered phones and filed documents' describes a job title; 'cut processing time 40% across a 200-invoice month' describes a person worth interviewing.
How to write CV achievements that quantify in reach, time, or impactEducation, certifications, and entry routes
Administrative roles value proven capability over a specific degree, so keep this section short and let certifications and software do the talking:
- Lead with relevance: a high-school diploma, an associate degree, or a bachelor's is fine - admin hiring rarely requires a specific major, so do not over-weight it.
- Highlight certifications: Microsoft Office Specialist (MOS), an administrative professional certificate (such as CAP), or bookkeeping credentials signal job-ready skills directly.
- Show software training: short courses in advanced Excel, a named CRM, or QuickBooks count for more here than they would in many other fields.
- Use transferable experience: retail, hospitality, and customer-service roles demonstrate the organization, multitasking, and people skills admin work depends on.
- Keep it brief: for an experienced admin, education sits at the bottom in two or three lines - your experience and software carry the application.
Career-changers and first-job applicants should lean on this section and the skills block to prove capability the experience cannot yet show. Name the certificate, the software course, the transferable role - concrete evidence of readiness beats a generic line about being a fast learner.
Common mistakes that sink administrative assistant CVs
Most administrative CVs are rejected for a handful of avoidable reasons. Check yours against this list before you send it:
- A duties-list with no numbers: 'answered phones, filed documents, scheduled meetings' describes the title, not your impact - quantify scope and results instead.
- Vague software claims: 'proficient in office software' fails the ATS keyword match; name Excel, Outlook, the specific CRM, and your real level.
- Decorative templates: tables, columns, text boxes, and graphics that look polished to you are frequently misread or dropped entirely by an ATS.
- A generic, one-size-fits-all CV: sending the identical document to every role ignores the exact software and title each posting names, and screeners notice.
- Typos and formatting slips: for a role whose entire value is accuracy and attention to detail, a single error on the CV is disqualifying - proofread twice and have someone else check.
Administrative hiring is, at its core, a test of reliability and attention to detail - so a CV that is precise, ATS-clean, quantified, and tailored is itself the strongest evidence you can do the job. Fix these five and you clear the bar most applicants fail.
How to get your CV past the ATS filters that screen admin rolesFinal notes and the hiring-manager test
Before you submit, run your administrative assistant CV through the test an office manager applies in the first scan:
- The software check: can a reader see, in the first third of the page, the exact systems you can use? If not, move them up.
- The scope check: is it instantly clear how many people you supported and how heavy the workload was? Numbers, not adjectives.
- The reliability check: does the CV itself look accurate, consistent, and error-free - the very qualities the job is hiring for?
- The tailoring check: does it echo the title and tools of this specific posting, or could it have been sent to any office in the country?
- The ATS check: is it a single-column PDF with standard headings, no tables or graphics, and the posting's keywords present in natural language?
If your CV passes all five in a thirty-second skim, it will clear the filter that rejects most of the pool. Build it in Cvida, tailor it to each posting's software and scope, and you give an office manager every reason to trust you with their calendar - which is the whole job.