Examples & writing guide
Assistant resume examples
Updated 17 November 2026
Show the check or decision behind the work: for general US Administrative Assistant resumes, database maintenance, preparing and editing memos, invoices or reports, creating spreadsheets, and preparing presentations offer possible evidence, with duties varying by experience, title, and specialty. Administrative assistants in the United States often prioritize tasks and make decisions on their employers' behalf and should communicate effectively and courteously when interacting with clients, customers, or staff. The entry and senior assistant resume examples below show different responsibility levels; use genuine overlaps with your opening, keeping this page's focus on general administrative support.
Examples by experience level
Administrative Assistant - First full-time role
TemplateTeal Signal2 / 5
Why this works
Record checks, document preparation, and referrals show what Riley contributed in supporting roles. This profile, employers, history, and every achievement figure are fictional and illustrative.
Continue writing your resumeSenior Administrative Assistant - Department operations
TemplateGrey Frame5 / 5
Why this works
Jordan's record checks, recurring workflows, and guidance to colleagues show broader responsibility without formal supervision. The biography, employers, education, and all achievement figures are fictional illustrations.
Continue writing your resumeJunior vs senior: what changes
| Aspect | Junior | Senior |
|---|---|---|
| Professional summary | Entry background: Riley identifies the target Administrative Assistant role while retaining the distinction between internship, customer service, project, and volunteer experience. The 46 corrected discrepancies establish a specific contribution, and supervisor review and exception referral keep the summary within the supporting role. | Senior background: Jordan identifies 10+ years at the title and 13+ years across support roles. The summary selects a recurring control across 5,200 records and an audit result, then explains guidance to four peers without implying formal supervision. |
| Request prioritization and authority | Entry background: Riley orders 25 to 35 daily requests using deadlines, student impact, and staff availability. Routine replies use approved information; policy-sensitive exceptions go to the coordinator. The evidence explains how assigned work is handled within a defined boundary. | Senior background: Jordan organizes about 245 monthly requests across a shared queue and guides four colleagues on priorities and coverage. A daily deadline and dependency review addresses a wider coordination problem, with completion measured across consecutive six-month periods. |
| Problem solving | Entry background: Riley checks records against forms and folders, corrects assigned discrepancies, and uses equivalent monthly retrieval checks to describe the outcome. The project entry separately shows how incomplete or duplicate contact details went to a coordinator before approved corrections were applied. | Senior background: Jordan establishes recurring duplicate, naming, and missing-field checks rather than describing a single cleanup. Baseline and fourth-quarter audits each cover 500 records, making the accuracy comparison understandable and showing continued responsibility for the control. |
| Stakeholder communication | Entry background: Riley describes routine student inquiries, customer follow-ups, resident availability checks, and complete referrals. Each setting shows an audience and purpose, while the internship and project entries identify the colleague responsible for exceptions or approval. | Senior background: Jordan coordinates recurring staff, customer, and vendor meetings, prepares materials from approved content, and tracks assigned follow-ups. The broader example connects communication with owners, deadlines, and dependencies across a department rather than suggesting executive-specialty access. |
| Records, documents, and presentation | Entry background: Riley combines a 720-record internship database, reviewed workplace documents, a service-task spreadsheet, and dated academic presentations. Education and projects add distinct evidence, with the spring 2025 capstone aligned to graduation and the community project separately dated in 2024. | Senior background: Jordan's recent employment supplies the main evidence: 5,200 operational records, recurring meeting materials, and request controls. Earlier employment adds document-return and retrieval-time comparisons, so the education entry can remain shorter while still preserving an accurate history. |
How to write an assistant resume
Build your assistant resume around the work you can explain clearly. Use reverse-chronological experience, with the latest position first, and give a relevant internship or project enough prominence to show its value. Choose the shortest readable length that covers useful evidence; remove repetition before shrinking the text. Keep original titles, consistent dates, and visible contact details.
UC Davis Career Center recommends tailoring a US resume to each application, selecting relevant content and incorporating words and phrases from the job description. Start by marking the opening's duties, qualifications, and submission directions. Beside each relevant duty, note a real example from your history. Adopt a phrase only when it describes that example accurately. A term in the posting is a prompt to examine your experience, rather than permission to add a claim.
Draft experience before the professional summary. That gives you a set of established facts to draw from and helps prevent a polished opening from promising more than the rest of the document demonstrates. Then arrange the sections around the strongest relevant evidence. Education or a substantive project can move higher for a first-role applicant; recent employment may deserve more space when it supplies stronger material.
| Section | Writing decision |
|---|---|
| Contact details | Include your name, city and state, professional email, and phone; add a relevant profile URL if useful. |
| Professional summary | Select the target role, relevant background, and one supported contribution. |
| Experience | Give titles, employers, dates, personal actions, useful scope, and outcomes. |
| Skills | Connect each selected capability to evidence elsewhere. |
| Education | Use accurate award wording, field, institution, and completion status. |
| Extras | Keep projects, volunteering, or development that add a distinct capability. |
For US resume presentation, University of Pennsylvania Career Services recommends white space and spacing between sections; UC Davis Career Center recommends clear headings and bullets instead of dense text blocks. Apply those ideas with restrained styling. The table here is a planning aid for the guide, rather than a suggested layout for your submitted resume.
Riley's supporting roles show how to present first-role preparation without retitling earlier employment. Jordan's example puts recurring controls, competing requests, and peer guidance into the experience itself. Use the same approach when adapting an assistant resume template: let the evidence determine emphasis instead of filling every available box.
Finish by checking the document as a whole. Can a reader connect each summary claim and important skill to a dated example? Are the dates consistent across employment and education? Does an optional section answer a useful question about your preparation? Follow the target application's stated file, naming, and submission directions, and check that the submitted version remains readable.
Professional summary examples
Entry professional summary, fictional and illustrative: "Administrative Assistant candidate with office support internship, customer service, project, and volunteer experience. Corrected 46 naming or indexing discrepancies across more than 720 student and program records during the first four internship months. Prepares documents for supervisor review and handles routine requests while referring policy-sensitive decisions to the office coordinator." Senior professional summary, fictional and illustrative: "Administrative Assistant with 10+ years at this title and 13+ years across administrative support roles. Established monthly checks across 5,200 active operational records, raising verified accuracy from 95.4% to 99.2% in equivalent quarterly audits. Coordinates recurring department workflows and guides four administrative colleagues on priorities and coverage without formal supervisory responsibility." Both versions select evidence already established in the worked resumes. Riley identifies supporting experience and the review boundary; Jordan identifies sustained scope and a measured process improvement. When drafting your assistant resume summary, replace these details with your own facts rather than borrowing the figures or tenure.
"Hardworking and motivated assistant seeking a challenging position with a good company. Organized, friendly, and comfortable handling many office duties independently or with a team." This opening gives no setting, scale, method, or identifiable contribution. Replace a broad adjective with a specific example from your experience, then check that the fuller account appears below. Keep the summary focused on the opening instead of trying to cover every possible assistant role.
Writing your experience
Write each achievement as a short account of your own work: an accurate action, a task and its scope, a useful method or constraint, and an outcome when one exists. Give each bullet one main story. A record-checking example can explain accuracy; a request example can explain prioritization. Combining unrelated tasks into one long sentence makes both harder to assess.
For US resume experience descriptions, University of Pennsylvania Career Services recommends replacing vague openings such as "helped" or "responsible for" with a verb that accurately identifies the applicant's contribution. Prepared, checked, updated, compared, coordinated, routed, and introduced can make that contribution clear. Choose the verb after deciding what you personally controlled. A stronger-sounding verb is useful only when it remains true.
For general US Administrative Assistant work, possible examples include maintaining databases, preparing or editing memos, invoices and reports, creating spreadsheets, preparing presentations, and arranging staff meetings; duties vary by experience, title, and specialty. Administrative assistants in the United States often prioritize tasks and make decisions on their employers' behalf, and they should communicate effectively and courteously when interacting with clients, customers, or staff. Select the activities that match your history rather than treating this range as a checklist.
These rewrites draw on the fictional worked profiles. Their figures are teaching examples, not targets or numbers to copy.
- Before: "Maintained office records." After: "Checked more than 720 student and program records against source forms and active folders; corrected 46 naming or indexing discrepancies in four months, while unsuccessful retrievals fell from 11 to 3 in equivalent 60-record monthly checks."
- Before: "Helped prepare documents." After: "Prepared attendance reports, memos, invoice cover sheets, and presentation slides; proofread 96 documents against supplied figures and templates during the first four months before supervisor review."
- Before: "Handled department requests." After: "Organized about 245 monthly administrative requests and guided four colleagues on priorities and coverage; introduced a daily deadline and dependency review, increasing completion by agreed dates from 87% to 97% across consecutive six-month periods."
The records rewrite identifies the material checked, the method, the period, and a comparable quality check. It does not turn the correction count into a claim that Riley designed the database or set records policy. The document rewrite gives useful scope without a percentage and preserves supervisor review. The senior rewrite shows wider coordination and a process change while keeping peer guidance separate from formal supervision.
Build your own measures from records you are permitted to use. Depending on your history, that might mean a request log, a document register, a project tracker, or a recorded quality review. Explain the period behind a total. "Checked 96 documents during four months" means something different from "checked 96 documents each month." Keep the distinction visible, and avoid figures reconstructed from memory merely because they sound plausible.
A before-and-after measure also needs a sensible comparison. State what was counted, when it was counted, and whether the checks used comparable methods. In Jordan's example, both database audits inspect 500 records against approved source documents. That definition helps explain the change in verified accuracy. If you cannot establish a comparable baseline, describe the work and the recorded outcome without claiming a precise improvement.
Be careful with causation. A team may improve a result while several things change at once. Describe the control you introduced and the observed result, but avoid taking sole credit for work shared with others. If your contribution was maintaining the tracker, obtaining missing information, or checking deadlines, say that. A clear account of one useful contribution is stronger writing than a claim to have transformed an entire operation.
Keep preparation, recommendations, and approvals distinct. Riley can describe checking source forms and applying coordinator-approved corrections. That does not establish authority to settle disputed information. Jordan can describe organizing a queue and guiding colleagues through an agreed process without claiming performance management. If you proposed an improvement and a manager approved it, explain your proposal and implementation rather than suggesting you made the final policy decision.
A numerical outcome is optional. Completing a reviewed packet by its deadline, identifying a conflict before a session, or giving a colleague a usable contact list can provide a meaningful ending. Add the context that lets someone understand the contribution. Riley's community project identifies the listening sessions, the coordinator's role, and the agreed document deadlines; those details carry the story without a percentage.
Communication needs the same precision. Identify whom you contacted, why, and what happened next. A routine status reply differs from a disputed request that you referred to a coordinator. If you gathered missing details before referral, describe that preparation. Avoid a general claim about resolving issues when your actual contribution was recognizing an exception and sending a complete case to the person authorized to decide it.
Connect software to the task you actually performed. Describe a spreadsheet's deadline fields or the source check behind a presentation, rather than naming software alone. Keep course practice separate from workplace use. A class project can demonstrate a real method, but it does not establish that you used the same product in employment. Mention document types only when you genuinely prepared or edited them.
For recurring work in a current position, use present tense. Use past tense for former roles and completed changes or projects. A current entry can contain both: "Maintains the request log" describes continuing work, while "introduced a daily review" describes a completed change. Keep that distinction deliberate instead of changing tense midway through the same activity.
After drafting, remove repeated demonstrations of the same capability. Keep the strongest account, then use another role to show a different method, audience, or constraint. Move genuine overlaps with the opening higher within each role. Retain dependable recurring work alongside distinct improvements so the entry explains both the workload and what you contributed to it.
Before keeping a bullet, ask whether its opening verb matches your action, its scope is explainable, and its outcome follows logically. Check the measurement period and any comparison method. Separate team results from your contribution and final decisions from preparation. Finally, confirm that every tool, document type, audience, and review boundary reflects what happened. Remove a doubtful figure or replace it with honest scope; do not estimate a result to complete the formula.
Key skills & ATS keywords
Hard skills
Soft skills
ATS keywords
Education & certifications
Use this section to describe your own education accurately, then compare it with the particular opening. Give the official award, field of study, institution, and completion date. Check the wording against your records rather than relying on a shortened title you remember. The degrees in the fictional profiles describe those candidates' histories; use your own awarded title rather than copying their education into an assistant resume sample.
Distinguish completed, ongoing, and incomplete study. For a completed program, give the award and completion year. For ongoing study, identify it as ongoing and use an expected date only when you have a reasonable basis for that date. If you left without receiving the award, describe completed coursework when relevant without formatting the entry as a conferred degree. A neat layout should never change the meaning of the record.
Place education according to the evidence it contributes. Riley's final-year project provides an additional example of process analysis and presentation work. Its spring 2025 date agrees with the graduation year, while the separate community project took place in 2024. Check similar relationships in your own history. A project completed before the final academic year should not become a final-year project merely because that wording sounds stronger.
Select academic notes carefully. Identify the assignment, what you personally did, and a useful outcome. If you maintained the task tracker for a group project, describe that contribution rather than claiming all of the group's decisions. If a coordinator or instructor reviewed the work, keep that boundary when leaving it out would exaggerate your responsibility. A short project description can stand on its own without an impressive grade or a numerical improvement.
For a more experienced applicant, shorten academic detail when recent employment supplies clearer evidence. Jordan's degree remains a concise record, with a capstone note showing an earlier contribution to process review. You could remove a similar note if it repeats stronger recent work. Keep education detail because it answers a useful question about your preparation, rather than because the template leaves room for it.
Historical US Administrative Assistant job-posting data for January–December 2023 included mentions of prior administrative experience; employers' expectations were employer-dependent, rather than a universal minimum duration. Read the actual opening to understand how it describes experience and education. Present your background against that wording without treating an illustrative tenure, or one employer's preference, as a rule for the occupation.
When reading a posting, keep its distinctions between requested, preferred, and optional qualifications intact. If it expressly accepts experience as an alternative to education, explain the experience you have. If a role-specific qualification appears in the posting, describe your own position accurately instead of implying that a different award is equivalent. Do not claim an award, completion date, or status that your documentation does not support.
Separate professional development from certification. A completed course can document instruction without establishing a professional certification or workplace competence. Use the official course title, provider, completion date, and honest completion status. If a course remains in progress, say so. Partial attendance should remain partial attendance. Retain development that adds distinct evidence relevant to the opening, and remove material included only to lengthen the section.
For any credential you choose to list, reproduce its name and issuer accurately from your documentation. Include the award date and applicable status or expiry information honestly. Keep this record separate from an experience bullet demonstrating actual use of the skill. Training and performance can support each other, but they describe different things; completing instruction does not by itself establish that you performed a particular workplace task.
Before submitting, review the section alongside the rest of the resume. Confirm that study dates agree with project descriptions and that no ongoing program appears completed elsewhere. Remove duplicated course lists, retain useful first-role evidence, and check any information the target application explicitly requests. This final comparison should leave a concise, accurate account of what you studied or earned and how it supports this particular application.
Common mistakes to avoid
AvoidCopying a large skills inventory into every assistant resume.
InsteadTailor your resume to the opening. Keep relevant information and use wording from the job description only when it accurately describes your experience. Cut entries you cannot connect to your own work, study, or volunteering.
AvoidListing skills without showing where they were used.
InsteadGive important capabilities a dated example. Describe the records you checked, the document you prepared, or the deadline you tracked. Show interpersonal skills in your experience too: explain whom you contacted, why, and how you handled the request.
AvoidBorrowing posting language that inflates supporting work.
InsteadKeep the original job title and identify your actual contribution. Preparing options, applying approved corrections, and referring exceptions can all supply useful evidence. Do not turn those actions into claims that you approved decisions or set policy.
AvoidInventing a connection between software and a task.
InsteadDescribe what you actually did with the product. Separate classroom practice from employment, and remove any claim about reports, presentations, or database work that you cannot explain through a real assignment.
AvoidTreating one vacancy's preferences as the standard for every opening.
InsteadKeep the preference attached to that application. Compare its wording with your history instead of rewriting your background to fit it. A useful resume for assistant work presents your preparation clearly while preserving the boundaries of your experience.
AvoidUsing adjectives instead of an identifiable contribution.
InsteadReplace "organized" or "accurate" with the work behind it: a source check, a deadline review, or a complete referral. Use a defensible scope measure when useful; if no outcome was measured, explain the context without inventing a number.
Frequently asked questions
Start with genuine coursework, volunteering, service employment, internships, or projects, and select an assignment you can explain from beginning to outcome. Keep original titles and state your contribution, including any review or approval boundary. Riley's example shows supporting experience presented as preparation for a first full-time title.
Compare the opening with work you have already done, then select the strongest truthful overlaps rather than renaming your previous occupation. Explain the setting, your action, and a useful result or scope measure. Keep unfamiliar responsibilities out of the summary even when the posting gives them prominence.
Check the target application's explicit presentation instructions. When planning the page, prioritize readable space for relevant experience, skills, education, and contributions rather than adding an element simply because a template includes it.
Read the particular posting and compare its qualification wording with your own records. If you list a credential, use its documented title, issuer, and completion information; keep course attendance separate from certification and avoid implying an award you have not earned.
Name a product when you genuinely know or have used it, and describe that knowledge accurately. Distinguish a class exercise from workplace use, and explain the actual task rather than inventing a connection because a product and a responsibility both appear in the posting.
For US Administrative Assistant work, possible evidence includes database maintenance, memo, invoice or report preparation and editing, spreadsheets, presentations, and staff meeting arrangements; duties vary by experience, title, and specialty. Administrative assistants in the United States often prioritize tasks and make decisions on their employers' behalf and should communicate effectively and courteously when interacting with clients, customers, or staff. Select the genuine overlaps between your experience and the opening.
From example to application
Turn this assistant example into a resume that sounds like you.
Keep the structure that works. Tailor the details around your experience, strengths, and the role you want.