The job description is where most VA hiring processes go wrong before they even start. A vague posting attracts a large, unqualified applicant pool; an overly detailed credential list filters out capable candidates who do not match every line item. A poorly structured description produces applications that are hard to compare and interviews that cover ground the description should have addressed upfront.
A well-written VA job description does specific work: it attracts candidates who can do the job, repels candidates who cannot, and provides the baseline for the first performance conversation once the engagement begins. This article covers what to include, what to leave out, and the most common mistakes that produce preventable hiring friction.
Why the job description matters more than you think
Most business owners treat the job description as an administrative step that precedes the real work of hiring. It is not. The job description is the specification document for the role: the clearer the specification, the easier every subsequent step becomes. Candidates self-select more accurately. Interviews produce more relevant information. Onboarding moves faster because the role was defined before the person started. Mismatches are identified earlier because the description provides an explicit standard to evaluate against.
A job description that is vague or generic produces the opposite: a broad applicant pool with no clear selection criteria, interviews that wander, and an onboarding period that involves re-defining the role because it was never clearly defined in the first place. The investment in a specific, well-structured description pays back across the entire engagement.
What to include in a VA job description
Role overview and context
The role overview answers the question a candidate asks first: what is this job, and what kind of business am I working with? A two-to-three sentence overview that describes the business, the business stage, and the general purpose of the VA role gives the candidate enough context to assess whether the environment is a fit.
Useful overview information includes the industry and business type (operations consulting firm, e-commerce brand, real estate team), the approximate business size or stage (bootstrapped founder, established SMB, scaling team of ten), and the general function the VA serves (owner's executive support, operations coordination, customer-facing support). Candidates who are not interested in the business context or stage will self-select out before applying; those who are interested will apply with genuine intent.
What to avoid in the overview: superlatives about the opportunity ("exciting," "dynamic," "growing"), vague descriptions of the culture that do not convey meaningful information, and claims about the company's trajectory that are not relevant to the candidate's daily experience in the role.
Core responsibilities
The responsibilities section is the most important part of the job description and the one most often written too vaguely. A list that says "manage communications," "support operations," and "coordinate projects" describes what a VA does at the level of a job category, not a specific role. A candidate cannot assess their fit from that description, and an interviewer cannot use it to evaluate whether a candidate's prior experience matches the actual tasks.
Write responsibilities at the task level, not the function level. Instead of "manage communications," write: "Respond to inbound customer inquiries using documented response templates and escalate non-standard requests to the owner within four hours." Instead of "support operations," write: "Maintain the weekly pipeline report by pulling data from HubSpot and the project tracker every Monday and delivering a formatted summary by 10 AM." That level of specificity lets candidates assess their prior experience against real tasks, not abstract functions.
Aim for five to eight specific responsibilities that cover the primary scope. If the role has more tasks than that, organize them by function area (administrative, communications, reporting) rather than listing every individual task. The goal is to convey the nature and scope of the work accurately, not to document every micro-task the role involves.
Tools and platform requirements
The tools section tells candidates what they need to be able to operate from day one or learn within a defined period. List the specific tools the VA will use rather than the generic category: "HubSpot CRM" rather than "CRM experience," "Asana" rather than "project management tools." Specific tool names allow candidates to accurately represent their experience and allow the interviewer to verify that experience with a practical task.
Distinguish between required experience (tools the VA must be familiar with before starting) and preferred experience (tools the VA will learn but that are not blocking). Over-specifying required tools narrows the candidate pool without improving match quality; some tools have short learning curves that do not justify treating familiarity as a hard requirement. A candidate who has worked in five project management tools and has no Asana experience specifically will typically learn Asana in a week.
Work schedule and hours expectations
The schedule section prevents one of the most common mismatches in VA engagements: a candidate who assumes flexible timing expectations and an owner who needs availability during specific business hours. Define the expected working hours, the overlap requirement if the VA is in a different time zone, and the expected weekly hours range.
Be accurate rather than aspirational about hours. A role that will realistically require fifteen to twenty hours per week should be posted as such, not as ten to fifteen hours that "might expand." Candidates who accept a role expecting fifteen hours and find themselves at twenty-five will leave or negotiate; either outcome is avoidable with an accurate description.
How to apply
The application instructions are a screening mechanism. Including a specific instruction in the application process (a brief task, a particular subject line, a specific question to answer) immediately identifies candidates who read the posting carefully from those who are mass-applying without reviewing the content. That filter is valuable enough to be worth including in every VA job posting.
A useful application instruction is a brief response to a specific question that relates to the role: "In two or three sentences, describe the most complex recurring workflow you have managed as a VA or in a prior coordination role." The responses to that question are more useful for initial screening than any amount of resume review.
What to leave out of a VA job description
Credential lists that do not predict job performance. Requiring a degree for a VA role that does not require the knowledge a degree represents narrows the candidate pool without improving match quality. Evaluate candidates on demonstrated capability in the relevant tasks, not on educational credentials that are not predictive of the work.
Personality trait lists. Descriptions that require candidates to be "self-motivated," "detail-oriented," "passionate," and "team players" describe what every hiring manager wants and what every candidate will claim to be. Those requirements do not distinguish candidates. Replace them with the specific behaviors that matter: "able to flag issues proactively before they affect deliverables" is more useful than "proactive."
Vague scope language. Phrases like "other duties as assigned," "support the team as needed," and "handle a variety of administrative tasks" communicate that the scope is not defined. Candidates with options will choose roles with clearer definitions; candidates who apply to vague postings may be hoping for a scope that differs from what you actually need.
Salary ranges that undercut the market. Posting a rate significantly below market for the required experience level produces a pool of candidates who either cannot meet the requirements or will leave quickly when a market-rate opportunity appears. The operations virtual assistant cost article covers market rate ranges by scope and experience level.
Common job description mistakes
Writing for a candidate who does not exist. A job description that requires five years of experience, fluency in six tools, and availability during US business hours for a part-time rate will produce either no qualified applicants or a poor match from a candidate who overstated their credentials to fit the description. Be honest about what the role requires and what you are offering in exchange.
Describing outcomes rather than tasks. "Help the business grow" and "make the owner's life easier" are outcomes, not responsibilities. A candidate cannot evaluate their ability to deliver those outcomes without knowing what specific tasks they would execute. Translate desired outcomes into specific tasks before writing the responsibilities section.
Leaving compensation out entirely. Posting a VA role without a rate range signals either that the rate is low or that compensation was not thought through. Candidates who do not see a rate will either not apply or will ask, adding friction before the first screening conversation. Include the rate range or hourly rate in the posting.
Treating the description as permanent. A job description written for the initial hire should be updated when the scope changes significantly. A VA hired for one function who is now covering three is operating in a role that has drifted from the original description; updating the description keeps the role definition current and provides the basis for any compensation review.
Example structure
A VA job description that works follows this general structure:
- Role overview (two to three sentences): business context, VA's purpose, and approximate scope.
- Responsibilities (five to eight bullet points): specific tasks at the level of "pull the weekly report from HubSpot by Monday at 10 AM."
- Tools (bulleted list): required tools with "preferred" labels for nice-to-haves.
- Schedule and hours: weekly hours, required overlap window, time zone.
- Rate: hourly rate or monthly retainer range.
- How to apply: specific instruction that screens for reading comprehension.
The dedicated vs. shared virtual assistant article is worth reviewing before writing the job description if you have not yet decided whether you want a VA who works exclusively for you or one who manages multiple clients simultaneously. That decision affects the scope, the hours expectation, and the rate range you should include.
The hiring virtual assistant checklist covers the steps that follow the job description: the application review process, the interview structure, and the test task design. Get a free consultation to get help defining the role and writing the job description before you post.