ROLE GUIDE
Administrative assistant interview questions
The job looks like calendar management and email. The interview is really about what happens when two priorities collide, a confidential document arrives, and three people believe their request is urgent.
What the interview is really testing
| Competency | What they listen for | A weak answer sounds like |
|---|---|---|
| Prioritisation | You can rank competing requests and explain the trade-off | “I do whatever is most urgent.” |
| Organisation | A system for calendars, documents and follow-ups | “I have a good memory.” |
| Discretion | You know what not to share and where information lives | “I would ask my colleagues what they think.” |
| Communication | Clear, early updates when a deadline is at risk | “I would just work late and hope it is fine.” |
| Tool comfort | Calendar, email, spreadsheets and document formatting | A long list of tools you cannot describe using |
12 questions and answer checkpoints
1. How do you prioritise when everything is urgent?
Name your criteria: impact on customers or revenue, hard deadlines, dependency on others, and the cost of being late. Then say how you communicate: “I would confirm the deadline with both requesters, tell the one who can wait what will slip, and give a new time.” A concrete example is better than a productivity philosophy.
2. Two managers give you conflicting deadlines. What do you do?
Do not choose silently. Confirm the actual deadline and consequence with each, surface the conflict, propose a sequence, and ask the more senior or accountable person to decide if the trade-off is real. Then tell both what you will deliver and when.
3. How do you handle a confidential document?
Share only with the people who need it, use approved storage and access controls, do not forward it to a personal account, and ask before copying anyone. If you are unsure, ask the owner rather than guessing.
4. Tell me about a time you caught a mistake before it became a problem.
Show the check you performed, what you noticed, what you did, and what you changed afterwards. The interviewer wants evidence of attention to detail, not a story about working late.
5. How do you manage a busy calendar?
Talk about buffers, time zones, recurring commitments, travel, and how you handle last-minute changes. Mention that you confirm the purpose and duration before accepting an invitation, and that you protect focus time where the role allows it.
6. A client is waiting and your manager is unavailable. What do you do?
Acknowledge the client, give a realistic time, find the information you are authorised to share, and escalate through the agreed channel. Do not improvise a commitment your manager has not approved.
7. How do you keep track of follow-ups?
Describe a real system: a task list with dates, flags in email, a shared tracker, or a daily review. Explain how you make sure nothing falls through when you are away.
8. Tell me about a time you had to say no.
Show that you protected a priority without being obstructive. Explain what you declined, what you offered instead, and how the requester responded.
9. How do you handle a colleague who repeatedly misses deadlines?
Start with a direct, private conversation about the impact and the next deadline. If it continues, document it and involve the manager. Avoid gossip and avoid silently absorbing the work forever.
10. What tools are you comfortable with?
Be specific and honest: calendar, email, Word, Excel, PowerPoint, shared drives, video conferencing. Say what you have actually used and what you would learn. Do not claim advanced Excel if you have only used it for lists.
11. How do you handle a mistake you made?
Fix the immediate issue, tell the person affected, explain what happened, and change the check that failed. The interviewer is listening for ownership and a low-drama correction.
12. Why do you want this role?
Connect the work to what you are good at and what you want to learn: making a team run smoothly, owning a process, or building expertise in a particular industry. Avoid “I just need a job”.
Scenario: two managers, one afternoon
The classic administrative scenario is a scheduling collision. Use a sequence that protects the relationship and the deadline.
- Clarify the real deadline. Ask each manager what happens if the item slips. A “today” request is sometimes a “this week” request in disguise.
- Check dependencies. Does one task unblock the other? Does a client or a regulator set the time?
- Propose a sequence. Offer the earliest realistic slot for each and say what you will finish first.
- Escalate the trade-off, not the emotion. If both are genuinely immovable, ask the accountable manager to choose.
- Confirm in writing. Send a short message to both with what will happen and when.
I would first ask both managers what the deadline is driving, because “by 3pm” often means “before the client call at 3:30”. If both are real, I would tell them the conflict and propose that I finish the board pack first because it has an external deadline, then the travel itinerary by 4:30. If that is not acceptable, I would ask them to agree the order between themselves and confirm it in an email so there is no ambiguity later.
No direct experience? Use these examples
- Study or university: coordinating a group project, managing a shared calendar, formatting a dissertation, chasing contributions.
- Volunteering or a society: organising an event, keeping a budget, managing a shared inbox, taking minutes.
- Retail or hospitality: handling rota changes, cashing up, resolving a booking conflict, keeping a handover log.
- Family or freelance work: invoices, schedules, supplier email, travel. Describe the work, not the relationship.
Translate the activity into a transferable mechanism: “I kept a shared tracker for 12 volunteers, confirmed each shift the day before, and reduced no-shows” is stronger than “I helped organise an event”.
The mistakes that cost the interview
- Saying you are “organised” without describing a system. Show the list, the check or the handover.
- Pretending every request is equally urgent. The job is prioritisation; a flat answer signals you will burn out or miss the important item.
- Sharing confidential information to prove you are helpful. Discretion is a core requirement.
- Overclaiming software skills. Interviewers often ask a follow-up task; be accurate about your level.
- Criticising a previous manager. It raises a trust question before you have started.
A five-day practice plan
- Day 1: write three examples of organising other people’s work, using the situation-action-result format.
- Day 2: practise the conflicting-deadlines scenario out loud, including what you would say to each manager.
- Day 3: make a list of the tools you actually know and one task you can describe in detail.
- Day 4: practise the confidentiality answer and one “tell me about a mistake” story.
- Day 5: run a mock interview and review whether your answers included a system, a trade-off and a follow-up.
These guides are written and maintained by MockInterview as original practice material. They are not leaked employer questions, and no employer has reviewed or endorsed them. Sample answers are illustrative; use your own examples and verify role requirements, licensing and local policy with the employer. Last updated 2026-11-03.