Executive Assistant Interview Questions

I treat the calendar as one of the most important tools in the executive's day, so I am proactive rather than reactive with it. I start each week by reviewing the following two weeks in full: checking for back-to-back meetings that leave no buffer for preparation or travel, flagging any conflicts early, and confirming that pre-reads or materials are in place for every meeting that needs them. I use colour-coding in Google Calendar or Outlook to distinguish meeting types at a glance, and I keep a small block of protected time for the executive each morning where possible for focused work. When last-minute changes come in, which they always do, I work through a clear mental priority order: fixed external commitments first, internal meetings second, then flexible blocks. I communicate proactively with everyone affected rather than waiting for people to notice a change has happened.

I start by confirming the objective of the meeting and what decisions or outcomes the executive needs from the room. That shapes everything else. I gather the relevant data and inputs from across the organisation at least five working days before the meeting, which gives me time to identify gaps and chase them. I draft a clear agenda with timings, a concise executive summary, and supporting slides or documents that are edited down to what is actually needed in the room rather than everything that exists. Before I share anything externally I review it with the executive for accuracy and tone, then prepare a briefing note that gives them a one-page summary of the key points, the likely questions, and any background they need to know. On the day I confirm technology is working, materials are distributed, and all attendees have what they need before anyone enters the room.

Discretion is the foundation of the role, so I treat it as a default, not a special mode. Any conversation, document, or correspondence I handle is confidential unless the executive explicitly says otherwise. I do not discuss what I have seen or heard with colleagues unless there is a clear business reason to do so. In practice this means being careful about where I open sensitive documents, not leaving screens visible in shared spaces, and being thoughtful about how I phrase things when communicating on behalf of the executive. I also use secure channels: encrypted email where appropriate, and file sharing through approved company systems rather than personal accounts. When I am unsure whether something should be shared, I ask before doing rather than assuming. Trust is built slowly and lost quickly in this role, and I take that seriously.

My executive was travelling to New York for a board presentation when our CEO called an emergency leadership meeting for the same morning at head office. Both were non-negotiable. I had 45 minutes to resolve it. I called the board meeting organiser directly and explained that our CEO had a prior commitment; I did not disclose the reason, only that it was a fixed obligation. I negotiated a dial-in option for our CEO for the first 30 minutes of the board meeting to cover the most critical agenda item, then arranged a car to take them directly to the emergency leadership meeting in time for the second hour. I pre-positioned a printed briefing note in the car so they could review it during the journey. I kept both meeting chairs informed of the plan and confirmed each step as it was confirmed. Both meetings went ahead, and the CEO did not miss either agenda item that needed their input.

I was made aware of a potential personnel issue involving a senior leader at my previous company. The information came to me through correspondence I was managing on behalf of the CEO. I immediately flagged it to the CEO and HR Director through a private verbal conversation, did not record it in any shared system, and did not discuss it with anyone else in the office. When follow-up correspondence came in I routed it directly to the CEO without processing it through the standard shared inbox. Over the following three weeks I handled several related communications with the same discipline: the matter was resolved internally before it escalated further. Afterwards the CEO specifically thanked me for handling it correctly. That moment reinforced for me that discretion is not about withholding information but about routing it correctly and protecting the people involved.

My CEO was leading a company restructure while simultaneously managing a major fundraising round over a six-week period. My role changed significantly during that time. I moved from managing a two-week diary to a rolling 48-hour view and checked in twice daily rather than once. I created a master tracker covering every commitment across both workstreams: investor meetings, internal announcements, legal review deadlines, and press timings. Each morning I put a one-page briefing on her desk covering the day's priorities, any overnight developments, and three things she needed to decide before noon. I also took more off her plate proactively: drafting responses for her approval rather than flagging emails for her to answer, pre-empting travel bookings before she asked, and managing inbound requests from staff who were anxious about the restructure. By the end of the six weeks she told me the tracker had been one of the most useful things she had had in years.

I work primarily in Google Workspace and Outlook depending on the organisation. For calendar management I use shared calendars with clearly defined access levels: the executive sees everything, delegates see non-confidential blocks, and external parties see availability only. I maintain a master contact list in the CRM or address book with notes on preferences, assistant names, and communication histories for key stakeholders. For task tracking I use a combination of the executive's preferred tool, whether that is Asana, Notion, or a shared Google Sheet, and my own daily checklist system. I keep all travel documents, meeting briefs, and supporting materials in a shared folder structure with a consistent naming convention so everything is findable in under 30 seconds. I also build calendar reminders for myself, not the executive, two to three days ahead of any meeting that requires preparation, so I am never chasing materials the night before.

A good briefing document should mean the executive walks in knowing exactly who they are meeting, why, what they want to achieve, and what they need to know. My standard format is one page, sometimes two for high-stakes meetings. I start with a one-paragraph context section: who is in the room, what their relationship with the executive is, and what the meeting is trying to achieve. Then a short bullet list of key facts or recent developments the executive should be aware of, without full sentences where a phrase will do. Then a section on likely questions or topics that may come up, with suggested talking points. Finally, any actions from the last meeting that are outstanding. I pull information from the CRM, recent email history, news searches on the counterpart's organisation, and input from the relevant internal owner. I aim to have it on the executive's desk or in their inbox by the evening before the meeting.

I build travel itineraries in a single master document that shows every leg, every confirmation number, every hotel address, and every meeting alongside local times in each city. I always include a column showing home timezone alongside local timezone so the executive can orient themselves quickly. I book direct flights wherever possible and build in a minimum 90-minute buffer between a long-haul arrival and the first commitment, even if the executive says they do not need it. I confirm all bookings 48 hours before departure and send a final consolidated document the evening before they travel. I include ground transport details, hotel check-in instructions, and emergency contact numbers for each destination. I stay accessible on the day of travel in case anything needs real-time adjustment, whether that is a delayed flight, a changed meeting room, or a last-minute cancellation. I also track visa and entry requirements as soon as travel is booked, not the week before departure.