You post a job, applications come in, and they’re the wrong people. The natural conclusion is that the market is thin or the platform is bad. The more accurate conclusion is that your job description told people it was a different job.
Most small business job descriptions follow the same structure: responsibilities, requirements, and a line about the company being fast-growing or mission-driven. That structure describes tasks, not a role that a specific kind of person would find compelling. The people who apply to a task list are the people who apply to everything.
A job description does two things simultaneously: it attracts the right people and filters out the wrong ones. Most descriptions fail at both. They describe work rather than outcomes, so they attract anyone who can do something adjacent. And they give no signal about what distinguishes the people who thrive in the role from the people who don’t.
How to Write a Job Description That Filters In, Not Just Out covers the full rewrite process. This article diagnoses what is going wrong before you rewrite.
Why the Task-List Job Description Fails
The obvious problem: you describe the job the way you’d explain it to someone already on the team. Twelve responsibilities, a broad skills list, a benefits section at the bottom. Someone casually searching reads that and says “I could do that” and applies.
The less visible cost is what this does at the filter stage. A task list cannot distinguish a strong candidate from a weak one because it describes inputs, not outputs. It tells people what they will be doing every day. It does not tell them what good looks like, what they will be held accountable for, or what makes someone genuinely successful in this environment.
The result is a pile of applications from people who read the tasks and figured they qualified. Buried in that pile is the person you were actually looking for. Finding them means reviewing every application, which takes time you don’t have, which leads to shortcuts, which leads to a hire that doesn’t work.
A job description that filters well is specific enough to make the wrong candidate self-select out.
The Three-Layer Job Description Problem
Most small business job descriptions fail in three predictable ways. They stack on each other, and each one compounds the last.
Layer 1 lists tasks when it should name outputs
A task is something the person will do. An output is something they will produce or own. Those are different, and candidates respond differently to them.
“Manages social media accounts” describes a task. “Grows the LinkedIn audience from 400 to 1,000 in six months and owns the posting calendar end to end” describes an output and a standard. The second version tells a candidate whether they’d be good at this job. The first tells them whether they’ve done something adjacent.
The candidates who apply to output-based descriptions have usually produced the output before. The candidates who apply to task-based descriptions have often done something similar but may have no track record with the actual result.
Before: “Responsible for email marketing, including list management, campaign creation, and performance reporting.” After: “Owns the email program end to end, with the goal of growing revenue per subscriber month over month. The owner reviews the strategy once a quarter.”
Layer 2 lists required skills without explaining why they matter
Skills sections are typically written as a compliance checklist: years of experience, proficiency in the relevant tools, a degree or equivalent. What is almost never stated is what problem these requirements are designed to prevent.
When requirements aren’t connected to the role’s actual challenges, two things happen. Candidates who meet the checkbox requirements but lack the relevant judgment apply anyway. Candidates who have the relevant judgment but don’t match the checklist don’t apply.
The fix is connecting each requirement to the reason it matters. “Strong written communication” is a checkbox. “Strong written communication, because you’ll be the primary contact for email-first clients and your tone defines those relationships” tells a candidate whether they belong.
Layer 3 signals the wrong culture to the people you actually want
The words used to describe the company in a job posting tell candidates what kind of person does well there. Most small business descriptions use the same vocabulary: fast-paced, collaborative, looking for a self-starter who thrives in a dynamic environment.
That vocabulary attracts people who have learned to recognize what it means. It also repels the experienced, selective candidates who’ve been burned by it before. Those are the people you were hoping to attract.
Specific, honest language works better. “A three-person team; you’ll be one of four” tells a candidate more about what they’re walking into than “dynamic startup environment.” “The founder is involved in every major client decision” is more useful than “collaborative culture.”
How the Conductor Reads Your Job Description’s Candidate Profile
The Living Library is the place where your business’s accumulated knowledge lives and stays findable. Save your current job description to a Job Description Collection and ask the Conductor what it is actually attracting. You get a reading from the perspective of the candidate who will respond to it, not the person who wrote it.
The Conductor, Kiluma’s context-aware AI, reads the description and returns the candidate profile it is most likely to surface. The seniority level the language signals. Whether the role reads as transactional or consequential. Whether the requirements reflect what success actually requires or what the last hire happened to have.
That reading is useful before you rewrite, not after. Most owners rewrite a job description by adding specificity to the same structure. The Conductor’s read gives you a clearer picture of what you are actually communicating right now, so the rewrite addresses the right problem.
Read Your Own Job Description as a Candidate Would
This week, take your current job description for any open role and read it as someone who has never heard of your business. Not as the person who wrote it.
Ask: if you had ten years of experience in this function and you were a selective job seeker, would this description make you apply? Would you be able to tell whether you’d be good at this job? Would you trust the description’s picture of what the role actually is?
If the answers are no, you have the diagnosis before the rewrite. How to Write a Job Description That Filters In, Not Just Out starts from exactly that diagnosis.
The Description That Filters Well
The Three-Layer Job Description Problem shows why wrong candidates apply and right ones don’t. The Conductor can read what the current description is actually communicating before you spend time rewriting something that hasn’t changed its signal. Try Kiluma free for 14 days at kiluma.ai.