Claude Cowork for job description writing turns a 60–90 minute drafting task into a 15-minute review exercise. When configured with your job description template, job level framework, and employer value proposition, Cowork produces role-specific, company-calibrated job descriptions that reflect your actual standards — not generic job board copy that every candidate has seen 50 times. The result is a five-fold increase in job description throughput per recruiter, and consistently better candidate quality because the descriptions attract people who understand precisely what the role involves.
Job descriptions are the first and most persistent communication between your organisation and potential candidates. A poorly written job description over-specifies requirements (deterring qualified candidates), under-specifies responsibilities (attracting people who are wrong for the role), or uses generic language that fails to differentiate the role from identical postings at competitors. Claude Cowork, given the right inputs, eliminates all three of these problems at scale.
This article covers the complete Claude Cowork job description workflow: from configuring your project to the 5-step writing process, from inclusivity checks to job board optimisation. For the broader Claude Cowork recruiting guide, see Claude Cowork for recruiters. To deploy Cowork for your recruiting team, see our Claude Cowork deployment service.
Why Job Descriptions Determine Hiring Outcomes More Than Recruiters Acknowledge
Most recruiting organisations measure job description quality by whether the role gets filled, not by whether it attracted the right candidates efficiently. This means poor job descriptions — ones that attract high application volumes of misaligned candidates — often look successful by the wrong measure. The true cost of a poorly written job description is screening time (reviewing misaligned applications), hiring manager time (interviewing candidates who should have self-selected out), and opportunity cost (qualified candidates who read the description and decided not to apply).
The research on job description quality and candidate behaviour is consistent. Candidates with fewer years of experience are less likely to apply when job descriptions use "requirements" language for nice-to-have skills — systematically reducing diversity in applicant pools. Job descriptions with vague responsibilities attract candidates who are optimising for the flexibility of the role rather than a genuine fit with the work. And job descriptions that fail to differentiate the role or team from competitors produce lower-quality applications because candidates are applying to the role description, not to your specific opportunity.
Claude Cowork for job description writing addresses all three issues. It enforces consistent requirements framing (using "required" only for genuinely required qualifications), produces specific and accurate responsibility descriptions, and incorporates your employer value proposition into the role description. The output is a job description that attracts the right candidates and deters the wrong ones — which is the function a job description is supposed to serve.
The Claude Cowork Job Description Workflow
The workflow that produces the best job descriptions consistently is a five-step process. Each step is faster with Cowork than without it, but the structure ensures that the inputs Cowork receives are accurate and that the output is reviewed by a recruiter before posting.
Step 1: Complete the Role Intake Form
Before writing a job description, you need specific, accurate information about the role. The hiring manager intake form is the source of that information. A good intake form captures: the job title and level, the primary purpose of the role (one sentence), the three to five most important responsibilities, the must-have experience and skills (genuinely required, not just desirable), the nice-to-have skills, the reporting structure, the key relationships and stakeholders, team culture and working style, the specific selling points of this role and team, and any constraints (location, hours, travel requirements).
Ask the hiring manager to complete this before the briefing call. Use the briefing call to clarify and add nuance, not to collect basic information. When the intake form is complete and accurate, everything downstream — job description, sourcing brief, interview kit — is faster and better quality.
Step 2: Input the Intake Form Information into Cowork
Open your recruiting Cowork project (which has your job description template, level framework, and employer value proposition already loaded) and paste the intake form information. Add a prompt (see templates below) specifying word count, tone requirements, any specific inclusivity considerations for this role, and any other constraints.
Step 3: Review Cowork's First Draft
Cowork produces a structured first draft in under 90 seconds. Review it against four criteria: factual accuracy (are the responsibilities correctly described?), requirements accuracy (is "required" used only for genuinely required qualifications?), differentiation (does it explain what makes this role and team specific, not generic?), and tone (does it match your employer brand?). Flag any issues in your review notes.
Step 4: Edit and Refine
Provide your review notes to Cowork and ask it to produce a revised version addressing each point. For most roles, this takes one revision cycle. For senior or highly specialised roles, you may want a second revision with more specific feedback on technical accuracy. The recruiter should not be the one correcting technical role details — flag any technical accuracy issues back to the hiring manager for clarification before finalising.
Step 5: Inclusivity Check and Job Board Optimisation
Before posting, run the finalised description through two additional Cowork prompts: an inclusivity check (see below) and a job board optimisation review (title, keyword placement, and any platform-specific requirements). Both take under two minutes and consistently improve the posting's performance.
Anatomy of a Cowork-Assisted Job Description
Understanding the optimal structure of a job description helps you brief Cowork effectively and review its output intelligently. Here is the section-by-section anatomy of a high-performing job description, with guidance on what Cowork handles well and what needs careful human review.
Job Title
Cowork produces the correct title based on your input. Review: is this the title candidates actually search for? Generic titles ("Analyst" vs "Financial Analyst") significantly affect job board visibility. Use the candidate-facing title in the posting, not the internal grade title.
Role Overview (2-3 sentences)
Cowork writes a concise summary of the role's purpose, team context, and primary impact. Review for accuracy: does it correctly represent what this role actually does and why it matters?
Key Responsibilities (4-6 bullets)
Cowork structures responsibilities as action-oriented bullets. Review carefully: are these the actual responsibilities in priority order? Hiring managers often list responsibilities that sound impressive but are not the primary focus of the role.
Required Experience and Skills
Cowork uses "required" only for items you have explicitly labelled as must-haves in your input. Review: is everything listed here genuinely required to do this job on day one? Requirements inflation is the most common source of diversity reduction in applicant pools.
Nice-to-Have / Preferred
Cowork presents preferred qualifications separately and with softer language. Review: are any of these actually required? If so, move them. Are any irrelevant or potentially exclusionary? Remove them.
About the Team / What We Offer
Cowork pulls from your employer value proposition document to write a team description and benefits overview. Review for accuracy and authenticity: does this reflect the actual team culture and what is genuinely offered?
Writing Inclusive Claude Cowork Job Descriptions
Inclusive job description writing is not about removing all standards — it is about ensuring the standards you list are genuinely related to role performance, described in language that does not unnecessarily exclude qualified candidates, and not inflated beyond what is actually required. Claude Cowork for job description writing has specific capabilities in this area that go beyond generic grammar checkers.
Common Inclusivity Issues Cowork Identifies and Fixes
Gendered language: Words like "rockstar," "ninja," "dominant," "aggressive" (as in aggressive growth targets), and even "he/she" pronouns have documented effects on which candidates apply. Cowork uses gender-neutral language by default and flags any gender-coded terms in your input for discussion.
Requirement inflation: "5+ years of experience required" for a role where 3 years would actually be sufficient. "Bachelor's degree required" for a role where equivalent practical experience is demonstrably sufficient. "Native English speaker preferred" for a role requiring professional-level communication. Cowork flags these patterns and asks whether the requirement is genuinely necessary.
Culture fit language: Vague culture references ("must thrive in a fast-paced environment," "comfortable with ambiguity," "we work hard and play hard") tend to function as proxies for cultural homogeneity rather than role performance predictors. Cowork converts these into specific, observable behaviours where possible.
To run an inclusivity check, ask Cowork: "Review the job description above for any language that may unnecessarily deter qualified candidates from applying. Flag gendered terms, potentially inflated requirements, vague culture-fit language, and any other patterns known to reduce diversity in applicant pools. For each flag, suggest a more inclusive alternative."
Job Board Optimisation with Claude Cowork Job Descriptions
A job description that is accurate and inclusive but invisible on job boards is a failed asset. Job board optimisation for recruiting is structurally similar to SEO for content: the right keywords, in the right places, in a format that the platform's ranking algorithm rewards.
The Cowork Job Board Optimisation Check
After finalising the job description copy, ask Cowork to review it specifically for job board visibility. The prompt should specify the platforms you are posting on (LinkedIn, Indeed, Glassdoor, specialist boards) and ask Cowork to check that: the job title matches the terms candidates search for on that platform, key skills appear in the first 150 words (where most platforms' ranking algorithms place the highest weight), the description is within the optimal word count for the platform (typically 300–700 words for LinkedIn and Indeed), and there are no formatting elements that may render incorrectly on specific platforms.
For specialist boards (technical roles on Stack Overflow Jobs or Hired; finance roles on eFinancialCareers; legal roles on Legal Week Jobs), provide Cowork with the platform's posting guidelines and ask it to identify any format or keyword adjustments needed. This takes under five minutes and consistently improves application volumes on platforms where you are competing for attention.
Maintaining a Consistent Job Description Library with Claude Cowork
One of the most valuable long-term benefits of using Claude Cowork for job description writing is the ability to maintain a consistent, up-to-date job description library. Without Cowork, job description libraries tend to become stale: descriptions are reused without review, requirements drift upward over time, and inconsistencies in tone and format accumulate across the team.
With Cowork, you can conduct a quarterly job description library audit. Upload batches of existing job descriptions and ask Cowork to review them for: outdated technology references (listing tools that are no longer used), requirements inflation that has accumulated over repeated editing, inconsistent formatting or tone across similar roles, and any inclusivity issues. This audit takes two to three hours for a library of 50–100 roles and produces a prioritised list of descriptions for revision.
Cowork can also identify when the same role has been posted multiple times with significantly different requirement levels — a common problem when different hiring managers brief different recruiters without a consistent standard. Flagging these discrepancies and standardising the requirements, using your level framework as the reference, improves both hiring consistency and job description quality.
Prompt Templates for Claude Cowork Job Description Writing
Write a job description for the role detailed below. Use the job description
template, job level framework, and employer value proposition document in
this project as your structure and language reference.
JOB DETAILS:
Title: [Job Title]
Level: [Level]
Department: [Department]
Location/Remote: [Location or remote policy]
Reports to: [Manager title]
PRIMARY PURPOSE OF ROLE:
[One sentence]
KEY RESPONSIBILITIES:
1. [Responsibility 1]
2. [Responsibility 2]
3. [Responsibility 3]
4. [Responsibility 4]
5. [Responsibility 5 if applicable]
REQUIRED (genuinely must-have):
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
PREFERRED (nice to have):
- [Nice-to-have 1]
- [Nice-to-have 2]
SELLING POINTS (specific to this role/team):
- [Differentiator 1]
- [Differentiator 2]
- [Differentiator 3]
Target length: 500–650 words.
Use gender-neutral language throughout.
Mark "required" qualifications only for the items above labelled Required.Review the job description below for inclusivity issues. Specifically, flag:
1. Gendered or masculine-coded language (including words like "rockstar",
"ninja", "dominant", "aggressive" used in a non-role-specific context)
2. Requirements that may be inflated beyond what the role genuinely needs
(e.g. degree requirements for roles where experience is equivalent,
excessive years-of-experience requirements for the level)
3. Vague culture-fit language that functions as a proxy for homogeneity
rather than role-relevant competence
4. Any other language patterns known to reduce diversity in applicant pools
For each issue flagged, provide: the specific text, why it is a concern,
and a suggested alternative.
[Paste job description below]Update the existing job description below to reflect the following changes.
Do not alter any sections that are not affected by these changes.
Changes required:
1. [Change 1 — e.g. Updated technology: replace "Python 2.7" with "Python 3.x"]
2. [Change 2 — e.g. Updated reporting line: now reports to VP Engineering not CTO]
3. [Change 3 — e.g. Remove: "must have X" — this is now a nice-to-have]
Also: run an inclusivity check on the updated version and flag any issues
you identify, particularly in the requirements sections.
Output the complete updated job description, with a separate "Changes Made"
section listing each change and where it appears in the document.
[Paste existing job description below]Need Your Recruiting Team Writing Better Job Descriptions Consistently?
Our Claude Cowork deployment for recruiting teams includes job description template configuration, level framework setup, inclusivity guidelines, and a pre-built prompt library. Most teams are fully deployed in two weeks.
Book a Free Strategy CallKey Takeaways
- Claude Cowork for job description writing increases throughput five-fold while improving consistency and quality — provided the project is configured with your templates and the inputs are accurate
- The five-step workflow (intake, input, review, refine, optimise) produces better results than asking Cowork to write a job description from minimal information
- The inclusivity check prompt is one of the highest-value uses of Cowork in recruiting — it systematically identifies language patterns that reduce diversity in applicant pools
- Job board optimisation is a two-minute addition to the workflow that consistently improves application volume on competitive platforms
- A quarterly job description library audit using Cowork prevents the requirements inflation and tone inconsistency that accumulate when descriptions are edited ad hoc over time
More From the Blog
Frequently Asked Questions
Will Claude Cowork job descriptions all sound the same if multiple recruiters use the same project?
No — and this is one of the most common misconceptions about Cowork-assisted job description writing. Cowork uses the template and employer value proposition as structure references, but the specific content of each job description is driven by the role-specific information provided in the prompt. Two job descriptions written by different recruiters using the same project will share the same structural format and tone, but will be specific to their respective roles. Consistency of format and tone is a feature, not a limitation — it is how you build a recognisable, coherent employer brand across all your postings.
Can Cowork write job descriptions in multiple languages for international roles?
Yes. Cowork can produce job descriptions in French, German, Spanish, Dutch, Italian, Portuguese, Japanese, and many other languages. For international roles, specify the target language in your prompt and note any jurisdiction-specific requirements (for example, French job descriptions must comply with specific legal requirements about using French language in job postings in France). Review international language job descriptions with a native speaker or local HR team member before posting, as Cowork may produce grammatically correct but locally unidiomatic language in less common languages.
How do we prevent job descriptions from becoming outdated over time?
Schedule a quarterly job description library audit using the audit prompt pattern described above. Identify descriptions that are more than 12 months old without a formal review, descriptions for roles that have been rehired multiple times (which often carry accumulated requirements inflation), and descriptions that contain technology or tool references that are no longer current. Assign the audit task to a Cowork session rather than a manual review, which turns a half-day exercise into a two-hour one. Update the flagged descriptions before the next hiring cycle for each role.
What is the right word count for a job description?
Research on job board performance consistently shows that 400–700 words produces the best combination of application volume and candidate quality for most roles. Descriptions under 300 words are perceived as incomplete and generate lower application volumes. Descriptions over 800 words see reduced application rates because candidates self-select out before reading the requirements. Cowork defaults to 500–650 words when given this guidance in the prompt, which sits in the optimal range. For executive or highly specialised technical roles, slightly longer descriptions (700–900 words) may be appropriate to provide the level of context senior candidates expect.
Should we disclose that AI was used to write job descriptions?
There is no current legal requirement in most jurisdictions to disclose AI-assisted job description writing, since the recruiter and hiring manager review and approve all content. The distinction that matters legally is whether AI is making employment decisions (not the case here) versus AI assisting human professionals with drafting tasks (which is the case here). As AI transparency norms evolve, some organisations are proactively disclosing that "AI tools assist our recruiting team" in their careers page or privacy notice, which is reasonable and increasingly expected. Consult your legal team for jurisdiction-specific guidance.
Can Cowork help us write job descriptions for roles we have never hired for before?
Yes, and this is one of the areas where Cowork is particularly valuable. For new role types (emerging technical specialisations, hybrid roles, roles that did not exist three years ago), Cowork can draw on its training data to describe typical responsibilities, required skills, and industry-standard requirements for that role type — which you then refine based on your specific context. Always have the hiring manager validate the responsibilities and requirements for unfamiliar roles before finalising. For highly specialised or niche technical roles, consider asking a subject matter expert to review the technical accuracy of the requirements section before posting.