Tell me about yourself.
Why they ask: to test communication and relevance — whether you can summarise a career in a minute and point it at their job, rather than narrating a résumé.
How to approach it: give three beats: what you do now and for whom, one or two things you are known for, and why this role is the next step. Keep it under 90 seconds and name the size of the team or the number of people you support.
Sample answer — admin assistant at a 40-person architecture firm
I have been the administrative assistant for a 40-person architecture firm for three years, supporting two principals and the project managers. Day to day I run two heavily booked calendars, handle the main phone line, process about 60 expense claims a month in our accounting system, and keep the project filing structure in SharePoint tidy. The thing people come to me for is sorting out the impossible week — four site visits, a client presentation and a deadline all landing together. I built the travel and meeting checklist the whole office uses now. I am applying here because you support a larger leadership team, and I want more involvement in event and board-meeting work.
Mistake to avoid: starting at your first job and working forward chronologically. Fix: start with your current role and scope, then go back only where it is relevant.
How many people have you supported, and how do you keep their calendars straight?
Why they ask: this is the calendar-management competency, and it is the single most predictive task in the job. They want to know your scope and your system.
How to approach it: name the number of people, their level, and the mechanics — colour coding, travel buffers, how far ahead you confirm, how you handle recurring meetings. Mention the calendar tool by name.
Sample answer — assistant to three directors at a community health nonprofit
I support three directors in Outlook, roughly 45 meetings a week between them. Each director has a colour, external meetings are flagged, and I block 30 minutes of travel either side of anything off-site. I hold a standing 15-minute check with each director on Friday to confirm the week ahead and flag anything that needs to move. Recurring internal meetings are the first things I sacrifice when something urgent lands, and I have their written permission to do that without asking. Since I started holding the Friday check, we have had no double-bookings and no one has turned up at the wrong building.
Mistake to avoid: saying "I just keep on top of it." Fix: describe one rule you follow every week, such as a standing confirmation slot.
Two managers need you at the same time. How do you decide?
Why they ask: prioritisation and judgment. There is no correct answer, only a reasoned one, and they want to hear whether you escalate or guess.
How to approach it: give a criterion (external commitment, deadline, client impact, who else is blocked), say that you communicate a time rather than going silent, and mention agreeing a tie-break rule with both managers in advance.
Sample answer — admin assistant supporting two department heads at a university
I supported two department heads, and this happened most weeks. My rule, which I agreed with both of them in my first month, was that anything with an external deadline or an outside party waiting beats internal work. So if one needs a grant form submitted by 4pm and the other wants a report formatted for an internal review, the grant wins. I tell the second person straight away — "I can start yours at 2:30, it will be with you by 4" — because a time is more useful than an apology. If both are genuinely external and fixed, I ask them to settle it between themselves. In two years I escalated like that maybe four times.
Mistake to avoid: promising you would do both at once. Fix: name your criterion and give the second person a specific time.
How do you handle a difficult or angry caller?
Why they ask: answering telephones, giving information, taking messages and transferring calls is a core task of the occupation (O*NET OnLine, undated), and you are often the first voice a customer hears. They are testing composure and active listening.
How to approach it: describe the sequence — listen without interrupting, acknowledge, state what you can do, take ownership of the follow-up. Use a real example, including what you did not promise.
Sample answer — front-desk administrative assistant at a medical practice
At the practice I took around 70 calls a day, and the hardest ones were patients whose appointments had been moved. One man had rearranged work twice and was shouting by the second sentence. I let him finish, repeated back what had happened so he knew I had heard it, and apologised for the disruption without blaming the scheduling system. Then I told him exactly what I could do: find the first available slot with the same physician, and put a note on his file so he was called first if anything opened up earlier. I got him in two days later. I also logged the pattern, and when three similar calls came in that week I raised it with the practice manager.
Mistake to avoid: matching their tone or over-promising a resolution you cannot deliver. Fix: say what you can do and when, then follow up in writing.
A colleague asks what was discussed in a confidential meeting. What do you say?
Why they ask: discretion. Administrative assistants see salary letters, disciplinary notes, patient or student records and draft decisions before anyone else does.
How to approach it: give the exact words you would use, show you do not make an exception for friendly colleagues, and mention the handling habits that keep it from arising — locked screens, printer collection, sealed envelopes.
Sample answer — executive assistant at a professional services firm
I would say, "I can't talk about what's in the diary, but if you ask Priya she'll tell you what she can." Short, friendly, and it does not hint at whether there is anything to tell. I use the same line for everyone, including people I am close to, because inconsistency is what people read. Practically, I lock my screen whenever I leave the desk, I collect print jobs immediately rather than at the end of the day, and HR documents go in sealed envelopes with the recipient's name, not just a surname. When I booked redundancy consultations last year, I used neutral meeting titles so nothing was readable from a shared calendar.
Mistake to avoid: saying "I'd just tell them it's confidential" and stopping. Fix: add one handling habit that shows discretion is built into your routine.
How advanced are you in spreadsheets? Give me an example.
Why they ask: software fluency. Many candidates write "advanced Excel" on a résumé and mean sorting. They want a verifiable example, and some employers will test it.
How to approach it: be honest about your level, name the specific functions or features you actually use, and describe one thing you built. If you have gaps, name them and say what you are doing about them.
Sample answer — office assistant at a construction subcontractor
I would call myself solid intermediate. I use VLOOKUP and XLOOKUP, pivot tables, conditional formatting and data validation daily; I do not write macros. The piece I am proudest of is the subcontractor insurance tracker I built. We had 60-odd certificates expiring at different times and no one was watching them, so I set up a sheet with expiry dates, conditional formatting that turns a row amber at 30 days and red at 14, and a pivot that gives the ops manager a one-page summary each Monday. We went from chasing certificates after they lapsed to zero lapses in 18 months. I also work in Google Sheets and Microsoft Word, and I am working through a pivot-table course on my own time.
Mistake to avoid: claiming "expert" and then stalling on a basic question. Fix: pick the honest label and back it with one artefact you built.
Tell me about a mistake you made at work.
Why they ask: accountability and accuracy. In a job where a wrong date or a wrong recipient has consequences, they want to see how you catch and correct errors.
How to approach it: pick a real mistake with a real consequence, be quick about the error and long about the fix, and end with the control you put in place. Do not pick something trivial or secretly a strength.
Sample answer — administrative assistant at an engineering consultancy
I booked a flight for our principal engineer on the right date but into the wrong airport — two hours from the client. I found it the night before while doing my pre-trip check. I called him first, before fixing anything, because he needed to know there was a problem. Then I rebooked onto a morning flight, arranged a car, and moved his first meeting by 90 minutes with an apology to the client. It cost about $400 extra, which I flagged to our finance lead myself rather than letting it surface in the statement. After that I added an airport-code confirmation line to our travel checklist, and I now send a draft itinerary for approval before anything is paid for.
Mistake to avoid: choosing a mistake that cost nothing, or blaming a colleague. Fix: name the cost, say who you told first, and end with the control you added.
How would you set up a filing or records system for a team that has none?
Why they ask: office and records management — one of the knowledge areas most associated with this career (CareerOneStop, undated). It tests whether you can impose structure without being told how.
How to approach it: show that you ask before you build. Cover naming conventions, access permissions, retention, and how you get people to actually use it.
Sample answer — administrative specialist at a county nonprofit
I would spend the first two weeks watching what people actually look for and asking the three heaviest users what they can never find. Then I would design around retrieval, not storage: a shallow folder tree, no more than three levels, with a naming convention like YYYY-MM-DD_Client_DocumentType so sorting does the work. Permissions get set by group rather than by individual, so leavers do not leave gaps. Anything with a legal retention period — contracts, HR files — gets its own area with a review date in my calendar. I did this at the nonprofit with eight years of shared-drive sprawl; I migrated about 4,000 files over six weeks and ran two 20-minute lunch sessions so people knew where things went. The rule that made it stick was that I would not retrieve a file for anyone who had saved it outside the structure.
Mistake to avoid: describing the folder tree and nothing else. Fix: include adoption — how you get colleagues to file correctly.
You are asked to take minutes on a subject you do not understand. How do you handle it?
Why they ask: writing and reading comprehension under pressure, both listed among the essential skills for this occupation (O*NET OnLine, undated). Minutes are a common admin deliverable and an easy place to get it wrong.
How to approach it: separate preparation, capture and circulation. Say what you record (decisions, owners, deadlines) versus what you do not (every remark), and how you verify technical terms afterwards.
Sample answer — board secretary support at a housing association
Before the meeting I read the papers and write out the agenda as a skeleton, with a line for each item and space under it. During the meeting I capture three things only: the decision, who owns the action, and the date. I do not try to transcribe debate. If a term goes past me, I write it phonetically and circle it rather than stopping the meeting. Straight afterwards, while it is fresh, I check circled terms against the papers or ask the chair in one short message — usually five minutes of questions. Draft minutes go to the chair within 24 hours and to the board within three working days. Over eight board meetings I had two factual corrections, both names rather than decisions.
Mistake to avoid: trying to capture everything verbatim. Fix: commit to decisions, owners and dates, and agree that scope with the chair in advance.
Tell me about an event or meeting you ran end to end.
Why they ask: event and project coordination, which sits in most administrative assistant job descriptions and is one of the domains covered by the Certified Administrative Professional body of knowledge (International Association of Administrative Professionals, 2018).
How to approach it: give scale (people, budget, venues), the hardest logistical problem, and the outcome. Mention the tracking tool you used.
Sample answer — administrative assistant at an independent school
I ran the annual staff training day for 120 people: venue, catering, five breakout rooms, external speakers and all the printed materials. I tracked everything on a single shared sheet with owners and due dates, and I worked backwards from the date with three checkpoints — eight weeks for the venue and speakers, four for catering numbers and dietary requirements, one for room layouts and signage. The hard part was dietary requirements arriving late; I set a firm cut-off and labelled every plate so nobody had to ask. On the day I had a printed run sheet with everyone's mobile number. One speaker cancelled at 7am and I moved the schedule around rather than cancelling a session. Feedback forms came back with the logistics rated highest of the three sections.
Mistake to avoid: describing the event rather than your decisions. Fix: name the thing that went wrong and what you changed on the spot.
Why do you want this job?
Why they ask: motivation and retention. Administrative roles turn over, and they want evidence you chose this employer rather than applying to everything.
How to approach it: tie one concrete thing about the organisation to one concrete thing you want to do more of. Mention the sector if it matters to you — healthcare, education and professional services employ about half of all workers in this occupation (U.S. Bureau of Labor Statistics, 2025), and each has a different rhythm.
Sample answer — administrative assistant moving from retail head office to healthcare
I have spent four years as an administrative assistant in a retail head office, and the part I liked least was that the work was interchangeable from week to week. I want to be in a setting where the admin has consequences for someone, which is why I started looking at clinical and patient-facing organisations. Your posting mentions supporting a clinical team of nine plus the department's scheduling, and that is the scale I work well at — close enough to the team to know what each person needs. I also noticed you run your records in a defined retention structure, which matters to me; I spent a year cleaning up a shared drive with no rules and I would rather join something already disciplined.
Mistake to avoid: praising the organisation in general terms. Fix: quote one line from the job posting and say what it means for how you would spend your week.
