Administrative Assistant Interview Questions

I start by assessing urgency and impact: not everything that feels urgent is actually urgent, and not everything that seems low priority is actually low stakes. I ask two questions for each incoming request: when does this genuinely need to be done, and what is the consequence if it slips? Most apparent conflicts resolve themselves once you have that information. When I genuinely have two things that both need doing now and I cannot do both, I communicate proactively rather than silently dropping one. I go to the person whose task I need to deprioritise, explain the situation, and agree a revised timeline. I also track everything in a single system rather than across emails, sticky notes, and memory, because a priority you cannot see is a priority you will miss. At the start of each day I do a five-minute triage of what is outstanding, what is due today, and what I can proactively get ahead of for tomorrow.

Confidentiality is the foundation of the role. I treat information I access through my work as confidential by default, not just information that is explicitly labelled as such. In practice this means: I do not discuss the details of meetings, decisions, or personal matters I am aware of with colleagues who do not need that information; I am careful about what I leave open on my screen in shared spaces; I use secure channels for sensitive documents rather than casual email threads; and I follow whatever data and document management policies the organisation has in place. If I am ever unsure whether something is appropriate to share, I ask the relevant person rather than making my own judgement call. I have supported executives in sensitive situations including restructuring, HR matters, and M&A activity, and maintaining absolute discretion in those contexts is something I take seriously.

I start by understanding the executive's preferences and constraints: do they protect mornings for focused work, avoid back-to-back meetings, have standing commitments that should never be touched, or have specific preferences for how travel is arranged? Those rules become my defaults. For calendar management I build in buffer time around external meetings and travel, block preparation time before important presentations, and keep a rolling view of what is coming in the next two to four weeks so I can flag potential conflicts early rather than the day before. For travel I build itineraries with contingency time built in, keep all documents in one place the executive can access on any device, and confirm bookings 48 hours before departure. I also anticipate the things that go wrong: backup contact numbers for hotels, airport transfer alternatives, and awareness of time zone changes that affect meeting availability. The goal is that the executive never has to think about the logistics.

I use a combination of tools depending on the task. For calendar and email management I use the native features in Outlook or Google Workspace to their full capability: rules for sorting incoming mail, template responses for recurring queries, and keyboard shortcuts that save significant time over a day. For task and project tracking I use whatever system the team has in place, and if there is no system I tend to set one up: usually a shared list in Notion or a spreadsheet that the relevant people can see and update. For document creation and formatting I use the built-in automation features in Word and Google Docs to avoid manual reformatting. For AI tools, I use them to draft first versions of routine communications and meeting summaries, which I then edit before sending. The principle I apply is: anything I do more than once a week is worth automating or templating. The administrative tasks that take the most time are usually the ones that have not been thought about systematically.

My manager was travelling and unreachable for a four-hour window when a key external partner called to say they needed to pull out of an event we had been planning for three months, with 48 hours notice. The event involved 80 attendees and several booked venues and suppliers. I made a quick decision about what I could resolve independently and what needed my manager: I could handle the supplier calls and venue negotiations myself, but the decision about whether to cancel or reschedule the event needed her input. I called the venue to pause the catering order and extend the timeline on cancellation fees, giving us more time. I reached the key supplier to understand whether there was any flexibility. I prepared a one-page summary for my manager with three options (cancel, reschedule, find a replacement speaker) with the cost and logistics of each, so she could make a decision in five minutes when she became available. She chose option two. The event ran two weeks later without further issues.

I joined a team where the monthly board report required contributions from six people across three departments. The process involved chasing each contributor by email, consolidating responses manually in a Word document, and then reformatting everything to match the template. It took me about eight hours each month. I mapped the process end to end and identified three sources of wasted time: the chasing cycle, the manual formatting, and the back-and-forth over small wording changes once the document was in review. I set up a shared Google Doc with each section pre-formatted and assigned to the relevant contributor, with a clear deadline visible to everyone. Contributors added content directly rather than emailing it. I added a version-controlled comments stage so edits happened in the document rather than in email chains. The same report now takes me about two hours. I also documented the new process so it could continue after me.

An external client presentation was scheduled for 9am and at 7:30am the AV system in the booked room developed a fault. The room seats 20 people and the presentation included video content. I called the facilities team immediately and was told the repair would take until at least 10am. I checked room availability in the building management system, found an alternative room, confirmed with the client contact by text that we were moving location, updated the calendar invites for all internal attendees, printed new directions and placed them at the original room entrance, and repositioned the catering order to the new location. The meeting started on time. The executive presenting was informed of the change by the time he arrived at the building and walked into a fully prepared room. The most important thing in a situation like that is speed over perfection: a good solution in five minutes is worth more than a perfect solution in 30.

I treat my inbox as a workflow system, not a storage system. My default approach is: touch an email once and either act on it, delegate it, defer it to a specific time, or delete it. I use folders and labels sparingly, because too many categories create their own overhead. For the executive inbox I manage, I use a triage system: emails that need the executive's direct response are flagged and summarised, emails I can handle myself are dealt with and the executive is cc'd, and emails that are informational only are filed without action. For action items, I keep a single list updated throughout the day rather than relying on memory or scattered notes. I review it at the end of each day and move anything unfinished to a specific slot in the next day's schedule. The key principle is that nothing should exist only in my head or only in one email thread.

I start with a brief document that captures the key decisions before any logistics are booked: dates, number of attendees, budget, tone, and any accessibility or dietary requirements. Once those are confirmed I work to a backwards timeline from the event date: venue contract signed by X, agenda confirmed by Y, invites sent by Z. I build a master document that contains everything in one place: the agenda, attendee list, venue confirmation, travel and accommodation details, supplier contacts, emergency numbers, and a day-of-event run sheet with times and responsibilities. I confirm all suppliers 48 hours before the event and again on the morning. I also prepare a contingency note for the two or three things that most commonly go wrong: AV failure, a key speaker dropping out, catering numbers changing at the last minute. I share the run sheet with anyone who has a role on the day so the information is not bottlenecked through me.

My core tools are Outlook or Google Workspace for email and calendar, Microsoft Office or Google Docs for document creation, and a task management tool such as Asana, Notion, or Trello. I also use Teams or Slack for internal communication. The key to staying organised across tools is having clear rules about where things live: tasks go in the task tool, documents go in the shared drive with a consistent naming convention, and communication stays in the relevant channel rather than being duplicated across email and chat. I am quick to learn new tools when an organisation uses something I have not used before. What matters more than which tool is used is whether the system behind it is consistent, because a tool that is used inconsistently creates more confusion than no tool at all.