How to write a job posting that doesn't attract unqualified applicants

Most owners who tighten up a job posting do it in the requirements section. Cut the fake must-haves. Add a real salary range. Stop asking for a four-year degree nobody currently on the team actually has. Then the same posting goes up, and the same flood of resumes rolls in from people who don’t look anything like what the role needs.

An Indeed survey of employers found that 62% now call too many unqualified applicants their single biggest hiring challenge, even though 65% of them revised a job posting in the past year specifically trying to fix it. The requirements advice they followed usually works. The catch is that a job posting has two jobs to do, and almost everyone only edits one of them.

The advice you followed only fixes half the posting

The standard fix for a flooded posting is well known by now, and for good reason. Trim the requirements down to what you’d genuinely reject someone over. Post the pay range. Cut inflated experience thresholds that describe an aspirational hire, not the actual bar. All of that advice is correct, and it works on the part of the posting it touches.

But look at what employers are actually doing with it. That same Indeed survey found 42% of employers revised a job description because they were getting too many unqualified applicants, and 25% revised specifically because candidates lacked the qualifications the role needed. Requirements editing is already the most-used lever in the toolbox. It’s not a lever people are ignoring. SHRM’s 2026 Recruiting Executives report found 53% of recruiting executives expect underqualified applicants to keep getting more common regardless, which tells you the industry doesn’t think tightening requirements is solving this on its own either.

Here’s what that gap usually means. Somewhere in the posting, a section is still doing zero filtering work, and it isn’t the one everyone’s been trained to look at.

A job posting has to answer two different questions

A candidate reading your posting is actually deciding two separate things, even if they don’t experience it that way.

The first is can I do this. That’s what the requirements section answers: the license, the years, the software, the shift availability. Get specific here and unqualified people rule themselves out before they apply.

The second is do I want to do this, specifically, this week, in this building. That’s the job of the responsibilities section, the paragraph or bullet list describing what the role actually involves day to day. Almost nobody edits this part with the same care, and it shows. It’s still where most postings say something so general that it fails to filter anyone out on the “want” question at all.

Requirements tightening is a real fix. It’s just a fix for one axis. A candidate can meet every listed requirement and still be completely wrong for what the role actually is on a Tuesday, and your posting never gave them the information to notice that before they applied. That’s a different split than the one between what candidates read and what your screening tool needs to score them well, but the two overlap: a posting doing real filtering work on both axes also happens to give a screening tool a much clearer standard to measure against.

Why the responsibilities section filters nobody

Phrases that could describe any job

Pull up almost any posting for an admin, coordinator, or front-desk role and you’ll find some version of the same six phrases: wears many hats, thrives in a fast-paced environment, provides excellent customer service, assists with day-to-day operations, other duties as assigned, works well independently and as part of a team.

Every one of those is true of almost every job in the category. None of them tells a reader what they’d actually be doing at 10am on a Tuesday. So nobody self-selects out based on them, because there’s nothing specific enough to disagree with. A candidate who hates phone work reads “provides excellent customer service” and still applies, because the phrase doesn’t say the job is 80% inbound calls.

What specific looks like instead

Take a hypothetical posting for a scheduling coordinator at a multi-location physical therapy clinic. The generic version reads: “Manage scheduling and support front-desk operations in a fast-paced clinical environment.”

A specific version says something closer to: “Answer 40 to 60 inbound calls a day rebooking missed appointments, most of them from patients who are frustrated about a cancellation. Rebuild the next day’s schedule by 5pm when a therapist calls out, which happens two to three times a month.”

Nothing about that second version is a requirement. It doesn’t ask for a certification or a number of years. But it tells a very different story about the job than “fast-paced clinical environment” does, and a candidate who can’t stand an angry phone call or reshuffling a calendar under pressure will read it and think twice. The requirements section was never built to do that kind of filtering, because qualification and fit with the actual work are two different questions with two different answers.

Won’t a more specific posting scare people off, or just make it longer

This is the real objection, and it’s worth taking seriously, because the standard advice on posting length isn’t wrong either. Candidates spend, on average, three to five minutes deciding whether to apply to a posting. A wall of text loses people who’d otherwise be a great fit.

But specific and long aren’t the same thing. “Answer 40 to 60 inbound calls a day rebooking missed appointments” is one sentence. “Provides excellent customer service in a fast-paced environment” is also one sentence. You’re not adding length. You’re spending the same words on something a candidate can actually check themselves against.

The trade you’re actually making is between two groups of the same size: applicants who would have quietly hated the job once they started it, and applicants who read the posting and thought, correctly, that it sounded like something they’d be good at and want to keep doing.

A tighter posting still won’t catch everyone, and that’s fine

Self-selection is never perfect, even with both sections doing real work. Some candidates overestimate how they’ll feel about 50 phone calls a day until they’re three weeks in. Some undersell themselves and skip a posting they’d have been great at. A posting can only screen for what someone believes about themselves before they’ve done the job. And if a flood is already sitting in your inbox from a posting you can’t rewrite retroactively, tightening the next one won’t clear this one; that’s a separate, more immediate problem.

That’s where the posting’s job ends and screening starts, and it’s worth being honest that they’re different tools solving different parts of the same problem. On Truffle, the structure actually forces the split this post is arguing for. Building a position walks you through the Job Description candidates see, then an Intake step where you name what success looks like in the first six to twelve months and which traits help or hurt on your specific team, then Qualification Questions that flag whether a candidate meets the handful of things you consider must-haves, without silently rejecting anyone before you’ve seen the rest of their application. You can’t skip straight from a vague posting to a pile of applicants the way a plain job board listing lets you.

Once candidates apply, resume screening, a one-way video interview, and a talent assessment check what the posting’s self-selection couldn’t. A resume confirms the credentials the requirements section asked about. A one-way interview shows whether someone actually comes across the way a phone-heavy, high-pressure role demands, not just whether they claim to be fine with it. An assessment shows temperament and work style under something closer to real conditions. Truffle is a candidate screening platform built for small businesses that combines all three, so the people who still don’t fit after a specific posting get caught by evidence, not by however resume number 60 happens to read at 9pm.

The posting is your cheapest screening round

Most owners have already fixed half of what a job posting can filter. The requirements section usually gets attention the moment a role starts flooding, and that attention is warranted. What rarely gets touched is the section telling candidates what the work is actually like, which means the posting is running at half its filtering capacity every time it goes live.

A job posting that answers both questions, can you do this and do you want to do this specifically, is doing screening work before a single resume lands in your inbox. That’s the cheapest round you’ll ever run, and it’s also the round almost nobody finishes writing.

Frequently asked questions about writing job postings that attract fewer unqualified applicants

Should a job posting include specific numbers and details, or does that scare candidates off?

Specific details filter better than they scare off. A candidate who reads a concrete description of the actual work and doesn’t like it wasn’t going to be a good hire anyway. The goal is accuracy, not a softer description that pulls in more people who apply without knowing what they’re signing up for.

How specific is too specific for a responsibilities section?

Aim for two or three concrete lines about the actual day-to-day, not a full shift-by-shift breakdown. The goal is giving a candidate enough to self-assess honestly, not writing a training manual. If a sentence describes something true of most jobs in the category, it’s not specific enough yet.

Does a better job posting mean I can skip screening candidates?

No. Self-selection based on a posting is never complete. Some candidates misjudge how they’ll feel about the actual work, and some undersell a real fit. A specific posting reduces the volume and improves the average quality of who applies. Screening is still what verifies who’s telling the truth about meeting your bar.

What’s the difference between a knockout question and a specific responsibilities section?

A knockout question checks whether a candidate meets a hard requirement, like a license or work authorization, usually with a yes-or-no answer. A specific responsibilities section works earlier and softer than that. It doesn’t disqualify anyone. It gives a candidate enough real information about the work to decide for themselves whether to apply at all.