A vague job post attracts vague applicants. This article covers how to write a listing that filters in the right candidates and filters out the wrong ones.
What should a good VA job post include?
Cover the actual day-to-day tasks, the tools you use, expected hours or availability, communication expectations, and any must-have skills. Candidates decide within seconds whether a role matches what they're looking for, so lead with the specifics rather than generic mission-statement language.
How specific should I be about tasks and hours?
Very specific. "General admin support" tells a VA almost nothing; "manage a 50-email daily inbox, book 5-10 appointments a week, and update a CRM" tells them exactly what the job is and lets them self-select. The same goes for hours — state whether you need 10, 20, or 40 hours a week, and whether the schedule is fixed or flexible.
Should I list required tools or software?
Yes, if the role depends on them. Naming the specific tools (a CRM, a scheduling app, an accounting platform) helps candidates with relevant experience recognize the fit immediately, and helps you avoid onboarding someone who has to learn everything from scratch.
How do I avoid attracting the wrong applicants?
Be upfront about anything that's a dealbreaker — required overlap hours, language requirements, industry experience — right in the post instead of discovering the mismatch during interviews. A realistic post about scope and pace attracts VAs who actually want that kind of role, rather than everyone who's simply looking for any job.
Does a clear job post really make a difference?
Yes — a clear, specific listing brings in better-matched applicants and saves you time later, because you spend less of your review time filtering out people who were never a fit. Vague posts generate volume; specific posts generate quality. For a first hire especially, quality of applicants matters more than quantity.