What executive assistant interview questions should I expect?

Executive assistant interviews test judgment under constraints far more than tool familiarity. Most questions fall into four groups.

• Prioritization and calendar judgment. Two executives want the same hour; a flight is cancelled the night before a board meeting. The interviewer wants your decision rule, not your scheduling app.
• Confidentiality and discretion. You see compensation data, an unannounced departure, a document left on a printer. They want to hear where your line is and who you tell.
• Communicating for someone else. Drafting in an executive's voice, declining on their behalf, chasing a senior stakeholder without creating friction.
• Operational range. Travel, expenses, board packs, vendor coordination, and the systems you have actually run.

Tool questions do appear, usually about calendar and travel systems, expense platforms, and document software. They are screening questions and rarely decide the outcome.

The scenario questions are where most candidates lose ground, usually by describing a tool instead of a decision. This section gives a shape you can reuse for any of them. It is the STAR method with one addition that matters for this role specifically.

State the situation and the constraint, say what you decided, say who you told, then say what changed afterwards. The addition is that third step. An executive assistant is judged on escalation judgment, so an answer that never mentions informing anyone reads as someone working alone in a job that is structurally about coordination.

Take a double-booked hour. A weak answer explains how you would find a free slot. A strong one says which meeting carried the external dependency, which executive you asked, what you moved, and how you told the person whose meeting shifted. The interview types cluster applies the same structure to other roles.

Support roles attract high application volume, so a growing share of first rounds are one-way: a question appears, a timer starts, and you record an answer with nobody listening. Some are scored by software before a person ever watches.

Three things change. Nobody prompts you, so an answer that trails off stays trailed off. Nobody signals interest, so you cannot tell whether to go deeper. And the time limit punishes long preambles.

Answer as though the listener will only ever hear this one take. Restate the question in your first sentence, then give the decision, then one concrete example with scope in it: how many executives you supported, across how many time zones, and the size of the travel budget you handled. Concrete scope is what a reviewer working through a stack of recordings remembers afterwards.

These answers improve by being said out loud, not by being reread. Saying that you moved the internal meeting because the external attendee was already in the air is a different skill from knowing that you would.

The SubcueAI mock interview asks a question, listens to your spoken answer, and gives feedback, which is the closest available rehearsal for a one-way recording. For live conversational rounds over Zoom, Google Meet, or Microsoft Teams, the desktop app on macOS and Windows and the browser extension Side Panel both show suggestions while the interviewer is speaking. A recorded one-way screen has no interviewer to listen to, so a live assistant has nothing to work with there, and that limit is worth planning around rather than discovering on the day.

Aaron Cao, founder of SubcueAI, built the mock flow around exactly that gap: the questions people fumble are usually the ones they have only ever answered in their head. The profile that gets you into these rounds is handled by the resume builder.