Back/Operations/Claude
BeginnerOperations

How to Standardize Job Descriptions Across a Company Using Claude Projects

Use a Claude Project to turn a structured hiring brief into a consistent job description, while keeping responsibilities, level, compensation, location, accessibility, legal language, and inclusive requirements tied to approved company policy and the actual role.

How to Standardize Job Descriptions Across a Company Using Claude Projects

Zach shows a Claude Project that combines Gamma's company and hiring guidance with examples of strong listings, allowing any hiring manager to describe a role and receive a consistently structured job description for review.

Before you start

What you need

  • An approved job architecture, level, title, employment type, location, and compensation policy
  • A role brief with outcomes, responsibilities, collaborators, constraints, and interview evidence
  • Company voice, equal opportunity, accessibility, benefits, and legal templates
  • Strong approved examples plus rejected patterns and inflated requirements to avoid
  • Recruiting, hiring manager, compensation, and legal owners for the posting

What you’ll make

A consistent job description with role outcomes, responsibilities, required and preferred qualifications, compensation and location details, hiring process, accessibility information, and a revision record tied to the approved brief.

Tools used

Step by step

The workflow

Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.

4 steps

Step01

Set up a Claude Project with Examples

Create a Claude Project with versioned company, voice, job architecture, compensation, location, accessibility, equal opportunity, benefits, and legal guidance. Add approved examples and clearly label any fictional sample.

Step02

Add an Instruction to Use the Examples

Tell Claude which blocks are canonical, which fields must come from the hiring brief, and which claims it must never invent. Require it to flag missing information instead of filling gaps.

Example prompt
Use the approved project guidance to draft job descriptions. Preserve canonical company, compensation, location, accessibility, equal opportunity, and legal blocks. For role specific content, use only the supplied brief. Return MISSING_INFORMATION for unsupported level, scope, requirements, benefits, or process details.
Step03

Generate a New Job Description with a Simple Prompt

Give the project a structured role brief with mission, outcomes, responsibilities, collaborators, level, must have competencies, teachable skills, location, compensation, and interview plan.

Example prompt
Draft a job description from this approved role brief: [brief]. Organize it as role impact, outcomes, responsibilities, required qualifications, preferred qualifications, compensation and location, benefits, process, and accessibility. Use direct inclusive language. Do not invent requirements or company claims, and list unresolved fields first.
Step04

Review, Tweak, and Publish

Have the hiring manager, recruiting, compensation, and legal owners compare the draft with the role brief and interview rubric. Correct the project instructions when a recurring problem appears, then publish only through the normal recruiting workflow.

What good looks like

  • The posting matches the approved level, compensation band, location, employment type, and actual responsibilities.
  • Requirements are necessary, specific, and separated from preferences without proxying for protected characteristics.
  • Boilerplate remains consistent while role specific claims are confirmed by the hiring manager and recruiting owner.
  • The final text is accessible, inclusive, legally appropriate for the jurisdiction, and synchronized with the recruiting system.

Build your next product with ChatPRD

Turn an idea into a PRD, user stories, and a plan.

Try ChatPRD free

After the steps

Runbook notes

How to recover when the loop fails and where human judgment helps.

Recover

If it goes sideways

The model adds years, credentials, or leadership scope that the role does not require
Generate from the approved level and outcomes, justify every requirement, and remove unsupported proxies.
Examples or model defaults introduce exclusionary, gendered, age coded, or inaccessible language
Run a structured inclusive language review and have recruiting or legal correct the template and source examples.
Company, benefits, compensation, location, or policy language is outdated
Reference versioned approved blocks owned by the responsible team and refresh them centrally.
A polished listing does not match the interview plan or evaluation rubric
Derive both from the same role outcomes and competencies, then reconcile them before opening the role.

Start shipping
better products.

Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.

Free to start
No credit card
SOC 2 certified
Enterprise ready