What you'll learn
- Why most job descriptions fail
- The anatomy of an effective job description
- Writing requirements that do not filter out the right candidates
- Language and tone that attracts top candidates
- Common job description mistakes and how to fix them
The average job posting gets 250 applications. Of those, roughly 4 to 6 are worth advancing to a phone screen. That gap between volume and quality is mostly a writing problem. Job descriptions that are too vague attract everyone. Job descriptions that list 27 required skills attract no one qualified. Job descriptions written entirely in corporate jargon confuse candidates who would have been a strong fit. The job description is the first touchpoint in the hiring process. It is the recruiter's pitch to the candidate pool, the candidate's first impression of the company, and the specification that determines what applications you receive. Get it right and your funnel runs efficiently from the first day the role is posted. Get it wrong and you spend the first two weeks sorting through mismatched applications. This guide covers the structure, language, and specific writing decisions that make a job description attract the right people rather than the most people.
Why most job descriptions fail
Quick answer
Most job descriptions are not written — they are assembled. A hiring manager copies last year's posting, adds three new requirements from a recent team discussion, removes two things they are no longer sure about, and sends it to the recruiter. The recruiter reformats it into the standard template. The result is a document that describes a mythical ideal candidate and tells real candidates almost nothing useful about the role, the team, or what success looks like.
The most common failure patterns: requirements that are inflated beyond what the role actually needs (inflated requirements filter out qualified candidates and signal that the company does not know what it wants), duties lists that are so generic they apply to any role at any company (candidates cannot tell if this job is different from the last three they applied to), and missing information about the actual work environment, team structure, and what the first 90 days look like.
The second failure pattern is bias-coded language. Research from Textio and other writing analysis tools consistently shows that job descriptions with certain word patterns — aggressive, dominant, competitive — receive significantly fewer applications from women and from many underrepresented groups. Job descriptions loaded with jargon and acronyms filter out strong candidates from non-traditional backgrounds. The words you choose do not just describe the role — they signal who is welcome to apply.
The anatomy of an effective job description
Quick answer
An effective job description has six components, in this order. The role overview: one to two sentences explaining what this person does, who they work with, and why this role matters. Not a mission statement. Not a list. A clear, honest description of the job in plain English. The team context: two to three sentences about the team this person joins, what they are working on, and where this role fits in the organization. Candidates want to know who they will be working with and what the team cares about.
The core responsibilities: a list of 5 to 7 things this person will actually do. Not 15. Not a comprehensive job function audit. The five to seven things that will occupy most of their time and that, if done well, will make the hire a success. Use active verbs. Write in the present tense. Make each item specific enough that a qualified candidate can recognize themselves in it. The requirements: split them into two clear groups. Required: the things a candidate must have on day one to do this job. Preferred: the things that would make them stronger. Keep the required list short — 4 to 6 items maximum. If everything is required, nothing is.
The compensation and work arrangement: if you can include a salary range, do so. Research consistently shows that job postings with salary ranges receive more applications from qualified candidates, reduce time-to-fill, and reduce the frequency of compensation mismatches at the offer stage. In an increasing number of US states, disclosing the salary range is legally required. For the work arrangement, be specific — remote, hybrid with specific in-office days, or fully onsite. 'Flexible' means nothing. The company overview: two to three sentences maximum. Not your founding story. Not your values statement. The one or two things about the company that would genuinely appeal to the type of candidate you are trying to attract.
The requirements section does the most damage in most job descriptions. Keep the required list to 4 to 6 genuine must-haves. Anything you would train someone on belongs in the preferred section. Every additional inflated requirement narrows the applicant pool and increases time to hire without improving candidate quality.
Writing requirements that do not filter out the right candidates
Quick answer
The requirements section is where most job descriptions do the most damage. Requirements that are inflated beyond what the role needs filter out qualified candidates who self-select out when they see the list. Research from LinkedIn and Harvard Business Review shows that men apply to a job when they meet 60 percent of the listed requirements. Women apply when they meet 100 percent. This means that long requirements lists systematically reduce applications from women and other candidates who tend to require a high bar of qualification confidence before applying.
Practical rules for requirements: if you would hire someone without it and train them on it in the first six months, it is not a required skill — it is a preferred one. If you have not actually tested for it in past hiring, you probably do not need it. If it is listed because it was on the old posting and no one removed it, remove it. Every requirement you add that is not genuinely required narrows your applicant pool and increases the time it takes to find the right person.
The years-of-experience requirement deserves specific attention. Listing 'five or more years of experience' as a proxy for skill level is a poor substitute for specifying what the person actually needs to be able to do. It filters out strong candidates who gained equivalent depth faster, and it does not filter out candidates who have five years of shallow exposure to the technology without real depth. Replace years-of-experience requirements with skill-level descriptions wherever possible. 'Experience leading cross-functional engineering projects with three or more teams' tells you more about what you need than 'seven or more years of software engineering experience.'
Language and tone that attracts top candidates
Quick answer
Top candidates — the ones who are currently employed, performing well, and selective about their next move — read job descriptions the same way they read anything important. They scan first, then read the parts that catch their attention. They are looking for evidence that the company knows what it wants, has thought clearly about the role, and is the kind of place that would be worth leaving a good job for.
Write in plain, direct language. Avoid corporate-speak. Phrases like 'synergize cross-functional deliverables' or 'leverage strategic initiatives to drive stakeholder value' communicate nothing and signal organizational bureaucracy. Strong candidates who see that language in a job description assume the culture has that language built in. Specificity signals clarity of thinking. Specificity in a job description — a real project this person will own, a real problem they will solve, a real metric they will move — signals that the company knows what it needs and has thought clearly about why.
The tone should match the actual work environment. A job description for a startup should feel different from a job description at a large enterprise. Both can be professional. But a startup job description written in the voice of a Fortune 500 press release signals a culture mismatch to the candidates most likely to thrive in a startup. Write the job description in the voice of someone who actually works at the company and talks to the kind of person you are trying to hire.
Common job description mistakes and how to fix them
Quick answer
Mistake: listing the same job description across ten different job levels. A junior engineer role and a senior engineer role at the same company often use nearly identical job descriptions with only the years-of-experience requirement changed. This wastes the strongest signal you have for attracting the right level — the actual scope and expectations of the role at each level are completely different.
Mistake: writing the responsibilities as a job function audit. 'Responsible for all aspects of product development including design, development, testing, and deployment' tells a candidate nothing. Every software product role involves those things. Tell them what is specific to this role, this team, this quarter's priorities. What problem will they solve first? What system will they own? What does a successful first 90 days look like? Mistake: not updating the job description when the role changes. Requirements that were accurate for the last person hired two years ago may not accurately describe what this role needs today. A job description that has not been revisited since 2022 is likely to generate a mismatch between what candidates expect and what they find when they join.
The fastest fix for a weak job description: ask the hiring manager to describe the person who succeeded in the last version of this role and explain specifically what they did in their first six months that made them successful. Then write the job description around that answer. Real performance data about what success looks like in the role is more useful than a requirements list, more attractive to qualified candidates, and more likely to generate a hiring decision that holds up at the six-month performance review.
Specificity is the single biggest differentiator between a job description that attracts strong candidates and one that attracts volume. Real project context, real team descriptions, and real success metrics in the first 90 days outperform generic duties lists because they allow qualified candidates to recognize themselves in the role.
Frequently asked questions
Common questions about talent acquisition and how InCruiter helps teams solve them.
InCruiter Editorial Team
AI Hiring Research · Interview Intelligence · Enterprise Talent Strategy
The InCruiter editorial team covers AI-driven hiring, interview intelligence, and modern talent acquisition strategy. Our guides draw on platform data from 2,000+ hiring teams, conversations with talent leaders, and published research in industrial-organizational psychology.
