Administrative assistant interview questions that test judgement, not software lists
Most administrative assistant interviews test the wrong thing. Software proficiency is a checkbox that every candidate claims and that two weeks of use settles anyway. What actually separates candidates is judgement under competing priorities, the discretion to sit on information they hear, and whether they have a system for not dropping things. Because dropping things is the only real failure mode of the role.
What the job actually involves
An admin assistant absorbs the work that would otherwise fragment other people's days: diaries, travel, documents, expenses, meeting logistics, and the constant stream of small requests that arrive without warning. Very little of it is difficult on its own. All of it is time-critical, and the volume is what makes it hard.
The role also sits close to information. Who is meeting whom, what is being discussed, who is unhappy. Handling that without becoming a channel for it is part of the job that never appears in the description, and it is one of the few parts that cannot be trained quickly.
The questions, and what a good answer sounds like
Ask these as written. Each one is paired with what a strong answer sounds like, so two people rating the same candidate reach the same conclusion for the same reason.
1. Two people both need something from you by end of day and you can only finish one.
A good answer: Tells both people, quickly, instead of quietly finishing one. Strong answers ask about consequences to decide, and escalate if the two can't be reconciled. The failure mode is silent choosing, which produces one surprised person at 5pm.
2. How do you make sure nothing gets dropped?
A good answer: A specific written system — a list, an inbox rule, a habit of capturing a request the moment it arrives. What you want to hear is that it exists outside their head. 'I'm very organised' is the answer that precedes a missed booking.
3. You overhear something confidential while setting up a meeting room.
A good answer: Nothing. Says so plainly. Any answer that involves mentioning it to a colleague, however casually, is a fail. This role hears a great deal and the norm has to be absolute.
4. Someone senior asks you to do something you think is a bad idea.
A good answer: Says the concern once, clearly, then does it if they still want it. The signal is that they will speak up at all. An assistant who never pushes back is less useful than one who does it well.
5. A meeting has to move and six people's diaries conflict. Walk me through it.
A good answer: Has a method: identify who is essential, propose two concrete options instead of asking for availability, and confirm in writing. Strong answers reduce the number of messages. Weak ones start a thread that runs for a day.
6. You made a booking error that will cost money to fix.
A good answer: Surfaces it immediately with the options and the costs, instead of trying to solve it quietly first. Speed of disclosure is the whole signal.
7. How do you handle a week where the volume is genuinely more than one person can do?
A good answer: Names it before the week ends, with a proposal about what to drop. Candidates who describe working later every night are describing a resignation in month five.
8. What is something you automated or simplified in a previous role?
A good answer: Anything concrete. A template, a recurring booking, a checklist. This separates people who do the work from people who improve it, and on a small team that difference compounds quickly.
A scorecard you can rate against
Rate every candidate 1 to 4 on each row, and write the rating down before you watch the next one. Ratings drift badly when they're relative to whoever you just saw.
| Criterion | What a 4 looks like |
|---|---|
| Transparent prioritisation | Tells both requesters when only one can be done. A 2 quietly picks one. |
| An external system | Describes a written capture method. A 2 relies on memory or general organisation. |
| Discretion | Would repeat overheard information to nobody; a 2 would mention it to a colleague. |
| Appropriate pushback | Raises a concern once and then complies. A 2 either never objects or argues. |
| Early disclosure | Surfaces a costly error immediately with options. A 2 tries to fix it quietly first. |
How to run the screen
- Don't ask about software in the interview. Put it on the application form as a checklist and spend the interview on judgement.
- Ask four questions, capped at two minutes. This role rewards concise clear communication and the format tests it directly.
- Weight the confidentiality question as pass or fail. It is short, it is unambiguous, and the answers vary more than most hiring managers expect.
- Score before moving on. Admin pools are large and the differences are behavioural, which is where memory-based comparison fails hardest.
- Consider a small written task alongside the recording, rescheduling a conflicted meeting in an email. Much of this job is written, and a recording doesn't test writing.
Running this on a large applicant pool is where it gets expensive. VoxScreen sends these questions as a single link, transcribes and scores every answer against criteria you set, and hands back a ranked list. Free for 50 candidates a month, no card.
Common hiring mistakes for this role
- Testing software proficiency. Every candidate claims it, two weeks of use settles it, and it correlates with nothing you care about.
- Treating the role as junior. A good assistant returns hours a week to several people. A weak one costs the same hours back in dropped threads.
- Screening for pleasantness. Pleasant and unable to say 'that won't fit' is how a diary becomes unmanageable.
- Using only a recorded interview. Much of this job is written communication, and a recording tells you nothing about it — pair the screen with a short written task.
- Not asking about the overload week. It is the question that predicts retention, and almost nobody asks it.
Common questions
What should I ask an administrative assistant in an interview?
Ask about competing deadlines, how they avoid dropping things, what they do with overheard confidential information, and how they handle a week with more work than one person can do. Those four cover prioritisation, systems, discretion and retention risk. Software questions belong on the application form, not the interview.
How do I test organisational skills in an interview?
Ask what their system is, specifically, and listen for something that exists outside their head: a written list, an inbox rule, a capture habit. Candidates who answer 'I'm very organised' or 'I have a good memory' are describing the exact conditions under which requests get dropped.
Should administrative assistants be screened with a written task?
Usually yes, alongside the interview instead of instead of it. A large share of the job is written (emails, documents, scheduling threads) and no recorded answer tests that. A five-minute task like rescheduling a conflicted meeting in an email tells you more about the daily work than another spoken question would.
What is the most overlooked quality in an admin assistant?
Discretion, and it is overlooked because it feels obvious. The role hears a great deal simply by being present for logistics, and the norm needs to be absolute instead of sensible. It is worth asking directly, because the answers separate far more sharply than hiring managers expect.