Executive assistant hiring

Executive assistant job description for a growing startup

Write a startup executive assistant job description around outcomes, decision rights, operating pace, and realistic support demands.

Hiring guide desk with scorecards, interview notes, and executive support planning materials
In this guide
  1. Define the executive support outcome
  2. Match role scope to leadership cadence
  3. Use a structured selection process

Start with the real operating need

A startup executive assistant job description should explain the work that gives a founder or leadership team leverage, not collect every administrative task the company has avoided. Start with the next twelve months: fundraising, hiring, customer travel, leadership meetings, board cycles, or a growing management team. Identify where executive attention is lost today and what dependable support would change. Candidates need enough operational truth to judge the role, including ambiguity, pace, working hours, location expectations, reporting line, and the systems they will inherit.

Set authority and boundaries

Separate core outcomes from possible future work. Define who sets priorities when leaders disagree, what the assistant may schedule or communicate independently, what requires approval, and which work stays with finance, people, legal, security, or functional leaders. State the expected employment arrangement and compensation information required in the hiring location. Avoid promising strategic exposure as a substitute for clear scope, sustainable workload, and fair terms.

Build the first control

Open with five measurable outcomes: a protected executive calendar, prepared leadership meetings, reliable travel, visible commitments, and a controlled inbox. Describe what accepted work looks like and how often each outcome occurs. This helps applicants compare the role with their experience rather than guessing from a broad title.

Make ownership visible

Add a representative week. Show recurring reviews, planning blocks, external meetings, travel preparation, and the likely mix of planned and urgent work. Name predictable peaks such as board weeks or fundraising. A realistic demand picture supports a better conversation about coverage and capacity.

Test the workflow

List required capabilities only when they connect to the work. Ask for evidence of prioritization, discreet communication, workflow design, and recovery from changes. Treat particular software as learnable unless immediate mastery is genuinely necessary. Do not use years of experience as a shortcut for defining senior judgment.

Protect judgment and access

Explain the selection process before applications begin. Identify interviews, a bounded and compensated work sample where appropriate, reference checks, decision timing, and accessibility contact. Use the same job-related evidence for finalists and keep personal information outside the scorecard.

Create reliable follow-through

Close with mutual-fit facts: manager, team, work location, schedule, travel, benefits, compensation, and how success will be reviewed. Have the appropriate owners review employment and pay-transparency requirements for every location in scope before publication.

See the approach in practice

A founder initially asks for an assistant who can do anything. The hiring owner maps the real week and finds that calendar collisions, investor follow-up, leadership meeting preparation, and travel changes cause most disruption. The final description names those four outcomes, gives the chief of staff priority authority, excludes bookkeeping and legal work, and shows the interview stages. Applicants can now assess the actual job instead of responding to a personality wish list.

Review evidence and improve

After hiring, compare the description with the first thirty and sixty days. Track work that arrived outside scope, decisions delayed by missing authority, recurring after-hours demand, corrections, and executive direction time. Update the operating handbook for genuine changes, but preserve the original hiring record. If the role repeatedly absorbs unrelated work, revisit ownership and capacity rather than praising flexibility while allowing the job to become undefined.

Check authoritative guidance

Before adopting this approach, review the real workflow with the accountable executive, the person doing the work, and any qualified owner needed for employment, legal, security, privacy, finance, travel, or governance questions. Use EEOC guidance on job-related selection procedures as a current starting reference, not as a substitute for advice based on the organization's facts and location. Record confirmed facts separately from assumptions, name the decision owner, and identify the safe action while information is missing.

Write the operating brief

Turn the decision into a one-page operating brief for executive assistant hiring. Include the intended outcome, trigger, inputs, source of truth, authority, service window, exception path, completion evidence, backup, and review date. Connect it to executive assistant support and executive assistant interview scorecard so the surrounding service and practical guidance stay easy to find. Walk through an ordinary case and an ambiguous case before applying the rule to consequential work.

Design for continuity

Protect continuity by keeping current records in company-approved systems and limiting access to the work a person performs now. Material changes, approvals, and exceptions should remain visible instead of being rewritten after the fact. A named backup needs to understand what is open, why it matters, which action is permitted, who owns the next decision, and when action becomes too late. Test that handoff with a bounded scenario before relying on it during an absence.

Rehearse the exception path

Run a tabletop review related to executive assistant hiring. Remove one expected input, introduce a priority collision, and make the usual decision owner briefly unavailable. Ask the team to show how the request enters, where current status lives, which action can proceed, when escalation starts, and what evidence proves completion. Treat confusion as a system defect, assign the correction, and repeat the affected step with the named backup.

Choose the next operating cycle

HireExecutiveTeam helps founders and leadership teams define and staff practical executive support. Apply this guide to the real calendar, inbox, board, travel, meeting, project, and follow-through workload. Keep executive judgment with accountable leaders and specialist decisions with qualified owners. Begin with a bounded operating cycle, review accepted evidence, and preserve the option to revise or stop the arrangement when the facts do not support expansion.

Related resources

Read also: executive assistant support and executive assistant interview scorecard. Source: EEOC guidance on job-related selection procedures.

FAQ

Who should approve this operating model?

The executive accountable for the outcome should approve scope, authority, service expectations, and exceptions, with qualified specialist owners reviewing matters in their domains.

What should support do when a rule is unclear?

Record the missing fact, use the safest approved default, and escalate to the named owner before the last useful decision date rather than treating an assumption as permission.

When should the workflow be reviewed?

Review after the first two operating cycles and whenever supported leaders, scope, access, personnel, service windows, or the risk profile changes materially.

Discuss executive support