Virtual assistant interview questions for hiring someone you'll never meet
Hiring a virtual assistant removes every informal signal you would normally rely on, no shared office, no overhearing, no reading the room. What replaces it is written communication and proactive updates, because those are the only ways you'll know what's happening. The interview should therefore test how someone communicates when nobody has asked, and what they do when they're blocked and you're asleep.
What the job actually involves
A virtual assistant handles scheduling, inbox management, research, data entry, travel, invoicing and whatever else is delegated, usually across a timezone gap and usually for someone who doesn't have time to explain things twice. The work is broad and the instructions are often incomplete.
The thing that determines whether the arrangement works is the update habit. In an office you would see progress; remotely you only know what you're told. An assistant who reports proactively, flags blockers early and asks a clarifying question before spending four hours is worth several who are merely capable.
The questions, and what a good answer sounds like
Ask these as written. Each one is paired with what a strong answer sounds like, so two people rating the same candidate reach the same conclusion for the same reason.
1. You're blocked on a task and I am asleep in another timezone.
A good answer: Moves to something else, documents the blocker precisely, and has it waiting when you wake up. Strong answers include what they tried. Sitting idle and waiting is the answer that wastes a day per blocker.
2. My instructions are ambiguous and could mean two things.
A good answer: Asks before starting, with the two interpretations named and a recommendation. The recommendation is the part that separates a good assistant from a question generator.
3. How do you keep me informed without flooding me?
A good answer: A rhythm — a daily or end-of-day summary, immediate flags for blockers only. Strong answers distinguish what needs an interruption from what can wait for the summary.
4. You made a mistake that has already gone out, an email to the wrong person, a booking on the wrong date.
A good answer: Tells you immediately with the fix already in motion. Remote work makes concealment easier and more damaging, and this question is the closest available proxy for whether it happens.
5. How do you handle access to my accounts and information?
A good answer: Mentions a password manager, least privilege, not storing credentials in plain text, and returning access when work ends. Anyone with no view on this is a security exposure in a role that requires broad access.
6. You finish everything assigned and I am unreachable.
A good answer: Finds useful work — cleanup, documentation, getting ahead on recurring tasks — and says what they did. This is the self-direction question and it matters more remotely than anywhere else.
7. How do you track tasks across several different clients?
A good answer: A named system and a boundary between clients. Vagueness here predicts dropped work, and mixing clients' information is a confidentiality problem.
8. What working hours can you actually commit to, and what overlaps with mine?
A good answer: Specific and honest, including what they can't do. Overpromising on overlap is the most common cause of these arrangements failing in month one.
A scorecard you can rate against
Rate every candidate 1 to 4 on each row, and write the rating down before you watch the next one. Ratings drift badly when they're relative to whoever you just saw.
| Criterion | What a 4 looks like |
|---|---|
| Behaviour when blocked | Switches tasks and documents the blocker precisely. A 2 waits for a reply. |
| Clarifying with a recommendation | Names both readings and proposes one. A 2 either guesses or asks an open question. |
| Update rhythm | Describes a summary cadence plus immediate flags for blockers. A 2 reports only when asked. |
| Disclosure of errors | Reports a sent mistake immediately with a fix in motion; a 2 fixes quietly. |
| Credential hygiene | Mentions a password manager and least privilege. A 2 has no view on access. |
How to run the screen
- Weight written communication as heavily as spoken. Most of this relationship happens in writing, so pair the recorded answers with a short written task — a reply to an ambiguous request.
- Ask four questions, capped at two minutes. Concision matters because you'll be reading their updates every day.
- Give a small paid trial task before committing. It is cheap, and it tests the update habit in a way no interview can.
- Be explicit about hours and overlap in the interview. Mismatched expectations here end more of these arrangements than capability ever does.
- Check references on proactive communication specifically, not on general competence.
Running this on a large applicant pool is where it gets expensive. VoxScreen sends these questions as a single link, transcribes and scores every answer against criteria you set, and hands back a ranked list. Free for 50 candidates a month, no card.
Common hiring mistakes for this role
- Hiring on a skills list. Software proficiency is easy to claim and the arrangement fails on communication, not on tooling.
- Not testing writing. If most of your contact will be written, a spoken interview is testing the wrong channel.
- Skipping the credentials question. Virtual assistants get broad access to inboxes, calendars and sometimes payments, and a candidate with no security habits is a real exposure.
- Underestimating the timezone conversation. An assistant who is only reachable when you're asleep can still work well, but only if both sides plan for it deliberately.
- Using a recorded interview as the whole process. A small paid trial task is the single most informative step available and it costs very little.
Common questions
What should I ask a virtual assistant in an interview?
Ask what they do when blocked and you're unreachable, how they handle ambiguous instructions, how they keep you updated without flooding you, and what they do about an error that has already gone out. Those four cover the behaviours that make remote delegation work, none of which are on a skills list.
How do I test a virtual assistant before hiring?
Give a small paid trial task. It is the most informative step in the whole process, because it tests the update habit (whether they confirm receipt, ask a clarifying question before spending hours, and report back without being chased) which is exactly what an interview struggles to show.
How do I handle account access with a virtual assistant?
Ask about it in the interview and listen for a password manager, least privilege and returning access at the end of an engagement. Then implement it that way: shared vault rather than emailed credentials, the minimum permissions needed, and a documented offboarding step. A candidate with no view on this isn't disqualifying, but it tells you the setup work is yours.
Should virtual assistant interviews include a written task?
Yes, and it should probably outweigh the spoken round. Most of the working relationship happens in writing — updates, questions, drafted replies — and a recorded answer tests speaking instead of writing. A short task like responding to a deliberately ambiguous request tells you more about the day-to-day than any interview question.