How to Write a Better Job Description and Cut Over-Specs

Most hiring problems begin before the first résumé arrives. The job description — often written quickly, copied from a previous posting, or padded with requirements that sound rigorous — shapes who applies, who self-selects out, and what biases enter the process. Getting it right is not an aesthetic concern. It is a structural one.

This guide gives you a repeatable procedure for writing job descriptions that are accurate, defensible, and genuinely useful as screening instruments. It is aimed at hiring managers and people ops leads who want criteria that hold up — not language that inflates the bar or, worse, inadvertently narrows the candidate pool along demographic lines.

Why Over-Specification Costs You

Before the procedure, a grounding point on stakes.

Requiring credentials or years of experience beyond what a role actually demands is not merely inefficient — it has measurable downstream effects. Research on degree requirements, for example, has shown that employers frequently require four-year degrees for roles where workers without degrees perform comparably. A widely cited analysis by Burning Glass Technologies and Harvard Business School (Fuller et al., 2017, Dismissed by Degrees) documented this pattern across millions of job postings, finding that degree inflation was most acute in middle-skill roles and that it disproportionately excluded otherwise-qualified candidates.

On the years-of-experience dimension, Schmidt & Hunter's (1998) meta-analysis in Psychological Bulletin — one of the most replicated findings in applied psychology — demonstrated that years of experience is among the weaker predictors of job performance, particularly beyond the early stages of a role. Structuring a job description around experience proxies rather than capability criteria is, on the evidence, a poor trade.

The practical consequence: over-specified job descriptions shrink the applicant pool, reduce diversity, and do not reliably improve hire quality. Cutting specs is not about lowering the bar — it is about pointing the bar at the right thing.

The Procedure: Six Steps to a Better Job Description

Step 1 — Start From the Work, Not the Worker

Open a blank document and answer one question before writing a single requirement: What will this person actually do in the first 12 months, and what does success look like?

Write three to five concrete deliverables or outcomes. These are not job duties ("manages stakeholder relationships") — they are results ("produces a quarterly competitive-intelligence brief used by the product team to inform roadmap decisions").

What good looks like: Each outcome is specific enough that you could, in principle, evaluate whether it was achieved. Vague outcomes produce vague requirements.

Step 2 — Derive Requirements From Outcomes, Not Convention

For each outcome you wrote, ask: What does someone actually need — knowledge, skill, judgment, or access — to achieve this? Write those down as your draft requirements.

Then apply a culling test to every requirement you list:

• Is it necessary on Day 1, or can it be learned in the first 90 days? If the latter, consider removing it or converting it to a "nice to have."
• Is this a proxy for the real thing? A degree requirement often proxies for analytical skill or writing ability — which you can assess directly. A specific tool requirement ("must have 3+ years in Salesforce") often proxies for CRM fluency — which transfers across platforms.
• Would a strong candidate who lacks this credential still be capable? If yes, the requirement is over-specified.

What good looks like: Your requirements list is shorter after this step than before.

Step 3 — Separate Must-Haves From Nice-to-Haves (and Label Them)

Combining non-negotiable qualifications with aspirational ones in a single bulleted list causes two problems: strong candidates self-select out when they don't hit every point, and weak candidates apply undifferentiated from strong ones.

Research by Hewlett et al. (2013, Harvard Business Review, "How Diversity Can Drive Innovation") and subsequent replications have documented that women are more likely than men to apply only when they meet all listed criteria — a pattern that contributes to gender gaps in applicant pools. Labeling requirements clearly is one corrective.

Create two explicit sections:

• Required: The short list. If someone cannot do the job without it, it belongs here.
• Preferred / Helpful: Everything else. Frame these as honest signals about your context, not filters.

What good looks like: The "Required" section has no more than five items and could be defended in an interview debrief.

Step 4 — Audit Language for Exclusionary Signals

Specific word choices in job descriptions have been shown to influence who applies. Gaucher, Friesen & Kay (2011) in the Journal of Personality and Social Psychology demonstrated experimentally that job ads using more "masculine-coded" words (e.g., "dominant," "competitive," "aggressive") attracted fewer female applicants, even controlling for the role type.

Run your draft through these checks:

• Remove unnecessary superlatives: "rockstar," "ninja," "guru," "world-class." These signal culture fit as a vague personality preference, not job-relevant criteria.
• Replace coded intensifiers with behavioral descriptions: instead of "thrives in a fast-paced environment," write "manages concurrent workstreams with shifting priorities and communicates status proactively."
• Check credential sentences for scope creep: "Bachelor's degree required" in a role where the outcomes do not depend on it is a legal and talent risk.

What good looks like: Every sentence in the requirements section could be connected, in a debrief, to a specific outcome from Step 1.

Step 5 — Write the Role Context, Not Just the Role

Candidates evaluate employers as much as employers evaluate candidates. A job description that explains why this role exists now, what team it sits in, and what a realistic first 90 days looks like gives strong candidates the information they need to self-assess fit honestly.

This is not marketing copy. It is operational clarity. Include:

• The team size and reporting structure
• The stage of the problem this person will work on (building from scratch vs. scaling vs. optimizing)
• One honest challenge or constraint the role carries

What good looks like: A strong candidate who reads this description can write a specific cover note. A candidate who cannot fit their experience to this context self-selects out before the phone screen — saving everyone time.

Step 6 — Test the Description Before Posting

Before publishing, run two validation checks:

1. The mirror test: Give the draft to someone unfamiliar with the role. Ask them to describe back what the job is, what success looks like, and what kind of person would be a poor fit. Gaps in their answer are gaps in your description.

2. The debrief test: Ask yourself whether each listed requirement corresponds to a question or exercise you would actually use in the hiring process. If a requirement cannot be evaluated, it should not be in the description. (For more on building evaluation criteria that hold up in a debrief, see Candidate Evaluation Criteria: How to Score Candidates.)

What good looks like: The description could be handed to an interviewer as a briefing document with no additional explanation needed.

Worked Example

Original requirement (over-specified):

"8+ years of B2B marketing experience, MBA preferred, deep expertise in enterprise SaaS, demonstrated ability to build world-class pipeline."

After applying the procedure:

First, the outcome this maps to: Owns demand generation for mid-market segment, producing $X in sourced pipeline per quarter in partnership with a two-person SDR team.

Now derive and test:

Evaluating candidates against the revised description, you can assess each requirement against Verdict's six dimensions: Capability (can they run multi-channel programs?), Track Record (have they hit pipeline numbers?), Trajectory (is their skill set growing toward or away from this work?), Influence (can they move an SDR team without direct authority?), Domain edge (do they understand the buyer, or just the channel?), and Risk surface (are there gaps — tenure, scope — that need probing?). Each dimension maps to a question you can actually ask. See The Forensic Approach to Evidence-Cited Hiring Verdicts for how to structure that debrief.

Pitfalls to Avoid

• Copy-pasting last year's JD. Role requirements drift as companies change; the description should be rebuilt from outcomes each time, not inherited.
• Committee inflation. When multiple stakeholders add requirements, the list grows without culling. Assign one owner to the requirements section and require a written justification for any addition.
• Treating the description as a wish list. Requirements that cannot be evaluated in the hiring process are not requirements — they are noise that makes the description harder to use and harder to defend.
• Ignoring legal exposure. Credential requirements that cannot be shown to be job-related can create disparate impact liability under Title VII (U.S.) and analogous statutes in other jurisdictions. If in doubt, consult counsel before posting.
• Omitting the honest constraint. Hiding a known challenge (budget limitations, team instability, ambiguous scope) produces mismatched hires who leave early. Disclosing it attracts candidates who have navigated it before.

A Note on Tooling

A well-written job description is necessary but not sufficient. It defines the criteria; you still need a consistent process to evaluate candidates against them. If you want to see how structured criteria translate into side-by-side candidate evaluation — grounded in evidence rather than impression — Verdict is built for exactly that. You can request a demo to see a live evaluation run against a real job description.