Most virtual assistant interview questions get answers like this: the candidate says they're proactive, organised and comfortable working independently.
You ask how they handle deadlines. They say they prioritise important work and communicate clearly.
Nothing wrong with that answer. But you still have absolutely no idea what they'd do with the awkward email sitting in your inbox right now.
That's the problem with most virtual assistant interview questions. They invite people to describe their personality. And everyone describes themselves the same way.
Better questions follow a decision. What would you check? What would you do? Where does your authority end? How would you know it was done?
This guide gives you a set of questions that reveal how someone thinks, a scenario you can adapt to your own business, a scoring method that keeps you fair, and a full interview script at the end.
Here, a virtual assistant (VA) is an independent freelancer or agency you're buying a service from. The interview should help both of you decide whether the service fits.
Pick the decisions the job will actually throw at them
Before writing a single question, look at the job and find the everyday judgement calls.
- Calendar work: the difference between a slot that's free and a slot that's suitable.
- Research: deciding whether a source actually supports a claim.
- Customer support: spotting a request that's beyond their refund authority.
Pick decisions that matter for the first task. Don't spend half the interview on marketing strategy if you're hiring for document coordination.
Then, before meeting anyone, write down:
- What a strong answer would include.
- What facts you need to give them to make the question fair.
- How you'll tell a thoughtful pause from not knowing.
- What you can't learn without seeing real work.
This idea comes from structured interviewing, which the US Office of Personnel Management describes as using job-related questions and the same rating standards for everyone. You don't need their full formal process. You just need to decide what good looks like before charm takes over.
Tell them what's coming, so you see competence instead of nerves
Send the job brief and meeting details in advance:
- how long you'll talk,
- the time zone,
- whether you'll discuss a made-up scenario.
Give them an easy way to mention any accessibility or connection needs.
Tell them you'll take notes. Don't record or transcribe the call by default. If you want to, ask permission and think about how you'll handle the recording.
Start the call by confirming the job in plain words:
"We need help preparing booking records and flagging exceptions. Price decisions stay with us. Does anything there not match the service you offer?"
That gives both of you a solid starting point.
And don't use surprise pressure as a test. A candidate who takes a moment to read a scenario is being responsible, not slow. If fast live communication truly matters for the role, test that directly with a relevant situation, not by interrupting or confusing them on purpose.
Question 1: "What was your part, and how did you know it was right?"
Start with real experience:
"Tell me about a recent job similar to this one. What did you receive at the start, what did you personally do, and what showed you the result was correct?"
Let them remove names and confidential details.
If they describe what "the team" did, gently ask which part was theirs. Working in a team is real experience. But you need to know the difference between following a process and designing it, or preparing work and approving it.
Follow the evidence trail:
- Where did the information come from?
- Which check mattered most?
- What happened when something was missing?
Then ask what was outside their authority. A great answer might be: "I prepared the options, but the client made the final decision." That's not weakness. It shows they understand where their role stops.
If they haven't done this exact kind of work before, that's fine. Don't push them into inventing a story. Note the gap and move to a hypothetical scenario instead.
Question 2: hand them a messy, realistic request
Now give them a small scenario from your actual business.
Here's an example for a consultancy that wants an assistant to coordinate client appointments. The assistant can offer released slots, but can't move existing client meetings or promise work outside the agreed service.
Give them a made-up calendar summary:
- Tuesday morning: a client meeting, followed by reserved preparation time.
- Tuesday afternoon: a released, bookable slot.
Then the request:
"A customer asks for a morning consultation. They say it's urgent, but don't say why the afternoon wouldn't work. What would you do?"
A weak answer: "I'd fit them in, because customer service comes first." It sounds helpful but ignores both the rules and the preparation time.
Another weak answer: "I'd just forward it to you." No information gathered at all.
A strong answer: offer the released afternoon slot, ask what's driving the urgency, and record anything that needs the owner's decision. They don't treat empty-looking preparation time as bookable. They don't promise anything they can't authorise.
Question 3: change one fact and watch the reasoning move
This is the most revealing technique in the whole interview, and almost nobody uses it.
After they answer, change one detail:
"Now the customer says they need the consultation before a lunchtime decision at their company."
A thoughtful candidate realises the afternoon slot no longer solves the problem. They might check for other released options, gather the exact deadline, and send the owner a clear, specific request.
What you're testing: does their answer change when the facts change?
Someone who gives a memorised answer will say the same thing regardless. Someone who's actually thinking will adjust.
Two tips:
- Don't lead them. "You'd check with me first, wouldn't you?" tests agreement, not judgement. Ask "What would you do now, and what would you need to know?"
- Allow different good answers. Two different methods can both be safe and sensible. Your favourite approach isn't the only right one.
If you give one candidate an important clarification, give it to everyone else too.
Question 4: "What would you write down while you wait?"
Ask what they'd record after sending a question to you.
A case isn't finished just because a message left their inbox. It needs a status, a decision owner, and a time by which the answer still matters.
In the appointment example, a good record might say:
"Customer needs a consultation before lunchtime. No suitable released slot available. Owner needs to decide whether to offer an alternative."
And the booking stays unconfirmed until that's settled.
Then ask:
"What happens if I don't reply in time?"
A good answer might include sending an approved holding message to the customer, keeping an eye on it during their working hours, and using an agreed backup contact. It shouldn't involve inventing new authority under pressure.
Finally:
"How would you know the booking actually happened?"
They might mention checking the invitation, the recipient, the time zone and the joining link. "I sent it" isn't the same as "it's confirmed and correct."
These questions show whether someone sees a task as a click or as a case that needs to reach a proper finish.
Question 5: ask about a mistake, but not for a confession
"Tell me about a mistake or misunderstanding in your work that you can talk about without sharing anything confidential. How was it spotted and fixed?"
You're looking at the sequence:
- How was it discovered?
- Did they stop further harm?
- What did they tell the client?
- What changed afterwards?
A modest, clearly explained mistake often tells you more than a dramatic rescue story.
If someone says "I never make mistakes," ask how their work gets checked, and what happens when a client gives them wrong information. Every service needs a way to handle errors, even if they can't think of an example on the spot.
Don't push for confidential details from another client's dispute. A candidate who protects that information is showing exactly the discretion you'll want.
Question 6: the money-and-time conversation
Talk about service fit honestly:
"What availability and capacity can you genuinely commit to for this work? How would you flag if you're overloaded, going on holiday or getting a request outside the scope?"
Then:
"Which assumptions in our brief would affect your quote?"
This is a business conversation between two independent parties. The provider is deciding whether your work suits them as much as you're deciding about them.
Ask only about availability and conditions the work needs. Not family arrangements. Not a tour of their home. Not the private details of their other clients.
Score what they reasoned, not how charming they were
Decide your scoring scale before the first interview.
For the appointment scenario, you might rate four things from 1 to 3:
- Spotting the constraint (the preparation time, the authority limit).
- Taking a permitted action.
- Quality of escalation.
- Tracking until finished.
Where:
- 1 = misses something important,
- 2 = sees the issue but the handover is vague,
- 3 = safe action with clear evidence and a clear escalation.
Say a candidate scores 3, 3, 2, 2. That's 10 out of 12. But the useful bit isn't the total. It's knowing that escalation and tracking need more evidence. That's what your paid trial should test.
(Those numbers are just an illustration, not a pass mark.)
Keep serious concerns separate. Willingness to share private client information, or ignoring a clear authority limit, needs addressing even if the person is lovely to talk to. Don't let a high total hide it.
And write your score before discussing candidates with anyone else. Another person should be able to read your notes and understand why you scored as you did.
The full interview script
Adapt this to your job. Keep each question tied to something the work genuinely needs.
OPENING
We're discussing an independent service for [result]. We supply
[inputs and policies]. You'd own [routine responsibilities], while
[reserved decisions] stay with us. Is anything inconsistent with the
service you offer?
RELEVANT EXPERIENCE
Describe a comparable assignment. What did you receive, do and check?
What belonged to someone else?
Follow-up: Which source or record showed the result was right?
ORDINARY DECISION
Here's a made-up request and the rule that applies. What would you do
first, what could you finish, and what would stay unresolved?
Follow-up: What extra fact would change your decision?
CHANGED CIRCUMSTANCE
Now assume [one realistic change]. What changes in your response?
Follow-up: What would you tell the customer without promising
something you can't authorise?
OPEN-CASE OWNERSHIP
What would you record while waiting for an answer? Who needs to act,
and how does the case come back to your attention?
Follow-up: What happens if that person doesn't reply in time?
MISTAKE AND CORRECTION
Tell me about a mistake or misunderstanding you can discuss without
revealing confidential information. How was it found and fixed?
Follow-up: What changed afterwards?
SERVICE FIT
What availability and capacity can you commit to for this scope?
How would you flag overload, holidays or out-of-scope requests?
Follow-up: Which assumption in our brief would affect your quote?
CLOSE
What do you need from us to deliver this reliably? Which part would
you want to test in a short paid task before ongoing work?
Scenario ideas for other kinds of VA role
The appointment example works for scheduling. Here are starting points for other common roles. Adapt each to your real rules, and remember to change one fact afterwards.
Inbox management
"A supplier email says their bank details have changed and asks you to update our records before Friday's payment. What do you do?" Listen for: not updating anything, and verifying through a contact route you already had.
Customer support
"A customer says your colleague promised a full refund last week, but our policy only allows a partial one. What would you check, and what would you reply?" Listen for: searching the history for the promise before deciding, and not inventing a policy exception.
Bookkeeping admin
"A bank payment arrives with no reference, and two open invoices are for similar amounts. What do you do?" Listen for: not forcing a match, and flagging it for identification.
Social media
"Our product notes say a bag is 'easy to clean'. You'd like to write that it's 'waterproof'. What do you do?" Listen for: sticking to what the evidence supports.
Research
"A reseller's website lists a product specification that the manufacturer's site doesn't mention. Which do you use?" Listen for: telling the difference between a manufacturer's claim and a third party's.
In every case, the strongest answers look for evidence before acting, and know where their authority stops.
Close with a decision about the next piece of evidence
Leave time for their questions. They might ask who supplies the policies, how fast you answer exceptions, or whether the volume supports the fee. Those are fair questions from someone running their own business.
After the call, compare notes with your requirements:
- What's been shown?
- What hasn't?
- Can a short paid task answer the remaining questions?
If it's clearly not a fit, don't drag it out with a trial that can't change the answer.
Send the next step in writing. If it's a paid trial, define the scope, fee, deadline and allowed tools before work starts. If you're declining, keep it brief and factual.
If you're in the UK, the ICO's recruitment guidance covers contractors as well as employees. When checked in September 2026, it was marked as under review following the Data (Use and Access) Act. Keep only the notes you need, and be careful about uploading interview recordings to AI transcription tools without checking their data terms.
A good interview doesn't prove someone is perfect. It shows you how they'd approach a normal difficult case, and exactly what's left to test. That's a far better basis for hiring than remembering they seemed confident and friendly.
Next steps: screen your applicants before the interview, and run a paid trial afterwards. For the whole process, see how to hire a virtual assistant.
Frequently asked questions
What are the best questions to ask a virtual assistant in an interview?
Questions that follow a real decision: describe a similar job and your part in it, what you'd do with a specific realistic request, what changes if one fact changes, and how you keep unfinished work visible.
How long should a virtual assistant interview be?
Long enough to work through a few relevant scenarios properly, often 30 to 45 minutes. A few questions with good follow-ups reveal more than a long list asked quickly.
Should I record a virtual assistant interview?
Only with the candidate's knowledge and permission, and only if you have a good reason and a plan for handling the recording. Written notes against your criteria are usually enough.
What questions should I avoid asking a virtual assistant?
Avoid questions about family, personal life or anything unrelated to the work. Ask about the availability and conditions the service actually needs.
Is it a bad sign if a candidate asks clarifying questions?
Usually the opposite. A thoughtful question that spots missing information often shows better judgement than a confident answer built on a guess.