How to Hire an Executive Assistant: The Step-by-Step Guide

Before you post the role, spend a week on the definition. For one week, every time you do work you suspect could be delegated, write it down. Be specific. Not 'calendar', 'Tuesday afternoon, looked at my Wednesday calendar, noticed a conflict between the investor call and the team standup, moved the standup, emailed the team.'

Sort into three buckets: 'definitely delegate' (no founder context needed), 'delegate with judgment' (needs context about your priorities), and 'founder only.' The first two buckets are your EA's job description. Write the role around what the EA owns, how success is measured, and who the person is. Resist the urge to make it a list of generic skills, every EA job description on the internet says 'detail-oriented.' That filters nothing.

Lock in the parameters before sourcing. Hours, most founders start at 20 hours a week and expand. Overlap, what hours do you need them awake? US morning? Full day? That determines which market fits. Market, South Africa, LATAM, Philippines, or US-based, chosen on hours and required seniority.

Budget, for a senior remote EA at $25/hour full-time, the monthly cost is roughly $4,000. Part-time at 20 hours is $2,000. Add 15–30% if going through an agency that handles recruiting and account management.

The job posting is where most founders lose the candidates they actually want. Generic postings attract generic applicants. Specific postings attract specific applicants.

The structure that works:

Lead with the why. Two to three sentences about who you are, what your business does, and what kind of person thrives in this role. Senior candidates self-select based on this first.

Specify what they will own. Not "various administrative tasks." Specific: "You will own my calendar, inbox triage, travel logistics, vendor relationships, and meeting preparation for a US-based founder running a [specific business type]."

Be honest about pace and style. "I move fast. I expect direct communication. I want someone who will push back when I am wrong." This filters for fit before the interview, which saves everyone time.

Specify hours and overlap explicitly. "Full-time, 40 hours per week, with at least 4 hours of overlap with US Eastern morning hours (8am-12pm ET) every business day." Vague hours produce candidates with mismatched availability.

Specify pay range. "$2,800-$4,000 per month for the right candidate" filters out candidates expecting twice that and shows respect to candidates whose time you are about to use.

Specify the must-haves. "5+ years supporting senior executives, strong written English, fluent communicator on video, experienced with Google Workspace and Slack."

Specify the must-not-haves. "This is not a junior VA role. If you are looking for first-time EA experience, this is not the right fit." Counterintuitively, the negative filter sharpens the positive applications.

Resist generic phrases like "detail-oriented" and "team player." Every applicant claims these. They filter no one. The specific phrases are what filter.

Two viable approaches: a specialized recruiting firm (shortlist of 3–5 qualified candidates in 2–4 weeks, costs 15–30% of first-year comp or a flat fee), or direct LinkedIn sourcing (expect to message 100 people to filter to one hire, 20–30 hours of founder time over 4–6 weeks).

Avoid Indeed and ZipRecruiter for senior remote EA roles, saturated with junior VA candidates. Avoid Upwork and Fiverr, the senior operator pool largely isn't there.

A 20–30 minute first call to filter for basics: English fluency, communication style, hours availability, pay range alignment, basic role fit. Most candidates fail screening. That's the point, fail candidates fast so you don't spend two hours on interviews with people who could've been screened out in twenty minutes.

A 60–90 minute interview using behavioral questions where you push for specifics. 'Walk me through a time you anticipated a need before your principal asked.' 'Tell me about a time you disagreed with your principal, how did you raise it?' 'Describe a complex travel itinerary you handled where something went wrong.'

If the candidate gives a generic answer like 'I always try to anticipate needs,' ask for a specific example. If they can't, the answer is they don't actually do this. You're also listening for confidence and clarity, EAs spend their day communicating on behalf of other people. How they communicate in your interview is a direct read on how they'll communicate on your behalf.

The single highest-leverage step in the entire process. Pay a flat fee equivalent to 2–4 hours at their hourly rate. Give them real work that mimics the role.

Good trial tasks: a calendar exercise with conflicting meetings, an inbox exercise with 12 mocked emails to triage and respond to, an agenda exercise drafted from a brief, a travel exercise with constraints and a curveball. The output across candidates will be dramatically different and the difference is usually clear within the first few minutes of review.

Beyond the obvious skill assessment, certain patterns in how candidates show up are reliable predictors of how they will perform once hired.

Reschedules of the first call. Senior operators do not reschedule the first call. Once is acceptable with a strong reason. More than once, or vague reasons, is a hard signal of unreliability. The first call is the easiest professional commitment in their world right now.

Late to interview calls. Two minutes late is fine. Five plus minutes late without a heads-up is a red flag. EAs whose job is owning calendars cannot be late to their own interview calls.

Asking what your business does. Acceptable in the very first message exchange. Not acceptable in the second interview. Senior candidates research the business before the interview. The ones who do not are signaling effort level.

Generic answers in behavioral interviews. When you ask for a specific example of anticipating a need, the strong candidate gives you a specific story with names, situations, and outcomes. The weak candidate gives you a generic "I always try to..." answer. The generic answer means they cannot produce the specific story because they do not actually do this.

No questions for you. A senior candidate has questions about the role, the business, the principal, how decisions are made, what success looks like. A candidate with no questions either has not thought seriously about the role or is desperate enough to take any role. Both are bad signs.

Trial task delivered late or sloppy. The trial task is the candidate's audition. Late delivery, sloppy formatting, or surface-level work means this is how they will operate once hired. Better to find out before the offer.

Trust these signals. They are remarkably reliable.

Reference-check the top candidate with their most recent direct manager. Ask: what did they own, where did they excel, where did they struggle, would you hire them again, what kind of leader gets the best work out of them. The last question is the most useful, it surfaces management-style fit that nothing else will.

Offers are typically structured as contractor agreements or EOR arrangements through Deel or Remote. Cover: hourly rate or monthly retainer, hours expectation, time off, start date and onboarding plan, notice period (usually 2–4 weeks both sides), and confidentiality.

Most US founders start with contractor and convert to EOR after 6–12 months once the relationship is proven.

Days 1–30: shadow you. Read your inbox alongside you, sit in on meetings as a fly on the wall, learn how you make decisions. By end of week 4, they're taking first drafts of calendar moves and inbox responses.

Days 31–60: real ownership. They own the calendar end-to-end with check-ins on big decisions, handle inbox triage, run travel logistics autonomously, drive follow-ups. Days 61–90: full autonomy on the core scope. The weekly one-on-one is the main coordination touchpoint. You should be spending less than an hour per week directly managing the EA by day 90.

The single most important onboarding tool is a weekly 30-minute one-on-one, every week, religiously. Skip these and the relationship erodes. Hold them and the relationship compounds.

Most founders underestimate how much pre-work is required on the systems side to make an EA hire successful. The hire ends up blocked by access issues, missing context, and tools that were never set up for a second user.

Do this work before the EA starts.

Delegate calendar access. In Google Calendar or Outlook, give the EA full delegate access to your calendar. Not view-only. Full edit access. Anything less and they cannot do the job.

Set up email delegation. Gmail and Outlook both allow delegated email access where the EA can read and send on your behalf without you forwarding everything. Set this up before they start.

Create shared password storage. 1Password, Bitwarden, or Dashlane work fine. Add the EA to a shared vault containing the credentials they will need. Do this once and avoid the slow drip of password sharing in Slack messages.

Document your standing preferences. A one-pager covering: travel preferences (airlines, seat type, hotel brands), meeting preferences (default length, focus block times), communication preferences (response time expectations, tone). The EA reads this in week one and saves themselves dozens of clarifying questions.

Set up a shared workspace. Notion, Google Drive, or whatever you use. Create a dedicated workspace for the EA with templates for meeting notes, follow-up tracking, and SOPs. They build on this from day one rather than starting from blank.

Pre-record context videos. Five to ten short Looms (under five minutes each) covering: how you handle scheduling conflicts, how you triage email, how you make travel decisions, what your weekly operating rhythm looks like. These compress weeks of onboarding into hours.

Doing this prep before the EA starts is the single biggest accelerator of their ramp. The founders who skip it spend the first month explaining things that could have been explained once in a recorded video.