Executive Assistant Job Description Template

What to Include in an Executive Assistant Job Description

A well-written executive assistant job description does two things: it attracts candidates who actually match what you need, and it filters out everyone who does not. Most EA job postings fail at both. They use generic language like “must be organized” and “excellent communication skills” that tells a qualified candidate nothing about whether the role is the right fit and tells an unqualified candidate nothing about why they should not apply.

A strong executive assistant job description is specific, honest, and structured around what the executive actually needs, not what looks good in a template. That means naming the tools in use, describing the decision-making authority the EA will hold, specifying the availability window and communication cadence, and being explicit about the seniority and complexity of the support required.

The Six Core Elements to Include

There are six core elements every EA job description should include:

• Job title and reporting structure. “Executive Assistant to the CEO” is more specific than “Executive Assistant.” Include who the EA reports to directly and whether there is a secondary executive they will support.
• Scope of support. List the primary responsibility areas: calendar management, inbox triage, travel coordination, meeting preparation, stakeholder correspondence, project tracking, expense reporting. Be specific about which of these is the primary weight of the role.
• Tools and systems. Name every tool the EA will use regularly. Google Workspace or Microsoft 365? Asana, Notion, or Monday.com? Calendly or Acuity? Travel booking platform? Expense tool? Candidates who see their exact stack are faster to onboard and more confident in applying.
• Communication expectations. Define response time norms, the preferred communication channel for urgent requests, and whether the EA is expected to draft and send messages on behalf of the executive or prepare drafts for review only.
• Availability window. For offshore roles especially, specify the expected overlap hours with the executive’s local time zone. Candidates need to know whether this is a morning-shift or evening-shift role relative to their own location.
• Judgment level required. Some EAs handle purely tactical tasks within clear parameters. Others are trusted to make decisions, decline meeting requests on behalf of the executive, and manage sensitive stakeholder relationships. State explicitly where this role sits on that spectrum.

The more concrete each of these elements is, the better the quality of applications you receive and the faster a hired EA can contribute from day one.

Full EA Job Description Template

The template below is designed to be copied directly into a job posting or internal hiring document. Replace the bracketed placeholders with your specific details. Every section has been included because it materially affects candidate quality and onboarding speed. Trim nothing unless you have a specific reason.

How to Tailor the Template for Offshore Hiring

The template above works for any EA hire. When you are specifically recruiting an offshore executive assistant from India or the Philippines, three sections require additional specificity to produce the right candidates and set the working relationship up correctly from day one.

Time Zone and Availability Window

The single most common source of friction in offshore EA arrangements is a mismatch between what the executive expected and what the EA understood about their availability requirement. Address this directly in the job description.

India Standard Time is 10.5 hours ahead of EST. The Philippines is 13 hours ahead of EST. An EA based in either country covering US business hours is working a late shift or a split shift by local standards. Be honest about this in the posting. State the required overlap window in US time zone terms and in local time for the hiring region. Candidates who accept a role knowing the exact hours are far more likely to sustain that commitment long term.

A well-worded clause reads: “This role requires availability from 8 PM to 2 AM IST (8 AM to 2 PM EST), Monday through Friday. Additional async coverage outside these hours is encouraged but not required.”

Async Communication Norms

Offshore EAs who thrive are those who communicate well in writing, not just on calls. Add a clause to the About the Role section that explicitly describes the async-first working style: how tasks are assigned, where priorities are tracked, what the expected response time is for non-urgent messages, and how end-of-day handoff notes work.

EAs who have worked in async environments before will recognize this language immediately and self-select in. EAs who need constant real-time direction will self-select out. Both outcomes are valuable before you invest time in interviews.

English Communication Proficiency

The required qualifications section already asks for strong written English fluency, but for an offshore role it is worth reinforcing this with a practical signal. Consider adding a line in the application instructions: “Please submit a 150-word cover note (not a resume summary) describing your most complex calendar management challenge and how you resolved it.” Candidates who cannot produce 150 clear sentences will not make it past the application review, which saves everyone time.

Common Job Description Mistakes That Attract the Wrong Candidates

Even hiring managers with significant experience make predictable errors when writing EA job descriptions. These mistakes do not just reduce application quality; they actively attract candidates who are wrong for the role and filter out candidates who are right for it.

Using Vague Personality Descriptors Instead of Specific Requirements

Phrases like “self-starter,” “highly organized,” and “strong communicator” appear in virtually every EA job description and signal nothing to a qualified candidate. Every applicant believes they are a self-starter. What separates a strong EA from a weak one is not disposition but demonstrated capability in specific contexts.

Replace vague descriptors with concrete requirements. Instead of “strong communicator,” write “capable of drafting professional correspondence independently without requiring editorial review.” Instead of “highly organized,” write “maintains a shared calendar with zero double-bookings and tracks all open action items in a central project management tool.” These requirements are verifiable and they accurately describe what excellent performance looks like.

Omitting the Tools Stack

An EA who has used Google Calendar daily for three years will onboard in days. An EA who has only used Microsoft Outlook will need two to three weeks to reach the same productivity level in a Google Workspace environment. This is not a fatal gap but it is a gap, and it affects onboarding speed and early performance.

List every tool. Not just “Microsoft Office” but Microsoft 365 including Outlook, Teams, SharePoint, and OneNote. Not just “project management tools” but Asana specifically, or Monday.com, or Notion. Candidates who match your stack will move faster and cost less to onboard. Candidates who do not will know what they need to learn before they start.

Burying the Availability Requirement

Job descriptions that mention “flexible hours” without specifying what that means for an offshore hire attract candidates who will later discover the actual hours and either accept reluctantly or resign within the first few months. If the role requires EST business hours coverage from India, say that in the first paragraph. Transparency at the application stage saves weeks of onboarding investment.

Failing to Indicate Decision-Making Authority

There is a meaningful difference between an EA who drafts emails for executive approval and one who sends correspondence on behalf of the executive. There is a difference between an EA who researches travel options and one who books without pre-approval. EAs who are given broader authority than they expected feel exposed. EAs given less authority than they expected feel micromanaged. Specify the level of autonomous action the role requires so candidates can honestly assess whether it fits their working style and experience level.

Listing Too Many Nice-to-Have Items as Requirements

When a job description lists 15 required qualifications, qualified candidates who meet 12 of them frequently self-screen out, assuming they are not a strong enough match. Reserve the required section for genuine non-negotiables. Put everything else in a clearly labeled nice-to-have section. This expands your qualified applicant pool without lowering your hiring bar.

How Kore BPO Sources Pre-Vetted Executive Assistants

Writing a strong job description is the foundation, but sourcing and vetting candidates at scale is where most companies hit a bottleneck. Posting to job boards produces volume but not quality. Internal referrals are inconsistent. Building a sourcing pipeline from scratch for a single hire is expensive and slow.

Kore BPO runs a dedicated offshore EA sourcing operation with active talent pools in India and the Philippines. When a client engages us with a scope document or a completed job description, here is what happens on our end before a profile reaches the client’s inbox.

Structured Sourcing Against the Scope

We do not post to job boards and wait. Our sourcing team actively searches our talent database and live networks for candidates whose prior experience matches the specific scope elements in your job description. If you need someone with board-level correspondence experience and Calendly proficiency, we filter for exactly that, not just “executive assistant experience” broadly.

Writing Assessment Before Interview

Every EA candidate completes a written exercise before we present them to a client. The exercise involves drafting a meeting follow-up email from a set of bullet-point notes, editing a piece of correspondence that contains errors, and writing a brief summary of a scheduling conflict and how they would resolve it. Candidates who cannot produce clean, professional written output at this stage do not advance, regardless of their resume.

Tool Proficiency Verification

We verify tool experience through targeted questions during our screening call, not just through resume review. A candidate who lists Google Workspace on their resume is asked to describe specifically how they structure a shared calendar for a CEO with five recurring meeting series and three time zones to manage. The specificity of the answer tells us whether the experience is real.

Profiles in 2-5 Business Days

After a scope call, clients receive 2-3 pre-vetted EA profiles within 2-5 business days. Each profile includes a resume, writing samples from the assessment, tool verification notes, availability confirmation, and a sourcing summary from our team covering why this candidate is a match for your specific requirements. Zero upfront fees. You pay only after you hire.

If you have completed or adapted the template in this guide, sharing it with us on a 30-minute scope call is the fastest path to qualified candidates. Our sourcing team will match against your exact requirements rather than a generic EA profile.

Frequently Asked Questions