Why Does Your Job Posting Attract the Wrong Applicants?

Your job posting attracts the wrong applicants because it was written before you decided who you actually wanted. Specific in, specific out. I'm Christian Saab, founder of CPG Recruitment, and after building teams across 25+ industries in Canada and the US since 2020, I can tell you the fix is almost never in the posting itself. It's in the 17 questions you answer about your ideal candidate before you write a single line of it. One client did exactly that and went from terrible applicants to four dream candidates in one week. Nothing about her budget, her brand or her job board changed. Only the order of operations changed.

Why does a vague job posting produce vague applicants?

A vague job posting produces vague applicants because a posting is a filter, and a filter with wide holes catches everything. When your ad says "fast-paced environment," "team player" and "competitive compensation," you have described roughly every job in the country. Nobody reads that and thinks, this is not for me. So nobody screens themselves out, and the screening work falls entirely on you — 200 resumes deep, at 9pm, three weeks into a role you needed filled last month.

The applicants are not the problem. They are responding accurately to what you published. If you write a generic ad, generic people apply, and the specific person you actually wanted scrolls past it because nothing in it spoke to them.

What are the 17 questions you answer before writing a job posting?

They are 17 questions about your ideal candidate, not about the job. We work through them with clients before anything gets published, and they cover the same ground every time: what this person has actually done before, what they are doing right now, what would make them leave it, how they behave under pressure, who they need to get along with on your team, what the first 90 days look like for them, and what "great" looks like at the one-year mark.

Notice what is not on that list. Years of experience. Degree requirements. Software they should have touched. Those go in eventually, but they are the last 20% of the decision, not the first. I've written before about why your hiring standards being too low is the real bottleneck, and this is the same problem one step earlier in the process.

If you want the full 17-question template, message me and I'll send it — it's free, and it's the same one we use internally.

How specific does a job posting actually need to be?

Specific enough that the wrong person reads it and takes themselves out of the running. That is the whole bar. Not clever. Not polished. Specific.

Instead of "fast-paced environment," say what the pace actually is: you'll be juggling six live files at once and the phone doesn't stop between 8 and 11. Instead of "team player," say who they sit beside and who they'll be arguing with about priorities on a Tuesday. Instead of "opportunity for growth," say what the person in this seat two years ago is doing now.

A candidate who wants a quiet, deep-focus role will read that and move on. Good. That is a resume you didn't have to read, and a first-round interview you didn't have to run.

What actually changed for the client who tried this?

She went from terrible applicants to four dream candidates in one week, and the only thing that changed was that we answered the 17 questions before writing the ad instead of after. Same role. Same company. Same salary band. Same week of the year.

What people miss is that the 17 questions do not just improve the posting. They improve the screening, because now you know what you are screening for. They improve the interview, because your questions come out of the profile instead of out of the resume. And they improve the decision, because when two people look close, you have something written down to compare them against instead of a feeling in the room.

Should you write the ideal candidate profile or the job posting first?

The profile first, always — the posting is an output of the profile, not a substitute for it. Most business owners do it backwards. They open a blank document, write the job posting, publish it, and only figure out who they actually wanted somewhere around candidate number nine.

By then the damage is done. You have anchored your whole process to a description of duties instead of a description of a person. This is the same reason I insist on a recruitment launch meeting before a role goes live — get the definition right up front and every downstream step gets cheaper.

Does being more specific shrink your applicant pool?

Yes, and that is the point. A specific posting will get you fewer applications and more candidates, and those are two completely different numbers.

Business owners get nervous when volume drops. I understand it — 60 applications feels like progress and 11 feels like failure. But 60 applications where 3 are relevant is worse than 11 applications where 6 are relevant, because the 60 costs you a week of reading and the 11 costs you an afternoon. Volume is a vanity metric in hiring. It always has been.

If you're still ending up with the wrong people despite the volume, that's a different post: why you keep hiring the wrong person.

How do you know your job posting is working?

Count dream candidates, not applications — how many people in the pile would you be genuinely excited to hire? That's the only number that matters, and if it's zero, the posting failed no matter how full your inbox is.

The second number to watch is speed. Across our client work, defining the person properly before posting is a large part of how we've cut average time-to-fill from 68 days to 37. You are not moving faster by rushing the ad. You are moving faster by not wasting three weeks interviewing people who were never going to get the job.

Frequently Asked Questions

How long should a job posting be?

Long enough to be specific and short enough to be read — in practice, most good postings land between 300 and 600 words. Length is not the variable that matters. A 250-word posting that names the real pace, the real team and the real first 90 days will outperform a 900-word one built out of stock phrases every time.

Should you include a salary range in the job posting?

In a growing number of jurisdictions you are legally required to, and even where you aren't, leaving it out costs you good candidates who won't apply blind. Check what applies where you're hiring — CPG Recruitment keeps a breakdown of what pay transparency laws mean for hiring — and then treat the range as a filter that works in your favour, the same way the rest of the posting does.

Who should sign off on the job posting before it goes live?

Everyone who gets a vote on the hire — and that sign-off should happen on the ideal candidate profile, not on the wording of the ad. If your operations manager reads the posting for the first time after it's published, you will discover halfway through interviews that the two of you were hiring for different jobs.

Can you reuse the job posting from the last time you hired for this role?

Only after you re-answer the questions, because the role has almost certainly moved. The team around the seat changed, the tools changed, and what you learned from the last person in it changed what "great" means. Reusing an old posting is how a business ends up hiring for a job that stopped existing two years ago.

Where should you start?

Before you post your next role, stop and answer the questions about the person first. If you want help doing it properly, CPG Recruitment builds ideal candidate profiles and job postings with employers every week, and you can get in touch with me directly here. If you'd rather read the institutional version of this with the full employer checklist, CPG published a companion piece on how to write a job posting that attracts the right candidates.

And if you want the step before this one, start with the 3 steps to hire the right person.