What a Job Description Is Actually For
A job description serves two audiences simultaneously: the candidates deciding whether to apply, and the hiring manager clarifying what they actually need. For candidates, the description is a filter: it should clearly communicate what the role does, what qualifications are required versus preferred, what the compensation is, and what it is like to work at this company. For the hiring manager, writing the description forces the clarity exercise of defining what success looks like in the role before a single resume is reviewed.
Most small business job descriptions fail at both purposes. They are written by listing every task the employer can think of, adding a list of requirements that reflects an ideal candidate rather than a realistic one (ten years of experience for a $55,000 role, a degree requirement for a job that does not need one), and omitting compensation entirely. The result is a posting that repels qualified candidates who assume the worst about pay, attracts unqualified candidates who cannot self-screen against vague requirements, and produces interview feedback (“not quite what the employer needed”) that reflects an unclear role definition rather than a hiring quality problem.
Job Description Structure: What Each Section Does
| Section | What to include | What to avoid | Length guide |
|---|---|---|---|
| Job title | The title the employee will actually hold. Use standard industry titles that candidates search on job boards | Internal titles that are meaningless externally (“Client Success Ninja,” “Growth Hacker”). Inflated titles that misrepresent seniority | 2–5 words |
| Role summary | 3 sentences: what the role exists to accomplish, who it supports, and the primary success metric | Generic company descriptions that do not describe the role. Mission statements that tell candidates nothing about the job | 3–4 sentences |
| Responsibilities | 5–8 specific work products or activities that represent 80% of the role’s actual work | Exhaustive lists of every possible task. Vague responsibilities like “support the team as needed”. Tasks that apply to every job in the company | 5–8 bullets |
| Requirements vs. preferences | 2 separate lists: hard requirements (non-negotiable for the role) and preferred qualifications (nice to have, not required) | Combining required and preferred in one list. Requiring degrees for roles that do not need them. Requiring more experience than the market can provide at the offered salary | 3–5 requirements. 2–4 preferences |
| Compensation and benefits | Salary range (required in some states. Recommended everywhere). 3–4 benefits highlights. Work arrangement (remote/hybrid/on-site) | No compensation information. Vague “competitive salary”. Burying compensation at the bottom after 8 sections | 3–5 lines |
| Application instructions | How to apply. What to submit. If a specific action is requested (cover letter, work sample), state it explicitly. Timeline for response | Complex multi-step applications for entry-level roles. No response timeline. Instructions that differ from the job board apply flow | 2–3 sentences |
How to Write a Job Description That Attracts Qualified Candidates: 5 Steps
- Start with one sentence that says what the role exists to accomplish: not what it does. Most job descriptions begin with a list of tasks. The most effective ones begin with a purpose statement: “This role exists to ensure every client project is delivered on time and within scope, giving senior consultants the operational support they need to focus on client relationships.” This sentence tells a qualified candidate immediately whether the role matches what they want to do. Task lists describe the work. The purpose statement describes why the work matters. And it is what attracts candidates who are motivated by outcomes rather than activities.
- Write the requirements list as two distinct categories and audit for credential inflation. Separate your job requirements into “required” (the candidate cannot be effective in the role without this) and “preferred” (this would be helpful but the employer can teach it or work around it). Then audit each required item: is this actually required, or is it what an ideal candidate would have? Requiring a bachelor’s degree for a role that does not involve specialized academic knowledge reduces your qualified applicant pool by 30–40% without improving hire quality. Requiring 5 years of experience for a role where 2 years of strong performance is sufficient eliminates candidates who are fully capable and priced appropriately for the role.
- Write 5–8 responsibilities as outcome-oriented statements, not task descriptions. The difference between “manage the company’s social media accounts” and “grow the company’s LinkedIn following by posting 3 times per week, engaging with comments, and producing monthly analytics reports showing reach and engagement trends” is specificity. The specific version tells the candidate exactly what success looks like, what the workload is, and what skills the role requires. It also screens out candidates who want to do social media differently than this role requires. Write each responsibility as a verb + object + context: what action, on what output, with what frequency or standard.
- Include the compensation range in the posting: placed in the first or second section, not buried at the bottom. Salary information is the first thing most candidates look for. Placing it at the bottom, after the company culture section and the full benefits list, does not change what the number is: it just wastes the time of every candidate who would have self-screened out at the number. Post the range in the first or second section, framed as: “Compensation: $X–$Y salary, dependent on experience. Benefits include: [3–4 highlights].” If the honest range is below market for the qualifications required, that is a job design problem, not a compensation transparency problem: the description needs to be rewritten to match the budget, not the budget hidden.
- Test the description against one question before publishing: “Would the right candidate recognize themselves in this posting?” Read the completed job description as if you are the candidate you most want to hire. Would they see their experience in the requirements? Would the responsibilities match what they want to do? Would the compensation confirm the role is worth their time? Would the company description make them want to learn more? If the answer to any of these is no, the posting will underperform. The most common failure is a description written from the employer’s perspective, what the employer needs, without translating that into what the candidate is looking for. Rewrite any section that does not speak directly to the candidate’s decision to apply.
Looking for ATS software that distributes your job posting to 50+ job boards automatically?