Most job descriptions are written to explain the role. They should be written to do two things at once: attract the right candidate and repel the wrong one. Those goals require opposite writing strategies, and most descriptions try for neither.
A description that filters well is specific enough that the wrong candidate self-selects out before applying. Every application from someone who would not succeed in the role is time you spend reviewing rather than hiring.
The three-layer problem that produces wrong-candidate piles is diagnosed in Why Your Job Description Is Attracting the Wrong Candidates. This article is the rewrite that follows that diagnosis.
The Filter-Forward Job Description has four components. Each one addresses a specific reason the wrong candidate applies or the right candidate doesn’t.
The Failure Mode the Rewrite Must Avoid
The natural rewrite instinct is to add specificity to the existing structure: more detail in responsibilities, an extra bullet in requirements, a revised company blurb. The description ends up longer and still sends the same signal.
A filter-in rewrite doesn’t add to the existing structure. It changes what the structure is for.
The description is no longer for the hiring manager explaining the role to HR. It is for two readers at once: the person who is right for this role, and the person who is not. Both should finish reading knowing which one they are.
The Filter-Forward Job Description
Each component addresses one of the main reasons wrong candidates apply or right ones don’t.
Component 1 leads with the outcome, not the tasks
The first thing the description says sets the category of person who keeps reading. A list of tasks keeps everyone reading. An outcome statement sorts them.
“Manages the marketing calendar, oversees content creation, handles social media” describes the work. “Owns the marketing output: success means marketing runs without the founder” describes what the role is for. Candidates who want to own an outcome self-select in. Candidates who need more structure self-select out.
Replace the opening responsibilities list with two or three sentences that name the outcome the role exists to produce. Specific enough that a candidate at a different company in a similar function would recognize whether this is the same kind of role.
Component 2 describes the actual working environment
Most descriptions say nothing about what working in this business actually is like. Adjectives (“fast-paced,” “collaborative,” “dynamic”) tell a candidate the job exists. They do not tell them whether they would succeed.
Honest specifics do the filtering. A description that says “six people, founder in every client decision, most processes still being built” tells candidates whether they belong. Candidates who build self-select in. Candidates who need structure self-select out.
Be accurate about the real conditions. A candidate hired under a misleading description leaves inside six months. The one who knew what they were walking into stays.
Component 3 names the two non-negotiable traits, not the preferred checklist
Requirements sections list skills and experience. They rarely state the one or two things that actually separate people who succeed in this role from people who struggle.
Those traits are rarely credentials. An operations role needs someone who creates order where none existed, not just someone who can run a spreadsheet. A customer-facing role needs someone who reads when a client needs reassurance, not just someone with five years of customer experience.
State them in behavioral language, not credential language. “You build systems where none exist and prefer that to maintaining ones someone else built” tells a candidate more about fit than any years-of-experience requirement.
Component 4 states what the role is not
One or two explicit not-statements filter as effectively as any positive description. Most descriptions skip this.
“This role does not have a budget or a team yet” filters for candidates who work lean and repels candidates expecting resources. “Priorities are not handed to you here” repels candidates who need direction and attracts candidates who set their own. These are not disclaimers. They are the honest picture that lets the right person recognize themselves.
Be specific. Generic not-statements (“not for someone who wants to coast”) are as invisible as generic positive statements. Connect each not-statement to the actual working condition that would cause a wrong hire to fail.
How the Living Library Keeps Your Job Description Current
The first version of a role’s job description reflects what you think the role is. After six months, you know more.
You know what mattered on day one. You know what the description failed to communicate that caused early friction. You know what the role required that you didn’t anticipate. That knowledge is the Living Library’s input.
The Living Library is the Kiluma platform’s layer for organizing and maintaining what your business has built up over time. Every time you add a hiring note or a 30-day check-in record, it reads that observation. The Conductor, Kiluma’s context-aware AI, draws from the accumulated record to keep the role’s job description current.
When the role opens again, you open the platform and find the description already refined. The outcome statement reflects what the role actually produced. The not-statements are specific to what caused the prior hire’s friction. The trait requirements name what actually mattered, not what the previous JD guessed might matter.
Start With the Opening Paragraph
Before you post anything, rewrite the first paragraph of the job description using Component 1. Replace the responsibilities list with two or three sentences that name the outcome the role produces.
Read the new opening as a candidate who would not succeed in the role. If they would still apply, the outcome statement isn’t specific enough. Sharpen it until the wrong candidate reads it and thinks “that’s not what I’m looking for.”
That’s the description doing its job.
Both Readers, One Document
The right candidate reads the Filter-Forward Job Description and recognizes the role as theirs. The wrong candidate reads it and self-selects out. That is what the description was written to do, and it is what the task-list version was never capable of. Try Kiluma free for 14 days at kiluma.ai.