Executive assistant: job description, interview questions, and screening workflow

Most owners screen an EA candidate the way they'd screen an administrative assistant: for organization and responsiveness. That's necessary, but it's not the thing that actually determines whether this hire works out. An EA's real job is making judgment calls on your behalf when you're not available to ask: which meeting actually matters more, what can wait until Monday, what needs to reach you today versus what should be handled without bothering you at all. A resume can show you someone organized. It can't show you whether you'd trust their judgment with your calendar and your inbox. This guide is built to screen for that trust, because it's the thing that separates an EA hire that frees up your time from one that just adds another person to manage.

What an executive assistant actually does at a small business

At a large company, an EA might support one executive inside a structure with a chief of staff, other EAs, and defined escalation paths. At a small business, the EA usually supports the owner or founder directly, with no layer of structure around them and no one else doing a similar job to compare notes with.

The core responsibilities, in practice:

• Owning the owner's calendar: not just scheduling, but deciding what deserves priority when requests conflict
• Filtering communication: deciding what reaches the owner immediately, what can wait, and what can be handled without involving them at all
• Handling travel, logistics, and the small but constant stream of details that would otherwise eat into the owner's own time
• Sometimes representing the owner in communication, which requires writing and speaking in a way that reflects well on them
• Managing confidential information (financial details, personnel matters, competitive information) with real discretion
• Anticipating needs before being asked, since a big part of the value is reducing how much the owner has to think about logistics at all
• Knowing the difference between a decision they can make and one they need to check on, and not defaulting to either extreme

The scheduling and logistics work is the visible part of the job, but it's rarely what makes or breaks the hire. What makes it work is judgment: can this person make a reasonable call on your behalf, understand your priorities well enough to protect your time without your constant input, and handle sensitive information the way you would yourself. That's exactly what a list of calendar tools on a resume can't show you.

Job description you can post today

Copy this, then adjust the specifics (your industry, your tools, your travel needs) to match your company.

Executive assistant
[Company name] is looking for an executive assistant to support [owner/founder name or title] directly. You'll own their calendar, filter communication, and handle the logistics and details that would otherwise eat into their time, using your own judgment on what needs their attention and what doesn't.

What you'll do
Manage a busy calendar, prioritizing and resolving conflicts using your judgment, not just first-come-first-served scheduling. Filter email and requests, deciding what needs immediate attention, what can wait, and what you can handle directly. Coordinate travel and logistics. Handle confidential information (financial, personnel, or competitive) with discretion. Draft and sometimes send communication on the owner's behalf.

What we're looking for
Real judgment under ambiguity: comfort making a reasonable call without checking in on every small decision. Strong written and verbal communication. Discretion with sensitive information, demonstrated through past experience, not just a promise. Proficiency with Excel or Sheets for tracking budgets, expenses, or schedules. Previous EA or high-level admin experience is a plus but not required if you can demonstrate the judgment this role needs.

Schedule
[Insert hours and any after-hours or travel expectations]

[Insert pay range, per your company's policy and any applicable state salary transparency requirements]

10 interview questions, and what a good answer sounds like

1. Two important people both want a meeting at the same time tomorrow. How do you decide who gets it?

You're testing decision-making under competing priorities, not a scheduling trick. A strong answer describes weighing what's actually at stake for each meeting (not just who's more senior or louder), checking whether either can move, and communicating the decision clearly to both sides. A weak answer just says "whoever asked first" with no real reasoning.

2. Tell me about a time you made a decision on someone else's behalf that turned out to be the right call, without checking in first.

This surfaces real comfort with ambiguity and judgment. Listen for a specific story: what the situation was, why they didn't check in, and how they knew it was the right call to make independently. A candidate who can't produce a real example may default to constantly checking in, which defeats the purpose of the role.

3. Now tell me about a time you made the wrong call on someone's behalf. What happened, and what did you learn?

Good candidates own the mistake plainly and describe what they changed afterward (asking more questions upfront in similar situations, checking a specific type of decision going forward). A candidate who can't admit to ever getting it wrong is either inexperienced with real ownership or not being honest with you.

4. An email arrives that looks urgent but you're not sure if it actually needs the owner's attention today. What do you do?

This tests their triage instinct. Strong answers describe a framework: checking the sender, the actual stakes, whether it can be handled without escalating, and defaulting to a quick check-in only when genuinely uncertain, not for everything. A weak answer either escalates everything or nothing.

5. Tell me about a time you had to handle genuinely confidential information. How did you make sure it stayed that way?

Listen for specifics: what they didn't share, who they didn't tell even when asked, and how they thought about who actually needed to know. A vague assurance ("I'm very trustworthy") without a real example is a flag, since discretion under real pressure is what this question is trying to surface.

6. Walk me through how you'd get up to speed on someone's priorities well enough to make calendar decisions without asking them constantly.

Good answers describe an onboarding process they'd drive themselves: asking direct questions early about what matters most, observing patterns, and checking in more at the start with the explicit goal of needing less oversight over time. A candidate with no plan for this may expect to be told everything indefinitely.

7. Describe a time you anticipated a need before being asked.

This surfaces the proactive instinct that separates a strong EA from someone who only executes instructions. Listen for a concrete story showing they were paying attention to context, not just waiting for a task list.

8. Tell me about the most complicated travel or logistics situation you've had to untangle.

You want a real story with actual complexity: a cancelled flight, a scheduling conflict across time zones, a last-minute change. Listen for how calm and methodical they were under the pressure of it, since this is a low-stakes preview of how they'll handle a genuinely stressful logistics problem for you.

9. How do you handle it when you disagree with a decision the person you support has made?

Good answers show they'd raise it directly but respect the final call, rather than either staying silent or pushing past the point of usefulness. This surfaces whether they'll actually flag something important to you or just go along with anything to avoid friction.

10. Why are you interested in supporting one person directly at a small company, rather than a team or department at a larger one?

This checks whether they understand the isolation and intensity of the role: no team of other EAs to lean on, and a much closer, higher-trust relationship with one person. A candidate who can't name a real reason may be underprepared for how different this is from a broader administrative role.

A scorecard you can score candidates against

Ten questions only help if everyone on your side is listening for the same signals. Score every candidate on the same six dimensions, so you're comparing evidence instead of a gut feeling about who seemed "put together." Copy this into a doc and fill in a row per candidate.

How to screen executive assistant candidates without losing a week to it

Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, so you can build a screening workflow around what actually matters for a hire this close to your day-to-day decisions.

EA postings pull a lot of well-formatted, similar-looking resumes, since organization is exactly the skill candidates know to foreground. What a resume can't show is judgment, discretion, or how someone actually communicates under a real scenario. That's a screening gap, not a sourcing gap.

A workflow that fits a small business hiring an EA:

• Resume screening first. Cut obvious mismatches on relevant experience and communication clarity (a resume with typos or disorganized formatting is itself a signal for a role this detail-dependent).
• A short one-way video interview for your first real look. Ask 2-3 of the scenario questions above, like the competing-meetings question or the confidential information question, so you hear how someone actually reasons through judgment calls before committing any live interview time.
• A short practical skills check for the baseline. Our basic Excel exam confirms real spreadsheet competency (budgets, expense tracking, simple formulas) without demanding a lengthy take-home, since this is a fast baseline check, not the main signal for this role.
• A live conversation only for candidates who clear the first three steps. By the time you're on a call, you already know they can reason through judgment calls and communicate clearly. The live conversation is where you check personal fit and chemistry, since you'll be working closely with this person.

Our resume screening and one-way video interview tools handle the first two steps in one place, with AI that surfaces your strongest matches against the criteria you set. You review the evidence and decide. It doesn't pick for you. For the fuller argument on what actually makes this hire work, see our guide on how to hire an executive assistant who actually makes you faster.

3 questions from the skills check we'd actually run for this role

A skills check for this role is a baseline, not the deciding factor, since judgment matters more than spreadsheet speed. These three are pulled straight from Truffle's basic Excel exam, the assessment we'd point you to for confirming real, practical spreadsheet comfort. Try them yourself before you decide what "proficient" means for your opening.

The point isn't these three questions specifically. It's that a fast, practical skills check confirms the baseline quickly, so you can spend your actual interview time testing the judgment and discretion that determine whether this hire really works out. Truffle's AI scores and surfaces the results against the bar you set. You still make the call on who clears it.

Common hiring mistakes for this role

Screening for organization instead of judgment. A well-formatted resume and a tidy interview presence tell you someone is organized. They don't tell you whether you'd trust this person's calendar decisions or discretion. Weight the judgment questions above at least as heavily as anything about tools or systems.

Skipping the "what would you do" scenario questions. It's tempting to spend the whole interview on background and rapport. The scenario questions (competing meetings, confidential information, disagreement) are where the real signal lives, and they're easy to run out of time for if you don't protect the space for them.

Underestimating the fit and chemistry factor. Unlike most roles on this list, an EA works this closely with one person by design. A candidate can pass every judgment question and still be a poor personal fit. Don't skip a real conversation just because the earlier steps looked strong.

Not being honest about the scope in the job posting. If the role is really "administrative assistant with an EA title," say so. Overselling the seniority of the role attracts candidates who'll be disappointed by the actual day-to-day, and you'll be back hiring again within months.