Executive assistant interview questions for board support
Interview executive assistant candidates for board-cycle judgment, version control, confidentiality, deadlines, and clean follow-through.

- Define the executive support outcome
- Match role scope to leadership cadence
- Use a structured selection process
Start with the real outcome
Board support exposes whether an executive assistant can combine exact administration with calm judgment. The work may include a calendar built months ahead, contributions from several executives, late revisions, confidential files, director preferences, and actions that must survive beyond the meeting. An interview should therefore test how a candidate makes the process visible. It should not reward someone merely for saying that they are organized or comfortable with senior stakeholders.
Diagnose the current workflow
Begin with the board workflow the role will actually support. Name the meeting cadence, packet owner, source owners, review stages, portal or document system, agenda process, minute-taking boundary, and post-meeting action process. Separate coordination from governance and legal judgment. The assistant may chase inputs, preserve versions, check completeness, and route approvals. Directors, executives, counsel, finance, and the company secretary retain the decisions and professional responsibilities assigned to them.
Define the first control
Ask the candidate to walk backward from a fictional meeting date. A strong answer identifies the final approval point, executive review, contributor deadlines, agenda lock, formatting and accessibility checks, distribution window, and a contingency for a late material change. Follow up by asking which dates are promises and which are internal buffers. This reveals whether the candidate can design a dependable sequence instead of maintaining a list of loosely related due dates.
Make ownership explicit
Use a version-control scenario. Two leaders send conflicting revisions to a financial narrative after the packet has entered final review. Ask what the candidate records, which file remains authoritative, who decides the conflict, and how recipients learn about an approved replacement. Look for a response that preserves both facts and authority. Quietly combining language or sending several files with final in their names is not sound board support.
Test the operating model
Test confidentiality with a specific boundary. A director asks the assistant for a document that is not in the approved board workspace. The candidate should verify the request, check the access rule, and route uncertainty to the authorized owner rather than making a status-based assumption. Ask how the person would handle accidental sharing, a suspicious login prompt, and offboarding. Good answers name immediate reporting and containment within assigned authority.
Protect access and judgment
Explore follow-through after the meeting. Give the candidate three decisions, five actions, and one discussion item with no decision. Ask how each would be recorded and accepted. The candidate should distinguish a decision record from minutes, an accountable owner from a participant, and evidence of completion from a casual done message. This is where board support becomes an operating system rather than a one-day event.
Choose a reviewable next step
Score every candidate against the same job-related rubric. Useful dimensions include deadline design, record accuracy, escalation, confidentiality, written clarity, stakeholder handling, and respect for decision boundaries. Record observable evidence from the answers. Avoid vague judgments about polish or executive presence. If the role requires a simulation, use fictional material, pay finalists consistently, and provide the same instructions and time limit.
Apply the framework in practice
A candidate receives a fictional timeline for a Thursday board meeting. On Tuesday morning, finance has not approved one table, the CEO changes the narrative, and a director says the portal link fails. The candidate proposes a controlled draft, identifies finance as the approval owner for the table, routes the narrative conflict to the CEO and packet owner, troubleshoots access without emailing an unrestricted attachment, and records the distribution change. The sequence gives the hiring team evidence about judgment, not just confidence.
Measure whether it works
After hiring, compare interview evidence with the first two board cycles. Review contributor deadlines met, corrections after final approval, access exceptions, executive time spent rescuing the process, actions accepted by owners, and questions escalated before harm. Use the comparison to improve the interview rubric. It should become more predictive and more closely tied to the actual board workflow, not longer for its own sake.
Review evidence before changing the system
Before changing this board support hiring system, hold an evidence review with the accountable executive, the person who performs the work, and any qualified owner needed for security, privacy, legal, tax, people, travel, or governance questions. Read the actual workflow, agreement, access record, or work sample rather than relying on a summary. Record what is confirmed, what is still an assumption, the decision owner, the safe action while information is missing, and the date when the choice will be reviewed. EEOC employment tests and selection procedures guidance provides a relevant external reference, but the responsible specialist must interpret requirements that depend on the organization's facts or location.
Write the operating brief
Turn the decision into a one-page operating brief. Include the supported leaders, intended outcome, trigger, input owner, system of record, service window, authority boundary, escalation contact, completion evidence, backup, and review date. Link board liaison support and board meeting support checklist so the surrounding service and workflow rules are easy to find. Walk through one ordinary case, one ambiguous case, and one failure case before expanding scope. If the team cannot agree on the safe response, the rule is not ready for an assistant or provider to apply under pressure.
Turn this guide into action
HireExecutiveTeam helps founders and leadership teams define and staff practical executive support. Use this guide to compare the proposed rule with the real calendar, inbox, meeting, board, travel, project, and follow-through workload. Keep executive judgment with the accountable leader, specialist decisions with qualified owners, and administrative execution within written authority. The next useful step is a small, reviewable operating cycle with evidence, not a permanent commitment based on assumptions.
Related resources
Read also: board liaison support and board meeting support checklist. Source: EEOC employment tests and selection procedures guidance.
FAQ
Who should own this decision?
The executive accountable for the outcome should approve the scope, authority, evidence standard, and exception path; support staff can prepare and maintain the operating record.
What should support do when information is missing?
Record the gap and its owner, use the safest approved default, and escalate by the last useful decision date instead of treating an assumption as permission.
When should the system be reviewed?
Review after the first two operating cycles and whenever the scope, supported leaders, access, provider personnel, service window, or risk profile changes materially.
Discuss executive support