Here’s a fun fact nobody tells you: you can run a profitable freelance business for three years, file your quarterly taxes like a responsible adult, learn to say no to scope creep — and still be a complete idiot the first time you try to hire someone. I found this out in real time, in public, on Indeed, with a job post that I now keep a screenshot of specifically so I can feel embarrassed on a schedule.
For two years it was just me. Me, my laptop, and a client roster that finally — finally — got big enough that I couldn’t answer every email the day it came in. That’s a good problem. That’s the problem you want. So I did the thing every business podcast tells you to do: I decided to hire help. What none of those podcasts mention is that “deciding to hire help” and “successfully hiring help” are separated by a swamp of mistakes so avoidable it’s almost insulting.
I want to walk you through exactly how I botched it, because I think we treat hiring like it’s instinctual — like the second you have enough money to pay someone, you’ll just know how to find the right one. You won’t. I didn’t. I’d spent years getting good at being managed by nobody, which turns out to be zero preparation for managing somebody.
The job post that attracted absolutely everyone except the person I needed
Here’s what I actually wrote, more or less word for word, for my first-ever job listing: “Looking for a Virtual Assistant to help with various tasks. Must be organized, reliable, and a self-starter. Flexible hours. Pay based on experience.”
Read that again. It says nothing. It’s the job-post equivalent of a mission statement — technically words, arranged in sentences, communicating zero information to an actual human being about what they’d do on a Tuesday. “Various tasks” could mean anything from formatting invoices to walking my dog to negotiating with my landlord. “Pay based on experience” is a sentence designed to make everyone assume I’m either lowballing them or hiding something. Spoiler: I was hiding something. I was hiding the fact that I had no idea what I was going to pay, because I hadn’t decided what the job actually was.
I posted it on a Sunday night, feeling very CEO about the whole thing. By Wednesday I had 74 applications. Seventy-four. I want you to sit with that number, because my instinct — and maybe yours — is to think “great, options!” It is not great. It is the opposite of great. When your post is vague enough, you don’t attract the right specialist, you attract everyone, because everyone can convince themselves they’re a fit for “various tasks.” I had graphic designers applying. I had a guy who does forklift certification training applying, unless that was a spam bot, which, honestly, fifty-fifty. I had people who wanted full-time salaried work applying to a post that said “flexible hours” because they read that as “remote-friendly corporate job” instead of what I meant, which was “I need maybe six hours a week and I have no idea how to describe that.”
A vague post isn’t neutral. It’s not “casting a wide net so I don’t miss anyone good.” It actively filters OUT the right people, because the person who’s actually great at, say, email management and light client communication reads “various tasks, pay based on experience” and thinks: this person doesn’t know what they need, and I don’t want to be the unpaid consultant who figures it out for them. The good ones self-select away from vague posts. The vague post is a filter, just an inverted one — it keeps the people who need everything nailed down and repels the people who’d nail it down for you.
The interview process, and I use that term extremely loosely
Here’s the part where I really let myself down. Faced with 74 applications and zero framework for evaluating them, I did what any overwhelmed person does: I skimmed for vibes. Good grammar in the cover letter, a friendly tone, a resume that didn’t look like it was assembled at 2am — that was basically my entire rubric. I did three 20-minute video calls, and in every single one, the question I asked most was some version of “so, tell me about yourself,” which is a question that tells you how someone talks about themselves and tells you nothing about whether they can do the job.
I hired a woman I’ll call Priya. Lovely on the call. Warm, funny, seemed sharp. I did not ask her to do a single task before hiring her. Not one. No sample assignment, no “here’s a fake inbox, sort it,” no “here’s a client email, draft a response.” I hired entirely on a 20-minute conversation and a gut feeling, and then I handed her access to my client email and my invoicing system, which — I want to be clear — is the digital equivalent of handing someone your car keys because they seemed nice in the parking lot.
Three weeks in, it was obvious the vibes had lied to me. Not because Priya was a bad person — she wasn’t, at all — but because “various tasks” turned out, once someone was actually doing them, to mean things she’d never done and wasn’t excited to learn on my dime. She was great at organization. She was not great at, and had no interest in, drafting client-facing copy, which was honestly half the job I actually needed done, if I’d bothered to write down what the job was before I posted it. That’s on me, not her. I set up a relationship where neither of us knew what success looked like, and then acted surprised when neither of us hit it.
We parted ways after five weeks — I’ll write about the actual “letting someone go” conversation another time, because that deserves its own post and its own therapy session. But the short version: it cost me roughly $1,400 in wages for work that didn’t move my business forward, plus the two weeks it took me to notice things weren’t working because I was too conflict-avoidant to say anything sooner. Call it an $1,800 lesson, all in, once you count what I paid myself to sit around being anxious about it.
What the job post looks like now
Here’s the version I use now, rebuilt from the wreckage. It’s not fancy. It’s specific, which turns out to be the entire trick.
“Part-time Client Communications & Ops Support, 8 hrs/week, $28/hr. You’ll own: responding to routine client emails within 24 hours using our templates, updating our project tracker in Notion every Friday, and sending invoices via our system by the 1st of each month. You will NOT be doing design work, sales calls, or social media. To apply: send one paragraph on how you’d respond to this client email [sample attached], plus your rate. No cover letters — I won’t read them.”
Notice what’s different. It says what she’ll own, not what she might touch. It says a real number — $28/hr, not “based on experience,” because “based on experience” is a sentence that exists to avoid a number, and avoiding the number is how you end up with 74 mismatched applicants instead of 12 good ones. It says what the job is NOT, which sounds unnecessary until you remember I once had a forklift-training guy apply to a VA post. And it replaces the interview-as-vibe-check with an actual work sample, built into the application itself, so I’m evaluating output instead of charisma.
That last part changed everything. I posted this version for my second hire — a subcontractor for client email support, a guy I’ll call Marcus — and got 11 applications instead of 74. Eleven, and every single one had already shown me a sample of their actual work before I spent a minute of my time on a call. I picked Marcus because his sample email was clear, warm, and correctly declined a fake refund request I’d planted in the sample — something Priya, bless her, would have just approved to keep the peace. I would never have learned that on a “tell me about yourself” call. I only learned it because I made him do the job, in miniature, before I hired him for the job at full size.
The other shift: I stopped treating the interview as a personality test and started treating it as a 20-minute working session. I’d ask Marcus-types things like “walk me through how you’d prioritize these three emails” or “here’s a slightly annoyed client message, draft a reply right now while I watch.” Uncomfortable for both of us, sure. But it’s a lot less uncomfortable than finding out five weeks and $1,400 later that vibes don’t file invoices.
The five things I nail down before I ever post a job again
If you’re about to hire your first anything — VA, subcontractor, part-time whatever — do this first. It takes an evening. It will save you weeks.
- Write the outcome, not the task list. Not “help with various tasks” — “owns X, delivers Y by Z deadline, measured by [this].” If you can’t finish that sentence, you’re not ready to post the job yet.
- Name a real number. A rate, a range, something. Vague pay language doesn’t protect you, it just filters out the people confident enough to want clarity — usually your best candidates.
- List what the job is NOT. One or two lines. It kills the mismatched applications before they ever hit your inbox.
- Build a work sample into the application, not the interview. Five minutes of real task beats twenty minutes of “tell me about yourself” every time. Look at output, not vibes.
- Decide your “not working out” signal before day one. Write down, in advance, what would make you end this. If you don’t define it ahead of time, you’ll talk yourself out of noticing it for weeks — I did, and it cost me real money to keep hoping instead of checking.
None of this makes hiring easy. I don’t think it’s supposed to be easy — you’re asking a stranger to take on a piece of a business you built out of nothing, and that’s always going to feel a little unnatural. But it stops being reckless once the job post actually says something. Mine didn’t, the first time. Now it does, and my inbox is smaller, and so is my regret.