20
Interview questions with listen-for notes
VIRTUAL ASSISTANT INTERVIEW QUESTIONS
A virtual assistant interview has one job: predict whether this person will take recurring work off your plate without creating new work in the process. Resumes for VA roles look interchangeable, so the interview carries almost all of the signal.
Use the questions below to test the three things that actually separate great VAs from mediocre ones: ownership of ambiguous tasks, written communication you never have to edit, and systems for keeping a hundred small things from slipping. Each question includes what a strong answer sounds like.
At a glance
Every question comes with a note on what a strong answer sounds like, so a non-specialist can run the interview and still read the signal.
20
Interview questions with listen-for notes
4
Interview stages covered
1
Paid test task blueprint
$2,100/mo
Median nearshore virtual assistant rate
Before you interview
The real failure mode
The most common VA hiring mistake is interviewing for pleasantness. Almost every candidate will be friendly, agreeable, and enthusiastic on a video call, because that is the easy part of the job. The hard part is what happens at 2 pm on a Tuesday when they hit a task they do not fully understand and you are in meetings all day. Weak VAs stall, guess silently, or fire off one-line questions that put the work back on you. Strong VAs make a sensible decision, document it, and flag it for review. Your questions need to surface which of those two people you are talking to.
What to test for
The second thing the interview must establish is process. A VA who keeps everything in their head will be fine for two weeks and then start dropping things as volume grows. Ask candidates to show you their system: how they track open loops, how they hand work back, how they make sure a recurring task never silently stops happening. Candidates who can describe a concrete system, whatever tool it lives in, are dramatically safer hires than candidates who promise to be careful.
Stage 1
Establish what the candidate has actually owned before. VA resumes often list tools rather than outcomes, so push every answer from what they used to what they were responsible for.
What to listen for: Specifics. A strong candidate describes real recurring duties, inbox triage rules, calendar constraints, reporting cadences, and can name what their principal cared about most. Vague answers about helping with various tasks suggest they executed one-off requests rather than owning a workload.
What to listen for: Whether anything was truly delegated to them. Candidates who never had unsupervised ownership will need much more management than their years of experience suggest. Listen for how they earned that trust, not just that they had it.
What to listen for: Self-awareness and fairness. Everyone has one of these. Strong candidates describe the mismatch factually and name what they would do differently. A candidate who blames every past client entirely, or claims it has never happened, is hiding something or lacks reflection.
What to listen for: A concrete answer with real numbers. Latin America based VAs typically overlap all or most of the US business day, so a candidate who is evasive here may be juggling another full-time commitment. Follow up on how many other clients they currently support.
What to listen for: Fit with what you are actually offering. A candidate who wants to grow into marketing strategy will quietly resent a role that is 80 percent inbox and scheduling. Honest answers here prevent the most common cause of six-month VA turnover.
Stage 2
Put the candidate inside realistic situations. You are testing judgment under ambiguity, not tool trivia. Any tool can be taught in a week; judgment cannot.
What to listen for: Whether they read the whole thread first, reconstruct what is being asked, check for commitments already made, and draft a reply for your review the first time rather than sending as you without permission. Strong candidates also say they would confirm how you want similar threads handled in the future so next time needs no review.
What to listen for: A decision, not paralysis. Good answers set a personal threshold, compare the next best option, book the sensible choice or a refundable fare, and leave a short note explaining the decision. The worst answer is waiting five hours and losing both fares.
What to listen for: Whether they gather context before acting: which meeting is more time sensitive, what can move, whether a 25-minute version solves it. Strong VAs propose a resolution to you rather than asking an open-ended question, and they protect the relationship with whichever party gets moved.
What to listen for: Checklists, calendar-driven triggers, confirmation steps, and documentation someone else could run from. This question separates candidates who have systems from candidates who have intentions.
What to listen for: A plan. Strong candidates talk about shadowing the inbox before touching it, building a preferences document as they learn your habits, proposing a weekly check-in format, and asking for a small set of fully owned tasks early to build trust. Weak candidates say they will do whatever you need.
What to listen for: Comfort with self-serve learning: documentation, video tutorials, sandbox practice. The specific tools matter less than evidence they can close a tool gap in days without hand-holding, because your stack will not match their last client's stack exactly.
Stage 3
A remote VA's writing is your writing once they draft as you, and their reliability is invisible until it fails. Test both directly.
What to listen for: Structure: what was done, what decisions were made, what needs your input, what is next. Candidates who hand back with just a done message force you to inspect everything, which erases the time they were supposed to save.
What to listen for: A real, current system in any tool. The strongest signal is a candidate willing to screen-share it on the spot. Head-based tracking is the single best predictor of dropped balls at scale.
What to listen for: Whether they disclosed it proactively. This is the highest-signal integrity question for an assistant role, because the entire relationship runs on you not needing to check their work. Watch for candidates who redirect to a mistake that was caught rather than one they confessed.
What to listen for: A tested answer: backup connection, a nearby cowork option, a charged hotspot. This is a normal professional question for remote roles across Latin America and strong candidates answer it without hesitation.
What to listen for: Candidates who assume silence means fine are risky; drift accumulates. Strong VAs push a short weekly summary regardless and explicitly ask for correction early, because they know small course corrections beat a painful reset at month three.
Stage 4
The best VAs compound: every month they own more and need less. These questions test for that trajectory.
What to listen for: Initiative with measurement. Even a small example, like turning a repeated request into a template, shows the candidate treats the role as ownership rather than task execution.
What to listen for: This tells you how to manage them, and whether they think about the collaboration as a system. Strong answers mention things like a shared priorities doc, fast decisions on flagged items, or honest feedback. It also reveals whether they have thought about their own performance at all.
What to listen for: Ambition that fits the seat. Growth into operations coordination or specialized skills is a retention asset if you can offer it. A candidate with no answer may treat the role as a placeholder; a candidate whose answer has nothing to do with the role will leave.
What to listen for: Honesty and specificity. Everyone has friction points. A candidate who can name theirs, like needing written rather than verbal instructions, is giving you a real operating manual. No answer means low self-awareness.
Beyond the interview
Before the final decision, pay finalists for a 60 to 90 minute simulation. Give them a fictional inbox of 10 to 12 messages containing two scheduling conflicts, one angry customer, one vendor invoice, several low-priority items, and one message where the right answer is to ask you a question. Ask them to process everything: draft replies, propose a calendar resolution, and hand the batch back with their notes. You will learn more from how they prioritize, write, and hand back than from any hour of interviews. Score the hand-back summary as heavily as the drafts themselves.
Red flags
Any one of these is worth a hard second look. Two or more, and the polished answers elsewhere in the interview stop mattering.
Hard-working and detail-oriented are claims. Checklists, templates, and tracking tools are evidence. A VA without systems fails exactly when you start relying on them.
Their drafts become your voice. If polished written English only appears in their pre-prepared documents and not in live chat or a quick drafting exercise, assume the resume was heavily edited.
A candidate who never asks what your company does, who they would interact with, or what success looks like is interviewing for any job, not this one. Context-free assistants stay task-takers forever.
Overcommitted VAs deliver fine for the first month, then response times slide. Ask directly how many hours per week they are currently committed and treat evasion as an answer.
You are hiring a second brain, not an echo. Push back on one of their answers during the interview and watch what happens. A candidate who folds instantly will also fold instead of flagging your mistakes.
FAQ
Two rounds plus a paid test task is the sweet spot: a 30-minute screen for communication and logistics, a 45 to 60 minute deep dive using the scenario questions on this page, then the paid simulation for finalists. More rounds than that rarely add signal for this role and cost you the best candidates, who get hired quickly.
Yes, at least once, with cameras on. You are testing the exact medium the working relationship will live in: spoken English, latency, professional setup, and how they handle a live conversation. But balance it with written exercises, since most day-to-day VA communication is written.
Match the requirement to exposure. A VA who drafts client-facing email in your name needs near-native written English and confident spoken English. A VA doing internal research and data work can be excellent at a B2 conversational level for a noticeably lower rate. Decide which role you are hiring before you screen, and test writing with a live exercise either way.
Pay 25 to 50 dollars for 60 to 90 minutes of simulated real work: inbox triage, a scheduling conflict, and a short research-and-summarize task. Never ask for free work, and never use test tasks to get real business tasks done. The paid task also signals to strong candidates that you run a professional operation, which improves your acceptance rate.
Keep planning
Budget first? See real virtual assistant rates across Latin America or browse interview questions for other roles.
Ready To Move
These questions exist because unvetted hiring is risky. LavaStaff runs this screening for you: every virtual assistant candidate is interviewed, tested, and reference-checked before you ever meet them, with contracting and payroll handled.