How to Screen Executive Assistants: 9 Questions and What to Listen For Screening Interview Template

Who have you supported directly? Give me the titles, how many executives at once, and what your day-to-day actually consisted of in your last EA role.

What this assesses: Establishes real scope and seniority, since executive assistant covers a range from supporting one director to running the gate for a CEO and a board. Strong answers name the titles (CEO, CFO, VP of Operations), say how many people they supported at once, and describe the actual work in concrete terms: calendar ownership, inbox triage, board or leadership meeting prep, expense and travel, vendor and stakeholder coordination. Listen for how much they owned versus executed, because an EA who was handed a list of meetings to book is a different hire from one who was trusted to decide what the executive's week looked like. Be cautious with a candidate who stays vague about who they supported, describes an EA title that was mostly reception or data entry, or has only ever supported a manager, since the jump to executive-level pace and stakes is where most of the first-90-days failures happen.

Walk me through how you run a calendar that changes all day. What is your process when two things the executive committed to land on top of each other and both parties think theirs is the priority?

What this assesses: Tests calendar ownership and prioritization, which is the core mechanic of the job and the part candidates most often describe passively. Strong answers describe a real system: holding blocks for focus and travel, protecting buffer between meetings, a standing weekly look-ahead, and clear rules about who gets moved. On the conflict, listen for a candidate who resolves it themselves using known priorities and only brings the executive a decision when the two options are genuinely equal, and who mentions how they communicated the change to the party who got moved. Be cautious with an answer that ends at 'I would ask my executive what they prefer,' since the whole point of the role is to absorb that decision, and with a candidate who has only ever managed their own calendar or a small shared one, since volume and constant reshuffling is what breaks people here.

Tell me about a time you handled confidential information: compensation, a reorg, a departure, legal or financial material. How did you handle it, and what did you do when someone asked you about it?

What this assesses: Assesses discretion, which is the non-negotiable of the role and the one thing you cannot coach after a leak. Strong answers describe a real situation without actually disclosing the confidential details in the interview, which is itself the signal, and cover the mechanics: who had access, how documents and calendar invites were titled or restricted, and a specific deflection when a colleague fished for information. Listen for someone who understands that a vague calendar entry and a closed door are part of the job. Be cautious with a candidate who spills identifiable details about a former employer's layoffs, comp, or executives while answering, since they will do the same to you, and with one who has never handled anything sensitive, since that usually means they were not trusted with it.

How do you handle it when two executives or two stakeholders need you urgently at the same time? Give me a specific example rather than a general approach.

What this assesses: Evaluates prioritization and composure when the demands are legitimate on both sides, which is the daily condition of supporting more than one leader. Strong answers name a real instance, describe how they judged urgency (external commitment versus internal, reversible versus not, who is blocked downstream), give an honest response time to the one who had to wait, and confirm they told that person rather than going silent. Listen for a candidate who protects the executive's stated priorities instead of defaulting to whoever asked loudest or last. Be cautious with a candidate who says they simply do both at once, since that is not an answer, and with one whose only tactic is escalating the collision back upward, since that hands the executive exactly the interruption the role exists to prevent.

How much of the executive's inbox have you handled? Did you draft or send on their behalf, and how did you decide what reached them versus what you handled yourself?

What this assesses: Reveals the level of trust the candidate has actually earned, since inbox and gatekeeping authority is the clearest marker separating a senior EA from a scheduler. Strong answers describe a real delegation model: what they answered directly, what they drafted for approval, what they flagged, and how the rules were set and adjusted over time, often mentioning writing in the executive's voice or a signature convention that made it clear who sent what. Listen for someone who can articulate a threshold rather than a feeling. Be cautious with a candidate who has never touched an executive inbox and is applying for a role that requires it, since that is a real ramp, and with one who claims broad send authority but cannot describe a single message they got wrong or a rule they had to renegotiate, since unchecked inbox access without judgment is worse than none.

Describe the most complex travel, offsite, or large meeting you coordinated. What went wrong, and what did you do about it?

What this assesses: Tests logistical planning plus recovery, and the second half of the question is the part that matters. Strong answers give real detail such as multi-city or international itineraries, visas, ground transportation, dietary and accessibility needs, room blocks, agendas and materials, and then name a genuine failure like a canceled flight, a double-booked venue, or a missing badge, followed by the specific fix and how quickly the executive knew. Listen for contingency habits: backup flights, printed and offline copies, a phone number for every vendor. Be cautious with a candidate who insists nothing has ever gone wrong, since that means either limited volume or a reluctance to own problems, and with one whose recovery was entirely someone else's doing.

How do you anticipate what the executive needs before they ask? Give me one concrete example of something you handled that nobody assigned to you.

What this assesses: Assesses whether the candidate operates proactively or waits for instruction, which is the difference between an EA who creates capacity and one who consumes it. Strong answers describe a specific unassigned catch: noticing a prep document was missing before a board meeting, spotting that back-to-back travel left no room to eat or work, building a briefing sheet on people the executive was about to meet, or flagging a commitment made in one meeting that never made it onto anyone's list. Listen for how they learned the executive's preferences, since most good EAs describe an explicit early conversation plus deliberate observation in the first month. Be cautious with an answer that stays theoretical or restates the question back as a philosophy, since anticipation either shows up as a specific story or it does not exist.

Tell me about a time you had to say no on the executive's behalf, and separately, a time you made a mistake that affected them. How did each one play out?

What this assesses: Reveals gatekeeping backbone and how the candidate handles being wrong, two traits that decide whether the executive can stop checking their work. On the no, strong answers describe declining a meeting request, a vendor, or an internal ask clearly and without hiding behind the executive's name, and offering an alternative such as a delegate or a later window. On the mistake, listen for a candidate who names a real error, says they surfaced it immediately rather than hoping it went unnoticed, describes the fix, and names the process change that followed. Be cautious with someone who cannot recall ever declining anything, since an EA who says yes to every request becomes a scheduling bottleneck rather than a filter, and with a candidate whose only mistake was somebody else's fault.

What tools do you work in for calendar, documents, travel, and expenses, and what are your practical constraints: onsite days, core hours, time zone, after-hours availability, notice period, and comp expectations?

What this assesses: Confirms system readiness and surfaces the logistics that quietly kill otherwise strong EA matches, so ask them together and ask them now rather than after the offer. Strong answers name specific tools (Google Workspace or Microsoft 365, Concur, Navan, Expensify, Slack, Zoom, Notion or Asana) and describe what they did in each, then give clear and specific limits: which days they can be onsite, whether they can take a 6 a.m. or a Sunday message during travel weeks, what time zone they operate from, and a real comp number. Treat unqualified flexibility such as 'always available' as unconfirmed rather than ideal, since it collapses the first time a trip goes sideways at 11 p.m. Score every candidate against the same [structured interview](/glossary/structured-interview) rubric and record the answers on one [interview scorecard](/glossary/interview-scorecard), because in a role that selects for polish, side-by-side evidence is the only thing that keeps warmth from outvoting judgment.