How I write a VA job post that filters for the right people
# How I write a VA job post that filters for the right people
A great virtual assistant hire starts before anyone applies. It starts with the job post itself, the words a hundred people will read before a single one writes to you.
I learned this the slow way. My early posts pulled in a flood of the wrong people, dozens of replies that all looked the same, none of them a real fit. I sat there sorting the pile and wondering what I was doing wrong. Then I changed how I wrote the post, and the next role I hired for brought in about eighty genuinely good applicants, real people who clearly wanted that specific job. Here is what the post looked like, section by section, so you can write one like it.
Why most job posts fail
The classic mistake is the vague post. Looking for a rockstar assistant to join our amazing team. You have seen a hundred of them and they all say nothing. A post like that tries to appeal to everyone, so it lands with no one. A skilled worker reads it, cannot tell what the job actually is, and moves on. The people who do reply are the ones who reply to everything, because nothing in the post filtered them out.
The shift that fixed it for me: specificity is a filter. Every concrete detail you add, the exact tasks, the real hours, the honest pay, quietly turns away people who are a bad fit and pulls in the ones who match. A narrow, specific post feels like it should get fewer replies. It does, and that is the entire point. You trade a big pile of noise for a small stack of signal.
The anatomy of the post
The whole thing is short, shorter than you would think, and every part earns its place. Six pieces: a specific title, a short honest intro about who you are, the exact day to day tasks in plain language, the tools they will actually use, the hours, and the pay range stated in the open. No fluff, no corporate mission statement, no wall of buzzwords.
Plus one more line near the end that does more filtering than everything else combined.
A specific title
The title is the space almost everyone wastes, and it is the most valuable line you have, because it decides whether a good person opens your post at all. Do not write virtual assistant wanted. That could mean anything. Say the actual thing: part time virtual assistant for a small automation business, comfortable with spreadsheets and email.
Nothing clever, nothing catchy, and that is exactly why it works. A specific title pulls in the reader who thinks, that is me, that is the work I do. It gently pushes away the person who does not do that work, before either of you wastes time. I would rather the right forty people open the post than the wrong four hundred. Write the title for the one person you want, never for the crowd.
A short honest intro
Under the title, before any task list, I put a few plain sentences about who I am and what working with me is like. No company bio, no mission statement. I am one person running a small business with some automation, I work mostly over chat and email, I care about clear communication, and I pay on time. That is the whole intro.
It feels almost too simple, but it does something important. Good people are choosing you just as much as you are choosing them. The best applicants have options, and they read your post trying to figure out whether you are worth working for. A warm, honest, human intro says there is a real person on the other side of this, and it sets the tone for everything after.
The exact day to day tasks
This is the heart of the post and it does most of the filtering. Get specific to the point of feeling boring. Skip handle administrative duties and describe the days as they actually look. You will sort and reply to the support inbox each morning. You will move finished files into the right folders and rename them by our system. You will update a tracking sheet with the day's numbers. You will format documents from a template.
Real tasks, in words a normal person uses. A skilled worker reads that list and instantly knows whether this is work they are good at, or work they would quietly come to hate. It also screens out anyone spraying applications everywhere, because a generic reply cannot fake excitement about a specific list of tasks it never read. Plain, specific, a little boring. That is the sweet spot.
The tools and the hours
Name the real tools. We use a shared inbox, a spreadsheet, a simple project board, and a chat app. If you have used tools like these, you will be comfortable fast. That lets a good applicant size up the job in ten seconds, and it saves you from interviewing someone who has never touched the kind of software the role runs on.
Then the hours. How many per week, full time or part time, and if the work has to overlap a certain time of day, say so plainly. Never dress this up. A person is fitting your job into a real life, with a real family and a real schedule. The more honest you are about hours, the fewer painful surprises land on either of you later.
State the pay openly
Now the part most people are scared to write. Put the pay range in the post, in plain numbers. The instinct is to hide it and negotiate later, and that instinct only costs you.
Leave the pay out and two bad things happen. Experienced applicants who know their worth skip your post, because a listing that hides pay usually means the pay is poor. Meanwhile your inbox fills with people who have no idea what you are offering, so you both waste time discovering you were never in the same range.
An open, fair range does the opposite. It signals confidence and respect, tells people you value their time enough to spare them the guessing, and means everyone who replies already knows the money works for them. Be fair, be open, and put the number in the post.
The one line that changed everything
The single most powerful thing in the whole post is almost embarrassingly small. One line, tucked near the end, with a quiet request in it. When you reply, please start your message with the word banana, so I know you read this far. Or: in your first line, tell me your favorite tool for staying organised.
That is it. One tiny instruction, unrelated to skill, entirely about attention. And it is the cleanest filter I have found, because when replies come in I barely have to read most of them. Either they followed the instruction or they did not. The person who included the code word read the whole post carefully enough to catch a small ask near the end, and was thoughtful enough to honor it. The person who skipped it either never reached the end or chose to ignore directions, and attention to detail is most of what this job actually is.
It feels a little sneaky the first time. It is nothing of the sort. You are rewarding the people who did the basic, respectful thing of reading before writing. That one line will save you hours.
Write it like a human
Tone runs through every section. Write like a human talking to another human, never like a corporate template passed through three departments. Use normal words. Let some personality show. It is completely fine, good even, to say this is a small business, some days are messy, but we are kind and we pay on time.
That honesty is the draw. The best people are reading between the lines, working out whether you will be decent to work for or one more client who overpromises and underpays. A post that sounds like a fair, honest person cuts straight through the sea of copy pasted listings around it.
What to keep out
Four things stay out of my posts, and what you leave out matters as much as what goes in.
No fake urgency. Skip urgent, hiring immediately, apply now when none of it is true. Good people smell manufactured pressure and it reads as desperation.
No unpaid work. Never demand a free trial task or a sample done for nothing just to be considered. Real work deserves pay from the first minute, and asking for free labor in the listing tells every good worker exactly how you will treat them later.
No hidden pay, which we covered.
No empty buzzwords. Rockstar, ninja, guru, work hard play hard. Those words mean nothing and tend to mark a place that talks big and pays small. A post with no hype, no pressure and no games stands out precisely because almost nobody writes one.
What actually happened
The flood stopped. I got fewer replies than before, and every one was better. That one role brought in about eighty genuinely good applicants over a few days, and almost all of them were real, thoughtful, on the mark replies from people who plainly wanted this exact job. The code word did its work up front, so my first pass took minutes instead of hours. Instead of wading through hundreds of generic templates hunting for a few live ones, I read a small stack of strong candidates and chose between people who were all, honestly, hireable.
That is the trade a specific post makes. It maximises the quality of your applicants rather than the count, and hands you a pool small enough to actually read and good enough that the hard part becomes choosing.
The skeleton to copy
Up top, a specific title naming the role and a key detail or two. Then two or three honest sentences about who you are and what the work is really like. Then a short list of the exact day to day tasks, in the boring specific version. Then the tools. Then the hours, full time or part time. Then the pay range, in the open. And tucked near the end, one hidden instruction, a code word or a small question, so you instantly know who read the whole thing.
Seven parts. Write each one honestly, in your own plain voice, and resist every urge to dress it up. The shape adapts to almost any remote role, a support assistant, a data helper, a content person, and it is worth keeping a copy to reuse every time you hire.
I post mine on OnlineJobs.ph, which is a paid job board, so weigh that against your situation before using it. For more hands on breakdowns of hiring and running a small automated operation, everything is at [xavierfok.com](/).
Get new guides and videos first — join the Telegram channel.