How to Write a Virtual Assistant Job Description That Attracts the Right Candidates

One financial advisor posted “looking for help with various tasks” and received 200 applications, none of them right. Another posted a 47-bullet-point job description requiring expertise in Asana, HubSpot, QuickBooks, Canva, copywriting, podcast editing, and bookkeeping for $9/hour and received zero qualified responses. Both mistakes are avoidable with the same seven-component framework.

A VA job description does not describe your situation, it describes the person you need and what success looks like for them. That shift in orientation changes everything: the length, the language, the specificity, and the quality of candidates who apply.

The seven-component framework below works for any VA role, any skill tier, and any industry. It takes more work than posting from memory. It produces radically better candidates.

The Seven Essential Components Every VA Job Description Must Include

Component 1: Role Title Not “Virtual Assistant.” A specific title that tells candidates what this role is about at a glance. “Executive Assistant, Calendar, Inbox, and Project Coordination.” “Social Media and Content VA.” “Bookkeeping and Administrative VA.” The title is the first filter, it should attract the right candidates and signal clearly to the wrong ones that this is not the role for them.

Component 2: Role Overview / Hook (3–5 sentences) This is your one chance to sell the role before the candidate reads the requirements. What is the business? What problem does this role solve? Why would a talented VA want this specific job? Most executives skip this section entirely or write three sentences about themselves. That is a mistake. The best candidates have options. Your hook is the reason they read the rest.

Example of a weak overview: “We are a growing company looking for a VA to help the CEO.” Example of a strong overview: “You will be the operational backbone of a 12-person e-commerce company growing 40% year-over-year. The CEO currently spends 15 hours per week on tasks that do not require her, inbox management, vendor follow-ups, and scheduling. Your job is to own those completely so she can spend her time on growth.”

Component 3: Core Responsibilities (5–8 bullet points) Specific, verifiable actions, not vague categories. “Manage inbox” is a category. “Process inbox daily, apply the provided labeling system, draft responses to vendor inquiries using approved templates, flag any client or investor communication for CEO review before responding” is a responsibility.

Each bullet should pass the same test: could a candidate reading this know exactly what they would be doing on a typical Tuesday? If the answer is no, the bullet needs more specificity.

Component 4: Required Skills, Seven Maximum This is the section where most executives destroy their candidate pool. Every additional requirement beyond seven items reduces the number of qualified candidates who apply by 30–50%. At 15 requirements, you are statistically unlikely to receive any applications from someone who meets them all, and even if you did, you would be paying far above the rate listed.

Required skills should be non-negotiables, skills without which the person cannot do the core responsibilities. Nice-to-haves belong in the next section. When in doubt, cut.

Component 5: Nice-to-Have Skills List 3–5 skills that would accelerate success in the role but are not required from Day 1. This section serves two purposes: it tells candidates what training you are willing to provide, and it gives highly qualified candidates a way to differentiate themselves from average candidates. Never put nice-to-haves in the required section, that is how unicorn job descriptions get built.

Component 6: 30/60/90-Day Success Metrics This is the component that separates excellent job descriptions from average ones, and it is the most commonly skipped. Without measurable success criteria written into the job description itself, you have no objective basis for evaluating whether the hire is working. Both parties will feel this absence.

Write specific, measurable outcomes for each phase:

• 30 days: “Inbox at zero by 9 AM daily. Calendar maintained with no double-bookings. All vendor invoices logged in QuickBooks within 24 hours of receipt.”
• 60 days: “Handling all vendor communication independently without review. Weekly project status report delivered every Friday by 3 PM.”
• 90 days: “Running daily operations with no more than 30 minutes of check-in time required from the CEO per week.”

These metrics do three things: they make your expectations concrete before the hire starts; they give the VA a clear definition of success to work toward; and they make your 90-day performance conversation objective rather than subjective.

Component 7: Working Arrangement Hours per week, time zone requirements, expected overlap window, communication tools used (Slack, email, project management software), response time expectations, and compensation range. Include the rate. Job descriptions that omit compensation waste time for both parties, qualified candidates self-select out when they do not see a number, not because the rate is wrong, but because the ambiguity signals disorganization.

Writing for Different Skill Levels: How the Language Must Change by Tier

The language of your job description signals the seniority of the hire you are actually looking for. Tier 1 and Tier 2 candidates, entry-level and experienced generalists, respond to task-focused, execution-oriented language. Tier 3 and Tier 4 candidates, specialists and senior operators, respond to outcome-focused and strategic language. Using the wrong register produces mismatches: senior candidates who dismiss your listing as beneath them, or junior candidates who apply for roles far outside their capability.

Tier 1, Entry-Level Admin ($8–15/hour) Use task-focused language. “You will manage the CEO’s calendar.” “You will process expense reports weekly.” “You will respond to customer support tickets using provided scripts.” The candidate should immediately understand: this role has defined processes, and their job is to execute them consistently and accurately.

Tier 2, Experienced Generalist ($15–25/hour) Use outcome-focused language. “You will own inbox management, with discretion to resolve any communication that does not require the CEO’s personal judgment.” “You will maintain the vendor relationship pipeline, ensuring no follow-up goes more than 48 hours without a response.” The shift to “own” signals accountability, not just execution.

Tier 3, Specialist ($25–45/hour) Use strategic language. “You will lead our content distribution strategy across three channels.” “You will design and implement the CRM migration from HubSpot to Salesforce.” These candidates need to see that the role has genuine scope, if the job description reads like Tier 1 work with a specialist title, they will not apply.

Required Skills vs. Nice-to-Haves: How to Avoid Unicorn-Hunting

The unicorn job description is the single most common self-inflicted wound in VA hiring: “Must have experience in Asana, HubSpot, QuickBooks, Canva, SEO, podcast editing, bookkeeping, and customer support. Rate: $10/hour.” The candidate who meets every requirement would charge $35–50/hour. Your $10/hour rate will produce zero qualified applicants.

The Required Skills section answers one question only: what does this person need to know to do the core responsibilities on Day 1? Everything else belongs in Nice-to-Have or in your onboarding plan.

Practical test: if the perfect candidate had all other listed skills but lacked this one, would you reject them? If no, cut it.

For most Tier 1 and Tier 2 roles, the required list runs 4–6 items: fluent English, proficiency in your primary tool stack, and any hard non-negotiable like “demonstrated QuickBooks bookkeeping.” Six items. No more.

The 30/60/90-Day Success Metrics: Making Performance Expectations Objective From Day One

The most common cause of the “I gave them 90 days and they still weren’t working out” conversation is the absence of written metrics in the original job description. Without them, both parties fill the ambiguity with their own assumptions.

Write your metrics before you post, not after you hire. Posting with metrics signals that you are an organized employer and filters out candidates who are uncomfortable being measured. The best VAs want to know exactly how performance will be evaluated.

• “30 days: Handles all Tier 1 tasks independently without requiring explanation.”
• “60 days: Produces weekly status report by Friday 3 PM. Manages vendor follow-ups without prompting.”
• “90 days: Operates as first point of contact for all admin decisions within scope. CEO check-in under 30 minutes per week.”

Three milestones. A structured check-in framework. A fair basis for a difficult conversation if the hire is not working.

The Seven Most Common Job Description Mistakes (With Fixes)

1. The Unicorn JD, 47 skills for $8/hour. Fix: cap required skills at seven; move everything else to nice-to-have.

2. The Vague Description, “Help with various tasks.” Fix: write core responsibilities specific enough to pass the Tuesday test.

3. The Task Laundry List, 60 bullet points of every task. Fix: group into 5–8 core responsibility areas.

4. Experience Inflation, requiring 10+ years of experience for a $12/hour role. Fix: Tier 1 roles need 0–2 years, not 10.

5. No Success Metrics, the description ends with requirements and no definition of success. Fix: add the 30/60/90-day section before posting.

6. Selling Too Hard, four paragraphs about the company and one sentence about the role. Fix: lead with what the VA will own.

7. Ignoring Culture Fit, no information about communication style or decision-making authority. Fix: two sentences on how the team operates and what autonomy this role carries.

Application Instructions That Filter for Quality

Most job descriptions end with “send your resume.” That is also what 200 unqualified applicants do.

Add one specific question that cannot be answered without reading the full description: “Tell us which of the three core responsibilities in this listing you are most confident handling on Day 1 and why.” Mass-appliers skip it. Qualified candidates answer it in detail, and immediately separate themselves from the noise.

Your Next Step: Writing Your First Draft Using the 7-Component Framework

Take your completed time audit, your Phase 1 and Phase 2 delegation lists, and map each delegated task to one of the seven components. The delegation list becomes your Core Responsibilities section. The tasks you marked as highest priority become the 30-day success milestones. The skills required to execute those tasks become your Required Skills list, which you then filter down to seven or fewer.

Your first draft does not need to be perfect. It needs to be specific, honest about what the role is and what it is not, and written in the language appropriate for the tier you are hiring. A specific, honest job description at $12/hour will outperform a vague, inflated one at $25/hour every time, because the candidates who apply will actually be able to do the job.

Write the description, post it, and read the first 20 applications before you adjust anything. The quality of those applications is direct feedback on the clarity of your description, and now you have the framework to improve it precisely rather than guessing.