Job Description Checklist for Better Candidate Screening

A job description checklist should do more than catch typos before a posting goes live. It should make the role clear enough that a recruiter, a hiring manager, and a later interviewer can recognize the same evidence when they see it.

That is where many job descriptions break down. They name every tool a team has used, blend essential requirements with preferences, and describe a person the manager would like to meet without describing the work that person must do. The result is a difficult applicant review: one recruiter reads for titles, another reads for keywords, and the hiring manager revises the brief after the first promising resume arrives.

Use this checklist before publishing a role. Its purpose is not to predict a perfect hire or turn screening into an automatic decision. It is to turn a vague brief into a small set of job-related criteria a human reviewer can inspect. The U.S. Office of Personnel Management’s job-analysis guidance describes the core connection: identify the tasks performed in a role and the competencies needed for them, then use that information to inform recruitment and selection. That is a useful operating principle for any recruiting team, even when the checklist stays lightweight.

What a job description must make clear

Before reviewing individual sections, test the document against one question: could two people who know the business explain what this person will accomplish and how their work will be recognized? If the answer is no, the rest of the document will be hard to use in screening.

A useful description gives the team four anchors:

• Role outcome: the change the person is expected to create, not merely a list of activities.
• Priority work: the recurring decisions, deliverables, and handoffs that occupy most of the role.
• Required evidence: the experience or capability a person needs to begin the work.
• Open trade-offs: where adjacent experience, a different background, or a learning curve could still be worth a conversation.

Those anchors make a job description usable after it is published. They help a recruiter write a search brief, compare resumes, prepare a phone screen, and explain a shortlist to the hiring manager without rewriting the role each time.

The job description checklist

Review the following items with the hiring manager. Do not treat it as a form to complete alone: the useful decisions are usually in the follow-up questions.

1. Name the outcome before listing responsibilities

Start with one or two sentences that answer: what should be different after this person has been in the role long enough to make an impact? “Own customer onboarding” is an activity. “Create a repeatable onboarding path that helps new customers reach the first meaningful result” gives the team a direction, a population, and a result to discuss.

Then ask the manager for the work behind that outcome. Which decisions will this person make? Which teams will they work with? Which deliverables matter? Which problems keep recurring today? These details become better responsibility bullets and later give a recruiter a basis for judging whether a resume is relevant.

2. Write responsibilities as observable work

Every responsibility should describe work a candidate could recognize from their own experience. Replace broad labels with the actual work:

• Too broad: “Drive cross-functional alignment.”
• More useful: “Coordinate product, support, and operations teams to resolve recurring onboarding handoffs.”
• Too broad: “Be data-driven.”
• More useful: “Use customer and workflow signals to choose an improvement priority and explain the decision.”

This is not a writing exercise for its own sake. When the work is observable, the resume review can look for comparable examples: a project, a decision, a handoff, an outcome, or a defined scope. When the work is abstract, reviewers tend to substitute personal impressions.

3. Separate required criteria from preferences

For each proposed requirement, ask two questions: is it needed for the person to begin the role, and what would count as evidence? If the answer to the first is no, place it in a preferred or discuss-later group rather than presenting it as a firm gate.

A short required list is easier to apply consistently. It also forces the hiring manager to state the trade-offs that are otherwise discovered only after resumes arrive. For example, a team may want prior experience in a particular sector, but the real need may be someone who has handled a similar operating problem. Record that distinction. It gives the recruiter permission to surface a credible near-match rather than dismissing them because a familiar label is missing.

4. Define what evidence would support each requirement

Next to every required criterion, add three quick notes:

• Strong evidence: what a relevant resume example would include.
• Partial evidence: what is adjacent, shared, or incomplete.
• Follow-up: the question a recruiter or hiring manager should ask before drawing a conclusion.

Consider a role that needs someone to lead a workflow launch across several teams. Strong evidence may show the candidate’s own responsibility, the teams involved, and what changed. Partial evidence may show collaboration but not ownership. A follow-up may be needed when the resume uses a broad phrase such as “led launch” without describing scope. This gives the reviewer a common language without pretending the document answers every hiring question.

For a fuller role-calibration process, use a recruiting intake form to record the outcome, evidence standard, and screening route before the first applicant review.

5. Remove requirements that do not change the review

Long requirement lists create a misleading signal: every line appears equally important, yet the hiring manager may only care deeply about three of them. Review every item and ask, “If this were missing, would it change who we advance for a conversation?” If not, it may be context, a preference, or something to learn on the job.

Do the same for tool lists. Tools can be useful evidence when they are central to the work, but a pile of names rarely explains the underlying capability. Write the problem and the work first. Add a specific tool only when its absence would make it difficult to perform a core part of the role.

6. Check whether the reader can find the important information

A recruiter should be able to scan the description and find the outcome, priority work, required criteria, and preferred criteria without decoding a dense paragraph. Use short sections, direct verbs, and grouped bullets. Put the role-defining work near the beginning instead of burying it under a generic company introduction.

Before publication, run the text through the Job Description Health Checker. Use its clarity and requirement-bloat signals as prompts for a recruiter’s review, then decide which wording changes preserve the actual work of the role. The tool can highlight text to revisit; the hiring team remains responsible for the final description.

7. Test the description against a representative profile

Choose one profile the hiring manager would likely advance and one credible near-match. Read the job description as if you were screening those resumes. Can you point to the required criteria? Can you distinguish direct evidence from adjacent evidence? Can you name one useful follow-up question?

If the answer is no, improve the role definition before posting. This small calibration step often reveals that a requirement is too vague, a responsibility is duplicated, or a preferred background has quietly become an unspoken gate. Capture the changes in the role brief so every reviewer starts from the same version.

Turn the checklist into a screening workflow

Once the job description is ready, convert its required and preferred criteria into a simple review table. For each resume, record whether the document shows direct evidence, partial evidence, or an open question. Add a short supporting note rather than a general impression.

This is the bridge between a written job description and a defensible shortlist. A recruiter can compare candidates on the same role criteria while keeping context visible: an unfamiliar title may still contain strong evidence, and a familiar background may still leave an important question unanswered. Our guide to screening candidates against a job description walks through that evidence-first review in more detail.

AI-assisted screening can help organize that first review when it is grounded in the actual role criteria and checked by a recruiter. It should surface evidence and unanswered questions for human inspection, never make the advancement decision on its own. If a result exposes an unclear requirement, revise the definition with the hiring manager and apply the clarified standard consistently to the remaining review.

Use the checklist as a handoff, not a one-time edit

The best job descriptions keep working after the posting is live. They tell a recruiter what to look for, give a hiring manager a basis for reviewing a shortlist, and help interviewers choose questions that test the work rather than repeat the resume. When a team learns something new during the first reviews, update the role definition deliberately and make the change visible.

When the role is clear, see Resume Autopsy to compare a candidate batch against the same criteria and review the supporting resume evidence before your team decides who advances.