LavaStaff

EXECUTIVE ASSISTANT INTERVIEW QUESTIONS

Executive Assistant Interview Questions

An executive assistant interview is a trust audit. You are about to hand someone your calendar, your inbox, and a running commentary on everything confidential in your business, so the interview has to test judgment and discretion far more than software skills.

The questions below are organized around the four things an EA hire lives or dies on: anticipation, judgment under pressure, discretion, and communication that represents you well. Use the scenarios verbatim; they are designed so that weak candidates give confident wrong answers.

  • 20 questions
  • Employer-side guide
  • Includes a paid test task

At a glance

What this executive assistant interview kit covers

Every question comes with a note on what a strong answer sounds like, so a non-specialist can run the interview and still read the signal.

20

Interview questions with listen-for notes

4

Interview stages covered

1

Paid test task blueprint

$2,600/mo

Median nearshore executive assistant rate

Before you interview

What a executive assistant interview has to establish

The real failure mode

The difference between an executive assistant and a very good virtual assistant is direction of travel. A VA executes work you route to them. An EA intercepts work before it reaches you, makes calls in your name, and tells you things you do not want to hear, like the fact that your Thursday is unsurvivable or that you are about to double-book an investor. That requires a candidate with a spine and a track record of being trusted with authority, which is why the strongest interview signal is evidence that a previous executive let them decide things, not just do things.

What to test for

Discretion is the other non-negotiable, and it is testable. EAs see compensation data, personnel issues, deal terms, and personal matters. In the interview, watch how candidates talk about previous principals. A candidate who shares juicy details about a past executive to impress you is showing you exactly what they will do with your information. The best candidates describe past work in ways that are specific about the craft and completely opaque about the confidences.

Stage 1

Track record and trust

Establish how much authority the candidate has actually carried. Titles vary wildly; the interview must establish what was really delegated to them.

Describe the executive you supported most recently: their role, their communication style, and what they trusted you to do without review.

What to listen for: Concrete delegated authority: sending email in the executive's name, accepting or declining meetings unilaterally, managing other vendors or staff. Notice whether they describe the executive's style with professional respect while keeping specifics confidential. That balance is the job.

What is a decision you made on your executive's behalf that they never had to know about, because you handled it completely?

What to listen for: Comfort with invisible ownership. Strong EAs have dozens of these stories: rebooked travel, defused scheduling conflicts, caught errors in outgoing material. A candidate who cannot name one operated as a task executor, not an EA.

Have you ever had to push back on your executive directly? Tell me about it.

What to listen for: Whether it happened at all, and how. The most valuable thing an EA does is deliver unwelcome truths early. Listen for tact plus firmness: they raised it privately, framed it around the executive's own goals, and did not back down when it mattered.

Why are you looking for a new principal, and what would make you stay with the next one for years?

What to listen for: EA relationships are sticky when they work, so departures are informative. Fair, non-bitter reasons and a clear picture of the working relationship they want tell you whether you can actually offer that relationship.

What industries or types of executives have you supported, and where did you have to learn a whole new vocabulary?

What to listen for: Adaptability. An EA moving into your industry will drown in unfamiliar names and acronyms for a month. Candidates who have made that jump before, and can describe how they built context fast, de-risk the transition.

Stage 2

Judgment scenarios

These scenarios have no perfect answer by design. You are scoring the quality of the candidate's reasoning, their defaults under uncertainty, and whether they protect you first.

I am on a flight with no wifi for six hours. A board member emails asking to move tomorrow's meeting to today at 4 pm, and my calendar shows a conflicting call with our biggest customer. What do you do?

What to listen for: Information gathering before action: is the customer call movable, what does the board member actually need, can a 30-minute version work. Strong candidates propose a resolution to both parties without pretending to be you, and have a drafted summary waiting when you land. Weak candidates either freeze until you land or overstep by unilaterally cancelling the customer.

You learn from the finance team, in confidence, something that materially affects a decision I am about to make. The finance lead asked you not to tell me yet. What do you do?

What to listen for: Who they serve. The right instinct is that their duty runs to you, handled with care: push the finance lead to tell you immediately, or make clear they cannot sit on information that harms you. Candidates who would simply keep the secret fail the core loyalty test; candidates who would casually break every confidence fail the discretion test. The reasoning matters more than the exact answer.

My inbox gets 200 emails a day. Design your triage system: what do I see, what do you handle, what disappears?

What to listen for: A real methodology: categories, response-time rules, a daily digest of what they handled, and an explicit learning loop where your corrections tune the filter. The best answers include how they earn the right to expand what they handle over time.

You notice I have accepted three evening commitments in one week, and you know from experience that I regret this every time. What, if anything, do you do?

What to listen for: Whether they see calendar defense as part of the job. Strong EAs raise the pattern, propose which commitment to move, and increasingly enforce stated preferences without being asked. This question also reveals whether they think about the principal's wellbeing as an operating input.

Plan a three-city, five-day international trip for me with two constraints: I hate red-eyes and I need to be fresh for the final meeting. Walk me through your process.

What to listen for: Sequencing logic, buffer time, time zone arithmetic, backup options for the fragile legs, and a clean itinerary format. Listen for questions back to you, like meeting flexibility and airline preferences. Great travel planning is mostly great question-asking up front.

A journalist calls the main line and reaches you, asking to confirm a detail about the company. How do you handle it?

What to listen for: Instant recognition that this is not their call to make: take the details, commit to nothing, route to you or comms immediately, and flag it as urgent. Any candidate who would confirm or deny anything, however harmless it seems, needs media training you should not have to provide.

Stage 3

Communication and representation

An EA is the voice most people hear before they reach you. These questions test whether that voice will raise or lower your standing.

Draft, out loud, how you would decline a meeting request from someone senior who I do not want to meet, without damaging the relationship.

What to listen for: Warmth, brevity, and no fake reasons that can unravel. Strong candidates protect your optionality with honest softeners and offer a genuine alternative when appropriate. This live exercise exposes spoken polish that resumes hide.

How do you adjust tone when writing as your executive versus writing as yourself on their behalf?

What to listen for: Awareness that these are different registers with different risks. Candidates who have actually drafted in a principal's voice talk about studying sent mail, keeping a phrases file, and knowing which messages must never be ghost-written.

What does your end-of-day update to your executive look like? Walk me through a real example from your last role.

What to listen for: A tight, scannable format: decisions needed, things handled, tomorrow's shape, and early warnings. EAs who volunteer a daily digest without being asked tend to be the ones who keep principals genuinely ahead of their week.

Tell me about a time you had to manage someone more senior than you, a board member or important partner, who was being difficult about scheduling or logistics.

What to listen for: Composure and creative problem-solving with no ego. The candidate should show they can absorb friction so you never feel it, while still landing the outcome you needed.

Working remotely from Latin America, how do you build the kind of trust with an executive that in-office EAs build through physical presence?

What to listen for: A thought-through answer: aggressive responsiveness during agreed hours, a visible daily rhythm, proactive video check-ins, and over-communication in the first 90 days that relaxes as trust builds. Candidates who have done this remotely before will have specifics; nearshore time zone overlap makes their playbook credible.

Stage 4

Systems and anticipation

Great EAs run on systems that make anticipation look like magic. Make candidates show you the machinery.

What information do you keep about your executive's preferences, and in what form? Give me examples of entries.

What to listen for: The existence of a preferences document: airlines and seats, food, meeting length tolerances, people to always put through, personal dates. This artifact is the difference between an EA who anticipates and one who asks the same questions forever.

How do you prepare your executive for a meeting with someone they have never met?

What to listen for: A briefing habit: who the person is, why the meeting exists, what they likely want, the one thing to know, and the desired outcome, all in something readable in two minutes. Candidates who do this unprompted for every external meeting are operating at the right level.

What recurring review do you run on the calendar itself, and what are you looking for?

What to listen for: A weekly look-ahead pass: conflicts, missing prep time, travel buffers, meetings that should be emails, and misalignment with stated priorities. The strongest candidates describe reporting back on where the time actually went versus where the executive wanted it to go.

If you joined me next month, what would you need from me in the first two weeks to be effective by week four?

What to listen for: A concrete onboarding demand: access decisions, an hour of preference download, introductions to key contacts, and explicit authority boundaries. Candidates who ask for nothing plan to guess, and guessing EAs create incidents.

Beyond the interview

Paid test task: the compressed principal week

Give finalists a paid 90-minute simulation built from your real (sanitized) world: a week of calendar with two buried conflicts, six inbound emails of mixed importance including one from a VIP and one confidential item, and a request to plan a two-city trip at a high level. Ask for the resolved calendar, drafted replies, the trip outline, and a end-of-exercise summary to you. Score anticipation and the summary quality hardest. An EA who hands back a clean decision-ready digest under time pressure will do it every day at 5 pm.

Red flags

Executive Assistant red flags that predict a bad hire

Any one of these is worth a hard second look. Two or more, and the polished answers elsewhere in the interview stop mattering.

Shares confidential color about past principals

If they tell you another executive's secrets in an interview, they will tell yours in their next one. Specific about craft, vague about confidences is the correct posture; the reverse is disqualifying.

Has never disagreed with an executive

A candidate who cannot recall one instance of pushing back has either never been trusted enough to matter or defaults to compliance. Either way, you lose the early-warning function that makes EAs valuable.

No preferences file, no briefing habit, no look-ahead ritual

Anticipation is not a personality trait, it is tooling. Candidates who describe great instincts but no artifacts are describing luck.

Treats the role as a stepping stone to something else soon

EA relationships pay off in year two, after the preference-learning investment. A candidate whose sights are visibly set on a different function in twelve months makes that investment a write-off. Growth within the EA and chief-of-staff track is different and is a good sign.

Cannot handle interruption in the interview itself

Politely interrupt an answer and redirect them mid-interview. The job is constant redirection. A candidate who gets flustered or needs to finish their script is telling you something the resume cannot.

FAQ

Interviewing a executive assistant: FAQ

What is the difference between interviewing an EA and a VA?

Scope of authority. VA interviews test execution: will delegated tasks come back done and well-communicated. EA interviews test delegated judgment: can this person decide things in your name, intercept problems before they reach you, and hold confidential context. Practically, EA interviews need more scenario questions with no clean answer and a harder look at discretion and pushback, which is how the question sets on this page differ.

How senior does an executive assistant need to be for a founder or CEO?

Look for at least two to three years supporting a specific named principal, not general admin experience, because principal support builds the anticipation and discretion muscles the role runs on. For a first EA hire at a startup, prior startup exposure matters more than a Fortune 500 pedigree; the role is broader and messier than a large-company EA seat.

Can an executive assistant work effectively from Latin America?

Yes, and time zones are the reason nearshore works where offshore often fails for this role. An EA in Mexico City, Bogota, or Buenos Aires shares most or all of your business day, so calendar emergencies, live triage, and end-of-day debriefs happen in real time. The interview should still verify overlap hours explicitly and test live spoken English, since the role is heavy on real-time conversation.

What should an EA interview scenario include to be predictive?

Three ingredients: incomplete information, two stakeholders with competing needs, and you unavailable. That combination forces the candidate to reveal their defaults, which is what you are hiring. Scenarios with a findable right answer test preparation instead of judgment, and preparation is the easiest thing to fake.

Ready To Move

Skip the screening: hire a pre-vetted executive assistant

These questions exist because unvetted hiring is risky. LavaStaff runs this screening for you: every executive assistant candidate is interviewed, tested, and reference-checked before you ever meet them, with contracting and payroll handled.