How to write a job description that attracts skilled people (not just credentialed ones)

The job description is the most underrated document in hiring. Long before any interview, before any assessment, before a recruiter reads a single résumé, the job description has already done something decisive: it has determined who applies at all. Every requirement you list is a filter, and filters do not distinguish between the candidates you meant to exclude and the excellent ones you did not. Write the description carelessly and you have quietly pre-rejected people you would have loved to hire — and you will never know, because they simply never applied.

This is why a skills-based hiring process has to start at the job description, not at the screening stage. You can build the fairest, most structured funnel in the world, but if the role posting funnels a narrow, credential-skewed pool into the top of it, that is the pool you are stuck choosing from. Getting this document right is the cheapest, earliest leverage you have.

Lead with what they'll do, not who they should be

Most descriptions open with a paragraph about the company and then a list of attributes the ideal candidate should possess — “self-starter,” “strong communicator,” “five-plus years in a fast-paced environment.” Flip it. Open with the work: the three to five things this person will actually spend their time doing, and what success looks like in the first six to twelve months. Concrete tasks do double duty — they help the right candidates recognize themselves, and they force you to be honest about what the role really needs rather than padding it with aspirational traits.

The discipline here is to translate every vague attribute into the task it is standing in for. “Strong communicator” becomes “you'll write the weekly update that goes to the leadership team and run the cross-team handoff.” “Detail-oriented” becomes “you'll own the reconciliation that has to be exactly right every month.” When you do this, two things happen: candidates can self-assess accurately, and you get a ready-made specification for the assessment you will use later. The job description and the assessment should describe the same work.

Separate the must-haves from the wish list

The single most damaging habit in job descriptions is the inflated requirements list — a dozen bullet points under “Requirements,” most of which are really preferences. This matters more than it looks, because of a well-documented asymmetry in who applies: candidates from underrepresented groups, career-changers and self-taught talent are far more likely to disqualify themselves unless they meet nearly every listed criterion, while others apply at fifty or sixty percent. A long requirements list therefore does not just shrink your pool — it skews it, filtering hardest on exactly the capable, non-traditional candidates skills-based hiring is meant to surface.

So be ruthless about the distinction. A must-have is something without which a person genuinely cannot do the job on day one and could not reasonably acquire quickly. Everything else is a nice-to-have, and it belongs in a clearly separate, short list — or not in the posting at all. Pay special attention to two notorious offenders. Years-of-experience minimums are usually arbitrary and exclude people who acquired the skill faster or differently; ask what capability the years are a proxy for, and require that instead. And degree requirements, for most roles, are a proxy for skills you can measure directly — keep them only where a degree is legally mandated or maps to a specific, non-substitutable body of knowledge.

Write language that widens the door

Even with the right requirements, the wording can quietly narrow your pool. Heavily aggressive or competition-soaked language (“crush targets,” “work hard, play hard,” “rockstar,” “ninja”) reliably skews who feels invited to apply, and jargon-dense postings filter for insiders over ability. The fix is not to scrub all personality from the writing — it is to make the language clear, specific and welcoming, so that the filter doing the work is the actual requirements, not the vibe.

A few concrete moves carry most of the benefit: write in plain, direct sentences; describe the work and the team honestly rather than in superlatives; state compensation and location/remote arrangements openly, since vagueness there disproportionately deters the candidates who can least afford to gamble their time; and explicitly invite people who meet most-but-not-all of the nice-to-haves to apply. None of this lowers your bar. It just makes sure the bar is the skills, and not an accidental test of who feels entitled to apply.

A reusable structure

Pulling it together, a skills-based job description has a predictable shape you can reuse for any role. It is short, concrete, and honest — and it maps cleanly onto the rest of your process:

• A one-paragraph, jargon-free summary of the role and why it exists.
• “What you'll do” — the 3–5 real tasks and what success looks like in the first 6–12 months.
• “What you'll need” — only the genuine must-have skills, each one something the job actually requires.
• “Nice to have” — a short, clearly-separate list of preferences, with an explicit invitation to apply without all of them.
• Transparent compensation, location/remote details, and the steps of your hiring process.

How Spoon carries it through

A skills-first job description deserves a skills-first process behind it, or its promise breaks at the first screening step. On Spoon, the tasks and skills you defined flow straight into a structured AI interview that every applicant sits, and into an anonymized, skills-ranked shortlist that judges candidates on the work rather than the résumé. The document and the funnel tell the same story.

That is what closes the loop between attracting a wide, capable pool and actually hiring fairly from it. See Spoon for companies, or read the skills-based hiring guide for the full picture.

Frequently asked

Keep reading