← all posts

How to Write a VA Job Post That Gets Great Applicants

A great hire starts before anyone applies. It starts with the words on the screen, the ones a hundred people will read before a single one of them ever writes to you. For a long time I got this wrong, and a bad virtual assistant job post cost me more hours than the hiring itself. My early posts pulled in a flood of the wrong people, dozens of replies that all looked the same and not one a real fit. Then I changed one thing: how I wrote the post. The video above walks through the same breakdown if you would rather watch than read.

Why most job posts fail

Once you see why most posts quietly fail, you cannot unsee it. The classic mistake is the vague post: "Looking for a rockstar assistant to join our amazing team." You have read 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 cannot tell what the job actually is, so they move on. The people who do reply are the ones who reply to everything, because there was nothing in the post to filter them out.

Here is the shift that fixed it for me. Specificity is a filter, not a limitation. Every concrete detail you add, the exact tasks, the real hours, the honest pay, quietly turns away the people who are not a fit and pulls in the ones who are. A narrow post feels like it should get you fewer replies. It does. That is the point. You are trading a big pile of noise for a small stack of signal.

The anatomy of a post that works

The post that finally worked for me was shorter than you would think, and every part of it was doing a job. There are 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 whether it is full time or part time.
• The pay range, stated openly.

No fluff, no mission statement, no wall of buzzwords. Let me take them one at a time.

The title

The title is the part almost everyone wastes, and it is the most valuable space you have, because it is the one line that decides whether a good person opens your post at all. Do not write "virtual assistant wanted." That could be anything.

Say the actual thing instead: "Part-time virtual assistant for a small automation business, comfortable with spreadsheets and email." It is not clever and not catchy, and that is exactly why it works. It pulls in the person who thinks that is me and pushes away the person who does not do that work. Write the title for the one person you actually want, not the whole crowd.

The intro

Right under the title, before any list of tasks, put a few plain sentences about who you are and what it is actually like to work with you. Not a company bio. Just the truth: you are one person running a small business, you work mostly over chat and email, you care about clear communication, and you pay on time.

Remember that good people are choosing you as much as you are choosing them. The best applicants have options, and they are reading your post to figure out if you are worth working for. A warm, honest intro tells them there is a real person on the other side of this, not a faceless company that sees them as a seat to fill.

The tasks

Next comes the heart of the post, the part that does most of the filtering: the exact day-to-day tasks, in plain language. This is where you get specific to the point of feeling boring.

Do not write "handle administrative duties." Tell them what the days look like. 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. A skilled worker instantly knows whether it is work they would enjoy, and a generic reply cannot fake excitement about a task list it never read.

The tools and the hours

After the tasks, name the tools and spell out the hours, and keep both honest. List the real ones: a shared inbox, a spreadsheet, a project board, a chat app. That lets a good applicant size up the fit in seconds.

Then the hours. Say how many per week, whether it is full time or part time, and if the work overlaps a certain time of day, say that plainly too. A person is fitting this job into a real life, so the more honest you are here, the fewer painful surprises you both get later.

The pay

Then the part most people are scared to write: state the pay range, right there in the post, in plain numbers. The instinct is to hide it and negotiate later, but that only costs you.

When you leave it out, the experienced applicants who know their worth quietly skip your post, because a hidden rate usually means the pay is not good. And you fill your inbox with people who have no idea what you are offering. A fair, open range does the opposite: it signals confidence and respect, and everyone who replies already knows the money works for them.

The hidden filter line

Now the single most powerful thing in the whole post, and it is almost embarrassing how small it is. One line, near the very end: a hidden instruction.

When you reply, please start your message with the word banana, so I know you read this far.

That is it. One tiny request that has nothing to do with skill and everything to do with attention, and it is the cleanest filter I have ever found. When the replies come in, I do not 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. The person who skipped it did not, and attention to detail is most of what this job actually is.

It feels a little sneaky the first time, but it is not. You are simply rewarding the people who read before they wrote.

Write it like a human

A quick word on tone, because it runs through every part of this. Write the post like a human talking to another human, not like a corporate template that got passed through three departments. Use normal words. Let a little personality show. It is completely fine to say some days are messy but you are kind and you pay on time. That honesty is not a weakness in a job post, it is the whole draw, and it cuts straight through the sea of copy-pasted listings around it.

What to avoid

What you leave out matters just as much as what you put in.

• No fake urgency. Do not write "urgent, apply now" when it is not true. Good people can smell manufactured pressure.
• Never ask for unpaid work in the post. Real work deserves pay from the first minute, and asking for free labor in the listing quietly tells every good worker how you will treat them later.
• No hidden pay. We covered it, but it belongs on this list too.
• Cut the empty buzzwords. Rockstar, ninja, guru. Those words mean nothing, and they tend to signal a place that talks big and pays small.

The results

So what happened when I posted the specific, honest version? The flood stopped, and that was the point. I did not get more replies, I got fewer, and every one was better. That one role brought in about eighty genuinely good applicants over a few days, almost all of them thoughtful messages from people who plainly wanted this exact job. That was my own outcome from that one post, not a promise of what yours will do.

The code word did its work up front, so my first pass took minutes, not hours. Instead of wading through hundreds of templates, I was reading a small stack of strong candidates who were all, honestly, hireable. That is the whole trade a specific post makes: it does not maximize the number of applicants, it maximizes the quality of them.

None of it is clever. It just respects the reader enough to tell the truth and ask them to pay attention. The paid job board where I post all of this is OnlineJobs.ph, and if you want to try it yourself, that is what the button below is for.