Executive Assistant Interview Scenario Rubric

Start with the decision: job analysis

For interview work samples, job analysis matters because hiring teams observe candidate judgment while respecting candidate time. The first design choice is to define the decision this element supports. Collecting information without a decision target creates busywork and invites inconsistent interpretation. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Establish a baseline: exercise scope

For interview work samples, exercise scope matters because hiring teams observe candidate judgment while respecting candidate time. Observe the current process for a representative period before promising an improvement. Note normal demand, exceptions, dependencies, and where executive attention is actually required. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Define ownership: fictional data

For interview work samples, fictional data matters because hiring teams observe candidate judgment while respecting candidate time. Name the operator, accountable decision maker, and escalation owner separately. This prevents administrative execution from being mistaken for authority to make the underlying business decision. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Set an observable standard: time limit

For interview work samples, time limit matters because hiring teams observe candidate judgment while respecting candidate time. Translate expectations into evidence a reviewer can inspect. A status label alone is weak; a source, timestamp, next action, and acceptance condition make the work reviewable. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Test the exception path: candidate instructions

For interview work samples, candidate instructions matters because hiring teams observe candidate judgment while respecting candidate time. Walk through a realistic missing-input or urgent-change scenario. The normal path rarely exposes unclear permissions, weak handoffs, or hidden reliance on personal memory. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Protect sensitive context: scoring anchors

For interview work samples, scoring anchors matters because hiring teams observe candidate judgment while respecting candidate time. Apply least privilege and keep confidential material in its approved system. Coordination records should point to controlled sources rather than duplicate sensitive details. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Pilot before scaling: reviewer calibration

For interview work samples, reviewer calibration matters because hiring teams observe candidate judgment while respecting candidate time. Use one bounded workflow and a short review window. A pilot should reveal unclear fields, unrealistic response expectations, and decisions that still lack an owner. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Review quality fairly: accessibility

For interview work samples, accessibility matters because hiring teams observe candidate judgment while respecting candidate time. Sample both routine items and exceptions. Separate operator error from unclear instructions, unavailable access, late upstream input, and changing executive priorities. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Measure the useful outcome: feedback record

For interview work samples, feedback record matters because hiring teams observe candidate judgment while respecting candidate time. Choose measures that reveal reliability or decision speed, not raw activity. Volume can rise while value falls if rework and unresolved exceptions are hidden. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Recalibrate deliberately: validation

For interview work samples, validation matters because hiring teams observe candidate judgment while respecting candidate time. Schedule a review after the operating context changes. New leaders, systems, travel patterns, or business priorities can invalidate a previously sensible design. Write down the current state, the desired state, and the person who can approve a change. Then use one recent, non-sensitive example to see whether the rule is understandable in practice.

Scenario prompts for interview work samples

Use these prompts in a working session. They connect operating details so the team can find dependencies that a single checklist field may miss. Compare job analysis with exercise scope during interview work samples. If time limit changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare exercise scope with fictional data during interview work samples. If candidate instructions changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare fictional data with time limit during interview work samples. If scoring anchors changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare time limit with candidate instructions during interview work samples. If reviewer calibration changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare candidate instructions with scoring anchors during interview work samples. If accessibility changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare scoring anchors with reviewer calibration during interview work samples. If feedback record changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare reviewer calibration with accessibility during interview work samples. If validation changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare accessibility with feedback record during interview work samples. If job analysis changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare feedback record with validation during interview work samples. If exercise scope changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow. Compare validation with job analysis during interview work samples. If fictional data changes, identify the affected owner, approval, source, and acceptance evidence before updating the workflow.

A simple implementation sequence

Choose one representative workflow, name the accountable manager, and document the current path before changing it. Agree on a small field set and two or three acceptance tests. Run the design for a limited period, including at least one exception, then review the evidence with the people who perform and receive the work. Correct unclear permissions first, simplify fields that do not inform a decision, and publish the approved version where the team already works.

Questions to take into a provider or candidate conversation

Ask for a job-relevant example of how the person would clarify scope, protect sensitive information, surface a conflict, and document completion. Ask who reviews quality, how continuity works, and what happens when the request exceeds the agreed authority. Strong answers distinguish facts from decisions and describe escalation without claiming that every situation can be scripted.

Related resources

• Executive support services
• Executive support research
• Contact HireExecutiveTeam