TopRec
Hiring Playbook

How to Write a Job Description That Attracts the Right People (and Screens Out the Wrong Ones)

A good job description is a filter, not a wish list. Here is how to write one that pulls in qualified candidates, repels the mismatches, and makes every downstream screening step faster and more accurate.

The short version: write the job description as a filter, not a wish list. Lead with what the person will actually do, be honest about must-haves versus nice-to-haves, name the real scope and level, and cut the generic boilerplate. A sharp JD attracts fewer but better applicants — and, just as importantly, it becomes the precise yardstick you screen every resume against later. Vague in, vague out; specific in, specific out.

The job description is your first screen

Every requirement you list either invites the right people or the wrong ones. A vague post — "5+ years of experience, strong communication skills, thrives in a fast-paced environment" — attracts everyone and filters no one. The result is 300 applications and a screening problem you created for yourself. A specific, honest JD does the opposite: it quietly screens out mismatches before they ever apply, so the pile you do get is smaller and better. Treating the JD as a filter is the highest-leverage move in the whole funnel, because it improves the input to everything that follows.

1. Lead with the work, not the company boilerplate

Candidates decide in seconds whether a role is for them. Open with what they will actually do in the first 90 days and the problems they will own — not three paragraphs about your mission and values. The strong candidates you want are scanning for the work; give it to them first, in concrete terms. "You will own our billing service and cut its error rate" beats "we are a mission-driven team disrupting an industry" every time.

2. Separate must-haves from nice-to-haves — honestly

Long requirement lists do not raise the bar; they shrink your pool and scare off strong non-traditional candidates, who are more likely to self-select out when they do not tick every box. Pick the four to six things that genuinely predict success and clearly label the rest as "bonus" or "nice to have." This is the same short list you will screen against, so getting it right here pays off twice: better applicants now, faster and more accurate screening later.

Test every requirement: "Would I reject an otherwise excellent candidate for missing this?" If no, it is a nice-to-have — move it out of the must-haves.

3. Be specific about scope, tools, and level

"Senior engineer" means five different things at five companies. "You will own our billing service — a Go and Postgres system serving two million users — on a team of six, reporting to the Head of Platform" means exactly one. Name the stack, the team size, who they report to, and the real level. Specificity attracts people who can do this job and filters out those who cannot, which is precisely what you want a JD to do.

4. Cut the things that quietly repel good people

  • Salary secrecy. Omitting a range costs you qualified applicants, erodes trust, and is increasingly required by law. Post a real range.
  • Buzzword soup. "Rockstar ninja who wears many hats" reads as "understaffed and chaotic." Strong candidates run from it.
  • Degree gatekeeping where the work does not require it. You are excluding capable people for zero signal.
  • Endless "requirements" that are really preferences. Every false must-have costs you a good applicant.

5. Structure it so people actually read it

Format for scanning: a short intro on the role and its impact, a "what you will do" section in plain language, a tight "what you need" list (must-haves), a short "bonus" list, and the practical details (location or remote policy, salary range, how to apply). Keep it to a few hundred words. Length is not the goal — clarity is. A candidate should understand the job, the level, and whether they fit within a minute.

6. Write the JD you will screen against

Here is the part most guides miss: the JD is not just an advertisement, it is the specification your screening runs against. If your JD is sharp and specific, ranking resumes against it is accurate and fast — the criteria are already explicit. If it is vague, every downstream step inherits that vagueness: screening is fuzzy, interviews are unfocused, and the hiring manager and recruiter are never quite aligned on what "good" means. A precise JD is the cheapest quality upgrade available to your entire hiring process.

A reusable structure

  • Title & one-line summary — the real level and the core outcome.
  • What you will do — 3–5 concrete responsibilities and first-90-days impact.
  • What you need — 4–6 genuine must-haves, each defensible.
  • Bonus — nice-to-haves, clearly optional.
  • Details — location/remote, salary range, team, reporting line, how to apply.

From a sharp JD to a ranked shortlist

Once you have a sharp JD, TopRec reads every resume against it — not against keywords, against the actual meaning of the role — and ranks candidates 0–100 with the strengths, gaps, and exact quotes behind each score. A well-written description in, an evidence-backed shortlist out, in minutes. The better you specify the job, the more accurate the screening; write the JD as a filter and the rest of hiring gets easier at every step.

Stop guessing who to interview.

Drop in a job description and your shortlist. TopRec ranks the fit, writes the questions, and briefs your hiring manager — in minutes.

Start screening free → 1 free trial job · no credit card · no subscription