Executive assistant screening questions: calendar complexity and confidentiality
On this page
- How many principals, and at what level
- Knockout questions
- Calendar complexity and travel questions
- Confidentiality and judgment questions
- Communication, gatekeeping and stakeholder management questions
- Software and systems questions
- How executive assistant experience gets overstated
- Scoring rubric and checklist
- Questions people ask
Executive assistant screening questions need to establish how many principals the candidate supported, at what level, and what authority they actually had over the calendar, communications and confidential material. Ask for a specific week that went sideways and how they handled it. A resume that says "executive support" can mean managing one CEO's entire calendar and inbox with real decision-making authority, or booking meeting rooms for a director who still controlled their own calendar; the interview should surface which one you are hiring.
This page is for roles supporting senior leaders directly. For broader administrative or department support work, use administrative assistant screening questions, which covers general software proficiency and inbox prioritization for a wider range of roles. If the role is front-desk and visitor-facing rather than principal support, use receptionist screening questions.
How many principals, and at what level
| Question | Why it matters |
|---|---|
| How many executives did you support at once, and at what level (C-suite, VP, founder)? | One demanding, high-travel principal can be more work than three low-travel ones; the number alone is not the useful signal. |
| Did you have full calendar authority, or did the executive make their own scheduling decisions and you executed them? | Separates candidates who actually triage and decide from those who only book what they are told. |
| Did you support the executive's direct reports or team as well, or only the principal? | Scope creep into supporting a whole leadership team is common and worth knowing about upfront. |
| What was the company size and industry? | Board-level support at a public company differs from founder support at an early-stage startup, even at similar title levels. |
Knockout questions
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| This role requires availability outside standard hours for urgent scheduling or travel issues. Is that workable for you? | Yes, or a specific limitation stated now. | Raises the conflict only after an offer is close. |
| Do you have experience managing complex, multi-leg travel and international time zones? | A specific example, including handling a disruption (a cancelled flight, a missed connection). | Only domestic, single-leg travel experience, for a role that clearly needs more. |
| Have you handled confidential material such as compensation, legal matters or pre-announcement information? | A general, non-specific "yes, and I understand why it stays confidential," without volunteering details about a prior employer. | Volunteers specifics about a former employer's confidential matters, which signals they might do the same with yours. |
| This role is [on-site / hybrid, with X days in office]. Does that work for you? | A direct answer matched to the order. | Assumes remote flexibility that the role does not offer. |
Calendar complexity and travel questions
-
"Describe managing a week where the calendar had three conflicting priorities at once."
- Strong answer: describes a triage method (who is affected, what is reversible, what the principal actually cares about), makes a call rather than escalating everything, and follows up to confirm the choice landed well.
- Red flags: describes forwarding every conflict to the executive to decide, which is not calendar management, it is calendar relaying.
-
An example only, with invented numbers, to check time-zone reasoning: "Your executive is in New York and needs a 30-minute call with someone in Singapore and someone in London on the same day, plus a 9 a.m. New York internal meeting. Walk me through how you'd find a slot."
- Strong answer: reasons through the offsets (Singapore is roughly 12-13 hours ahead of New York depending on daylight saving, London roughly 4-5 hours ahead), proposes a New York evening or very early morning slot for Singapore, and a mid-morning slot for London, while protecting the 9 a.m. internal meeting.
- Red flags: cannot reason through the time zones at all, or proposes a plan that ignores the stated 9 a.m. conflict.
-
"Tell me about a travel booking that went wrong. What did you do?"
- Strong answer: a specific disruption, a description of rebooking under pressure, and communicating clearly with the traveling executive throughout.
- Red flags: no example at all, for a role with meaningful travel volume.
Confidentiality and judgment questions
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| How do you decide what to escalate to the executive immediately versus handle yourself? | A described framework (urgency, reversibility, who is affected) with a specific example of each. | Escalates everything, or handles things that clearly needed the executive's input. |
| Describe a time you knew something sensitive before it was public. How did you handle it, generally? | Describes keeping it compartmentalized, not discussing it even with close colleagues, without disclosing specifics of a prior employer's confidential matter. | Shares specific confidential details from a former employer to answer the question. |
| What would you do if someone senior asked you for information about the executive's schedule that you were not sure they should have? | Describes checking with the executive or a defined protocol before sharing, even under social pressure. | Would share it to avoid an awkward conversation with someone senior. |
Communication, gatekeeping and stakeholder management questions
-
"How do you decide who gets time with your executive when everyone thinks their request is urgent?"
- Strong answer: describes criteria set with the executive in advance, and a specific example of saying no or redirecting someone without damaging the relationship.
- Red flags: says yes to everyone and lets the calendar absorb the consequences.
-
"Describe writing or sending a communication on your executive's behalf. How did you make sure it sounded like them?"
- Strong answer: describes studying the executive's tone and past communications, drafting for review initially, and eventually being trusted to send certain things directly.
- Red flags: has never drafted anything on the executive's behalf, for a role that clearly requires it.
Software and systems questions
Ask for a specific task rather than a list of tools. "How would you give a delegate access to a calendar without giving them access to private appointment details?" tests real Outlook or Google Workspace fluency in a way that "Are you good with Outlook?" does not. Ask similarly specific questions about expense platforms (Concur, Expensify), travel booking tools, and any board or meeting-management software the role uses, since fluency with the specific stack matters more at this level than general familiarity.
| System | A task-based question | What a strong answer sounds like |
|---|---|---|
| Calendar (Outlook / Google Workspace) | "How do you mark an appointment private while keeping a delegate able to see the time is blocked?" | Describes the actual privacy setting and what a delegate sees versus what the executive sees. |
| Expense reporting (Concur, Expensify) | "Walk me through reconciling a month of an executive's travel expenses." | Describes matching receipts to statements, flagging anything unclear before submission, and the approval workflow. |
| Board or meeting management (Diligent, BoardEffect) | "Have you assembled or distributed board materials? What was your role in that process?" | Describes the actual steps: collecting materials from stakeholders, formatting, and distribution under a confidentiality process. |
How executive assistant experience gets overstated
- Relaying called managing. Forwarding scheduling conflicts to the executive described as owning the calendar.
- Coordinator work called EA work. Supporting a team's shared calendar described the same way as dedicated single- or dual-principal support.
- Software listed without a task. Tools named on a resume with no ability to describe a specific workflow in them.
- Confidentiality claimed but not demonstrated. Says "very discreet" but then volunteers specific confidential details from a former employer during the interview.
- Travel complexity inflated. Occasional domestic travel described the same way as frequent international, multi-leg coordination.
Scoring rubric and checklist
Knockouts are pass or fail. Score the rest 0 to 2 each.
Pass or fail
- Can work the schedule flexibility, including any outside-hours availability, the role requires.
- Has genuine calendar authority experience, not only relaying decisions.
- Discusses confidentiality appropriately, without volunteering a former employer's sensitive details.
- On-site or hybrid expectations match what the role requires.
Scored, 0 to 2 each (10 possible)
- Calendar reasoning: works through a real scheduling conflict with a clear method, including time-zone math.
- Judgment: has a real framework for what to escalate versus handle independently.
- Gatekeeping: a concrete example of managing competing demands for the executive's time.
- Communication: has drafted or sent communications on an executive's behalf, with a described process.
- Software fluency: can describe a specific task in the actual tools the role uses.
Send the client a short candidate note with the submittal:
Candidate: [name]
Principals supported: [number and level], [months], [how recent]
Calendar authority: [full authority / partial / relayed decisions only]
Travel complexity: [domestic / international, multi-leg], example: [what they described]
Confidentiality: [how they described handling sensitive information]
Software: [specific tools and tasks demonstrated]
Candidate's own gap: [e.g. "no experience with board meeting logistics"]
Available to start: [date]A focused executive assistant screen covers calendar authority, one confidentiality answer, one gatekeeping example and specific software tasks; anything beyond that is worth a second conversation with the executive's current or former assistant as a reference. Interview Signal keeps the transcript on your computer during the call and ticks off each question as it is covered, so the candidate note above is built from what the candidate actually said.
Questions people ask
What is the difference between an executive assistant and an administrative assistant?
An executive assistant supports one or a small number of senior leaders directly, often with authority to manage their calendar, represent them in communications and handle confidential material. An administrative assistant more often supports a team or department with broader, less principal-specific work. See administrative assistant screening questions for that role.
How many executives can one EA realistically support well?
It depends heavily on the executives' travel, meeting load and how much decision-making authority the EA is given. Ask the candidate how many principals they supported at once and how that felt in practice, rather than assuming a number, since a single demanding principal can be more work than three low-travel ones.
Should I test an executive assistant candidate's software skills directly?
Yes, for anything specific to the role, such as a particular calendar system, expense platform or board-meeting tool. Ask them to describe a specific task step by step, such as scheduling across time zones or reconciling a expense report, rather than accepting a list of software names.
What is a fair confidentiality question to ask in an interview?
Ask how they have handled sensitive information in the past in general terms, such as knowing about a reorganization before it was announced, without asking them to disclose specifics about a current or former employer. How they describe handling the situation tells you what you need to know.