Weekly responsibilities
How to Hire a General Virtual Assistant
A strong hiring process begins before interviews. Define the recurring workload, systems, hours, live overlap, required experience, and decisions the role may make. Then screen candidates against the same brief.
Write the role from the workload
List the work that should move every week. For a General Virtual Assistant, that may include email and calendar support, data entry, web research, CRM maintenance, document updates. Rank the responsibilities by importance so candidates can understand what the job is actually about.
Required live coverage
Main systems
Must-have experience
Quality standard
Decisions that require escalation
Screen for evidence that matches the role
Do not rely on self-ratings or long tool lists. Ask for examples that show the candidate has already done similar work and can explain their quality checks. Strong evidence for this role includes a recurring admin workflow they owned, a research or data task with clear sources, how they prioritize mixed requests, how they document handoffs and exceptions.
a recurring admin workflow they owned
a research or data task with clear sources
how they prioritize mixed requests
how they document handoffs and exceptions
Use workflow scenarios in the interview
Give the candidate a realistic version of the work and ask them to talk through the sequence, source of truth, checks, and escalation points. Their reasoning is usually more useful than a polished answer to a generic interview question.
Ask how they would begin email and calendar support.
Ask what could go wrong during data entry.
Ask what they would record after web research.
Ask which part of the workflow would make them stop and escalate.
Use the first month to prove the operating model
Start with a narrow scope, review real outputs, and increase responsibility only after the process is stable. By the end of month one, the client should be able to see whether the assistant owns the recurring queue, keeps records current, asks better questions, and surfaces exceptions before they become problems.
Week 1: systems, examples, access, and supervised repetition
Week 2: independent ownership of the first workflows
Weeks 3 to 4: score quality, fix handoffs, then add scope
Continue the topic without creating duplicate intent.
Use the canonical role, candidate hub, and supporting resources below to move to the next question.
Questions about how to hire a general virtual assistant
These answers cover the common decision points around this topic.
How do I hire a good General Virtual Assistant?
Start with a written brief covering email and calendar support, data entry, web research, CRM maintenance, required tools, weekly hours, schedule overlap, and evidence from similar work. Interview against that same brief.
What experience should I look for?
Prioritize evidence relevant to flexible recurring support across administration, research, coordination, CRM, and customer follow-up. The candidate should be able to explain what they owned, how they checked quality, and where they escalated.
Should I hire full-time or part-time?
Base the schedule on recurring workload and required coverage. Track the work for a short period if you are unsure, then choose a weekly commitment that matches the real queue.
What should happen in the first 30 days?
Limit the initial scope, give examples of good completed work, confirm access rules, review outputs frequently, and document recurring questions. Expand responsibility only after the first workflows are reliable.
Turn the guide into a clearer hiring brief.
Define the responsibilities, systems, weekly hours, schedule, and evidence that matter before comparing candidates.