A useful virtual assistant interview tests prioritisation, written communication, verification habits, confidentiality, and remote follow-through. Ask for recent examples and use short job-related scenarios instead of rewarding polished but uncheckable promises. State the actual hours, tools, access level, and response expectations before scoring the answers.
Virtual assistant interview questions and red flags for a hiring manager
Use the agenda as written, then record the candidate’s evidence before choosing a 1, 3, or 5 score. The text is designed to copy into an interview document or print from your browser without a separate template.
30-minute interview agenda
0–3 min
Set the role constraints
Give every candidate the same hours, task mix, tools, and access assumptions.
“This role covers calendar, inbox, documents, and vendor coordination during [hours and time zone]. I will use the same scenarios and scorecard for every candidate.”
3–8 min
Prioritisation scenario
See how the candidate separates urgent, important, and blocked work.
“A customer meeting conflicts with a board call, an invoice is due today, and the founder asks for travel options. Talk me through your first 20 minutes.”
8–13 min
Written communication sample
Evaluate clarity, tone, and questions using work similar to the role.
“Draft a short email moving an important client meeting when the reason is confidential. Tell me what you would confirm before sending it.”
13–18 min
Verification and follow-through
Test whether the candidate checks details and closes loops rather than guessing.
“Tell me about an administrative mistake you caught before it reached a client or payment. What check found it, and what changed afterwards?”
18–23 min
Confidentiality and access
Make credential, document, and unusual-request judgment visible.
“You receive an urgent request from a familiar name asking for a confidential file through a new email address. What do you do?”
23–27 min
Remote hand-off and availability
Check how work stays visible across time zones without asking about personal circumstances.
“How do you record unfinished work, decisions, and deadlines so another person can take over when you are offline?”
27–30 min
Candidate questions and close
Let the candidate inspect the working relationship and clarify next steps.
“What do you need to know about priorities, decision rights, tools, working hours, or feedback to do this role well?”
Evidence rubric and interview scorecard
Score each criterion independently: 1 means the interview did not produce usable evidence, 3 means adequate evidence with open questions, and 5 means strong, specific, verifiable evidence. A high interview score is not proof of future performance.
Prioritisation under competing requests
Why score it: The role creates leverage only when the assistant can sequence work and surface conflicts early.
Listen for evidence: Clarifying questions, an explicit order based on consequence and deadline, communication to affected people, and a record of what remains open.
Verification follow-up: Which request would you delay, who would you notify first, and what information could change your order?
Red flags to investigate:
• Labels every request urgent without making a decision
• Promises to finish everything without communicating trade-offs
1 — weak evidence
No clear order, decision rule, or communication plan.
3 — adequate evidence
Chooses a defensible order and informs the main stakeholders.
5 — strong evidence
Prioritises by consequence and deadline, verifies assumptions, communicates early, and preserves a visible follow-up list.
Why score it: Many recipients will judge the company through messages the assistant drafts or sends.
Listen for evidence: A concise purpose, appropriate tone, the minimum necessary context, a clear next action, and questions before sending when facts are missing.
Verification follow-up: Which sentence would you change for a client, an internal teammate, and a vendor, and why?
Red flags to investigate:
• Sends a polished answer while silently inventing missing facts
• Cannot adjust tone or level of detail for the recipient
1 — weak evidence
Message is unclear, inaccurate, or missing an action and verification step.
3 — adequate evidence
Message is accurate and usable with minor editing.
5 — strong evidence
Message is concise, audience-aware, fact-checked, and makes the next action unmistakable.
Why score it: Calendar, invoice, travel, and client errors are usually reduced by explicit checks and closed loops.
Listen for evidence: A repeatable checklist, source-of-truth comparison, confirmation with the right person, documented completion, and a changed process after an error.
Verification follow-up: Show me the checklist or record you would create so another person could verify this task was complete.
Red flags to investigate:
• Relies on memory for recurring or high-consequence work
• Marks a task complete before confirming the recipient, amount, date, or required approval
1 — weak evidence
Describes effort but no reliable check, record, or closure signal.
3 — adequate evidence
Uses basic checks and records completion consistently.
5 — strong evidence
Builds proportionate verification, approval, documentation, and follow-up into the workflow.
Why score it: The role may encounter calendars, contracts, customer information, credentials, and financial documents.
Listen for evidence: Identity verification through a known channel, least-access thinking, secure sharing, escalation when uncertain, and no disclosure before confirmation.
Verification follow-up: How would you verify the requester without replying through the suspicious channel or exposing the document?
Red flags to investigate:
• Shares passwords or confidential files because the request sounds urgent
• Treats a familiar display name as sufficient identity verification
1 — weak evidence
Acts on urgency or familiarity without independent verification.
3 — adequate evidence
Pauses, verifies identity through a known channel, and escalates uncertainty.
5 — strong evidence
Combines independent verification, least access, secure handling, and clear incident documentation.
Why score it: A remote assistant must make status, blockers, and decisions visible without constant supervision.
Listen for evidence: A simple task system, owners and dates, end-of-day or shift hand-offs, proactive blocker updates, and agreed response expectations.
Verification follow-up: What would I see at the end of your shift if three tasks were finished, one was blocked, and one changed priority?
Red flags to investigate:
• Equates availability with being online at all times
• Reports blockers only after a deadline is missed
1 — weak evidence
Work status depends on live messages or memory.
3 — adequate evidence
Maintains a usable task list and communicates blockers.
5 — strong evidence
Creates clear asynchronous visibility, early escalation, and hand-offs another person can act on.
Use these after a strong or vague claim. They help you collect more job-related evidence; they are not traps and should not become questions about protected or personal circumstances.
1. What would you confirm before moving a calendar event with external guests?
Listen for: Priority, decision authority, attendee time zones, dependencies, confidentiality, and a clear replacement or next action.
Red flag: Moves the event immediately without checking the owner, impact, or attendee constraints.
2. How would you handle an invoice whose amount differs from the purchase record?
Listen for: Pauses payment, compares the source documents, records the discrepancy, and asks the authorised person or vendor for clarification.
Red flag: Approves the closest amount, edits the record to match, or relies on an unverified message.
3. Show me how you would turn an ambiguous request into a task you can complete.
Listen for: Restates the outcome, identifies missing facts, confirms deadline and owner, proposes a first step, and records the agreed scope.
Red flag: Starts work based on assumptions and plans to clarify only if somebody objects.
4. What should never be sent through ordinary email or chat in this role?
Listen for: Role-appropriate judgment about passwords, sensitive personal or financial data, access links, and confidential documents, plus a secure alternative.
Red flag: Says any information is acceptable if the recipient appears internal or the message is later deleted.