How to Write a Job Description That Attracts Top Talent

How to write a job description that attracts top talent is a question every hiring manager faces, and most get it wrong. The average job posting is a wall of jargon, vague responsibilities, and unrealistic requirements that repels the exact candidates you want to hire. A well-written job description does the opposite -- it sells the opportunity clearly enough that strong candidates self-select in, and poor fits self-select out.

Here is a practical, section-by-section guide to writing job descriptions that actually work.

The Anatomy of a Great Job Description

Know Your Odds Before You Apply

See your Interview Probability Score on every job match. Free 14-day trial — no credit card required.

Try Winnow Free →

Every effective job description has the same core structure. The details vary by role and industry, but the bones are consistent.

| Section | Purpose | Ideal Length | |---|---|---| | Job title | Attract the right search traffic | 3-6 words | | Company introduction | Sell the company and mission | 2-3 sentences | | Role summary | Explain why this role exists | 2-3 sentences | | Responsibilities | Define the day-to-day work | 5-7 bullet points | | Requirements (must-have) | State non-negotiable qualifications | 4-6 bullet points | | Requirements (nice-to-have) | List preferred but flexible qualifications | 3-5 bullet points | | Compensation and benefits | Provide salary range and perks | 5-8 bullet points | | How to apply | Tell candidates what to do next | 1-2 sentences |

Let's walk through each section.

Job Title: Keep It Searchable

The job title is the single most important line in your posting. It determines whether candidates find you in search results and whether they click.

Do: Use standard industry titles that candidates actually search for. "Senior Software Engineer," "Marketing Manager," "Staff Accountant."

Don't: Use creative internal titles. "Code Ninja," "Marketing Rockstar," and "Chief Happiness Officer" might be fun internally, but nobody searches for them. You will lose 90% of your potential applicant pool because they never see the posting.

Do: Include the seniority level. "Senior," "Lead," "Junior," "Staff" -- these signal the experience level you expect and help candidates self-select.

Don't: Inflate the title to attract more applicants. Calling a coordinator role a "Director" role will attract overqualified candidates who leave when they discover the actual scope.

Company Introduction: Two Sentences, Not Two Paragraphs

Candidates want to know three things about your company: what you do, who you serve, and why it matters. You have about 10 seconds of attention to convey this.

Good example: "Acme Health builds telemedicine software used by 2,000+ clinics across the US. We're a 150-person team backed by Series B funding, growing 40% year-over-year."

Bad example: "Founded in 2015 by visionary entrepreneurs with a passion for disrupting the healthcare space, Acme Health is a fast-paced, dynamic, innovative company that leverages cutting-edge technology to revolutionize how patients and providers interact in the digital age..."

The good example gives concrete facts. The bad example is a string of meaningless adjectives. Candidates who care about your mission will research further on their own -- the job description just needs to give them enough to decide whether to keep reading.

Role Summary: Why Does This Job Exist?

This is the most underused section in job descriptions. Most postings skip straight from company intro to responsibilities, leaving candidates to guess why the role was created.

A strong role summary answers: What is the problem this person will solve? Who will they work with? What does success look like in the first year?

Good example: "We're looking for a Product Designer to own the patient-facing mobile experience. You'll work closely with our engineering and clinical teams to redesign the appointment booking flow -- our number one source of user drop-off. The right person will reduce booking abandonment by 30% within their first year."

This tells the candidate exactly what they are walking into. It is specific, outcome-oriented, and gives them a clear picture of the impact they could have.

Responsibilities: Be Specific About the Work

The responsibilities section is where most job descriptions go wrong. Vague bullets like "drive strategic initiatives" and "collaborate cross-functionally" tell the candidate nothing about what they will actually do on a Tuesday afternoon.

How to write good responsibility bullets

Each bullet should answer: "What will this person do, for whom, and to what end?"

Vague (bad):

Drive product strategy
Collaborate with stakeholders
Manage projects and deliverables

Specific (good):

Define the product roadmap for our mobile app based on user research, clinical feedback, and business metrics
Run weekly design reviews with the engineering team to ensure implementation matches specifications
Conduct monthly usability tests with 5-10 patients and synthesize findings into actionable recommendations

The specific versions give candidates enough detail to imagine themselves in the role. They can assess whether this work matches their skills and interests -- which is the entire point.

How many responsibilities to list

List 5-7 responsibilities. Fewer than five makes the role seem thin. More than seven overwhelms the reader and usually signals that the role is poorly scoped. If you cannot describe the job in 7 bullets, you might be hiring for two roles.

Order matters

Put the most important and most frequent responsibilities first. Candidates spend more time on the first three bullets than the last three. If the primary function of the role is data analysis, do not bury it below "attend team meetings" and "maintain documentation."

Requirements: Separate Must-Haves from Nice-to-Haves

This is the section with the highest stakes for your applicant pool quality. Get it right and you attract qualified, confident candidates. Get it wrong and you either scare off good people or drown in unqualified applications.

Must-have requirements

These should be genuinely non-negotiable qualifications -- the things someone literally cannot do the job without.

Good must-haves:

3+ years of product design experience with shipped mobile applications
Proficiency in Figma (our primary design tool)
Experience conducting user research and translating findings into design decisions
Portfolio demonstrating end-to-end product design work

Bad must-haves:

7+ years of experience (when 3 would be sufficient)
Expert in Figma, Sketch, Adobe XD, InVision, and Framer (pick one or two)
MBA or Master's degree (unless the role genuinely requires it)
Experience in our exact industry (transferable skills exist)

Every unnecessary must-have requirement shrinks your applicant pool. Before listing something as must-have, ask: "Would I reject an otherwise excellent candidate who was missing only this?" If the answer is no, move it to nice-to-have.

Nice-to-have requirements

Be honest about what is preferred versus required. Candidates -- especially those from underrepresented groups -- often skip postings where they do not meet every listed qualification. Clearly labeling nice-to-haves as such encourages a broader, more diverse applicant pool.

Good nice-to-haves:

Experience in healthcare or regulated industries
Familiarity with accessibility standards (WCAG 2.1)
Experience working in an agile/scrum environment
Basic understanding of HTML/CSS

Compensation and Benefits: Include the Salary Range

This is the section that will do the most to increase your applicant volume and quality. Include a salary range. Full stop.

Here is why:

Legal requirements are expanding. Colorado, California, New York, Washington, and other jurisdictions already require salary transparency in job postings. Even if your jurisdiction does not require it yet, the trend is clear.
Candidates filter by salary. If your posting does not include a range, many strong candidates will skip it entirely because they assume the compensation is below market.
It saves everyone time. Without a salary range, you will interview candidates who are $40,000 apart from your budget. That wastes your time and theirs.
It signals respect. Salary transparency communicates that you treat candidates as equals in the hiring process, not as adversaries to be negotiated down.

How to present compensation

| Element | Example | |---|---| | Base salary range | $120,000-$150,000/year | | Equity (if applicable) | 0.05-0.1% equity grant, 4-year vest | | Bonus | Up to 15% annual performance bonus | | Key benefits | Health/dental/vision, 401(k) match, 4 weeks PTO | | Remote/location | Remote-first with optional NYC office access |

Be specific. "Competitive salary" is not a salary range. "Generous benefits" is not a benefits description. Specificity builds trust.

How to Apply: Make It Simple

Do not make candidates jump through hoops. The more friction in your application process, the more qualified candidates you lose -- because strong candidates have options and will not tolerate a 45-minute application form for a first touch.

Good: "Apply through our careers page with your resume. Cover letters are welcome but optional. We review applications weekly and respond to every applicant within 10 business days."

Bad: "Submit your resume, cover letter, three references, a portfolio, salary requirements, and answers to 5 essay questions through our custom portal that requires account creation."

If you want additional materials, ask for them after the initial screen -- not in the application itself.

Common Mistakes That Drive Away Top Talent

Vague responsibilities

"Own the strategy" and "drive results" mean nothing. If a candidate cannot picture their first week on the job after reading your posting, the responsibilities are too vague.

Unrealistic requirements

Asking for 10 years of experience with a technology that has existed for 5 years is an obvious red flag. But less obvious versions -- requiring deep expertise in 6 different tools, demanding both strategic vision and hands-on execution at a level that would take two people -- are just as damaging.

Missing salary information

As discussed above. Include a range. Always.

Jargon and buzzwords

"Fast-paced environment," "self-starter," "wear many hats," "synergy," "disruptive" -- these words are used so often that they convey zero information. Replace every buzzword with a specific fact.

| Instead of | Write | |---|---| | "Fast-paced environment" | "We ship product updates every two weeks" | | "Self-starter" | "You'll define your own project priorities with input from the team lead" | | "Wear many hats" | "This role covers design, light front-end prototyping, and user research" |

Biased language

Research shows that words like "aggressive," "dominant," and "rockstar" discourage women from applying. Words like "nurturing" and "supportive" discourage men. Use neutral, professional language. Free tools like Gender Decoder can flag biased language automatically.

Too long

The ideal job description is 400-700 words. Anything longer than 1,000 words sees a significant drop in completion rates. If your posting is running long, cut the company boilerplate and the "About Our Culture" section. Candidates can find that on your website.

A Job Description Template

Here is a template you can copy and adapt for your next opening. If you are using Winnow Career Concierge for Employers, you can post directly from your employer dashboard and the platform will help distribute to multiple job boards.

[Job Title]

About [Company Name]

[1-2 sentences: what the company does, size, stage, notable facts.]

About the Role

[2-3 sentences: why this role exists, what problem the person will solve, what success looks like.]

What You'll Do

[Specific responsibility with context and outcome]
[Specific responsibility with context and outcome]
[Specific responsibility with context and outcome]
[Specific responsibility with context and outcome]
[Specific responsibility with context and outcome]

What We're Looking For (Must-Have)

[Non-negotiable qualification]
[Non-negotiable qualification]
[Non-negotiable qualification]
[Non-negotiable qualification]

Nice-to-Have

[Preferred qualification]
[Preferred qualification]
[Preferred qualification]

Compensation and Benefits

Salary range: $[X]-$[Y]
[Equity/bonus if applicable]
[Health benefits]
[PTO policy]
[Remote/hybrid/onsite]
[Any standout perks]

How to Apply

[1-2 sentences: where to apply, what to submit, expected timeline for response.]

Writing for Algorithms and Humans

Your job description needs to work for two audiences: the humans who will read it and the algorithms that will surface it.

For humans: be specific, be honest, be concise. Use short paragraphs and bullet points. Front-load the most important information.

For algorithms: use standard job titles, include common keywords for the role (the same terms candidates use when searching), and structure your content with clear headings. Platforms like Winnow, LinkedIn, and Indeed all parse job descriptions to match them with candidates. The clearer your posting, the better the matches.

For more guidance on building your hiring pipeline, visit the Employers FAQ for answers to common questions about posting jobs, managing candidates, and distributing across multiple boards.

The Bottom Line

A great job description is an honest, specific, well-structured document that helps the right people say "that's me" and the wrong people say "not this time." It takes 30-60 minutes to write one well. That investment pays for itself many times over in the quality of your applicant pool, the speed of your hiring process, and the likelihood that the person you hire actually succeeds in the role.

Write like you are talking to a smart person who has options. Because you are.