Day 1: Rewrite a Job Description for Clarity and Inclusion

The concept

Every hiring process begins before the first application arrives. It begins with the job description.

That document shapes who applies, who self-selects out, what recruiters search for, what hiring managers expect, and how interviewers later judge fit. Yet in many organisations, job descriptions are treated as admin. They are copied from an old role, patched with new responsibilities, approved quickly, and posted with language that nobody has questioned in years.

AI can help HR teams review job descriptions faster and more consistently. But this is not a cosmetic writing task. A better job description should clarify the work, protect the hiring bar, reduce unnecessary exclusion, and make it easier for qualified candidates to decide whether the role is worth their time.

Plain English

A good job description is not a wish list. It is a clear agreement about the work, the outcomes, and the evidence needed to hire fairly.

Why job descriptions drift

Job descriptions often drift because roles change faster than documents. A role that once needed heavy administration may now need stakeholder management. A requirement added for one hiring manager may remain long after the reason disappears. A degree requirement may sit in the template because nobody asked whether it predicts success.

Drift creates problems:

• candidates misunderstand the role
• recruiters screen for the wrong evidence
• hiring managers expect too many things from one person
• interviewers assess inconsistent criteria
• strong candidates opt out because the requirements look unrealistic
• underrepresented candidates may self-screen more heavily against inflated requirements

The goal is not to make every job description shorter. The goal is to make every requirement defensible.

Audit before you rewrite

The audit is often more valuable than the rewritten version. It shows which assumptions have become embedded in the document.

Look for:

Vague language

Phrases like "excellent communication skills" or "fast-paced environment" need translation. What communication? With whom? Under what conditions? What pace means fast here?

Inflated expectations

Long lists of requirements may describe an ideal candidate rather than the person needed to do the job well.

Exclusionary or coded language

Words like "rockstar," "ninja," "aggressive," or "digital native" can send unintended signals. So can unnecessary degree requirements, location assumptions, or years-of-experience thresholds that are not tied to actual complexity.

Mixed must-haves and preferences

If nice-to-haves appear beside genuine requirements, candidates may assume they need everything.

Internal jargon

Candidates should not need to understand your internal language to understand the job.

Keep the hiring bar clear

Inclusive hiring does not mean lowering standards. It means defining standards accurately.

A strong rewrite should preserve role scope and seniority while removing unnecessary barriers. For example:

• Instead of "10 years of experience required," specify the complexity of work the person must have handled.
• Instead of "excellent stakeholder management," describe the stakeholder situation.
• Instead of "degree required," ask whether equivalent experience is acceptable.
• Instead of "fast-paced," explain the practical reality: shifting priorities, short deadlines, or high-volume requests.

The hiring manager should still recognise the role. If the rewrite changes the role, it has gone too far.

A premium job description has three jobs

A polished job description does more than advertise a vacancy. It quietly performs three serious HR functions.

1. It aligns the internal team

Before candidates see the role, the job description should force agreement inside the organisation. If the hiring manager, recruiter, compensation partner, and interviewer group all read the same document and imagine different jobs, the process is already at risk.

Use AI to surface those differences. When the model separates must-haves from nice-to-haves, ask the hiring manager to respond line by line. Do not settle for "all of these are important." That may be true, but it does not mean all of them are required on day one.

A useful follow-up is:

Which three requirements would you defend if the candidate market pushed back?

That question changes the conversation. It asks the manager to prioritise, not simply prefer.

2. It gives candidates honest information

Candidates are making a decision too. A strong job description helps them understand the work, the level, the pressure points, and the likely shape of success.

For example, "work cross-functionally" is vague. "Partner with Product, Sales, and Customer Success to prioritise customer-facing release communications" gives a candidate a clearer picture of the role. It also helps them decide whether their experience is relevant.

This matters especially for candidates who do not come from identical companies or familiar career paths. Clearer language can widen the pool because it allows people to recognise transferable experience.

3. It becomes the foundation for assessment

The job description should connect to the interview plan. If a requirement appears in the job description but never appears in the assessment process, ask why. If interviewers assess something that is not in the job description, ask whether the role document is incomplete.

Use the rewrite to create a cleaner assessment chain:

• job outcome
• required capability
• interview competency
• evidence to collect
• scoring rubric

That chain makes hiring more disciplined and easier to explain.

A simple review framework

When reviewing the AI output, use four lenses.

Clarity

Can a qualified candidate understand what the role actually does? Remove phrases that sound impressive but do not carry information.

Relevance

Can every requirement be linked to a real task, risk, responsibility, or outcome? If not, it may be decoration.

Proportionality

Is the requirement appropriate for the level? A coordinator role should not read like a senior strategy role. A senior role should not be filled with junior task lists.

Inclusion

Could the wording unnecessarily discourage qualified candidates? Inclusion is not only about individual words. It is also about inflated criteria, narrow pathways, and unclear expectations.

Example: from inflated to useful

Weak version:

We are looking for a world-class communicator who can thrive in a fast-paced environment and manage multiple stakeholders.

Better version:

You will explain hiring progress, risks, and trade-offs to hiring managers each week, especially when priorities shift or candidate availability changes.

The second version is less dramatic, but much more useful. It tells candidates what communication looks like in the role. It also gives interviewers something to assess.

Another weak version:

Bachelor's degree required.

Better version:

Experience applying structured hiring, employee relations, or people operations practices in a professional environment. Equivalent practical experience is welcome.

This replacement should only be used if the degree is not legally, professionally, or genuinely required. The point is not to remove standards automatically. The point is to make every standard earn its place.

Use AI as a review partner, not the decision-maker

AI can flag language patterns, suggest clearer phrasing, and separate requirements. It cannot know your legal context, compensation philosophy, union environment, internal mobility goals, or workforce plan.

Before posting, HR should review:

• role scope
• pay band
• legal compliance
• physical or location requirements
• essential qualifications
• accessibility language
• internal equity considerations
• hiring manager expectations

AI improves the draft. HR owns the accountability.

Turn the rewrite into an intake conversation

The best outcome of today's exercise may be a better conversation with the hiring manager.

Use the audit to ask:

• Which requirements are truly essential on day one?
• What can be learned in the first six months?
• What will success look like after 90 days?
• What kind of experience predicts performance here?
• Which requirement would we remove if it narrowed the pool too much?
• What does failure look like in this role?

These questions turn job description editing into hiring design.

What to do after the AI rewrite

Do not move straight from AI output to posting. Treat the output as a working draft and run a compact review.

First, compare the rewrite against the current pay band. Sometimes a cleaner job description reveals that the role is bigger than the compensation range supports. That is not a copywriting issue. It is a job architecture issue.

Second, check whether the title fits the market. AI can suggest alternatives, but HR should validate whether the title is understandable to candidates and consistent with internal levelling.

Third, share the must-have and nice-to-have split with the hiring manager. Ask them to approve it explicitly. This reduces late-stage surprises when a strong candidate lacks a preference that was never truly essential.

Finally, save the clean version as the new source of truth. If the organisation keeps recycling old templates, the same problems will return in the next search.

Today's practice

Choose one real job description. Run the prompt. Then review:

1. Which requirement was hardest to justify?
2. Which phrase was too vague for candidates to interpret?
3. Which nice-to-have was accidentally written like a must-have?
4. What would the hiring manager need to confirm before posting?
5. What language makes the role clearer without weakening the standard?

By the end, you should have a stronger job description and a clearer understanding of what the role truly requires.