Executive assistant work sample test: a practical design guide

Start with the hiring decision

What small simulation can show prioritization, written communication, accuracy, clarification, and escalation without reproducing live company work? Start with that operating question rather than a preferred title, vendor, or hiring deadline. HireExecutiveTeam readers should map the actual calendar, inbox, meeting, project, board, travel, and follow-through work that consumes leadership attention. Record the outcome, current owner, frequency, service window, sensitive data, decision dependency, and evidence of completion. Include an ordinary week and a peak period so the scope does not fail as soon as demand changes.

Separate the roles

A useful work sample mirrors important job conditions but uses fictional or sanitized information, a realistic time limit, clear instructions, accessible delivery, and an anchored rubric. It does not ask candidates to solve an active business problem for free. Write the boundary in plain language: work the role may complete under standing authority, work it may prepare for review, and work that must remain with an accountable executive or qualified specialist. A senior-sounding title, urgent request, or familiar relationship does not create permission.

Gather demand evidence

Choose one representative workflow, define the permitted assumptions, provide equal materials, and score the same observable behaviors for every finalist. Decide compensation, accommodation, retention, and reviewer access before sending the exercise. Keep confirmed facts separate from assumptions. Note where work is merely inconvenient and where delay has a real customer, governance, financial, people, security, or leadership consequence. This prevents a broad wish list from becoming an unmanageable role.

Define measurable outcomes

Turn the evidence into five to seven outcomes. Each outcome should name its trigger, source of truth, accepted output, accountable reviewer, timing, exception path, and completion evidence. Describe a representative week and known peaks. Remove generic requirements that do not connect to an outcome, and identify tools as learnable unless immediate mastery is truly necessary.

Set priority rules

Define priority before work begins. Name who resolves a collision between supported leaders, how urgency is justified, the last useful decision time, and what can wait for the next service window. Provide one queue for open work and one authoritative location for current status. Chat and email may carry alerts, but they should not become invisible competing task systems.

Control access

Design access from workflows, not status. Use separate identity, approved delegation, multifactor authentication, least privilege, secure source links, and scheduled review. Do not place credentials, unnecessary personal details, regulated data, or sensitive board and people information in coordination records. Record who approves access and who removes it when scope changes.

Assess candidates consistently

Use a structured selection process. Give candidates the same core job-related questions, anchored rating criteria, and a clear explanation of the stages. If a work sample is useful, use fictional or sanitized information, keep it bounded, make accommodations available, and do not request unpaid production work. Have the appropriate owner review employment requirements for every hiring location.

See the decision in practice

Candidates receive a fictional calendar collision, incomplete travel request, and sensitive-looking message. Strong responses clarify authority, verify the risky request, present options, and preserve a record rather than racing to complete every task. This example does not prescribe the same answer for every company. It shows why the decision should follow observed work, explicit authority, and accepted evidence rather than title prestige or a promise that one person will handle everything.

Verify finalist evidence

Check references and claims only with candidate authorization and in line with applicable requirements. Ask about the same job-relevant capabilities evaluated earlier, such as prioritization, discretion, communication, recovery, and follow-through. Document evidence and uncertainty. Do not ask for protected information or let an informal back channel replace a consistent finalist review.

Use authoritative guidance

Use EEOC guidance on employment tests and selection procedures as a current starting point for the relevant operating or selection context. Guidance can change, and it cannot resolve company-specific legal, employment, governance, tax, privacy, or security questions. Ask the qualified internal or external owner when those issues affect the decision, and record the approved rule rather than relying on memory.

Write the operating brief

Before launch, write a one-page operating brief. Include outcome, scope, exclusions, decision rights, service windows, systems, access, acceptance criteria, escalation, backup, review cadence, and exit or handoff obligations. Walk through a normal request, a missing-input case, a priority collision, and an unavailable decision owner. Revise any step that depends on private context.

Review early performance

Review the first two operating cycles closely. Sample accepted work, corrections, clarification loops, waiting time, priority overrides, after-hours exceptions, access changes, reopened decisions, and work arriving outside scope. Activity counts are not enough. A busy assistant or chief of staff can still be operating inside a system that creates rework and hides ownership.

Plan continuity

Protect continuity from the first day. Maintain current instructions in a company-approved location, keep an open-work handoff, and name a backup with appropriately limited access. Test one bounded handoff before an absence. At transition, return records, revoke access, remove forwarding and integrations, confirm open decisions, and preserve required evidence according to company policy.

Choose the next step

Connect this decision to executive assistant support, then use executive assistant interview scorecard and executive assistant finalist comparison for the adjacent workflow. HireExecutiveTeam can help a founder or leadership team translate the work into a practical support scope. Begin with one representative operating cycle, keep consequential judgment with accountable leaders, and expand only when accepted evidence supports the change.

Related resources

• executive assistant support
• executive assistant interview scorecard
• executive assistant finalist comparison