Executive Assistant Interview: Questions to Ask the Employer
Twenty questions for executive assistant candidates to ask the hiring executive: what they expect in the first 90 days, how they decide and communicate, their calendar non-negotiables, the stakeholders you would handle, how travel should be run, and what the last great EA did well.
The questions
Open any question for the note
What are the top three outcomes you expect from your EA in the first 90 days?
Why ask it
Asking for outcomes rather than duties forces the executive to say what would count as working out. If the answer is a list of tasks, the role has not been thought through and your review will be based on impressions.
How do you prefer to communicate, and how do you like to make decisions?
Why ask it
You are asking about channel, speed and whether they think out loud or in writing. Executives who need to talk something through will find a written summary useless, and the reverse is just as true.
What are your non-negotiables for your calendar?
Why ask it
A specific answer, no meetings before nine, Fridays kept clear, a hard stop for school pickup, gives you rules you can defend without checking. No non-negotiables usually means the calendar is currently controlled by whoever asks last.
How much of this job is calendar and inbox, and how much is project work?
Why ask it
The split determines whether this is a coordination role or an operating one, and the job posting is rarely accurate about it. Ask for a percentage and watch whether they hesitate.
Who are the five people I would deal with most?
Why ask it
The names tell you where the real work sits, which is often outside the org chart. Ask which of the five is hardest to work with, since that person will shape your week more than the executive does.
How do you want travel planned, and how do you want it debriefed?
Why ask it
Preferences here are highly personal and rarely written down: aisle or window, hotel chains, buffer before a first meeting, whether they want a printed itinerary. The debrief half tells you whether follow-up actions are yours to track.
What should reach you daily, and what can wait for a weekly summary?
Why ask it
This is the filter that makes the job possible, and an executive who wants everything immediately is describing a problem you will inherit. Push for examples of things they were told too late and too early.
Which areas are confidential enough to need special handling?
Why ask it
Compensation, restructuring, legal matters and health information usually need separate handling from ordinary correspondence. The answer also tells you how much you will actually be trusted with, which affects how useful you can be.
What access and tools will I have on day one?
Why ask it
Delegated inbox access, calendar rights, a company card, expense approval, signature authority. Missing any of these turns your first month into asking permission, and it is much easier to negotiate before you accept.
What does good judgment look like in this role?
Why ask it
Good answers come as examples: what to decide alone, what to bring, what to interrupt them for. Anything abstract here means the escalation rules will be learned by getting one wrong.
How is my performance reviewed, and by whom?
Why ask it
EAs are often reviewed by one person on a subjective basis, which makes the criteria worth agreeing early. Ask whether anyone else contributes, since feedback from the stakeholders you manage can matter as much.
What is one thing a previous assistant did that you still miss?
Why ask it
This gets past the job description to the specific habit they valued, often something small like a Monday morning briefing note. It also reveals the standard you will quietly be compared against.
What does a normal week look like for you right now?
Why ask it
Walking through last week hour by hour shows the real rhythm rather than the version in the posting. Count the evening and weekend commitments they mention without noticing.
Which recurring problem would you most want gone in the first month?
Why ask it
Points to the highest-value work available before you start, and it is usually a scheduling bottleneck or an inbox nobody is triaging. If they cannot name one, the role may be less defined than advertised.
How much authority do I have to say no on your behalf?
Why ask it
This determines whether the job is workable, because an EA who must check every refusal cannot protect anyone's time. Ask for the boundary explicitly: which requests you decline, which you defer, which you always pass on.
What went wrong the last time this role was filled?
Why ask it
The answer is a warning label, and how candidly it is given tells you what working here will feel like. Blame placed entirely on the previous assistant is worth noting carefully.
How do you want mistakes raised with you?
Why ask it
Settle this before the first one, because it will happen and the handling matters more than the error. Look for whether they want immediate notice with no fix yet, or the problem and the proposed solution together.
What parts of your work should never leave your desk?
Why ask it
Draws the line between what you can take on and what they will keep, which is where frustration builds in this role. Executives who cannot name anything they would keep have often not delegated before.
How often will we meet one on one, and for how long?
Why ask it
Regular scheduled access is the difference between an effective EA and one guessing at intent. Fifteen minutes daily or thirty minutes twice a week is workable; catching them between meetings is not.
What is your expectation for response times outside business hours?
Why ask it
Ask directly rather than inferring, since this becomes the main source of friction if left unspoken. An answer of only for emergencies needs a follow-up asking what counted as one last month.
Using the Answers
Practical guidance for the conversation itself
What the answers are telling you
Vagueness about outcomes is the main warning sign
An executive who cannot describe what success looks like in 90 days will evaluate you on feel, and feel is unmanageable. If the answer stays abstract, ask what the last person was praised or criticised for.
Listen for who really controls the calendar
If several people can put meetings in without asking, your gatekeeping mandate is theoretical. Ask how many meetings last week they wished they had not attended.
Watch how they talk about the last assistant
Specific and fair is a good sign. Sole blame, or an inability to say why the role turned over twice, tells you the problem is structural rather than about hiring.
Notice what they refuse to hand over
Executives who keep everything sensitive will limit the job to logistics. That may be fine, but it should match what you were told the role involved.
Asking these in an interview
- Pick five or six, not twenty. This is a conversation, not an audit.
- Ask about the first 90 days early. It frames everything else you ask.
- Save the authority to say no, the previous hire, and out-of-hours expectations for the later stages, once there is interest on both sides.
- Ask for an example whenever an answer stays general. One story tells you more than three principles.
- Take notes visibly. For this role, how you handle information in the room is part of the assessment.
- Ask the recruiter or HR the logistics questions, and save the executive's time for how they work.
A cadence to propose if they ask what you would do
- 1A short daily brief: changes to the day, decisions needed, anything blocked.
- 2A weekly operating review: next two weeks of priorities, travel, stakeholder follow-ups.
- 3A weekly inbox pass with a written summary of what you handled and what you left for them.
- 4A monthly look back at what recurred, so meetings and requests get restructured rather than absorbed.
- 5A running decisions log, so the reasoning behind a scheduling call is available three weeks later.
- 6A quarterly check on whether the calendar still matches their stated priorities.