Administrative assistant interviews test whether people can hand you their day and stop worrying about it. Expect a few questions on why you want the role, stories about juggling several bosses, fixing your own mistakes and keeping secrets, what-would-you-do scenarios like a double-booked calendar or a rude caller, and practical checks on minutes, travel, filing and spreadsheets. Each question shows what the interviewer is really listening for, a shape for your answer, and a short answer you could say out loud. Swap in your own examples before the day.
Search all questions by round, difficulty and level, or save the ones you want to practise.
Path: the short version of how you got here, one or two roles or experiences.
What you enjoy: a specific part of the work, such as bringing order to a messy week.
Why now: why this role is the right next step.
"I started by helping out at the front desk of a small accounting office while I was studying. Within a few months I was running the partners' diaries and the filing, mostly because I kept tidying things nobody else had time for. What I found I really enjoy is being the person who makes a busy week feel calm for everyone else. When a manager walks into a meeting with the right papers and no surprises, that's my work, even if nobody sees it. Since then I've supported a team of five in a larger office, and I'm ready for a role with more responsibility, like managing senior calendars and organising bigger meetings."
Saying you fell into it and any office job will do, with nothing you actually like about the work.
What you found: the team's work, size or pace, from the job ad, website or people you spoke to.
What that means for support: the kind of help they probably need most.
Your fit: why your experience matches that.
"From the job ad and your website, it looks like the directors travel a lot and the team runs a lot of client meetings, some across different countries. So I'd guess the support that matters most here is keeping calendars and travel under control and making sure meetings run on time with the right papers. That's the part of my last job I was best at. I managed travel for three managers and scheduled calls across time zones every week. I also liked that the ad mentioned owning the office day to day, because I enjoy looking after suppliers and the space itself, not just the diary."
Reading the company's mission statement back without a word about the people you'd support.
Two or three things: real tasks you owned completely.
Proof: one small example for each.
Honest gap: one thing they'd say you're still working on.
"I think she'd say three things. First, her calendar: she stopped checking it herself because I kept it right and sent her a short plan for the next day every evening. Second, travel: I booked everything, and when a flight was cancelled she'd usually get a message from me with a new option before the airline told her. Third, the office itself, suppliers, repairs, stationery, the things that only get noticed when they go wrong. If she's honest, she'd also say I sometimes took on too much without asking for help. I've got better at saying early when a deadline won't work, rather than staying late to hide it."
Listing personality words like organised and hard-working with no task or example behind them.
The mistake: what went wrong, in plain words, owned by you.
The fix: what you did straight away and who you told.
The change: the habit or check you added afterwards.
"In my first year I booked a meeting room for the right day but the wrong week, for a client meeting my manager was hosting. I only noticed two days before, when I did my usual look at the week ahead and the booking wasn't there. The room was taken, so I told my manager straight away, found a room on another floor, and updated the invite and the reception list. The client never knew. What I changed was simple: I now read the full date back from the confirmation email, not just the day, and I check every external meeting against its room booking in my Friday review. I haven't had that mistake since."
Picking a fake mistake like working too hard, or blaming the system or a colleague.
The request: what was asked and why it was a problem.
How you said it: the actual words, respectful and specific.
The alternative: what you offered instead and how it ended.
"A director asked me to book a team dinner for thirty people for that Friday, but I was already committed to preparing the board pack for my own manager, due the same afternoon. I didn't want to just say I was busy, so I said, 'I can do the dinner, but it would push the board pack back half a day. Would you like me to check with Sam which matters more, or can I book it Monday for the following week?' He actually didn't know about the board pack. He chose the next week, and later thanked me for flagging it. I've learned that senior people usually don't mind a no if they get the reason and a choice."
Either saying you never push back on seniors, or describing a blunt refusal with no alternative.
The gap: why you were on your own and for how long.
What you decided: calls you made yourself and why they were yours to make.
What you held: what you parked for your manager and how you reported back.
"My manager was on leave for two weeks in a remote area with almost no signal. Before she left, we agreed what I could handle: routine scheduling, supplier orders under our usual limit, and replies to standard emails. So I moved meetings, approved a stationery order and dealt with a room booking clash without asking. When a client wanted to change the terms of a contract, I didn't touch it. I thanked them, said she'd be back on a set date, and passed it to her deputy. I kept a short log of every decision and every parked item, and on her first morning I walked her through it in ten minutes."
Either doing nothing without permission, or making big decisions that weren't yours to make.
Know the limit: who may sign a contract depends on the company's signing rules, and a quick message usually isn't enough.
Offer a route: e-signature, an authorised deputy, or a scanned signed copy.
Keep it moving: tell the supplier it's coming and when.
"I'd want to help, but I wouldn't sign a contract as my manager just because of a message. A contract commits the company, and who can sign what depends on the company's own signing rules, which usually don't include me. I'd say that openly and offer quicker routes. If we use an electronic signature tool, I can send it to their phone and they can sign in a minute. If not, they can sign and scan it wherever they are, or I can check who else is authorised to sign and ask them. Then I'd tell the supplier the signed copy is on its way and roughly when. If the company does have a written rule that lets me sign certain documents, I'd follow it exactly, but I'd check it first rather than assume."
Copying the manager's signature because they asked, without any thought about authority.
Your preference: honest and specific, not picky.
How you adapt: learning their style early and matching it.
Example: one manager whose style was new to you.
"I work best with a manager who tells me what matters to them and then trusts me to run with it, with a quick check-in each day. But I've worked with very different people. One manager I supported hated email and wanted everything on a short call first thing. Another wanted every detail in writing and never wanted to be interrupted. In the first couple of weeks I just watch and ask. How do you like updates? When should I interrupt you? What drives you mad? Then I adjust to them, not the other way round. Part of this job is making someone else's day run the way they work best."
Describing only one kind of manager you can work with, or criticising past managers.
Honest view: it's true, and that's partly the point.
What motivates you: the outcomes you care about.
How you stay visible: sharing results without seeking praise.
"It's true, and honestly I've made my peace with it. If a board meeting goes smoothly, nobody thinks about the room, the papers or the travel, and that means I did my job. What keeps me going is the satisfaction of a week that runs cleanly, and the trust that builds up when people stop double-checking my work. I also like getting better at things, like building a tracker that saves me an hour a week. I don't chase praise, but I do make my work visible in a sensible way, for example a short monthly note to my manager on what I've improved. That helps with my development conversations too."
Sounding resentful about not being thanked, or saying you need constant recognition to stay motivated.
Situation: who you supported and why it got messy.
System: how you tracked requests and set expectations.
Result: what improved and how people reacted.
"At my last job I supported four managers who all assumed I was theirs first. Requests came by email, chat and people stopping at my desk, and things slipped. So I set up one shared task list and asked everyone to send requests there with a deadline. Each morning I looked at the list and told anyone whose task would wait what time they could expect it. When two deadlines clashed, I asked them to agree, or took it to the senior manager, instead of choosing quietly myself. It took a couple of weeks to stick, but the complaints stopped, and one manager said she liked knowing exactly when things would land instead of chasing me."
Saying you just work faster and never need to prioritise between people.
Check fast: what each task is for and what happens if it's late.
Surface it: tell both managers straight away, with options.
Find a way: split, simplify or get help so both land if possible.
"I wouldn't pick one quietly, because then someone finds out at five that their task didn't happen. I'd spend two minutes finding out what each is for. If one is going to a client or a board and the other is internal, that usually settles it, but it's still not my call alone. I'd message both managers together, something like, 'I've got two tasks due at five and can finish one. Here's what each is for. Can you agree which goes first, or can one wait until nine tomorrow?' Meanwhile I'd start on the one that looks more urgent. I'd also check if a colleague can take part of the other, or whether a shorter version would do for today."
Choosing based on who is more senior or who you like, without telling the other person.
Agree the rules: what you can answer, what you draft, what you never touch.
Sort daily: handle routine, flag urgent, file the rest.
Report: a short summary so they see what needs them.
"First we'd agree the rules, because inbox access is a big trust. Usually I handle scheduling, confirmations, routine requests and anything that just needs forwarding. I draft replies for anything more personal or important, and they approve before it goes. Some things I never act on, like HR matters, pay or anything legal, unless they tell me to. Day to day I go through it a few times, file what's done into folders, and flag what needs them by urgency. At the end of the day I send a short note: these three need your answer today, these can wait, and here's what I've dealt with. Anything I'm not sure about, I ask. It's better than guessing in their name."
Replying in the manager's name on sensitive matters without asking, or leaving everything for them to read.
Sort: deadlines, who is waiting, what happens if it's late.
Plan: quick wins, then the most important work in a focused block.
Tell people: reset expectations early for anything that will slip.
"I start the day by looking at everything on the list and asking two questions: what has a hard deadline today, and what's blocking someone else. Those go first. Then I look for tasks that take two minutes, like confirming a meeting, and clear them so they stop cluttering my head. The bigger important work, like preparing a meeting pack, gets a block of time where I turn off notifications if I can. Anything that clearly won't happen today, I tell the person early, in the morning, not at five o'clock, and give them a new time. If I'm not sure what matters most, I ask my manager rather than guessing."
Saying you just work through it top to bottom, or that you stay late until everything is done.
The problem: what was slow or confusing, and who it hurt.
The change: what you designed and how you got people to use it.
The result: how you knew it worked.
"Our shared drive was a mess. People saved contracts wherever they liked, so finding the latest version of anything meant asking around. I proposed a simple structure: one folder per client, the same subfolders inside each, and a file name rule with the date first, then the client, then the document type. I tested it with two colleagues first, fixed what confused them, then wrote a one-page guide and moved the old files over two quiet afternoons. The real win was that people stopped asking me where things were. When we had an audit a few months later, I pulled every file they asked for in minutes instead of hours."
An improvement that only you understood or used, with no thought about getting others on board.
Structure: a few top-level folders that match how people think about the work.
Naming: one rule for names and versions that everyone follows.
Access and upkeep: who can see what, and a regular tidy-up and archive.
"I'd start by asking how people look for things. Usually it's by client, project or department, so that becomes the top level. Inside, every folder gets the same subfolders, so people learn the pattern once. Then a naming rule, for example the date written year, month, day so files sort in order, then the client, then what the document is. I'd keep one final version and move older drafts to an archive folder, so nobody works from the wrong copy. Access matters too. Confidential folders like HR or contracts are limited to the people who need them. Then I'd write a one-page guide and do a quick tidy each month, because any system drifts if nobody looks after it."
A system that only makes sense to you, or no thought about who should be able to see confidential files.
Core skills: sorting, filtering, simple formulas, conditional formatting.
Useful extras: lookups, counting and summing by condition, drop-down lists.
Something built: one tracker or report and what it saved.
"Day to day I use sorting and filtering, simple sums, and conditional formatting to make things stand out. The most useful thing I built was a stationery and supplies tracker. It had the item, the amount in stock and a reorder level, and a formula that showed Reorder when the stock dropped to that level, with the cell turning red. I added drop-down lists for the supplier so the names stayed consistent, and a summary sheet using SUMIFS to add up what we'd spent with each supplier from the orders log. It meant I placed one planned order a week instead of rushing out when someone found the last box of paper gone."
=IF(C2<=D2, "Reorder", "OK")
=SUMIFS(Orders!D:D, Orders!B:B, A2)
Claiming advanced skills but being unable to describe a single formula or thing you built.
Scale: what the event was, how many people, your role.
Planning: how you tracked venue, catering, guests and materials.
The near miss: what nearly failed and how you rescued it.
"I organised a two-day offsite for about sixty staff at a hotel outside the city. I kept everything on one tracker: rooms, dietary needs, transport, the agenda and the equipment each speaker needed. The near miss was the coach. The morning we left, the company called to say one of the two coaches had broken down. Because I had every guest's phone number and the list split by coach, I booked taxis for that group within twenty minutes and told them to meet at the front entrance instead. We arrived about half an hour late, and I'd already asked the hotel to push breakfast back. Afterwards I added a backup transport number to my checklist for every event."
A story where nothing went wrong, or where the fix was someone else's.
What broke: the cancellation, delay or missing booking.
What you did: the options you found and how fast.
Knock-on effects: meetings, hotels and people you updated.
"My manager's connecting flight was cancelled late in the evening, and she was stuck at the airport with a client meeting at nine the next morning. While she queued at the desk, I checked other flights online and found one leaving early the next morning that still got her there in time. I booked it on the company card, then found an airport hotel so she wasn't sleeping in the terminal. I texted her the booking references in one message, emailed the client's assistant to warn them she might be twenty minutes late, and moved her afternoon call. She made the meeting. Since then I always keep the traveller's booking references and the travel agent's emergency number in one note I can reach from my phone."
Waiting for the traveller to ask for help, or making changes without telling them.
What minutes hold: decisions, actions and key points, not every word.
Judge the request: harmless wording change or removing a real decision.
Route it: changes to a decision go through the chair and the group.
"It depends on what they want removed. Minutes record decisions, actions and the main points, not every comment. So if it's an offhand remark that shouldn't have been in there anyway, I'd happily tidy the wording. But if they want to remove a decision, an action or something they agreed to, I wouldn't quietly change it. I'd say something like, 'I can't change what was agreed on my own, but you can raise it with the chair.' In formal meetings the minutes are usually approved at the next meeting, and that's the proper place to correct a real mistake, so everyone sees the change. I'd keep my own notes too, in case there's a question later."
Changing the record because someone senior asked, or refusing flatly without explaining the proper route.
Before: a template built from the agenda, attendees listed.
During: decisions, actions with an owner and date, key points, not a transcript.
After: a check with the chair and sending within a day or so.
"I prepare before the meeting by setting up a template from the agenda, with the attendees and apologies already filled in. During the meeting I'm listening for three things: what was decided, what needs doing, and who is doing it by when. I capture the main points of a discussion in a sentence or two, but I don't write down who said every word, and I leave out side conversations and jokes. If an action isn't clear, I'll ask in the moment, something like, 'Just to confirm, who's taking that and by when?' Afterwards I tidy it up the same day while it's fresh, get the chair to check it, then send it out with the actions listed at the top so people can find theirs."
Trying to write everything word for word, or sending minutes a week later with actions buried in paragraphs.
Brief: dates, meetings, preferences and the travel policy.
Book: flights, hotels near the meetings, ground transport, sensible connection times.
Check: names match the passport, visas and entry rules, time zones, one clear itinerary.
"I start with the meetings, because they set the dates and the cities, and I check the company travel policy and the manager's preferences, like aisle seats or a hotel they like. Then I book flights with enough time for connections, hotels close to where the meetings are, and transport from each airport. Before I send anything, I check the name on every booking matches the passport exactly, that the passport is valid for long enough, and that each country's visa or entry rules are sorted. I put everything in one itinerary in date order, with local times, addresses, booking references and contact numbers, and I add the flights and meetings to their calendar in the right time zones."
Booking only the flights and forgetting passports, visas or how the traveller gets from the airport.
Weigh it: which meeting matters more, who is external, what can move.
Act within limits: ask one organiser about options without cancelling anything you shouldn't.
Hand over: a short message they'll see on landing with a recommendation.
"First I'd work out which one matters more. Is one with a client or a senior person? Does one have a deadline behind it? What has my manager told me about their priorities this month? Usually the internal meeting is easier to move. I'd contact that organiser and say there's a clash and ask if a later slot would work, without cancelling anything yet. If someone on the team could attend in their place, I'd line that up as an option too. Then I'd leave a short message for my manager to see when they land: the clash, what I've found, and my recommendation, so they can reply with one word. If they land too late to answer, I'd go with the plan we'd agreed for exactly this kind of case."
Cancelling one meeting on your own guess, or doing nothing until the manager lands.
Agreed rules: who can book directly, meeting lengths, no-meeting times.
Protected time: focus blocks, travel time, breaks between meetings.
Daily habit: a check of tomorrow and a short plan sent the evening before.
"I start by sitting down with the manager and agreeing the rules. Who can put things straight in the diary and who has to go through me. What times are protected, for example no meetings before ten or a block for thinking every afternoon. Default meeting lengths, because thirty minutes often does the job of an hour. I always add travel time between meetings in different places and a short buffer after long ones. Then there's the daily habit. Each afternoon I look at tomorrow, check every meeting has a room or a link and the right papers, and send a short summary. Once a week I look ahead a fortnight for clashes, deadlines and anything that needs preparing."
Treating the calendar as first come, first served with no rules agreed with the person it belongs to.
Find the overlap: list working hours in each zone and look for the shared window.
Send it right: create the invite in the calendar tool so it shows in each person's local time.
Be fair: rotate the awkward slot on recurring meetings and watch clock changes.
"I start with a world clock or the scheduling view in the calendar, and list each person's working hours in their own time. Usually there's a small window where everyone is awake and at work, even if it's early for one and late for another. I always create the invite inside the calendar tool, so it shows in each person's local time, instead of typing a time in the email, because that's where mistakes come from. If there's no fair window, I'll check who is most flexible or suggest two sessions. For a recurring meeting, I rotate the uncomfortable slot so it's not always the same people. And I watch for daylight saving, because countries change their clocks on different dates, so a meeting can shift by an hour for a few weeks."
Typing times in only your own zone, or forgetting that clocks change on different dates in different countries.
Stay calm: a steady, polite tone, no matching their energy.
Gatekeep with a route: explain what you can do, not just what you can't.
Pass it on: a clear message with name, number and any urgency.
"I'd keep my voice calm and polite, whatever tone they use. I'd say something like, 'I understand you'd like to speak to her now. She's not available at the moment, but I make sure she gets every message. If you can tell me your name and a little about what it's about, I'll get it to her straight away.' If they still won't say, I'd take their name and number and explain she decides on calls based on what they're about. If they get abusive, I'd say I'm happy to help but can't continue if they speak to me like that. Then I'd send my manager a short note with the caller's details and what happened, so she can decide."
Putting the caller straight through to make them go away, or hanging up without taking a message.
Phone: a clear greeting, your name, and an accurate message when needed.
Visitors: a warm welcome, sign-in, and telling the host straight away.
Small touches: a seat, a drink, an honest wait time.
"On the phone I answer with the company name and my own name, speaking slowly and clearly. If the person they want isn't free, I take a proper message: name, number, what it's about and when they're free, and I read the number back. Then I pass it on straight away, not at the end of the day. With visitors, I look up and greet them as soon as they come in, even if I'm on a call, with a smile or a nod. I get them to sign in, tell their host they've arrived, offer a seat and a drink, and give an honest idea of the wait. If it runs long, I go back and update them so they're not left wondering."
Taking messages without a number or reason, or leaving visitors standing unacknowledged.
Don't confirm or deny: no hints, no lies.
Make it about your role: you never discuss what you see in your work.
Flag it: tell your manager that rumours are going around.
"I'd keep my answer the same as I would for any question about something I've seen at work. I'd say, 'You know I can't talk about anything I handle for the directors, whatever the topic. That's not me hinting either way. It's the same answer I'd give about anything.' I wouldn't say it's not true, because that's a lie I might have to live with later, and I wouldn't pull a face that gives it away. I'd stay friendly and change the subject. Then I'd tell my manager that rumours are going around, because that's useful for them to know, without naming my colleague unless there's a real reason to."
Hinting, saying 'I can't say but I'd update your CV', or flatly denying something you know is true.
Paper: clear desk, locked drawers, collect printouts, shred don't bin.
Screen: lock when you step away, check recipients, share with the right people only.
Talk: no work details in public places or casual chat.
"On paper, I keep a clear desk. Anything sensitive goes in a locked drawer when I'm not using it, I collect printouts straight away, and I shred confidential paper rather than putting it in the bin. On screen, I lock my computer every time I step away, even for a minute, and I double-check the recipients before sending anything sensitive, because autocomplete can pick the wrong person with a similar name. I share files with named people rather than with anyone who has the link. And I'm careful what I say in the kitchen, on the train or on a call in a public place. For me, confidentiality is mostly boring habits you do every single time."
Saying 'I'm just a very discreet person' with no actual habits to back it up.
Today first: find another way to get the pack printed.
Escalate with the vendor: a firm call, then something in writing.
Longer term: review the contract and look at alternatives.
"The pack comes first. I'd check whether another floor or office has a working printer we can use, and if not, send it to a local print shop, getting quotes quickly and checking the spend with my manager. Then I'd call the repair company and ask for someone senior, not the booking desk. I'd explain it's the second missed visit, what it's cost us, and ask for a fixed time and a named engineer. I'd follow that up by email so there's a record. After it's fixed, I'd look at the contract to see what service levels they agreed to, and if this keeps happening I'd suggest getting quotes from other suppliers before renewal."
Just waiting for the engineer to turn up and telling the team to hope for the best.
Track: stock levels and reorder points for the things that matter.
Order on a rhythm: regular planned orders, approvals within limits.
Manage suppliers: compare prices now and then, keep records, deal with problems early.
"I keep a simple list of what we use regularly, like paper, toner, kitchen supplies and first aid items, with a level where I reorder. I check it on the same day each week and place one planned order, which is cheaper and less stressful than emergency runs. I stay within the spending limit I've agreed, and anything unusual goes to my manager first. With suppliers, I keep their contacts, prices and any problems in one place. Once or twice a year I get a couple of quotes to check we're still getting a fair price. And I ask the team to tell me when they take the last of something, because a system is only as good as the information going into it."
Ordering only when someone complains something has run out.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your resume and notes are never stored on our servers. It stays out of screen share on every plan; only you can see it.