Administrative Assistant Resume Example

Must-have

Core skills & ATS keywords

• Calendar Management
• Scheduling
• Data Entry
• Travel Coordination
• Office Management
• Document Management
• Meeting Coordination
• Expense Reporting
• Correspondence

Tools & tech

Tools and technologies to name

• Microsoft Office
• Outlook
• Google Workspace
• Excel
• Slack
• Concur

Soft skills

Soft skills recruiters look for

• Organization
• Communication
• Time Management
• Discretion
• Multitasking

Strong verbs

Action verbs to start bullets

• Coordinated
• Scheduled
• Organized
• Maintained
• Managed
• Streamlined

Credentials

Certifications that help

• Microsoft Office Specialist (MOS)

Opening questions

1. Walk me through your background as a administrative assistant.

   Keep it to 90 seconds, newest first, and end on why this role. Name Calendar Management and Scheduling early — if they're in the posting, they're on the interviewer's checklist, and this answer sets the agenda for the rest of the conversation.

2. Why are you interested in this administrative assistant position?

   Connect one specific thing about the company or team to your own track record — a product, a market, a way of working. Generic praise reads as a mass application; specificity reads as intent.

3. What does success look like in your first 90 days as a administrative assistant?

   Structure it as learn, contribute, own: understand the team's current Calendar Management setup first, ship something small by week four, and name the area you'd want to own by month three. Asking what THEY consider success is a strong closing move.

4. Why are you leaving your current role?

   Keep it forward-looking and under 30 seconds — what you're moving toward, not what you're escaping. Any negativity about a current employer gets projected onto how you'd talk about this one.

Role-specific questions

1. You're given three urgent requests at once.

   Give your actual triage rule — deadline risk, who is blocked, external commitments — and show that you confirm priorities rather than guessing silently. Managers hire administrators who ask once and then execute.

2. You spot an error in a document going to a client.

   Flag it before it goes, quietly and directly to the owner. Administrative hiring managers value people who catch things without making a public correction out of it.

3. How have you used Calendar Management in a recent project? Walk me through one example.

   Use STAR and end on a number — a percentage improved, hours saved, error rate cut. Mention the tools involved (Microsoft Office, Outlook) by name; concrete stacks are what separates practitioners from keyword-matchers.

4. Tell me about your experience with Microsoft Office.

   Go deeper than "I've used it for X years." Describe one thing you built or ran with Microsoft Office, one limitation you hit, and how you worked around it — knowing a tool's edges is stronger evidence than fluency claims.

5. How do you keep your Scheduling work accurate when you're under time pressure?

   Name your actual quality mechanism: checklists, peer review, a verification pass, automation. Then give one example where the mechanism caught something a rushed pass would have shipped.

6. How would you explain Data Entry to someone outside the field?

   This tests communication, not knowledge. Use one everyday analogy, keep it under a minute, and skip jargon entirely — the interviewer is imagining you in front of a stakeholder or a new teammate.

7. How do you stay current with administration practices and tools?

   Name real sources — specific newsletters, communities, or practitioners — and finish with one thing you learned recently and actually applied. The applied half is what makes the answer credible.

Behavioural questions

1. Describe a time you inherited a mess.

   Show your triage — what you stabilised first, what you deliberately left broken, and how you resisted rewriting everything. Judgement about sequencing is what this question is actually probing.

2. Describe a time you had to say no to a customer or stakeholder.

   The answer should include an alternative offered and the relationship surviving. Saying yes to everything is the failure mode; saying no without a path is the other one.

3. How do you handle competing priorities when everything feels urgent?

   Name a concrete framework — impact vs. effort, deadline risk, stakeholder cost — then give one example of telling someone their request would wait, and how you communicated it. Saying no gracefully is the skill being probed.

4. Tell me about a process you improved. What was the measurable result?

   Name the baseline, the change, and the number: time saved per week, error rate before and after, cycle time cut. If you can't quantify it precisely, give an honest estimate and say how you'd measure it properly today.

5. Describe a time you had to learn something quickly to do your job.

   Name the specific thing, how long you had, and the method — documentation, a mentor, deliberate practice. Finish with how you knew you'd learned enough to be safe rather than just confident.