How to Write a Job Description: A Complete Guide for Employers

All resources · How to Write a Job Description

Why your job description matters more than you think

Your job description is often the first interaction a candidate has with your company. Before they apply, before they interview, before they accept an offer — they read your job description. It shapes their perception of the role, the team, and the organization. A poorly written description attracts unqualified applicants and repels the ones you actually want. A clear, specific description works as a filter, saving your recruiting team hours of screening and improving the quality of every candidate in your pipeline. Research consistently shows that job postings with clear salary ranges and specific requirements receive significantly more qualified applications than vague, laundry-list postings. The cost of a bad hire is estimated at 30% of annual salary — it starts with a bad job description.

Start with a clear, honest job title

The job title is the first thing candidates see in search results and on job boards. It must accurately reflect the role. Creative titles like "Code Ninja" or "Marketing Guru" may seem clever but they hurt discoverability. Candidates search for specific titles, and recruiters filter by them. Use the industry-standard title for the position. If your company uses an internal title that differs from market norms, include both. Avoid inflating titles — calling a junior role "Senior" or a manager role "Director" creates misalignment during the hiring process and erodes trust with candidates who discover the mismatch.

• Use industry-standard titles that candidates actually search for
• Avoid invented or cutesy titles that reduce search visibility
• If internal titles differ from market norms, include both
• Be honest about seniority level — inflation backfires during screening
• Match the title to the actual scope of the role

Write a role overview that sets context

The first paragraph of your job description should tell candidates what the role is, why it exists, and how it fits into the organization. Avoid starting with generic filler like "We are looking for a passionate self-starter" — instead, describe the actual problem this person will solve. A strong role overview answers three questions: What will this person do? Why does this role matter? Who will they work with? For example: "We are hiring a Senior Product Manager to own our payments platform. You will lead a cross-functional team of engineers and designers, define the product roadmap for a system processing $2M+ in daily transactions, and report to the VP of Product." That is specific, honest, and informative.

• State what the role does in concrete terms
• Explain why the role exists and what problem it solves
• Identify who the person reports to and who they work with
• Include scope indicators like team size, revenue, or user base
• Avoid generic opening lines — lead with specifics

List responsibilities with outcomes, not just tasks

The responsibilities section is where most job descriptions go wrong. Employers list 15-25 vague tasks that could apply to almost anyone in the field. Effective responsibilities describe what the person will actually own and what success looks like. Start each responsibility with a strong action verb and tie it to an outcome where possible. Instead of "Manage social media accounts," write "Develop and execute a content strategy across LinkedIn, Twitter, and Instagram that increases engagement by 25% within six months." Instead of "Write code," write "Design and implement backend services in Python and PostgreSQL that support 10K concurrent users with 99.9% uptime." Aim for 6-10 core responsibilities. Too many dilute the focus.

• Keep responsibilities to 6-10 core items
• Start each with a strong action verb
• Tie responsibilities to outcomes or metrics where possible
• Distinguish primary duties from occasional tasks
• Describe what the person owns, not just what they participate in

Separate requirements from preferences

This distinction is critical and widely misunderstood. Requirements are the minimum qualifications someone needs to do the job effectively. Preferences are nice-to-haves that differentiate candidates at the same baseline level. Conflating the two is one of the biggest reasons qualified candidates self-select out of applying. Research shows women are significantly less likely to apply if they do not meet 100% of listed requirements, while men apply at around 60%. If you list every possible qualification as "required," you shrink your talent pool unnecessarily. Be honest about what is truly mandatory. Can someone do this job without a specific degree, certification, or tool? If yes, it belongs in preferences.

• Requirements: minimum qualifications to perform the job effectively
• Preferences: nice-to-haves that strengthen a candidacy
• Limit requirements to what is truly mandatory
• Be specific about tools, languages, and certifications
• Recognize that overly strict requirements filter out strong candidates

Include compensation and benefits

Candidates increasingly expect salary information, and many job boards now require it. Beyond candidate expectations, there are practical reasons to include compensation: it filters out candidates with misaligned expectations, demonstrates transparency, and reduces time spent on offers that fall through due to salary gaps. Include the salary range, not a single number. Ranges signal flexibility and are more honest — the actual offer will depend on experience, location, and other factors. If you cannot disclose the full range, disclose the floor: "Starting at $95,000, depending on experience." Beyond base salary, mention key benefits: health insurance, retirement matching, PTO policy, remote/hybrid flexibility, equity or bonus structures.

Describe your company honestly

The company description section is not your branding exercise — it is information candidates use to decide whether they want to work here. Skip the mission statement boilerplate and focus on what matters to candidates: company size, industry, growth stage, culture indicators, and what makes the team different. Be specific and honest. "Fast-growing startup" means different things at 10 people versus 200 people. "Flexible work environment" could mean full remote, hybrid, or just occasional Fridays off. The more precise your language, the better candidates can self-select.

Avoid these common mistakes

Most job descriptions fail for the same handful of reasons. Recognizing these patterns before you write or review your next posting will immediately improve its effectiveness.

• Listing too many requirements — every item you add filters out more candidates, often unnecessarily
• Using vague language — "fast-paced environment" and "ability to multitask" tell candidates nothing specific
• Copying job descriptions from competitors — your role has specific nuances that generic descriptions miss
• Omitting salary — the single most requested piece of information candidates look for
• Writing walls of text — use bullet points, headers, and white space to make descriptions scannable
• Using internal jargon — acronyms and company-specific terms mean nothing to outside candidates
• Exaggerating seniority — calling a mid-level role "Senior" creates mismatch during interviews
• Forgetting mobile — most candidates view job postings on phones, format accordingly

Review and test your job description

Before posting, read your job description out loud. If it sounds like something no human would say in conversation, rewrite it. Have someone outside your team read it — if they cannot understand what the role does, your candidates will not either. Check for unconscious bias in your language. Tools like gender bias decoders can flag phrasing that discourages certain demographics from applying. Test different versions if possible. Post one version for two weeks, note the volume and quality of applicants, then adjust and repost. Job descriptions are not static documents — they evolve as your understanding of the role evolves and as you learn what attracts the right candidates.

Related resources

Related job descriptions

Frequently asked questions