Most job descriptions are written to be fair to everyone who might apply. That is exactly why they fail. A posting that tries not to exclude anyone ends up describing nobody in particular, and the result is a stack of eighty applications where maybe four are worth a phone call. The fix is not a better ATS or a longer screening process. It is a job description written to filter, not to welcome.
The duties list is doing the wrong job
Open ten job postings for the same role across ten different organizations and you will find the same bullet points rearranged: manage communications, support the team, assist with events, other duties as assigned. None of that tells a reader whether they are the right person, because none of it describes what the job actually requires on a hard Tuesday.
Duties describe the job in the abstract. Filters describe the job in the specific, and specificity is what makes a stranger self-select in or out before they ever send a resume. A finance coordinator posting that says “reconcile accounts” gets applicants who took one bookkeeping class in college. A posting that says “close the books by the fifth business day of the month using QuickBooks, and flag variances over two percent before the director meeting” gets applicants who have actually done that, or who read it and quietly decide not to apply. Both outcomes save you time.
The goal of a posting is not maximum applications. It is maximum signal per applicant. A posting that produces fifteen qualified applicants beats one that produces two hundred unqualified ones, even though the second number looks better in a hiring dashboard.
Write the Tuesday, not the title
Before you write a single bullet point, describe an actual Tuesday the person will have three months from now. Not their career trajectory, not the mission of the organization, the Tuesday. What arrives in their inbox at 9am, what they are expected to have finished by 5pm, who they talk to in between, and what happens if they drop something. This single exercise surfaces the real requirements faster than any competency framework.
- Array
- Array
- Array
- Array
The three filters that matter more than a skills list
Skills lists are easy to pad and easy to fake. Three other filters do more work in practice, because they are harder to misrepresent on a resume and easier to self-assess honestly.
- State the real pace of change. Some roles are stable: same process, same calendar, every week. Others are chaotic: priorities shift daily, half the job is improvising. Say which one yours is. People who thrive on one burn out fast in the other, and this single sentence screens for fit better than a personality test.
- State the autonomy level honestly. “Works independently” means different things at different organizations. Does this person make decisions and report them, or do they check every decision first? Vague autonomy language is the number one cause of early-hire regret on both sides.
- State what good looks like in 90 days. Not a vision statement, a checkable outcome: the volunteer schedule runs two weeks out with no manager intervention, or the client pipeline has zero leads older than five days without a follow-up logged. A concrete 90-day bar filters out people who are applying because the title sounds nice.
Where salary ranges and must-haves actually belong
Posting a real salary range is one of the highest-leverage filtering tools available and most organizations still avoid it, usually out of habit rather than strategy. A range tells applicants immediately whether the role matches their situation, and it removes an entire category of mismatched applications that otherwise burn a screening call each.
| Section | What belongs there | What does not |
|---|---|---|
| Must-haves | 3 to 5 non-negotiables tied to actual tasks, e.g. "comfortable leading a room of 20 volunteers" | Vague traits like "team player" or "passionate" |
| Nice-to-haves | Skills that shorten ramp-up time, e.g. "experience with a CRM or church database" | Anything you would reject a great candidate for lacking |
| Compensation | A real range, even a wide one, plus benefits that matter (healthcare, flexible hours, remote days) | "Competitive salary" with no number |
| Culture notes | One or two honest sentences about pace and structure | A paragraph of mission statement copied from the website |
Screen with one question, not one more form field
Application forms tend to grow a field at a time until they become a wall nobody finishes. A better filter is a single, specific question that cannot be answered with a template cover letter. Ask for a two-sentence answer to something only a person who has actually done the work can answer well: “Describe a time you had to tell a volunteer or client no. What did you say?” Generic applicants skip it, submit something generic, or write three paragraphs that answer a different question entirely. Specific applicants answer it in four sentences and you already know more about them than a resume would tell you.
We used to get ninety applications and interview twelve. Now we get twenty-five and interview six, and five of those six are worth the hour.
Operations director, mid-size nonprofit
What this changes downstream
A filtered posting pays off long after the hire. The person who read a specific, honest description and applied anyway arrives already calibrated to the pace and expectations of the role, which shortens the onboarding runway and reduces the awkward month-three conversation where it turns out the job was never what they thought they signed up for. Vague postings do not just waste screening time, they also set up mismatches that surface as performance problems six months later when they were really expectation problems on day one.
Key takeaways
- Write the Tuesday, not the title. A concrete day in the role filters better than any list of duties or competencies.
- Name volume, tools, deadlines and failure modes. Specificity is what makes the wrong applicants self-select out before they apply.
- Post a real salary range. It removes mismatched applications at the source instead of during a screening call.
- Replace extra form fields with one sharp question. A specific, job-relevant prompt tells you more in four sentences than a resume tells you in two pages.
Questions to ask your team
Won't a very specific posting scare off good candidates who could grow into the role?
It will scare off candidates who want a different role, which is the point. Strong candidates read specificity as a sign the organization knows what it needs, not as a wall. If you genuinely want someone who grows into the role, say that explicitly and describe what growth looks like, rather than leaving the whole posting vague to cover every possibility.
What if we genuinely don't know the salary range yet?
Set a range before you post, even a wide one, using what the role is worth in your market and budget. Posting without a number almost always costs more time in mismatched applications than the discomfort of committing to a range costs you in negotiation.
How long should the posting actually be?
Shorter than most organizations write, usually 250 to 400 words. The Tuesday description, the three filters, must-haves, and compensation cover what matters. Mission statements and benefits boilerplate can live on a separate careers page instead of crowding out the signal.
Does this approach work for volunteer roles too, not just paid hires?
Yes, and arguably it matters more there, since volunteers rarely go through a formal interview. A specific role description, including time commitment and what a bad week looks like, prevents the quiet attrition that happens when someone signs up for something vaguer than what they actually get asked to do.
