An executive assistant protects one person's time. That sounds simple until you watch a strong EA work: they decide which meetings deserve a slot, they say no on the leader's behalf without burning relationships, they turn a messy week of travel into a plan, and they keep a board packet, an offer letter or a sensitive email thread quiet. These executive assistant interview questions are written to surface that judgment. They suit founders and owners hiring their first EA, operators at multi-location groups, and executives at larger companies replacing an assistant who knew everything.
Each question below includes a short model answer and a note on how strong and weak answers differ. Use them as prompts for a conversation, not a quiz. The best candidates will push back on a question or ask how you like to work, which is itself a good sign.
Pick eight to ten questions across the four groups, weighted toward the work you will actually hand over. If your calendar is the pain, spend more time in the first group. If you sit on boards or report to investors, lean on the third. Ask every candidate the same core set so you can compare them fairly, then use follow-ups ("what did you do next?", "how did the executive react?") to get past rehearsed stories.
Listen for specifics: names of tools, how they decided, what they would change. An EA who says "I'm very organized" is describing a hope. An EA who explains how they color-code deep work blocks and defend them on Thursdays is describing a system. Finish with the paid exercise further down, because how someone actually handles a calendar tells you more than any answer.
Model answer: I start by learning the leader's priorities for the quarter and the meetings that move them. Requests get sorted against that list. Anything that does not serve a priority gets redirected to someone else, handled by email, or offered a later slot. I review the coming two weeks every Friday with the executive so we agree on trade-offs before they happen.
Strong vs weak: Strong candidates talk about priorities and a review rhythm. Weak ones describe accepting requests in the order they arrive and fixing conflicts afterward.
Model answer: I audit the last month of meetings, group them by type, and bring the executive a short list: recurring meetings that could be shorter, ones a deputy could attend, and ones that could move to a single afternoon. Then I block focus time as real appointments and treat them as protected unless the executive says otherwise.
Strong vs weak: A strong answer starts with data from the calendar and proposes cuts. A weak one simply adds blocks and hopes nobody books over them.
Model answer: I treat it as high priority, offer two or three good slots quickly, and check whether it displaces anything that matters. If it does, I tell the executive what moved and why. I also find out what the meeting is about so the executive walks in prepared.
Strong vs weak: Strong candidates combine speed with context. Weak candidates either bump everything automatically or wait for permission and lose the slot.
Model answer: I keep the executive's home zone as the primary view and add a second zone for the region they deal with most. Every invite I send states the time in both zones. Before travel, I shift the calendar to the destination zone and check that recurring meetings still land at sensible hours.
Strong vs weak: Look for habits that prevent mistakes, like dual times in every invite. Weak answers rely on the calendar app to sort it out.
Model answer: Fifteen to thirty minutes, same time each week. I bring the next week's calendar, open decisions, deadlines and anything I need from them. We agree on what can move, what I can decline and what needs prep. I send a short recap afterward so nothing depends on memory.
Strong vs weak: Strong EAs run the session themselves with an agenda. Weak ones wait to be told what to do.
Model answer: I add travel time as its own block, leave ten minutes after long meetings, and avoid stacking difficult conversations back to back. If the executive tends to run over in certain meetings, I plan for that rather than pretending it will not happen.
Strong vs weak: A strong answer shows they know the executive's habits. A weak one treats every meeting as exactly its scheduled length.
Model answer: I look for the cause: a bad time slot, too many attendees, or no clear agenda. I would propose a new standing time that works for the required people, trim the invite list, and attach an agenda template. Then I protect that slot when other requests come in.
Strong vs weak: Strong candidates diagnose before rescheduling. Weak ones keep moving the meeting.
Model answer: Politely and with an alternative. I might offer a short call with a deputy, ask for the question in writing so the executive can answer by email, or suggest a date a few weeks out. I keep the tone warm because the person may matter later.
Strong vs weak: Strong answers protect the relationship while protecting the calendar. Weak answers are either blunt refusals or a habit of saying yes to avoid conflict.
Model answer: I read a few weeks of their sent mail and note their greetings, length, sign-offs and phrases they never use. I start by drafting replies for approval, then ask which kinds of messages I can send without review. Over time the approval list gets shorter.
Strong vs weak: Look for a staged plan that builds trust. A weak answer assumes they can write for anyone from day one.
Model answer: Nothing outside the executive's office. I do not forward it, discuss it, or let it change how I act with colleagues. If it creates scheduling work, like private meetings with HR, I book them with neutral titles and tell the executive I have seen it so they know what I know.
Strong vs weak: Strong candidates are calm and specific about discretion, including neutral calendar titles. Weak ones hesitate or describe telling a trusted colleague.
Model answer: I set up labels or folders by action: needs the executive, I will handle, waiting on someone, and read later. I clear it at fixed times each day, draft replies where I can, and send the executive a short summary of what needs them. Newsletters and notifications get filtered so they never land in the main view.
Strong vs weak: Strong EAs describe a system and a daily rhythm. Weak ones describe reading every email in order.
Model answer: A good candidate describes the situation, how quickly they raised it, what options they brought with it, and what they learned. For example, a missed filing deadline raised the same day with two ways to recover, not a week later.
Strong vs weak: Strong answers pair the problem with a proposed fix and show no delay. Weak answers wait for a better moment or blame someone else.
Model answer: The same as company secrets. I keep personal appointments private on shared calendars, store documents like passports in a secure vault, and never share details unless the executive has asked me to. I check with them on what the family can see and change.
Strong vs weak: Look for practical steps such as private events and secure storage. A weak answer is a general promise to be discreet.
Model answer: The fixed meetings and their locations, how they like to travel (airline, seat, hotel style, car or rideshare), whether anyone is traveling with them, and how much downtime they want. Then I build an itinerary with confirmations, addresses, contacts and backup options in one document.
Strong vs weak: Strong candidates ask about preferences and build a single source of truth. Weak ones book the cheapest options and send a stack of confirmation emails.
Model answer: I check rebooking options with the airline, hold the best alternative, and look at what the delay breaks on the ground: the hotel, the car, the first meeting. I message the people affected, move what I can, and send the executive a short update they will see when they land, with the new plan already in place.
Strong vs weak: Strong answers fix the downstream effects before the executive asks. Weak ones focus only on the flight.
Model answer: I work backward from the meeting date: deadlines for each section owner, a draft packet date, a review slot with the executive, and a send date to the board. I track who owes what, collect last quarter's minutes and open action items, and book prep time the day before. After the meeting I draft minutes for review and log follow-ups.
Strong vs weak: Strong EAs think in timelines and owners. Weak ones describe formatting slides the night before.
Model answer: Who is attending and their roles, the goal of the meeting, a summary of the last interaction, any open items, and the decision the executive needs to make. One page, at the top of the calendar invite or in a shared folder.
Strong vs weak: Strong answers keep it short and decision-focused. Weak ones produce long background documents nobody reads.
Model answer: I gather the numbers from finance early, keep a version-controlled deck, check that figures match across slides, and schedule a dry run. I keep the distribution list tight and track who has received what. Afterward I log questions the investors asked so the next update answers them.
Strong vs weak: Look for attention to version control and access. A weak answer treats it like any other deck.
Model answer: I capture action items with owners and dates, send a recap within the day, and add the executive's own items to their task list or calendar. I check in on items owed to the executive before the next meeting with that group.
Strong vs weak: Strong candidates own the loop. Weak ones take notes and file them.
Model answer: I find out what each meeting is about and what happens if it waits. Whatever has the higher cost of delay gets the slot. If it is genuinely close, I ask the executive with a one-line summary of each, so the decision takes ten seconds.
Strong vs weak: Strong EAs gather facts and make the decision easy. Weak ones pick the louder person or push the choice back without context.
Model answer: Routine scheduling, declining clear non-priorities, booking travel within agreed preferences, and replying to standard requests. I would agree on these boundaries in the first weeks and write them down. Anything involving money above a set amount, people decisions or external commitments goes to the executive.
Strong vs weak: Strong answers describe written boundaries that expand over time. Weak answers either ask about everything or assume broad authority.
Model answer: I would write a one-page plan with the goal, budget, dates and owners, then keep a simple tracker and send weekly updates. I bring decisions to the executive in batches rather than one at a time. Vendors report to me so the executive only sees what needs them.
Strong vs weak: Strong candidates shield the executive from noise. Weak ones forward every vendor email.
Model answer: I point out the conflict briefly and ask which one stands, with any consequences I can see. I do not quietly pick one. Then I note the decision so we both have a record.
Strong vs weak: Strong EAs raise it directly and respectfully. Weak ones guess or follow whichever was most recent.
Model answer: I ask the executive to copy me or send a quick message whenever they promise something. I also review meeting notes and sent mail for phrases like "I'll send you" and add those to a commitments list that I review with them weekly.
Strong vs weak: Look for a capture method that does not depend on the executive remembering. Weak answers rely on being told.
Model answer: Very little at first. I would spend two weeks learning their habits, then propose two or three changes with the reason for each, such as a planning session, inbox labels or a meeting-free morning. I would make changes only after they agree.
Strong vs weak: Strong candidates observe before changing things. Weak ones arrive with a fixed system they impose on everyone.
Model answer: As a partner, not a gatekeeper they resent. I share what is coming on the executive's calendar that affects them, help them get time when it matters, and keep confidential items confidential. I make sure they know the fastest way to reach the executive in an emergency.
Strong vs weak: Strong answers show they build goodwill with the team. Weak ones describe controlling access without explaining it.
Model answer: A good story names the warning sign, what they checked, how they raised it and the result. For example, spotting that a contract renewal date was two weeks away with no one assigned, and setting up the review before it lapsed.
Strong vs weak: Strong candidates show they read beyond the calendar. Weak ones struggle to name an example.
Pay the candidate for two to three hours of work using a realistic, anonymized scenario. Give them a mock week for an executive: a calendar export with fifteen meetings and three conflicts, twenty emails that include a board deadline, a vendor complaint and a personal request, and a trip that needs to happen Thursday with meetings in two cities.
Ask them to return:
Score on judgment (what they chose to protect), clarity of writing, completeness of the itinerary and the quality of their questions. Then spend twenty minutes walking through their choices. Candidates who explain trade-offs clearly tend to handle the real job well.
If you would rather meet strong candidates than run this process yourself, Ryz can place a dedicated executive assistant on your team from $3,000 a month, month to month. Ryz recruiters screen every candidate, and your EA keeps your US business hours and writes and speaks fluent English. You get a named shortlist with a plan and a price first, and most EAs start in under two weeks. To scope the role, use our executive assistant job description template, or tell us how you work.
Usually three: a short screening call, a structured interview using questions like these, and a paid exercise with a debrief. Add a conversation with the executive's chief of staff or a direct report if the EA will work closely with them.
Yes. The working relationship is close, and fit matters. The executive does not need to run every round, but they should meet the top two or three candidates and review the exercise.
An executive assistant runs the leader's time, communication and logistics. A chief of staff runs initiatives across the leadership team. Senior EAs often take on some chief-of-staff tasks, such as tracking commitments or running a project, which is why the last group of questions matters.
Ask scenario questions like the unannounced layoff example and listen for concrete habits. Also notice how the candidate talks about past bosses: someone who shares private details with you will share yours.
If most of the work is repeat business tasks such as a shared inbox, CRM updates and order entry, a virtual assistant may fit better. Our guide on executive assistant vs virtual assistant explains the split.
Questions we didn't answer? Email info@ryzlabs.com.