Write Job Descriptions: use the public role post where vague wording context

Finish a job description from "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." by keeping the source note, reviewer, and stop rule beside the prompt run.

Start with the right jobUse this workflow when your note, output, and switch point line up.

First move: The quickest safe job description path is source note, reviewer, prompt run, answer choice, then reusable variables; skipping one step usually creates a reusable-looking but unverified answer.
Keep after run: Keep one job description review note that explains why the answer was accepted, repaired, or rejected before it becomes job description prompt pattern with source notes, constraints, and review checklist for a later prompt run.
Wrong page signal: Wrong page signal: switch to ChatGPT Prompts for HR and Recruiters if the user cannot supply role outcomes, responsibilities, requirements, compensation range, and hiring process, if the desired result is not a job description, or if role outcomes, required skills, compensation clarity, and inclusive wording is no longer the controlling choice.

First usable run

Start with the note you actually have1/3 ready

A realistic example is loaded. Try the flow once, then clear it and paste your own working notes.

Next stepFinish the run setup2 items still need context before this becomes reusable.

Current note

Paste source notesMust keepDo not allow

PrepareSource noteReal notes are loaded.
RunCopy run prompt2 checks before copy.
ReviewReview answerCurrent choice: Repair.
SaveSave reusable version0/3 save checks closed.

Keep working laterPage work stays on this device until you save it.

Try the sample firstSee one messy note become a usable write job descriptions run

Messy input: For job description, the source note starts plainly: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." is the rough request. The ready check for job description is simple: the practical output is a job description with role outcomes, required skills, compensation clarity, and inclusive wording, checker ownership, and this boundary still visible: keep the wording fair, job-related, and reviewed by the appropriate human.
Better answer should: The target job description result should return a job description with field labels, short bullets, and a use-or-revise note; keep source-backed lines, guesses, and open questions in different lanes, attach the checker to the risky line before anyone reuses it, prepare job description section map with outcome language, and make the final pass check job description quality, role outcomes and required skills, and fairness and policy fit.
Human edit: HR and Recruiters final edit for job description work should keep the useful source-backed sections, rewrite vague requirements as observable outcomes and mark anything needing HR review, turn private names and temporary facts into variables, and make the saved wording fit a candidate, employee, hiring panel, or HR reviewer; read it beside "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and keep the closing version aligned with this standard: the human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related.

Fix before reuse2 gaps before reuseCopy can start the first pass, but the answer is not reusable until these checks are closed.

Separate facts from assumptionsMark which must-keep details came from the user and which details still need a person to check them.
Name the checker and stop ruleThe final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process. must know what to reject before the answer is reused.

Real note: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
What will change: Bring the exact source notes and mark what the model must not invent, especially anything tied to the pasted notes, concrete examples, hard limits, and reviewer judgment.
Human check: Source review, write job descriptions: the answer uses the supplied role outcomes, responsibilities, requirements, compensation range, and hiring process and does not fill missing facts with confident guesses.

Open run previewCheck the exact prompt before copying.

Run prompt preview

Copy this after checking the notes

Task: ChatGPT Prompts for HR and Recruiters to Write Job Descriptions
Who checks it: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.

Paste source notes:
Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.

Must keep:
Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
role outcomes, responsibilities, requirements, compensation range, and hiring process
role outcomes, required skills, compensation clarity, and inclusive wording

Do not allow:
Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Reject it if the useful part is still not formatted as copy options grouped by angle, audience, supporting detail, and revision note.

Readiness before copy:
- Separate facts from assumptions: Mark which must-keep details came from the user and which details still need a person to check them.
- Name the checker and stop rule: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process. must know what to reject before the answer is reused.

Run prompt:
Run this evidence-aware working copy prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return copy options grouped by angle, audience, supporting detail, and revision note.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get a working version they can inspect against the supplied notes.

Stop rule: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Record to keep: Keep the accepted answer beside the original note, the prompt variables that changed the answer, the section that still needs job description quality, role outcomes and required skills, and fairness and policy fit, and the final reason the accepted version can become job description prompt pattern with source notes, constraints, and review checklist.

Open answer reviewUse this after ChatGPT returns the first answer.

After ChatGPT answers

Check the answer before saving it

Check against: Source review, write job descriptions: the answer uses the supplied role outcomes, responsibilities, requirements, compensation range, and hiring process and does not fill missing facts with confident guesses. Output shape, write job descriptions: the result clearly becomes a job description, not broad advice about the task.
Reject if: Evidence issue, write job descriptions: the answer invents or overstates the pasted notes, concrete examples, hard limits, and reviewer judgment. Task drift, write job descriptions: it ignores role outcomes, required skills, compensation clarity, and inclusive wording and moves into a neighboring workflow.
Keep after run: Keep the accepted answer beside the original note, the prompt variables that changed the answer, the section that still needs job description quality, role outcomes and required skills, and fairness and policy fit, and the final reason the accepted version can become job description prompt pattern with source notes, constraints, and review checklist.

Open first answer choiceChoose accept, repair, or reject only after review.

First answer choice

Pick accept, repair, or reject before reuse

After the first write job descriptions answer, the recruiter should choose Accept, Repair, or Reject before saving anything as job description prompt pattern with source notes, constraints, and review checklist. The choice must compare "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." with copy options grouped by angle, audience, supporting detail, and revision note, role outcomes, required skills, compensation clarity, and inclusive wording, and the pasted notes, concrete examples, hard limits, and reviewer judgment.

Choose when: Choose Repair when the answer has a useful shape but loses one of the required pieces: role outcomes, required skills, compensation clarity, and inclusive wording, the pasted notes, concrete examples, hard limits, and reviewer judgment, the reviewer role, the source note, or the reusable fields needed for job description prompt pattern with source notes, constraints, and review checklist.
Do next: Ask ChatGPT for a second pass that keeps the usable structure, rewrites only the weak sections, adds missing support questions, and returns a job description in copy options grouped by angle, audience, supporting detail, and revision note without inventing details.
Keep after run: Keep the weak answer beside the repair note, mark which line failed job description quality, role outcomes and required skills, and fairness and policy fit, and save the corrected line only after it can be traced back to "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.".

Answer choice prompt

Repair this write job descriptions answer instead of accepting it. Source note: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." Weak answer: [paste_chatgpt_output_here]. Preserve any useful structure, but fix the parts that hide role outcomes, required skills, compensation clarity, and inclusive wording, turn the pasted notes, concrete examples, hard limits, and reviewer judgment into unsupported certainty, or skip the reviewer for job description quality, role outcomes and required skills, and fairness and policy fit. Return a repaired copy options grouped by angle, audience, supporting detail, and revision note, a list of changed lines, and one remaining question before this can become job description prompt pattern with source notes, constraints, and review checklist.

Do not save a reusable job description prompt pattern with source notes, constraints, and review checklist until one option has a written choice. The saved version must keep "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." as the example, turn private or one-time details into variables, and keep the risk check "keep the wording fair, job-related, and reviewed by the appropriate human" visible for the next run.

Open run logRecord what happened after each ChatGPT run.

Run notes

Save the answer, problem, and next try

Use this after the first answer. A reusable prompt improves when each run records what failed and what to try next.

Answer returnedProblem foundNext try

0No run notes yet
Run the prompt once, review the answer, then save the problem and next try here.

Open saved versionTurn the reviewed answer into a reusable saved version.

Saved version

Save the final answer, human edit, and variables

Save only after review. The reusable version needs the answer, the human edit, and the reuse rule in one place.

Final answerHuman editReusable variables

Save only when

The final answer passed the answer review.The human edit names what changed before reuse.Who checks it and reuse rule are saved with the asset.

Who checks it: The human owner who approves the final packet for HR and Recruiters to Write Job Descriptions before it is saved, shared, or reused.
Reuse rule: Save the job description answer only when private details are removed, one-time facts become variables, rewrite vague requirements as observable outcomes and mark anything needing HR review, and the review rule for role outcomes, required skills, compensation clarity, and inclusive wording still appears in the reusable prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.
Saved: 0/3 checks

Saved version preview

Final saved version for: ChatGPT Prompts for HR and Recruiters to Write Job Descriptions
Who checks it: The human owner who approves the final packet for HR and Recruiters to Write Job Descriptions before it is saved, shared, or reused.
Use or revise before saving: Repair

Save only after review:
- Source review, write job descriptions: the answer uses the supplied role outcomes, responsibilities, requirements, compensation range, and hiring process and does not fill missing facts with confident guesses.
- Keep the accepted answer beside the original note, the prompt variables that changed the answer, the section that still needs job description quality, role outcomes and required skills, and fairness and policy fit, and the final reason the accepted version can become job description prompt pattern with source notes, constraints, and review checklist.
- Keep a small receipt: source note, changed variables, the section the reviewer for job description quality, role outcomes and required skills, and fairness and policy fit approved, and why a candidate, employee, hiring panel, or HR reviewer can use it.
- Current answer choice: Keep the weak answer beside the repair note, mark which line failed job description quality, role outcomes and required skills, and fairness and policy fit, and save the corrected line only after it can be traced back to "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.".

Source note used:
Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.

Final answer:
The target job description result should return a job description with field labels, short bullets, and a use-or-revise note; keep source-backed lines, guesses, and open questions in different lanes, attach the checker to the risky line before anyone reuses it, prepare job description section map with outcome language, and make the final pass check job description quality, role outcomes and required skills, and fairness and policy fit.

Human edit:
HR and Recruiters final edit for job description work should keep the useful source-backed sections, rewrite vague requirements as observable outcomes and mark anything needing HR review, turn private names and temporary facts into variables, and make the saved wording fit a candidate, employee, hiring panel, or HR reviewer; read it beside "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and keep the closing version aligned with this standard: the human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related.

Reusable variables:
[source_material]: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: a candidate, employee, hiring panel, or HR reviewer
[goal]: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: keep the wording fair, job-related, and reviewed by the appropriate human

Reuse rule: Save the job description answer only when private details are removed, one-time facts become variables, rewrite vague requirements as observable outcomes and mark anything needing HR review, and the review rule for role outcomes, required skills, compensation clarity, and inclusive wording still appears in the reusable prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.
Stop if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

First run setup

Set up the first run

Edit notes

First move: Bring the exact source notes and mark what the model must not invent, especially anything tied to the pasted notes, concrete examples, hard limits, and reviewer judgment.
Bring first: Bring the rough case note: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
Switch if: The user cannot provide role outcomes, responsibilities, requirements, compensation range, and hiring process and would need ChatGPT to invent the important facts.
Keep after run: Keep the accepted answer beside the original note, the prompt variables that changed the answer, the section that still needs job description quality, role outcomes and required skills, and fairness and policy fit, and the final reason the accepted version can become job description prompt pattern with source notes, constraints, and review checklist.

Choose where you areGo to runner

Go to runnerWithin five minutes, the user should have a first job description prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps job description quality, role outcomes and required skills, and fairness and policy fit and the pasted notes, concrete examples, hard limits, and reviewer judgment visible before sharing anything. Start with: Bring the exact source notes and mark what the model must not invent, especially anything tied to the pasted notes, concrete examples, hard limits, and reviewer judgment.

Go to runner

Open switch notesWhat to bring, who checks it, and when to change workflows.

Who checks it

The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.

Check before using

Inspect role outcomes, responsibilities, requirements, compensation range, and hiring process, the case note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", and any open support around the pasted notes, concrete examples, hard limits, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

Compare later

Result job description hr check: open the top results and record whether they solve the task, not only a prompt phrase.

Visitor question: I have role outcomes, responsibilities, requirements, compensation range, and hiring process and need a job description for a candidate, employee, hiring panel, or HR reviewer; can this write job descriptions page turn "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." into copy options grouped by angle, audience, supporting detail, and revision note without hiding role outcomes, required skills, compensation clarity, and inclusive wording?
5-minute outcome: Within five minutes, the user should have a first job description prompt pattern with source notes, constraints, and review checklist, one copied run prompt, and a reviewer check that keeps job description quality, role outcomes and required skills, and fairness and policy fit and the pasted notes, concrete examples, hard limits, and reviewer judgment visible before sharing anything.
Wrong page signal: This is the wrong page if the work is closer to ChatGPT Prompts for HR and Recruiters, if role outcomes, required skills, compensation clarity, and inclusive wording is not the controlling choice, or if the user only wants broad ideas instead of a reviewable a job description.
Why this workflow fits: Save the rough note, the accepted prompt variables, the job description query language, and the section that shows why this a job description should stay separate from ChatGPT Prompts for HR and Recruiters.
Reuse choice: Reuse the output only when the answer traces back to role outcomes, responsibilities, requirements, compensation range, and hiring process, respects the risk check "keep the wording fair, job-related, and reviewed by the appropriate human", and gives a candidate, employee, hiring panel, or HR reviewer a clear accept, repair, or reject path.

Wrong page? Prepare interview questionsUseful next step when this workflow needs a related hr and recruiters output or review pass.

Working brief

Check the job before copying

The page earns its place by forcing the user to bring the concrete note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." before asking for polish, so the answer cannot coast on broad role advice.

Use this when: Use this workflow when role outcomes, responsibilities, requirements, compensation range, and hiring process is present and the answer has to survive a check for the pasted notes, concrete examples, hard limits, and reviewer judgment.
Paste this kind of note: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Expected result: The target job description result should return a job description with field labels, short bullets, and a use-or-revise note; keep source-backed lines, guesses, and open questions in different lanes, attach the checker to the risky line before anyone reuses it, prepare job description section map with outcome language, and make the final pass check job description quality, role outcomes and required skills, and fairness and policy fit.
Stop before reuse if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Human check: Source review, write job descriptions: the answer uses the supplied role outcomes, responsibilities, requirements, compensation range, and hiring process and does not fill missing facts with confident guesses.

Bring first: Bring the rough case note: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
Build when: Use this when the notes are ready and the next useful output is copy options grouped by angle, audience, supporting detail, and revision note, not more brainstorming.
Stop if: Stop if the answer hides missing context, blurs assumptions, or cannot trace key claims back to the notes.
Save when: Copy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Copy prompt Check answer

Fit and safety notes

Use this workflow for

HR and Recruiters who have real notes or context and need a structured first version of a job description.
Users who want ChatGPT to ask clarifying questions before it commits to copy options grouped by angle, audience, supporting detail, and revision note.
Teams that repeat job description work and need a prompt they can adapt without losing the review step.

Do not use for

Users who want ChatGPT to invent facts, credentials, numbers, or personal details.
Situations where the output needs final approval from a qualified human before it reaches a candidate, employee, hiring panel, or HR reviewer.
Work that includes private data that has not been removed or summarized safely.

Wrong page?Prepare interview questionsUseful next step when this workflow needs a related hr and recruiters output or review pass.

Editorial method Safe use About this library

Write job descriptions for recruiter Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a job description.

Real input: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Target output: The target job description result should return a job description with field labels, short bullets, and a use-or-revise note; keep source-backed lines, guesses, and open questions in different lanes, attach the checker to the risky line before anyone reuses it, prepare job description section map with outcome language, and make the final pass check job description quality, role outcomes and required skills, and fairness and policy fit.
Reject if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Scenario: A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. The job description work happens inside a public role post where vague wording can create screening risk. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible. For job description work, that context changes the prompt: it needs concrete inputs, a realistic output shape, and a stopping point for human judgment.
Bring: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. role outcomes, responsibilities, requirements, compensation range, and hiring process role outcomes, required skills, compensation clarity, and inclusive wording
Check: The human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible. Before handing off the job description, a careful final pass keeps the parts that save time, then rewrites anything that overstates evidence or misses the audience. Keep a short record of what changed before reuse. Recheck the hiring scope, salary or location policy, and approval owner before publishing role language.

Variable Builder

[source_material]Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.[audience]Who will read, use, approve, or act on this recruiter a job description.[goal]The choice or work outcome this recruiter job description work run should support.[constraints]Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.[review_lens]Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.[task_focus]The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.

Filled prompt

Copy this filled version

Run this evidence-aware working copy prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return copy options grouped by angle, audience, supporting detail, and revision note.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get a working version they can inspect against the supplied notes.

Show the full prompt

Expected output: Expect copy options grouped by angle, audience, supporting detail, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

First run

Run this page in four moves

Concrete outputThe target job description result should return a job description with field labels, short bullets, and a use-or-revise note; keep source-backed lines, guesses, and open questions in different lanes, attach the checker to the risky line before anyone reuses it, prepare job description section map with outcome language, and make the final pass check job description quality, role outcomes and required skills, and fairness and policy fit.

Keep after runKeep the accepted answer beside the original note, the prompt variables that changed the answer, the section that still needs job description quality, role outcomes and required skills, and fairness and policy fit, and the final reason the accepted version can become job description prompt pattern with source notes, constraints, and review checklist.

Reject before reuseHold the answer if it blurs what is known, what is assumed, and what still needs evidence.

PrepareCollect ContextUse this when the recruiter source notes are still uneven or missing the detail that would shape a job description.CopyBuild The AssetUse this when the notes are ready and the next useful output is copy options grouped by angle, audience, supporting detail, and revision note, not more brainstorming.GradeReview The AnswerUse this when ChatGPT has already answered and the risk is accepting fluent wording before job description quality, role outcomes and required skills, and fairness and policy fit is checked.SavePrepare HandoffUse this when the answer is close but needs to become a repeatable asset for a recruiter, not a one-off chat result.

Work notes

Start from the real note, not a blank prompt

Current input: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
First move: Bring the exact source notes and mark what the model must not invent, especially anything tied to the pasted notes, concrete examples, hard limits, and reviewer judgment.
Who checks it: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.

Stop rule: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Keep after run: Keep the accepted answer beside the original note, the prompt variables that changed the answer, the section that still needs job description quality, role outcomes and required skills, and fairness and policy fit, and the final reason the accepted version can become job description prompt pattern with source notes, constraints, and review checklist.

PrepareCollect ContextBring the rough case note: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.CopyBuild The AssetExpect copy options grouped by angle, audience, supporting detail, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.GradeReview The AnswerScan the answer before asking for a rewrite and check whether the answer shows enough context for the pasted notes, concrete examples, hard limits, and reviewer judgment.SavePrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Do not start if: Stop if the answer sounds polished but still cannot show the source notes behind role outcomes, required skills, compensation clarity, and inclusive wording.
Human check: Source review, write job descriptions: the answer uses the supplied role outcomes, responsibilities, requirements, compensation range, and hiring process and does not fill missing facts with confident guesses.

Real note check

Check the answer against your note

This works best when the answer stays tied to the note you pasted, the question people search, and the person who can review it.

Question to compare: chatgpt prompts for hr job description

Open reference checks

Paste into ChatGPT: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Question to compare: chatgpt prompts for hr job descriptionResult job description hr check: open the top results and record whether they solve the task, not only a prompt phrase.
Reference page: EEOC prohibited employment policies and practicesUsed for HR prompts where job descriptions, interview questions, scorecards, and employee communications need fair employment review.
Who checks it: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.Inspect role outcomes, responsibilities, requirements, compensation range, and hiring process, the case note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", and any open support around the pasted notes, concrete examples, hard limits, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.

This is the page for hr and recruiters who need job descriptions output that can survive a quick human review, not just polished wording. The working case on the page gives the user a fast way to swap in their own notes without guessing what each variable means. job descriptions channel fit: use a public role post where vague wording can create screening risk, where hidden assumptions become visible quickly. Keep the final human choice outside the model; the prompt prepares the work, but the reviewer owns acceptance. Prompts must support fair review and human judgment, not automated employment choices. The prompt is meant to shorten the blank-page step while keeping the user's judgment in control.

Real use plan for treating the prompt like a work note

0/12 checked

This write job descriptions plan prevents a smooth but thin response from becoming the saved pattern; every pass has to show where the note supports a job description and where a human still has to check.

Before copying

Begin with the parts a reviewer can check: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.Include the reader's context, not only the role name, so the answer fits a candidate, employee, hiring panel, or HR reviewer.State the editorial guardrail in the same prompt as the source notes: The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening.Make role outcomes, required skills, compensation clarity, and inclusive wording visible in the prompt before asking for the final format.

After ChatGPT answers

Scan the answer before asking for a rewrite and check whether the answer shows enough context for the pasted notes, concrete examples, hard limits, and reviewer judgment.Check job description quality, role outcomes and required skills, and fairness and policy fit before accepting the structure or tone.Use the follow-up to fix a real gap before requesting a cleaner final version.Make the reusable prompt shorter than the working version and keep job description quality, role outcomes and required skills, and fairness and policy fit intact.

Reject the answer if

Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.Reject it if the useful part is still not formatted as copy options grouped by angle, audience, supporting detail, and revision note.Reject it when a user could miss the privacy, policy, or approval limit.Reject it if a careful reviewer cannot trace the final answer back to the input.

Choose the next move

Begin with the messy notes, then choose the prompt path that matches the current state of the work.

Build The Asset

Use this when the notes are ready and the next useful output is copy options grouped by angle, audience, supporting detail, and revision note, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a job description with assumptions separated from source-backed details.
Bring first: Bring the task focus: role outcomes, required skills, compensation clarity, and inclusive wording. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a job description.
Next check: Use the run sheet's review mode before sharing anything with a candidate, employee, hiring panel, or HR reviewer.

Open prompt Prepare context Check answer

Before copying

Begin with the parts a reviewer can check: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
Include the reader's context, not only the role name, so the answer fits a candidate, employee, hiring panel, or HR reviewer.
State the editorial guardrail in the same prompt as the source notes: The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening.

Accept only if

Scan the answer before asking for a rewrite and check whether the answer shows enough context for the pasted notes, concrete examples, hard limits, and reviewer judgment.
Check job description quality, role outcomes and required skills, and fairness and policy fit before accepting the structure or tone.
Use the follow-up to fix a real gap before requesting a cleaner final version.

Reject when

Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Know when the answer is ready

Use this quick check before saving the answer, rerunning the prompt, or switching to a neighboring workflow.

Ready signal

Stop reading and run it when the supplied context "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." produces a job description with the usable answer first, then gaps and follow-up checks, keeps role outcomes, required skills, compensation clarity, and inclusive wording visible, and gives the operator checking whether the pasted notes, concrete examples, hard limits, and reviewer judgment is still visible a practical accept-it, fix-it, or rerun note before sharing with a candidate, employee, hiring panel, or HR reviewer.

First run action

Make the first message carry role outcomes, responsibilities, requirements, compensation range, and hiring process, the intended a job description, the audience, the stop rule "keep the wording fair, job-related, and reviewed by the appropriate human", and the support needed for the pasted notes, concrete examples, hard limits, and reviewer judgment.

Keep after run: Keep the accepted answer beside the original note, the prompt variables that changed the answer, the section that still needs job description quality, role outcomes and required skills, and fairness and policy fit, and the final reason the accepted version can become job description prompt pattern with source notes, constraints, and review checklist.
Use or revise: the operator checking whether the pasted notes, concrete examples, hard limits, and reviewer judgment is still visible should approve the output only if it can be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process, shows what is assumed, and does not turn the pasted notes, concrete examples, hard limits, and reviewer judgment into a confident claim without review.
What makes this page different: This page deserves its own search fit because tying the query "chatgpt prompts for hr job description" to a fillable prompt, a realistic case, an answer repair path, and a no-fake-metrics support boundary instead of only listing prompt phrases.
Why this page exists: This page deserves its own workflow for the job description query because job description changes the source material, reviewer, output shape, and failure mode; sending the user to a nearby recruiter page would hide role outcomes, required skills, compensation clarity, and inclusive wording and weaken the final a job description.

Second pass

Second pass before the answer becomes reusable

Source line

Editor margin source for job description work: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." It carries the constraint that separates this page from a nearby prompt workflow.

Human check note

the reviewer closest to a candidate, employee, hiring panel, or HR reviewer reads the first ChatGPT answer beside the rough note and decides what survives. The reviewer is not grading style first; they are checking whether the answer can still point back to the source note after it becomes usable. The check belongs before the prompt is saved as job description prompt pattern with source notes, constraints, and review checklist.

Keep

the rough note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check" as the visible source line for a job description

Keep this because the rough note is the only part a recruiter can compare against the answer when copy options grouped by angle, audience, supporting detail, and revision note starts to sound finished.

The accepted answer should repeat or clearly map back to "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." before it adds structure.

Cut

any confident claim about the pasted notes, concrete examples, hard limits, and reviewer judgment that the pasted note does not prove

Cut it because the support around the pasted notes, concrete examples, hard limits, and reviewer judgment is the review risk for this page, and fluent wording can make an unsupported detail look approved.

If the source note does not show the fact, the answer should move it into a needs-checking line or remove it.

Ask

the missing audience, owner, or review detail needed before a candidate, employee, hiring panel, or HR reviewer uses the answer

Ask before reuse because a job description only helps a candidate, employee, hiring panel, or HR reviewer when the channel, approval owner, and open support are visible.

The next run should name the missing field instead of burying it inside a polished answer.

Rewrite

the first polished paragraph so it shows role outcomes, required skills, compensation clarity, and inclusive wording before tone improvements

Rewrite the opening because this task is about role outcomes, required skills, compensation clarity, and inclusive wording, not a general job description answer that could fit any role page.

A reviewer should see role outcomes, required skills, compensation clarity, and inclusive wording in the first accepted section and again in the saved reuse rule.

Why this feels hand-edited

the reviewer closest to a candidate, employee, hiring panel, or HR reviewer leaves this margin pass because the workflow has to protect a real source note, not only offer another prompt. For hr and recruiters working on job description, the human-feeling part is the specific tradeoff: keep "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", cut unsupported certainty, ask for the missing owner, and rewrite the answer around role outcomes, required skills, compensation clarity, and inclusive wording. That support trail makes the page feel edited rather than assembled from repeated blocks.

Run the second pass

Run an editorial margin pass for this task. Source note: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." Output being reviewed: [paste ChatGPT answer]. Mark four choices: Keep the source-backed detail that should survive, Cut any unsupported claim about the pasted notes, concrete examples, hard limits, and reviewer judgment, Ask the missing question that blocks a candidate, employee, hiring panel, or HR reviewer from using the result, and Rewrite the section so role outcomes, required skills, compensation clarity, and inclusive wording stays visible before polish. End with one accept, repair, or reject choice and a reuse rule for job description prompt pattern with source notes, constraints, and review checklist.

Task actions for the next useful move

Bring the exact source notes and mark what the model must not invent, especially anything tied to the pasted notes, concrete examples, hard limits, and reviewer judgment.

CollectCollect ContextBring the rough case note: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.CopyBuild The AssetExpect copy options grouped by angle, audience, supporting detail, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.CheckReview The AnswerScan the answer before asking for a rewrite and check whether the answer shows enough context for the pasted notes, concrete examples, hard limits, and reviewer judgment.HandoffPrepare HandoffCopy the external review checklist, record what changed, and save a version with reusable variables instead of private details.

Wrong page ifThe user cannot provide role outcomes, responsibilities, requirements, compensation range, and hiring process and would need ChatGPT to invent the important facts.

Stay hereUse this workflow when role outcomes, responsibilities, requirements, compensation range, and hiring process is present and the answer has to survive a check for the pasted notes, concrete examples, hard limits, and reviewer judgment. First move: Bring the exact source notes and mark what the model must not invent, especially anything tied to the pasted notes, concrete examples, hard limits, and reviewer judgment.

Switch ifPrepare interview questionsUseful next step when this workflow needs a related hr and recruiters output or review pass.

Stop ifThe user cannot provide role outcomes, responsibilities, requirements, compensation range, and hiring process and would need ChatGPT to invent the important facts. The desired result is not a job description or cannot be shaped as copy options grouped by angle, audience, supporting detail, and revision note.

Not forUsers who want ChatGPT to invent facts, credentials, numbers, or personal details. Situations where the output needs final approval from a qualified human before it reaches a candidate, employee, hiring panel, or HR reviewer.

Before you use the answer, make the call

Who checks it: the teammate accountable for job description quality, role outcomes and required skills, and fairness and policy fit is the acceptance owner here because the final a job description has to preserve role outcomes, required skills, compensation clarity, and inclusive wording and the source trail.
Check before using: Inspect role outcomes, responsibilities, requirements, compensation range, and hiring process, the case note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", and any open support around the pasted notes, concrete examples, hard limits, and reviewer judgment; the answer should keep supplied notes, assumptions, and needs-checking points separate.
What this changes: The impact is practical: a visitor can compare the model output with the rough note, spot where the pasted notes, concrete examples, hard limits, and reviewer judgment is still open, and avoid handing a candidate, employee, hiring panel, or HR reviewer a polished guess.
Do next: The human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related. Then save only the repeatable fields, not the one-time case details, so the next run still asks for job description quality, role outcomes and required skills, and fairness and policy fit.
Before saving for reuse: Before reusing the answer, keep any search, traffic, ranking, or popularity claim out of the final asset unless someone can point to search performance tool evidence or other real search data after publishing for "chatgpt prompts for hr job description" and record where it came from.

Working case file: Write Job Descriptions working case for HR and Recruiters

The case starts before the polished answer, while the user still has mixed notes and a review risk. The user has enough material to start, but not enough to trust a smooth answer unless the prompt keeps role outcomes, responsibilities, requirements, compensation range, and hiring process, copy options grouped by angle, audience, supporting detail, and revision note, and a peer who checks job description quality, role outcomes and required skills, and fairness and policy fit in the same run.

Rough note

A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. The rough note says: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." The desired result is a job description for a candidate, employee, hiring panel, or HR reviewer.

Constraint to keep visible

The first pass must keep the pasted notes, concrete examples, hard limits, and reviewer judgment visible instead of smoothing it into a claim. Carry this rule into every section: keep the wording fair, job-related, and reviewed by the appropriate human.

What the user brought

The supplied case is "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", so the answer should begin from the user's actual wording and not from broad write job descriptions advice.

The finished a job description should point back to role outcomes, responsibilities, requirements, compensation range, and hiring process and show how role outcomes, required skills, compensation clarity, and inclusive wording changed the answer.

What is still missing

The model should ask for audience, channel, approval owner, and any support needed for the pasted notes, concrete examples, hard limits, and reviewer judgment before it treats the result as usable.

Missing inputs belong in a needs-checking line, not inside polished wording that a candidate, employee, hiring panel, or HR reviewer might treat as settled.

Who accepts the answer

a peer who checks job description quality, role outcomes and required skills, and fairness and policy fit should inspect job description quality, role outcomes and required skills, and fairness and policy fit, compare the answer with the rough note, and decide whether the output is ready, repairable, or too thin.

The page should leave a visible owner for the final check instead of implying that ChatGPT approval is enough.

What gets saved

The reusable version should keep variables for source notes, audience, reviewer, support need, stop rule, and role outcomes, required skills, compensation clarity, and inclusive wording.

One-time details should be removed only after the accepted answer proves that copy options grouped by angle, audience, supporting detail, and revision note works for this case.

Before copying

Can the user point to the exact role outcomes, responsibilities, requirements, compensation range, and hiring process ChatGPT is allowed to use?
Is role outcomes, required skills, compensation clarity, and inclusive wording visible before the prompt asks for a job description?
Has the user named the reviewer who checks job description quality, role outcomes and required skills, and fairness and policy fit?
Is there a stop rule for unsupported claims about the pasted notes, concrete examples, hard limits, and reviewer judgment?

Checks before sharing

Compare the first answer with "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and mark any section that invents context.
Check whether the output is shaped as copy options grouped by angle, audience, supporting detail, and revision note, not a general explanation.
Move uncertain claims into a needs-checking block before sharing the answer with a candidate, employee, hiring panel, or HR reviewer.
Save the pattern as job description prompt pattern with source notes, constraints, and review checklist only after private or one-time details become variables.

Run this case first

Use this case file before writing. Start from this rough note: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." Build a job description as copy options grouped by angle, audience, supporting detail, and revision note. Keep role outcomes, required skills, compensation clarity, and inclusive wording visible, separate supplied facts from assumptions, ask for missing support around the pasted notes, concrete examples, hard limits, and reviewer judgment, name a peer who checks job description quality, role outcomes and required skills, and fairness and policy fit as the checker, and stop before using any claim that the source notes do not support.

The handoff is useful only if a reviewer can see what came from the note, what still needs checking, and why the output shape fits. The accepted version should tell a candidate, employee, hiring panel, or HR reviewer what is ready, what needs checking, and which fields the next user must replace before rerunning the prompt.

Input triage before running ChatGPT

Which problem is most likely to break this write job descriptions run before a candidate, employee, hiring panel, or HR reviewer can use it?

Selected issue

Missing context

Build context

Symptom: Write Job Descriptions starts from a rough note like "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." but the audience, choice, or approval point is still implied.
Ask now: What does a candidate, employee, hiring panel, or HR reviewer already know, what source notes are available, and what must the final a job description decide?
Do next: Ask ChatGPT to list missing inputs before it writes a job description, then answer only the questions that change the final choice.
Prompt move: Before writing, ask me up to four questions needed to produce copy options grouped by angle, audience, supporting detail, and revision note; do not fill gaps with assumptions.
Stop if: Stop if the answer sounds polished but still cannot show the source notes behind role outcomes, required skills, compensation clarity, and inclusive wording.
Who checks it: a candidate, employee, hiring panel, or HR reviewer

Build context Readiness check

Notes to save before reusing this prompt

Sort the rough note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." before running write job descriptions in a public role post where vague wording can create screening risk. This note sheet tells ChatGPT what it may use, what it must label, and which part the teammate checking job description quality, role outcomes and required skills, and fairness and policy fit checks before a candidate, employee, hiring panel, or HR reviewer sees job description section map with outcome language. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.

Facts the prompt can safely use

Capture: Capture the concrete case first: A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. The note says "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and the requested asset is job description section map with outcome language. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.
Keep: Keep the facts that directly affect copy options grouped by angle, audience, supporting detail, and revision note, especially the audience, task focus, channel, and any details already present in role outcomes, responsibilities, requirements, compensation range, and hiring process.
Verify: Verify that every useful line in the answer can point back to the rough note or to role outcomes, responsibilities, requirements, compensation range, and hiring process.
Prompt direction: Tell ChatGPT to use only listed facts for the first pass and to put any extra idea in a needs-checking line.
Who checks it: the teammate checking job description quality, role outcomes and required skills, and fairness and policy fit checks whether the answer still reflects job description quality, role outcomes and required skills, and fairness and policy fit after the first pass.
If skipped: If this row is skipped, a job description can sound specific while drifting into generic write job descriptions advice.

Unknowns the model must not hide

Capture: List what the user did not provide but the answer may need: missing audience detail, missing support around the pasted notes, concrete examples, hard limits, and reviewer judgment, or an approval step for a candidate, employee, hiring panel, or HR reviewer.
Keep: Keep assumptions outside the usable sections until the user confirms them or chooses a safer fallback.
Verify: Check whether the answer names what is unknown before it recommends wording, order, or next steps.
Prompt direction: Ask ChatGPT to return a short assumption list before writing any final copy or checklist.
Who checks it: the teammate checking job description quality, role outcomes and required skills, and fairness and policy fit decides which assumptions are acceptable and which ones need another user answer.
If skipped: If assumptions are hidden, the answer may pass a style check while failing the real choice about role outcomes, required skills, compensation clarity, and inclusive wording.

Rules the answer must obey

Capture: Record the rule from this case: The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening. Also include keep the wording fair, job-related, and reviewed by the appropriate human and this field friction before the model writes: a role post can drift into vague requirements or unfair screening language. Job description failure sample: the role post sounds polished but uses vague requirements and hides the review point for fairness-sensitive language.
Keep: Keep the constraint near the requested format so it governs the whole copy options grouped by angle, audience, supporting detail, and revision note, not only the final paragraph.
Verify: Check whether the answer obeys the constraint even when it would be easier to produce a smoother or broader response.
Prompt direction: Tell ChatGPT to stop and ask before continuing if the constraint conflicts with the requested output.
Who checks it: the teammate checking job description quality, role outcomes and required skills, and fairness and policy fit checks the constraint before approving any handoff to a candidate, employee, hiring panel, or HR reviewer.
If skipped: If this row is skipped, the model may produce a fluent answer that the user cannot safely use.

Details to summarize before reuse

Capture: Mark names, private identifiers, account details, student or customer records, confidential strategy, and one-time case details before they enter the prompt.
Keep: Keep summaries that preserve meaning but remove details that should not travel into a reusable prompt.
Verify: Check whether the answer repeats private or one-time information that should have stayed outside the saved version.
Prompt direction: Ask ChatGPT to replace private details with role-safe descriptions and to flag anything it cannot safely generalize.
Who checks it: the teammate checking job description quality, role outcomes and required skills, and fairness and policy fit confirms that the final a job description can be shared in the intended channel.
If skipped: If this row is skipped, the page helps the user copy faster but may teach a bad reuse habit.

Reusable fields for the next run

Capture: Name the fields that should change next time: source notes, audience, output format, support needed for the pasted notes, concrete examples, hard limits, and reviewer judgment, reviewer, and stop rule.
Keep: Keep role outcomes, required skills, compensation clarity, and inclusive wording, job description quality, role outcomes and required skills, and fairness and policy fit, and job description section map with outcome language as required fields so the saved prompt does not collapse into a generic role prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.
Verify: Check whether the reusable version still asks for the facts that made this case work, instead of saving the finished wording alone.
Prompt direction: Tell ChatGPT to return a reusable prompt with variables and a reject-if rule after the human accepts the current answer.
Who checks it: the teammate checking job description quality, role outcomes and required skills, and fairness and policy fit signs off only when private details are removed and the next user can fill the variables without guessing.
If skipped: If this row is skipped, the user may save polished wording instead of a repeatable job description prompt pattern with source notes, constraints, and review checklist.

Copy these saved notes with the prompt only after the recruiter can point to the supplied facts, the uncertain parts, the hard limit, the reusable fields for role outcomes, required skills, compensation clarity, and inclusive wording, and the place where a role post can drift into vague requirements or unfair screening language. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible. Job description external support need: an independent HR or recruiting resource should cite the outcome-language and fairness-review workflow.

Iteration loop: run the prompt as a working thread

Write Job Descriptions needs a working thread with visible checkpoints between turns. Start from the rough note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", then ask ChatGPT to write, question, challenge, and hand off job description section map with outcome language without hiding the pasted notes, concrete examples, hard limits, and reviewer judgment. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.

Thread goal

Thread goal for recruiter: turn the rough case from A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. into copy options grouped by angle, audience, supporting detail, and revision note for a candidate, employee, hiring panel, or HR reviewer, while the person sending a job description to a candidate, employee, hiring panel, or HR reviewer can still inspect job description quality, role outcomes and required skills, and fairness and policy fit, role outcomes, required skills, compensation clarity, and inclusive wording, unsupported assumptions, and the friction that a role post can drift into vague requirements or unfair screening language. Job description failure sample: the role post sounds polished but uses vague requirements and hides the review point for fairness-sensitive language.

Write Job Descriptions should not be saved if the final answer cannot show where role outcomes, required skills, compensation clarity, and inclusive wording changed the result. The loop is stronger than a one-shot prompt because it makes the model show its first version, missing context, challenge, and reusable handoff before the recruiter treats job description section map with outcome language as finished. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.

1
First version
Use this first when the source note is messy but concrete enough to produce a reviewable a job description.
```
Write Job Descriptions first run: use the rough note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." from A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language.; build a job description as copy options grouped by angle, audience, supporting detail, and revision note; rely on supplied facts for the main answer, label assumptions, keep role outcomes, required skills, compensation clarity, and inclusive wording visible, and end with the support still needed for the pasted notes, concrete examples, hard limits, and reviewer judgment.
```
Keep
Keep the exact source note, the requested output shape, and any line that directly supports role outcomes, required skills, compensation clarity, and inclusive wording.
Accept if
Accept the first answer only if it separates source-backed details from assumptions and gives the person sending a job description to a candidate, employee, hiring panel, or HR reviewer something concrete to inspect.
Stop if
Stop if the answer invents missing context, treats the pasted notes, concrete examples, hard limits, and reviewer judgment as proven, or drifts into general write job descriptions advice.
2
Question pass
Use this after the first answer when the shape is useful but the model skipped questions that block real use.
```
Write Job Descriptions gap fill: compare the first answer with the rough note already in this thread; name the missing inputs that prevent a candidate, employee, hiring panel, or HR reviewer from using the result; ask up to five questions grouped by audience, source support, channel, reviewer, and reuse field, then say which part can continue with a safe fallback.
```
Keep
Keep any section that maps to role outcomes, responsibilities, requirements, compensation range, and hiring process; move guesses into open questions instead of deleting the whole answer.
Accept if
Accept this turn only if the missing questions would help a recruiter make a clearer choice before rerunning or revising.
Stop if
Stop if the model asks generic questions that do not affect copy options grouped by angle, audience, supporting detail, and revision note, job description quality, role outcomes and required skills, and fairness and policy fit, or the final handoff.
3
Risk pass
Use this before sharing the answer, especially when it sounds polished enough to hide weak evidence.
```
Write Job Descriptions skeptic pass: compare the current answer with the rough note already in this thread; mark unsupported claims, unclear owners, privacy issues, and weak spots around the pasted notes, concrete examples, hard limits, and reviewer judgment; give each issue a repair sentence that keeps role outcomes, required skills, compensation clarity, and inclusive wording visible without adding new facts.
```
Keep
Keep the usable structure from the first answer, but require every claim and recommendation to survive the skeptic pass.
Accept if
Accept this turn only if it gives repair instructions that the person sending a job description to a candidate, employee, hiring panel, or HR reviewer can apply without rewriting the whole asset from scratch.
Stop if
Stop if the critique only says the answer is good or bad without naming the exact line, risk, and repair move.
4
Reusable version
Use this after the answer survives the gap fill and skeptic pass and is ready to become a working asset.
```
Write Job Descriptions handoff: prepare the accepted a job description, a needs-checking block for the pasted notes, concrete examples, hard limits, and reviewer judgment, a reviewer note for the person sending a job description to a candidate, employee, hiring panel, or HR reviewer, and a reusable version with variables for source notes, audience, output format, support need, stop rule, and role outcomes, required skills, compensation clarity, and inclusive wording; remove one-time private details before saving.
```
Keep
Keep the accepted wording, the repair choices, and the variables that make job description prompt pattern with source notes, constraints, and review checklist safe to rerun.
Accept if
Accept the handoff only if a candidate, employee, hiring panel, or HR reviewer can tell what is ready, what needs review, and what must be replaced next time.
Stop if
Stop if the final version saves polished case details instead of a reusable prompt structure with visible boundaries.

Prompt readiness check before you copy

Use this quick pass to decide whether to collect more context, build a context pack, or run the prompt and grade the answer.

0/6 ready

Source notes readyNeed responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.Audience or recipient knownHR and Recruiters who have real notes or context and need a structured first version of a job description.Constraints and no-go rules clearPrompts must support fair review and human judgment, not automated employment choices. Ask ChatGPT to label assumptions and verification needs before using a job description.Facts to verify listedJob Description source sort: which lines in the rough note are facts, preferences, constraints, or open questions? Job Description blank rule: what should stay blank or flagged if the pasted notes, concrete examples, hard limits, and reviewer judgment is missing?Checker is namedThe final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.Reuse rule clearSave the job description answer only when private details are removed, one-time facts become variables, rewrite vague requirements as observable outcomes and mark anything needing HR review, and the review rule for role outcomes, required skills, compensation clarity, and inclusive wording still appears in the reusable prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.

Do next

Collect context first

The prompt can run, but the answer will likely fill gaps with assumptions. Start by collecting notes, constraints, and the person who will check it.

Use this prompt when: HR and Recruiters who have real notes or context and need a structured first version of a job description.
Wait if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Who checks it: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.
Reuse rule: Save the job description answer only when private details are removed, one-time facts become variables, rewrite vague requirements as observable outcomes and mark anything needing HR review, and the review rule for role outcomes, required skills, compensation clarity, and inclusive wording still appears in the reusable prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.

Collect context Open prompt Context pack Output grader

Session handoff: finish the run without losing the thread

Track the four steps that turn a copied prompt into a usable work session.

0/4 steps

Context readyBuild a context pack before copying anything.Open stepPrompt runRun the recommended prompt with the prepared context.Open stepAnswer checkedGrade the answer against the task checks and repair weak sections.Open stepReuse choiceDecide whether to save the run, rerun it, or discard it.Open step

Next action

Collect working context

Start by getting source notes, constraints, the person who checks it, and the stop rule into one place.

Working note: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Who checks it: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.
Stop rule: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
Reuse choice: Save the job description answer only when private details are removed, one-time facts become variables, rewrite vague requirements as observable outcomes and mark anything needing HR review, and the review rule for role outcomes, required skills, compensation clarity, and inclusive wording still appears in the reusable prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.

Open next step Prompt Context Grade

Work note: what the rough note changes

Use this when the answer must carry the original note, the missing context, and the review check into the final prompt run.

Original working note

For job description, the source note starts plainly: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." is the rough request. The ready check for job description is simple: the practical output is a job description with role outcomes, required skills, compensation clarity, and inclusive wording, checker ownership, and this boundary still visible: keep the wording fair, job-related, and reviewed by the appropriate human.

Received note: Received note for HR and Recruiters Write Job Descriptions: "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." arrives as the source note inside a public role post where vague wording can create screening risk, with The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening. as the first human concern and job description section map with outcome language as the target artifact.
Question before run: Before copying, ask what a candidate, employee, hiring panel, or HR reviewer must be able to decide from this a job description, and which source detail would change that choice.
First answer flaw: First answer flaw for HR and Recruiters Write Job Descriptions: the first answer can look useful but merge facts, assumptions, and missing details, making a job description hard for a teammate who can check job description quality, role outcomes and required skills, and fairness and policy fit to verify.
Human edit: Human edit for HR and Recruiters Write Job Descriptions: move unsupported claims into a check-needed line, keep role outcomes, required skills, compensation clarity, and inclusive wording in the first section, and make copy options grouped by angle, audience, supporting detail, and revision note readable for a candidate, employee, hiring panel, or HR reviewer; the editor also has to rewrite vague requirements as observable outcomes and mark anything needing HR review; the edit has to preserve "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and leave job description section map with outcome language ready for a reviewer, not just prettier.
Reusable field: Reusable field for HR and Recruiters Write Job Descriptions: keep the reusable version as job description prompt pattern with source notes, constraints, and review checklist only after the note becomes variables, the reviewer stays named, and the pasted notes, concrete examples, hard limits, and reviewer judgment has a visible checking slot. Keep the field set alert to this repeat risk: a role post can drift into vague requirements or unfair screening language.

Questions before reuse

Job Description source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Job Description blank rule: what should stay blank or flagged if the pasted notes, concrete examples, hard limits, and reviewer judgment is missing?
Job Description reviewer stop: which section should a peer who knows job description quality, role outcomes and required skills, and fairness and policy fit inspect before anyone uses the answer?

Who checks it

Job Description source note: treat "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." as the factual base, not decorative background; the next usable asset is job description section map with outcome language.
Job Description evidence check: mark any section where the pasted notes, concrete examples, hard limits, and reviewer judgment is assumed instead of shown, especially when a role post can drift into vague requirements or unfair screening language.
Job Description scope check: keep the answer on role outcomes, required skills, compensation clarity, and inclusive wording; do not drift away from a public role post where vague wording can create screening risk.
Job Description final polish: rewrite final wording only after job description quality, role outcomes and required skills, and fairness and policy fit is clear enough for a peer who knows job description quality, role outcomes and required skills, and fairness and policy fit, then rewrite vague requirements as observable outcomes and mark anything needing HR review.
Job Description freshness rule: Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.

Usable output

The target job description result should return a job description with field labels, short bullets, and a use-or-revise note; keep source-backed lines, guesses, and open questions in different lanes, attach the checker to the risky line before anyone reuses it, prepare job description section map with outcome language, and make the final pass check job description quality, role outcomes and required skills, and fairness and policy fit.

Save this noteRough note that changes the prompt: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. Task-specific source material: role outcomes, responsibilities, requirements, compensation range, and hiring process Human check to keep visible: job description quality, role outcomes and required skills, and fairness and policy fit

Stop hereHold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Save for reuseSave the job description answer only when private details are removed, one-time facts become variables, rewrite vague requirements as observable outcomes and mark anything needing HR review, and the review rule for role outcomes, required skills, compensation clarity, and inclusive wording still appears in the reusable prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.

Build context pack Check output Open work sample

Prompt run from pasted notes

Use this pass to see what should happen between the rough note and the answer that is safe enough to review.

Pasted notes

recruiter starts this job description work run from: A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. The source says "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." The answer needs to become job description section map with outcome language for a candidate, employee, hiring panel, or HR reviewer; the run lives in a public role post where vague wording can create screening risk and has to respect this rule before any wording polish: The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening.

Why this input is messy

Clean up the job description work note first because the note carries facts, preferences, limits, and open approval points in one line; a quick answer can smooth over the pasted notes, concrete examples, hard limits, and reviewer judgment, miss role outcomes, required skills, compensation clarity, and inclusive wording, or make a job description look ready before a peer who knows job description quality, role outcomes and required skills, and fairness and policy fit checks it, especially when a role post can drift into vague requirements or unfair screening language.

First prompt move

Open this job description work run by telling ChatGPT to tell ChatGPT to convert the rough note into named fields first, then pause if the audience, checker, or support for the pasted notes, concrete examples, hard limits, and reviewer judgment is missing; this is a context pass before polish because copy options grouped by angle, audience, supporting detail, and revision note has to stay traceable to the original note.

Questions ChatGPT should ask

Reader detail in job description work: who will read this a job description, and what do they already know?
Source detail in job description work: which note details are verified facts, and which parts still need the pasted notes, concrete examples, hard limits, and reviewer judgment?
Constraint detail in job description work: what tone, length, channel, or approval rule matters before the answer reaches a candidate, employee, hiring panel, or HR reviewer?
Reuse detail in job description work: which person will inspect job description quality, role outcomes and required skills, and fairness and policy fit, and what would make the answer unsafe to reuse?

Usable answer shape

The job description work result should return copy options grouped by angle, audience, supporting detail, and revision note, separate source-backed sections from assumptions and open questions, show how role outcomes, required skills, compensation clarity, and inclusive wording shaped the result, name a peer who knows job description quality, role outcomes and required skills, and fairness and policy fit, and end with a short check for job description quality, role outcomes and required skills, and fairness and policy fit before the answer is shared or saved.

Human revision

HR and Recruiters final edit for job description work should keep the useful source-backed sections, rewrite vague requirements as observable outcomes and mark anything needing HR review, turn private names and temporary facts into variables, and make the saved wording fit a candidate, employee, hiring panel, or HR reviewer; read it beside "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and keep the closing version aligned with this standard: the human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related.

Save or discard

Keep or rerun job description work based on whether the note, output shape, checker, job description section map with outcome language, and reuse rule stay visible; rerun or discard the answer when it could fit another recruiter task without changing the source notes, or when the pasted notes, concrete examples, hard limits, and reviewer judgment is implied but not checkable.

Run prompt Grade answer Repair answer

Choose the right workflow for this job

Work moment

Use this workflow when role outcomes, responsibilities, requirements, compensation range, and hiring process is present and the answer has to survive a check for the pasted notes, concrete examples, hard limits, and reviewer judgment.

Why this workflow

Do first

Bring the exact source notes and mark what the model must not invent, especially anything tied to the pasted notes, concrete examples, hard limits, and reviewer judgment.

Next best workflow

Prepare interview questionsUseful next step when this workflow needs a related hr and recruiters output or review pass.

What to look for

Rough note that changes the prompt: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
Task-specific source material: role outcomes, responsibilities, requirements, compensation range, and hiring process
Human check to keep visible: job description quality, role outcomes and required skills, and fairness and policy fit
Evidence pressure point: the pasted notes, concrete examples, hard limits, and reviewer judgment

Wrong page if

The user cannot provide role outcomes, responsibilities, requirements, compensation range, and hiring process and would need ChatGPT to invent the important facts.
The desired result is not a job description or cannot be shaped as copy options grouped by angle, audience, supporting detail, and revision note.
The task would be safer on Prepare interview questions because the main choice is closer to that workflow.

When workflows look similar

Use this when the page looks close, but the thing you need to make or the person checking it is different.

Prepare interview questions: Use this workflow
Stay with ChatGPT Prompts for HR and Recruiters to Write Job Descriptions when your notes already include this check: Task-specific source material: role outcomes, responsibilities, requirements, compensation range, and hiring process.; Switch instead
Switch to Prepare interview questions when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related hr and recruiters output or review pass.; Keep separate
Keep the pages separate if The user cannot provide role outcomes, responsibilities, requirements, compensation range, and hiring process and would need ChatGPT to invent the important facts.
Build interview scorecards: Use this workflow
Stay with ChatGPT Prompts for HR and Recruiters to Write Job Descriptions when your notes already include this check: Human check to keep visible: job description quality, role outcomes and required skills, and fairness and policy fit.; Switch instead
Switch to Build interview scorecards when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related hr and recruiters output or review pass.; Keep separate
Keep the pages separate if The desired result is not a job description or cannot be shaped as copy options grouped by angle, audience, supporting detail, and revision note.
Plan onboarding: Use this workflow
Stay with ChatGPT Prompts for HR and Recruiters to Write Job Descriptions when your notes already include this check: Evidence pressure point: the pasted notes, concrete examples, hard limits, and reviewer judgment.; Switch instead
Switch to Plan onboarding when the thing you need to make or the person checking it matches that workflow: Useful next step when this workflow needs a related hr and recruiters output or review pass.; Keep separate
Keep the pages separate if The task would be safer on Prepare interview questions because the main choice is closer to that workflow.

Run the page by work state

Begin with the messy notes, then choose the prompt path that matches the current state of the work.

Build The Asset

Use this when the notes are ready and the next useful output is copy options grouped by angle, audience, supporting detail, and revision note, not more brainstorming.

Open section

Do now: Copy the recommended prompt, replace the variables, and ask for a job description with assumptions separated from source-backed details.
Bring: Bring the task focus: role outcomes, required skills, compensation clarity, and inclusive wording. Add the channel, deadline, and any required sections.
Stop if: Stop if the first answer gives broad advice instead of a concrete a job description.
Next check: Use the run sheet's review mode before sharing anything with a candidate, employee, hiring panel, or HR reviewer.

Bring this

Bring role outcomes, responsibilities, requirements, compensation range, and hiring process; add the reviewer, the audience, and the boundary from this case: The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening.

Reusable handoff

The final pass should leave a job description ready for a candidate, employee, hiring panel, or HR reviewer, with the uncertain parts marked instead of smoothed over.

Reality checks

Does the page-specific note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." change the prompt, or could this still fit another task unchanged?
Can the reviewer check job description quality, role outcomes and required skills, and fairness and policy fit without asking ChatGPT to invent missing facts?
Does the answer become a job description, or does it stay at broad job description work advice?
Would a candidate, employee, hiring panel, or HR reviewer know what was provided, what was assumed, and what still needs review?

Prompt path by where the work is stuck

advanced

Write job descriptions for recruiter Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a job description.

Use this when: Use before asking ChatGPT for job description work so the model has enough task-specific context.
When this fits: Turn role outcomes, responsibilities, requirements, compensation range, and hiring process into a job description for a candidate, employee, hiring panel, or HR reviewer.
Do next: Scan the answer before asking for a rewrite and check whether the answer shows enough context for the pasted notes, concrete examples, hard limits, and reviewer judgment.

Open this prompt card

Context pack before copying

0/8

Source notes are availableAudience or recipient is namedConstraints are explicitFacts to verify are listedChecker is named

Working notesConstraintsWho checks it

Ready to paste

Context brief for the next prompt

Context pack for HR and Recruiters to Write Job Descriptions

Goal: Find a copyable prompt workbench that helps hr and recruiters with job description work, using the right source material, review lens, example, and follow-up prompts.
Working scenario: A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. The job description work happens inside a public role post where vague wording can create screening risk. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible. For job description work, that context changes the prompt: it needs concrete inputs, a realistic output shape, and a stopping point for human judgment.

What I know:
Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.

Constraints and no-go rules:
Prompts must support fair review and human judgment, not automated employment choices. Ask ChatGPT to label assumptions and verification needs before using a job description. Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.

Who checks it:
The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.

Readiness checks:
- [ ] Source notes are available
- [ ] Audience or recipient is named
- [ ] Constraints are explicit
- [ ] Facts to verify are listed
- [ ] Checker is named

Ask ChatGPT to request missing context before writing. Keep assumptions separate from source-based claims.

Ask first

Questions to ask before the next run

5 questions

What source note should the answer use for HR and Recruiters to Write Job Descriptions?
Who will read or use the final answer?
Which limits must stay visible, especially prompts must support fair review and human judgment, not automated employment choices.?
Which facts should be checked before accepting the answer for ChatGPT Prompts for HR and Recruiters to Write Job Descriptions?
Who should check the answer before it is reused: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.?

Output grader before reuse

0/5

Paste ChatGPT output

0 words checked against The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process.

Source review, write job descriptions: the answer uses the supplied role outcomes, responsibilities, requirements, compensation range, and hiring process and does not fill missing facts with confident guesses.Output shape, write job descriptions: the result clearly becomes a job description, not broad advice about the task.Handoff clarity, write job descriptions: the answer names missing inputs and the next human check for job description quality, role outcomes and required skills, and fairness and policy fit.Audience fit, write job descriptions: the result works for a candidate, employee, hiring panel, or HR reviewer, including channel, tone, length, and choice context.Risk boundary, write job descriptions: the final version respects keep the wording fair, job-related, and reviewed by the appropriate human.

Needs another review pass

a job description final pass: keep the useful structure, then rewrite vague requirements as observable outcomes and mark anything needing HR review; readiness means a candidate, employee, hiring panel, or HR reviewer can see what was provided, what was assumed, why a role post can drift into vague requirements or unfair screening language, and what still needs review.

Task-specific output diagnosis

Paste the first Write Job Descriptions answer and compare it with "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." before checking style. A useful recruiter output must prove it belongs to this page by keeping role outcomes, required skills, compensation clarity, and inclusive wording, copy options grouped by angle, audience, supporting detail, and revision note, and the task reviewer visible.

Pass when

The answer uses "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." as the controlling case, not as decoration, and turns it into copy options grouped by angle, audience, supporting detail, and revision note with role outcomes, required skills, compensation clarity, and inclusive wording still visible.
The answer shows which lines come from "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and which lines remain assumptions before a candidate, employee, hiring panel, or HR reviewer sees the job description.
The answer gives the task reviewer a clear check tied to "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", especially the point where the pasted notes, concrete examples, hard limits, and reviewer judgment cannot be treated as proven.
The answer can become job description prompt pattern with source notes, constraints, and review checklist only after the one-time facts in "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." are replaced with variables and the stop rule stays attached.

False pass

It sounds polished but never quotes or preserves the specific case in "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.", so the write job descriptions output could fit another page.
It gives a generic next step while hiding role outcomes, required skills, compensation clarity, and inclusive wording, which makes the answer feel useful before it can support the real a job description.
It skips the task reviewer or buries the review check, so the user cannot tell who should approve the answer before reuse.
It could fit a neighboring workflow because the response hides copy options grouped by angle, audience, supporting detail, and revision note, the pasted notes, concrete examples, hard limits, and reviewer judgment, or the source material that makes this write job descriptions page different.

Repair next

Rewrite the opening around "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and keep the first sentence tied to role outcomes, required skills, compensation clarity, and inclusive wording before improving tone or length.
Add a needs-checking block for the pasted notes, concrete examples, hard limits, and reviewer judgment, then separate supplied facts from assumptions before returning copy options grouped by angle, audience, supporting detail, and revision note.
Mark the line the task reviewer must inspect for job description quality, role outcomes and required skills, and fairness and policy fit, and move unsupported claims out of the usable answer.
Replace one-time details with variables for the saved job description prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the write job descriptions check.

Red flags

Evidence issue, write job descriptions: the answer invents or overstates the pasted notes, concrete examples, hard limits, and reviewer judgment.
Task drift, write job descriptions: it ignores role outcomes, required skills, compensation clarity, and inclusive wording and moves into a neighboring workflow.
Readiness gap, write job descriptions: it sounds complete while leaving job description quality, role outcomes and required skills, and fairness and policy fit impossible to verify.
Privacy issue, write job descriptions: it includes details that should have been summarized or removed.
Generic output, write job descriptions: it produces a broad template that could fit any task in the role.

Choose the next pass

Pick what happens to this answer before it becomes a saved version.

Repair

Issue note

Repair next

Run a narrower pass against the failed line, the source note, and the task-specific stop rule.

Rewrite the opening around "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and keep the first sentence tied to role outcomes, required skills, compensation clarity, and inclusive wording before improving tone or length.
Add a needs-checking block for the pasted notes, concrete examples, hard limits, and reviewer judgment, then separate supplied facts from assumptions before returning copy options grouped by angle, audience, supporting detail, and revision note.

Repair pass

Output next pass for: Write Job Descriptions: use the public role post where vague wording context
Next pass: Repair
Why: Run a narrower pass against the failed line, the source note, and the task-specific stop rule.
Checked items: 0/5
Issue note: Add the failed line or remaining risk before copying this pass.

Source task:
Find a copyable prompt workbench that helps hr and recruiters with job description work, using the right source material, review lens, example, and follow-up prompts.

Repair moves:
- Rewrite the opening around "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and keep the first sentence tied to role outcomes, required skills, compensation clarity, and inclusive wording before improving tone or length.
- Add a needs-checking block for the pasted notes, concrete examples, hard limits, and reviewer judgment, then separate supplied facts from assumptions before returning copy options grouped by angle, audience, supporting detail, and revision note.
- Mark the line the task reviewer must inspect for job description quality, role outcomes and required skills, and fairness and policy fit, and move unsupported claims out of the usable answer.
- Replace one-time details with variables for the saved job description prompt pattern with source notes, constraints, and review checklist, then rerun only the section that failed the write job descriptions check.

Keep if repaired:
- The answer uses "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." as the controlling case, not as decoration, and turns it into copy options grouped by angle, audience, supporting detail, and revision note with role outcomes, required skills, compensation clarity, and inclusive wording still visible.
- The answer shows which lines come from "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." and which lines remain assumptions before a candidate, employee, hiring panel, or HR reviewer sees the job description.

Answer being graded:
Paste the ChatGPT answer above before copying this pass.

Return the smallest revised answer, the line a person must check, and whether this should be accepted, repaired again, or rejected.

Answer repair for replies that sound right but are not ready

Weak answer pattern

The first HR and Recruiters Write Job Descriptions pass copies a line like "I turned the notes into a clean version with the key points, a simple structure, and a recommended action" and then moves on. Write Job Descriptions failure to avoid for recruiter: it treats the task as generic advice instead of a case with constraints; the actual note to protect is Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.

Why it fails

Write Job Descriptions repair note: the response has a tidy shape, yet the useful parts cannot be traced back to the rough note Put role outcomes, required skills, compensation clarity, and inclusive wording back where the reviewer can see it; mark every section that still needs the pasted notes, concrete examples, hard limits, and reviewer judgment, name a peer who can check job description quality, role outcomes and required skills, and fairness and policy fit before sharing with a candidate, employee, hiring panel, or HR reviewer, and address the real working constraint: a role post can drift into vague requirements or unfair screening language.

Trace the rough note

Problem: The answer mentions a job description but does not reflect the concrete case: A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language.
Repair: Rewrite the first section around the user note, then mark which details came from the note, which details still need confirmation, and where job description section map with outcome language changes the output.

Name the reviewer

Problem: The answer can move forward without anyone checking job description quality, role outcomes and required skills, and fairness and policy fit.
Repair: Add a reviewer line for a peer who can check job description quality, role outcomes and required skills, and fairness and policy fit, plus one question that must be answered before the result is shared.

Protect the evidence

Problem: The answer can imply the pasted notes, concrete examples, hard limits, and reviewer judgment even when the source notes do not support it.
Repair: Keep unsupported claims in a separate needs-checking block and remove any claim the user cannot verify.

Keep the task narrow

Problem: The response can drift from write job descriptions into broad advice that does not produce copy options grouped by angle, audience, supporting detail, and revision note.
Repair: Force the final answer back into copy options grouped by angle, audience, supporting detail, and revision note, keep role outcomes, required skills, compensation clarity, and inclusive wording as the main choice point, and rewrite vague requirements as observable outcomes and mark anything needing HR review.

Human-edited direction

Human Write Job Descriptions revision for HR and Recruiters: start with the actual case, name the audience, return copy options grouped by angle, audience, supporting detail, and revision note, keep supplied notes, assumptions, and missing checks separate, then rewrite vague requirements as observable outcomes and mark anything needing HR review, tell a candidate, employee, hiring panel, or HR reviewer what is ready to use, what a peer who can check job description quality, role outcomes and required skills, and fairness and policy fit must verify, and how the answer becomes job description prompt pattern with source notes, constraints, and review checklist without private or one-time details.

Rerun prompt

Rerun HR and Recruiters Write Job Descriptions: repair this write job descriptions answer, keep the result focused on role outcomes, required skills, compensation clarity, and inclusive wording, return copy options grouped by angle, audience, supporting detail, and revision note, put unsupported claims about the pasted notes, concrete examples, hard limits, and reviewer judgment in a needs-checking block, name the reviewer as a peer who can check job description quality, role outcomes and required skills, and fairness and policy fit, protect this boundary "keep the wording fair, job-related, and reviewed by the appropriate human", and use only these source notes: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.

Accept when

The answer visibly uses the rough note instead of generic write job descriptions advice.
The result is shaped as copy options grouped by angle, audience, supporting detail, and revision note and can be checked by a peer who can check job description quality, role outcomes and required skills, and fairness and policy fit.
Any uncertain point about the pasted notes, concrete examples, hard limits, and reviewer judgment is separated from the usable parts.
The reusable version keeps role outcomes, required skills, compensation clarity, and inclusive wording and removes one-time or private details.

Reject when

The answer could fit another recruiter task without changing more than the title.
The response sounds polished but cannot show where the key claims came from.
The result skips job description quality, role outcomes and required skills, and fairness and policy fit or hides who should approve it.
The answer asks the user to trust the model instead of checking the source notes.

Start from the user's actual notes

Reader situation

HR users need a role description that is clear, fair, outcome-based, and ready for human policy review. This page is for recruiters job description work when a role post can drift into vague requirements or unfair screening language. Job description search results edge: this page should win only if it separates outcomes, requirements, fairness checks, and approval ownership. Job description external support need: an independent HR or recruiting resource should cite the outcome-language and fairness-review workflow. Job description work for recruiter needs its own page because the page earns its keep when the searcher leaves with a sourced a job description path and a clear check for job description quality, role outcomes and required skills, and fairness and policy fit.

Concrete scenario

A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. The job description work happens inside a public role post where vague wording can create screening risk. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible. For job description work, that context changes the prompt: it needs concrete inputs, a realistic output shape, and a stopping point for human judgment.

Real user input

Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.

Editor take

The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening. In this job description review, the edit is to rewrite vague requirements as observable outcomes and mark anything needing HR review. Job description failure sample: the role post sounds polished but uses vague requirements and hides the review point for fairness-sensitive language. In the job description work review, a stronger page shows the difference between usable constraints and decorative detail, especially around the pasted notes, concrete examples, hard limits, and reviewer judgment; compare the answer with the actual notes before reuse.

Human polish

The human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible. Before handing off the job description, a careful final pass keeps the parts that save time, then rewrites anything that overstates evidence or misses the audience. Keep a short record of what changed before reuse. Recheck the hiring scope, salary or location policy, and approval owner before publishing role language.

Fast use path

Main card for a job description: start with the recommended prompt, then open other variations only if the first answer exposes a gap.
Source material for a job description: replace [source_material] with role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience details for a job description: name the person who will use the result and the one limit the answer must respect.
Review pass for a job description: use the review card to check job description quality, role outcomes and required skills, and fairness and policy fit before sharing the result.

Specificity signals

A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language.
Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
role outcomes, responsibilities, requirements, compensation range, and hiring process
role outcomes, required skills, compensation clarity, and inclusive wording
the pasted notes, concrete examples, hard limits, and reviewer judgment
keep the wording fair, job-related, and reviewed by the appropriate human
job description section map with outcome language
a role post can drift into vague requirements or unfair screening language
rewrite vague requirements as observable outcomes and mark anything needing HR review
a public role post where vague wording can create screening risk
Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.
Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.
Job description search results edge: this page should win only if it separates outcomes, requirements, fairness checks, and approval ownership.
Job description failure sample: the role post sounds polished but uses vague requirements and hides the review point for fairness-sensitive language.
Job description external support need: an independent HR or recruiting resource should cite the outcome-language and fairness-review workflow.

Real use sample: how the messy note changes the prompt

Messy brief

Ask before copying

Job Description source sort: which lines in the rough note are facts, preferences, constraints, or open questions?
Job Description blank rule: what should stay blank or flagged if the pasted notes, concrete examples, hard limits, and reviewer judgment is missing?
Job Description reviewer stop: which section should a peer who knows job description quality, role outcomes and required skills, and fairness and policy fit inspect before anyone uses the answer?
Job Description stop signal: which visible mistake would stop the team from using the answer?

Checks before sharing

Job Description source note: treat "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check." as the factual base, not decorative background; the next usable asset is job description section map with outcome language.
Job Description evidence check: mark any section where the pasted notes, concrete examples, hard limits, and reviewer judgment is assumed instead of shown, especially when a role post can drift into vague requirements or unfair screening language.
Job Description scope check: keep the answer on role outcomes, required skills, compensation clarity, and inclusive wording; do not drift away from a public role post where vague wording can create screening risk.
Job Description final polish: rewrite final wording only after job description quality, role outcomes and required skills, and fairness and policy fit is clear enough for a peer who knows job description quality, role outcomes and required skills, and fairness and policy fit, then rewrite vague requirements as observable outcomes and mark anything needing HR review.
Job Description freshness rule: Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.
Job Description failure pattern: Job description failure sample: the role post sounds polished but uses vague requirements and hides the review point for fairness-sensitive language.
Job Description choice owner: Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.

Before and after

Weak answer risk: The job description failure mode is practical: the answer sounds complete while turning "need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check;" into broad advice, hiding missing context around the pasted notes, concrete examples, hard limits, and reviewer judgment, and leaving a candidate, employee, hiring panel, or HR reviewer without a clear choice path because a role post can drift into vague requirements or unfair screening language. Job description failure sample: the role post sounds polished but uses vague requirements and hides the review point for fairness-sensitive language.
Improved outcome: The target job description result should return a job description with field labels, short bullets, and a use-or-revise note; keep source-backed lines, guesses, and open questions in different lanes, attach the checker to the risky line before anyone reuses it, prepare job description section map with outcome language, and make the final pass check job description quality, role outcomes and required skills, and fairness and policy fit.
Why it feels real: The job description case feels specific because: it starts from messy source notes, a public role post where vague wording can create screening risk, a named review moment, and task-level evidence instead of a clean prompt sentence. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.

When to save this version

Save the job description answer only when private details are removed, one-time facts become variables, rewrite vague requirements as observable outcomes and mark anything needing HR review, and the review rule for role outcomes, required skills, compensation clarity, and inclusive wording still appears in the reusable prompt. Approval for hr job description belongs with the accountable reviewer before the answer reaches a candidate, employee, hiring panel, or HR reviewer; keep the job description section map with outcome language review standard visible.

The job this page helps finish

For recruiters, the query means the prompt must preserve role outcomes, required skills, compensation clarity, and inclusive wording and make missing support visible. It should keep the pasted notes, concrete examples, hard limits, and reviewer judgment out in the open instead of burying it in polished copy. The grading step should catch any answer that skips role outcomes, required skills, compensation clarity, and inclusive wording.

Use Cases

Turn role outcomes, responsibilities, requirements, compensation range, and hiring process into a job description for a candidate, employee, hiring panel, or HR reviewer.
Review an existing job description work answer for job description checkpoint, missing details, and unsupported claims.
Create a repeatable job description prompt pattern with source notes, constraints, and review checklist so the next version starts from stronger context.
Make role outcomes, required skills, compensation clarity, and inclusive wording visible so the answer stays tied to a job description instead of drifting into a neighboring task.
Condense a long ChatGPT answer into copy options grouped by angle, audience, supporting detail, and revision note without losing the choices the human must make.

Input Prep

Write the audience or recipient in one sentence, including what they already know.
Paste or summarize role outcomes, responsibilities, requirements, compensation range, and hiring process; do not ask the model to guess it.
Name the final choice the job description work output must support.
Add constraints such as tone, length, required sections, privacy limits, and forbidden claims.
List the facts that must be checked after ChatGPT answers, especially the pasted notes, concrete examples, hard limits, and reviewer judgment.
Add the task-specific focus: role outcomes, required skills, compensation clarity, and inclusive wording.

Check the answer against real references

What users are trying to finish

The search page should answer the immediate job: how to ask ChatGPT for a job description and how to decide if the answer passes. The page should make it clear when the user has enough context to run the prompt and when more source material is required. Searchers should not have to infer the workflow; the page should make role outcomes, responsibilities, requirements, compensation range, and hiring process, a job description, and job description quality, role outcomes and required skills, and fairness and policy fit explicit.

Why the workflow matters

It covers the user journey from selection to handoff, including source prep, prompt variables, review ownership, and related workflows. The page is also internally connected, so users can move to adjacent workflows without starting from a vague role hub.

External references

Google Search Central people-first content guidanceUsed as the search-quality yardstick because this page must solve a real user task and make the pasted notes, concrete examples, hard limits, and reviewer judgment reviewable.
Google Search Central SEO Starter GuideUsed to keep titles, descriptions, links, and page structure focused on helping search engines and users understand a job description.
OpenAI ChatGPT business overviewUsed for work-related prompt boundaries where AI output should support productivity while staying subject to human review.
EEOC prohibited employment policies and practicesUsed for HR prompts where job descriptions, interview questions, scorecards, and employee communications need fair employment review.
NIST AI Risk Management FrameworkUsed as the second HR-risk reference so a job description keeps evidence, fairness review, and human approval visible.

Related ways people ask for this task

Question covered: chatgpt prompts for hr job description

What the reader wants: copy prompt workflow with template and review intent

Leave out popularity or ranking numbers until you can point to real search data after publishing.

Related ways people ask for this task

job description chatgpt prompt for hr
best chatgpt prompts for job description
job description prompt template for hr
copyable job description chatgpt prompt
job description ai prompt with review checklist
chatgpt job description workflow prompt

What to compare before using this prompt

Check whether ranking pages answer the task directly or only list broad prompts for hr and recruiters.
Compare whether competitors show a filled example for a job description and not just a blank prompt.
Look for missing-source risks around the pasted notes, concrete examples, hard limits, and reviewer judgment, especially claims that need manual checking.
Verify whether the search results favors a role hub, a task page, a template page, or a tool-like prompt builder.
Confirm no volume, ranking, CPC, or difficulty number is used unless it comes from a live keyword tool export.

Why this page should match the search

For "chatgpt prompts for hr job description", this page should win only if the reader can turn role outcomes, responsibilities, requirements, compensation range, and hiring process into copy options grouped by angle, audience, supporting detail, and revision note and still know who checks job description.

Compare against

A broad hr prompt collection that gives short examples without a worked job description section map with outcome language.
A role guide that explains hr and recruiters work but does not turn role outcomes, responsibilities, requirements, compensation range, and hiring process into copy options grouped by angle, audience, supporting detail, and revision note.
A prompt generator page that creates wording but leaves the job description check to the user.
A task article that teaches write job descriptions but does not give a copyable run with a check step.

This page is stronger when

It starts from role outcomes, responsibilities, requirements, compensation range, and hiring process, then shapes the answer into copy options grouped by angle, audience, supporting detail, and revision note instead of asking the reader to invent context.
It keeps the job description check visible, so a smooth answer is not treated as ready before a person checks it.
It shows a weak-answer repair path for a role post can drift into vague requirements or unfair screening language, which is the common failure a short example misses.
It links to nearby workflows when the user really needs a different output, owner, or source note.

Outside references to open

Open the official helpful-content guidance when you need to check whether the page is solving a real user task.
Open the role-specific outside reference when hr and recruiters work needs policy, education, hiring, sales, marketing, developer, or operations context.
Keep source links beside the prompt output when the pasted notes, concrete examples, hard limits, and reviewer judgment could change whether the answer is usable.

Improve the page when

Current search results mostly reward a different page type, such as a tool, forum thread, video, or role hub.
The top results answer a sharper question than "chatgpt prompts for hr job description" and this page does not yet answer that wording.
Readers cannot see job description section map with outcome language before they reach a long section of explanation.
The page starts getting visits for this topic but users would still need another page to check job description.

Check the answer before you reuse it

Who checks it

Real-world case

a job description scenario: this task feels human when the page handles the moment where hr and recruiters provide role outcomes, responsibilities, requirements, compensation range, and hiring process, need copy options grouped by angle, audience, supporting detail, and revision note, and must keep role outcomes, required skills, compensation clarity, and inclusive wording visible while checking the pasted notes, concrete examples, hard limits, and reviewer judgment. For hr and recruiters, write job descriptions is reviewed inside a public role post where vague wording can create screening risk, with job description section map with outcome language as the concrete item on the desk.

Checks before sharing

Source review, write job descriptions: the answer uses the supplied role outcomes, responsibilities, requirements, compensation range, and hiring process and does not fill missing facts with confident guesses.
Output shape, write job descriptions: the result clearly becomes a job description, not broad advice about the task.
Handoff clarity, write job descriptions: the answer names missing inputs and the next human check for job description quality, role outcomes and required skills, and fairness and policy fit.
Audience fit, write job descriptions: the result works for a candidate, employee, hiring panel, or HR reviewer, including channel, tone, length, and choice context.
Risk boundary, write job descriptions: the final version respects keep the wording fair, job-related, and reviewed by the appropriate human.

Compare with other results

Question to compare: chatgpt prompts for hr job description

Result job description hr check: open the top results and record whether they solve the task, not only a prompt phrase.
Example job description hr check: compare whether competing pages show a filled example for a job description using realistic role outcomes, responsibilities, requirements, compensation range, and hiring process.
Evidence job description hr check: mark whether each page explains how to verify the pasted notes, concrete examples, hard limits, and reviewer judgment and job description quality, role outcomes and required skills, and fairness and policy fit.
Differentiator job description hr check: compare the top results against this page promise: Job description search results edge: this page should win only if it separates outcomes, requirements, fairness checks, and approval ownership.
Failure job description hr check: mark whether competing pages show this failure mode or avoid it: Job description failure sample: the role post sounds polished but uses vague requirements and hides the review point for fairness-sensitive language.
Freshness job description hr check: record whether competing pages say how source notes stay current. Job description freshness check: recheck the hiring scope, salary or location policy, and approval owner before publishing role language.
Page type job description hr check: confirm whether Google is rewarding a role hub, task page, tool, article, video, or forum thread for this query.
FAQ job description hr check: record People Also Ask questions that should become FAQ or section coverage before publishing changes.

Do not assume

Confirm the trust pages cite official Search Central guidance for helpful content and SEO basics.
Confirm source references support the safe-use and human-review framing.
Add or keep a role-specific external reference if recruiters need policy, education, developer, hiring, sales, or marketing context beyond this prompt library.
External support need: Job description external support need: an independent HR or recruiting resource should cite the outcome-language and fairness-review workflow.

Numbers to leave out unless verified

This page can prove local readiness, source coverage, and review depth. It cannot claim ranking, traffic, search volume, CPC, or difficulty until those numbers come from search performance tool or another real search data source after publishing.

Weak prompt: too vague to trust

Help me write job descriptions for my work.

It gives no source material, no stakeholder, no output shape, and no review lens, so ChatGPT can fill gaps with generic advice.

Stronger prompt: specific enough to review

Help hr and recruiters write job descriptions by turning [source_material] into a job description for [audience]. Keep the task focus on role outcomes, required skills, compensation clarity, and inclusive wording. Use this output shape: copy options grouped by angle, audience, supporting detail, and revision note. Do not add facts beyond the source. End with a review checklist for job description quality, role outcomes and required skills, and fairness and policy fit and the pasted notes, concrete examples, hard limits, and reviewer judgment.

It names the task asset, required inputs, audience, format, evidence boundary, and human review step, so the answer is easier to adapt and check.

Rewrite case from vague request to usable prompt

Original need

A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. The user needs help with job description, but the real job is to turn a messy request into a job description that a candidate, employee, hiring panel, or HR reviewer can review without hidden assumptions.

Weak prompt

Write a good job description from this: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.

This weak version includes a real situation but gives ChatGPT no output shape, audience rule, evidence boundary, or review owner. It can sound polished while missing role outcomes, required skills, compensation clarity, and inclusive wording, inventing details, or skipping job description quality, role outcomes and required skills, and fairness and policy fit.

Stronger prompt

Act as a careful assistant for HR and Recruiters.
I need help with job description. Use only this source material: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
The usual source material for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
The audience is [audience], and the output must work for a candidate, employee, hiring panel, or HR reviewer.
Create a job description in this shape: copy options grouped by angle, audience, supporting detail, and revision note.
Keep the task focus on role outcomes, required skills, compensation clarity, and inclusive wording.
Respect this editorial rule: The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening.
If context is missing, ask up to three clarifying questions before writing.
After the answer, include a review checklist for job description quality, role outcomes and required skills, and fairness and policy fit, the pasted notes, concrete examples, hard limits, and reviewer judgment, and this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

The stronger version gives ChatGPT a role, real input, audience, output shape, editorial boundary, and review lens. It also forces missing-context questions before creation and keeps the pasted notes, concrete examples, hard limits, and reviewer judgment visible for human checking.

Sample input

A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. User notes: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. Audience: a candidate, employee, hiring panel, or HR reviewer. Constraints: avoid unsupported claims, protect private details, and keep focus on role outcomes, required skills, compensation clarity, and inclusive wording.

Example answer shape

A useful answer starts by restating the real situation, then provides copy options grouped by angle, audience, supporting detail, and revision note. It marks assumptions, shows which parts came from the user's notes, includes a concise next action, and ends with checks for job description quality, role outcomes and required skills, and fairness and policy fit, the pasted notes, concrete examples, hard limits, and reviewer judgment, and this boundary: keep the wording fair, job-related, and reviewed by the appropriate human. The output should already reflect the practical review target that matters here, so the human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related.

Human-edited final version

The human keeps the structure, removes any unsupported claim, adds missing facts from the real source, and saves the prompt as a reusable job description prompt pattern with source notes, constraints, and review checklist. Before sharing with a candidate, employee, hiring panel, or HR reviewer, the final pass checks tone, privacy, evidence, and whether role outcomes, required skills, compensation clarity, and inclusive wording is still the center of the answer. The pass is accepted only when the human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related.

Fit

Use when hr and recruiters have real source notes for job description.
Use when the desired result is a job description, not broad advice.
Use when a human can review job description quality, role outcomes and required skills, and fairness and policy fit before the output reaches a candidate, employee, hiring panel, or HR reviewer.

Not fit

Do not use when the model is expected to invent facts, numbers, credentials, or private details.
Do not use when the pasted notes, concrete examples, hard limits, and reviewer judgment is unavailable and cannot be checked.
Do not use as final judgment for sensitive outcomes covered by this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

Worked example: Write job descriptions example from rough notes

Example input

A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language. Raw input: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.

Prompt use

Use the evidence-aware prompt to convert those notes into a job description, then run the review prompt against this editorial rule: The prompt should separate outcomes from credentials and flag wording that could create unfair or unclear screening.

What the answer should look like

A useful answer would return copy options grouped by angle, audience, supporting detail, and revision note for a candidate, employee, hiring panel, or HR reviewer, while making the source details and assumptions visible. It should preserve the real constraint in the input, keep role outcomes, required skills, compensation clarity, and inclusive wording at the center, and avoid adding facts that are not present. The final section should tell the user what still needs checking, especially the pasted notes, concrete examples, hard limits, and reviewer judgment. The human pass is not decoration here: The human pass should verify compensation rules, role requirements, inclusive language, and whether each requirement is truly job-related.

Review notes

Confirm the answer reflects this actual situation: A recruiter is rewriting a customer support manager job post that currently mixes must-haves, nice-to-haves, and vague culture language.
Compare the output against the raw user input: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check.
Confirm the source material really supports the pasted notes, concrete examples, hard limits, and reviewer judgment.
Check that the wording fits a candidate, employee, hiring panel, or HR reviewer.
Confirm the answer handles role outcomes, required skills, compensation clarity, and inclusive wording instead of a neighboring task.
Remove details that violate this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

Build and check the prompt

advanced

Fill this prompt for the current run

Filled prompt preview

Run this evidence-aware working copy prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: role outcomes, responsibilities, requirements, compensation range, and hiring process. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: a candidate, employee, hiring panel, or HR reviewer. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: role outcomes, required skills, compensation clarity, and inclusive wording. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: make a job description easier to review, adapt, and use in a real hr and recruiters workflow. Constraints: keep the wording fair, job-related, and reviewed by the appropriate human. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to role outcomes, responsibilities, requirements, compensation range, and hiring process, and mark any detail the notes do not support.
Run mode for job description work: Run this as the first usable version: use the supplied fields, label assumptions, and produce the main artifact.
Stop rule: Stop if the request asks you to invent facts, evidence, credentials, numbers, or private details.
Return copy options grouped by angle, audience, supporting detail, and revision note.
Before writing a job description, ask up to 3 clarifying questions when role outcomes, responsibilities, requirements, compensation range, and hiring process does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on job description quality, role outcomes and required skills, and fairness and policy fit. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get a working version they can inspect against the supplied notes.

beginner

Write job descriptions for recruiter Context Intake Prompt

Use this before job description work when the notes are rough and ChatGPT should ask clarifying questions first.

Run this context intake prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as intake: ask the questions needed before writing, then wait for answers if the source material is missing.
Stop rule: Stop before creating the final asset if the audience, source material, or review owner is unclear.
Return a question list grouped by audience, source material, constraints, and review owner.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should leave with a short context pack and a safe next prompt, not a finished answer.

[source_material]: Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.Example: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: Who will read, use, approve, or act on this recruiter a job description.Example: a candidate, employee, hiring panel, or HR reviewer
[goal]: The choice or work outcome this recruiter job description work run should support.Example: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.Example: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.Example: role outcomes, required skills, compensation clarity, and inclusive wording

Expected output

Expect a question list grouped by audience, source material, constraints, and review owner that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

Follow-up prompt

Now improve this working version into a job description by tightening job description quality, role outcomes and required skills, and fairness and policy fit, emphasizing role outcomes, required skills, compensation clarity, and inclusive wording, removing unsupported claims, and giving me one stronger version for a candidate, employee, hiring panel, or HR reviewer.

Human review

Check whether the answer uses only provided context, handles the pasted notes, concrete examples, hard limits, and reviewer judgment, fits a candidate, employee, hiring panel, or HR reviewer, reflects role outcomes, required skills, compensation clarity, and inclusive wording, and respects this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.

Best for: Starting job description work when the source material still needs shape. Use when: Use before asking ChatGPT for job description work so the model has enough task-specific context.

advanced

Write job descriptions for recruiter Evidence-Aware Working Copy Prompt

Use this when the source material is ready and the answer needs to become a job description.

[source_material]: Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.Example: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: Who will read, use, approve, or act on this recruiter a job description.Example: a candidate, employee, hiring panel, or HR reviewer
[goal]: The choice or work outcome this recruiter job description work run should support.Example: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.Example: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.Example: role outcomes, required skills, compensation clarity, and inclusive wording

Expected output

Expect copy options grouped by angle, audience, supporting detail, and revision note that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Turning prepared context into a job description. Use when: Use before asking ChatGPT for job description work so the model has enough task-specific context.

workflow

Write job descriptions for recruiter Repeatable Workflow Prompt

Use this when job description work repeats often enough to become job description prompt pattern with source notes, constraints, and review checklist.

Run this repeatable workflow prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as a repeatable workflow: separate one-time facts from fields that should change next time.
Stop rule: Stop if the reusable version would preserve private details or hide a human approval step.
Return a reusable step-by-step workflow with inputs, checks, and follow-up prompts.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get reusable fields, a run order, and a reject-if rule for the next use.

[source_material]: Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.Example: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: Who will read, use, approve, or act on this recruiter a job description.Example: a candidate, employee, hiring panel, or HR reviewer
[goal]: The choice or work outcome this recruiter job description work run should support.Example: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.Example: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.Example: role outcomes, required skills, compensation clarity, and inclusive wording

Expected output

Expect a reusable step-by-step workflow with inputs, checks, and follow-up prompts that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Creating a reusable process for repeated job description work. Use when: Use when job description work repeats often enough to need a standard process.

review

Write job descriptions for recruiter Human Review Prompt

Use this after there is already working copy and the main need is job description quality, role outcomes and required skills, and fairness and policy fit.

Run this human review prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as a review of existing copy: score the answer, name the weak sections, and propose repairs.
Stop rule: Stop if the copy cannot be traced back to the supplied source material or the reviewer is not named.
Return a scored review table with issues, fixes, and what still needs human judgment.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get a choice about accept, repair, or reject before polishing the wording.

[source_material]: Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.Example: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: Who will read, use, approve, or act on this recruiter a job description.Example: a candidate, employee, hiring panel, or HR reviewer
[goal]: The choice or work outcome this recruiter job description work run should support.Example: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.Example: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.Example: role outcomes, required skills, compensation clarity, and inclusive wording

Expected output

Expect a scored review table with issues, fixes, and what still needs human judgment that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Finding weak spots in existing working copy. Use when: Use after hr and recruiters already have working copy and need to check job description quality, role outcomes and required skills, and fairness and policy fit.

format

Write job descriptions for recruiter Format Conversion Prompt

Use this when the substance is right but the output needs to fit a table, checklist, email, outline, or script.

Run this format conversion prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as format conversion: preserve the facts and change only the structure, order, or channel fit.
Stop rule: Stop if the requested format would require adding facts that were not in the original answer.
Return the same content reshaped without adding new facts.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get a reshaped version plus a note showing what stayed unchanged.

[source_material]: Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.Example: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: Who will read, use, approve, or act on this recruiter a job description.Example: a candidate, employee, hiring panel, or HR reviewer
[goal]: The choice or work outcome this recruiter job description work run should support.Example: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.Example: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.Example: role outcomes, required skills, compensation clarity, and inclusive wording

Expected output

Expect the same content reshaped without adding new facts that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Changing the output format without changing the facts. Use when: Use when the answer needs a precise structure before hr and recruiters can review it.

privacy

Write job descriptions for recruiter Privacy-Safe Prompt

Use this when the source material contains private, sensitive, or account-specific details.

Run this privacy-safe prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as a sanitizing pass: replace private details with role-safe descriptions before writing.
Stop rule: Stop if names, identifiers, account details, confidential strategy, or one-time records are still present.
Return a sanitized prompt-ready summary plus a list of removed details.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get a safe summary, removed-detail list, and a reusable version without sensitive data.

[source_material]: Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.Example: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: Who will read, use, approve, or act on this recruiter a job description.Example: a candidate, employee, hiring panel, or HR reviewer
[goal]: The choice or work outcome this recruiter job description work run should support.Example: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.Example: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.Example: role outcomes, required skills, compensation clarity, and inclusive wording

Expected output

Expect a sanitized prompt-ready summary plus a list of removed details that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Sanitizing context before asking ChatGPT for help. Use when: Use before adding sensitive context so private details stay out.

short

Write job descriptions for recruiter Fast Checklist Prompt

Use this for a quick pass when the user only needs the next few choices for job description work.

Run this fast checklist prompt for HR and Recruiters; stay practical, cite the pasted notes, and leave the final call with the human reviewer.
Task: help me with job description work. Target result: a job description.
Source material I can provide: [source_material]. Typical source for this task is role outcomes, responsibilities, requirements, compensation range, and hiring process.
Audience or stakeholder: [audience]. The output must work for a candidate, employee, hiring panel, or HR reviewer.
Task-specific focus to preserve: [task_focus]. If the pasted focus is broad, compare it with this page cue: role outcomes, required skills, compensation clarity, and inclusive wording.
Goal: [goal]. Constraints: [constraints]. Fact boundary for this run: keep the pasted notes, concrete examples, hard limits, and reviewer judgment tied to [source_material], and mark any detail the notes do not support.
Run mode for job description work: Run this as a fast choice pass: give only the next actions, the missing input, and the main risk.
Stop rule: Stop if the user needs a full artifact, a legal answer, a policy choice, or unsupported factual claims.
Return a concise checklist with the next action and the main risk.
Before writing a job description, ask up to 3 clarifying questions when [source_material] does not include role outcomes, responsibilities, requirements, compensation range, and hiring.
After the answer, include a human review section focused on [review_lens]. Verify the pasted notes, concrete examples, hard limits, and reviewer judgment; and respect this boundary: keep the wording fair, job-related, and reviewed by the appropriate human.
Check cue: for job description work, The user should get a narrow next step they can complete before opening a longer prompt.

[source_material]: Paste the concrete recruiter job description work notes, such as role outcomes, responsibilities, requirements, compensation range, and hiring process.Example: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: Who will read, use, approve, or act on this recruiter a job description.Example: a candidate, employee, hiring panel, or HR reviewer
[goal]: The choice or work outcome this recruiter job description work run should support.Example: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: Rules for recruiter job description work: tone, length, channel, privacy, and the pasted notes, concrete examples, hard limits.Example: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: Use this check before sharing: job description quality, role outcomes and required skills, and fairness and policy.Example: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: The detail that keeps this recruiter job description work prompt specific: role outcomes, required skills, compensation clarity, and inclusive wording.Example: role outcomes, required skills, compensation clarity, and inclusive wording

Expected output

Expect a concise checklist with the next action and the main risk that explicitly separates source-based content from assumptions and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

Follow-up prompt

Human review

Best for: Getting a quick choice checklist before spending more time. Use when: Use when time is short and the user needs the next action, not a full answer.

Variables

[source_material]: role outcomes, responsibilities, requirements, compensation range, and hiring process
[audience]: a candidate, employee, hiring panel, or HR reviewer
[goal]: make a job description easier to review, adapt, and use in a real hr and recruiters workflow
[constraints]: keep the wording fair, job-related, and reviewed by the appropriate human
[review_lens]: job description quality, role outcomes and required skills, and fairness and policy fit
[task_focus]: role outcomes, required skills, compensation clarity, and inclusive wording

Answer checks

Context: Does the prompt give enough role outcomes, responsibilities, requirements, compensation range, and hiring process to avoid guessing?
Specificity: Does the answer produce a job description rather than broad advice?
Task focus: Does it handle role outcomes, required skills, compensation clarity, and inclusive wording instead of drifting into a neighboring workflow?
Reviewability: Can a human quickly check job description checkpoint and the pasted notes, concrete examples, hard limits, and reviewer judgment?
Fit: Does the wording match a candidate, employee, hiring panel, or HR reviewer and the real channel?
Safety: Are private details, unsupported claims, and policy-sensitive assumptions controlled?

Common mistakes

Asking ChatGPT to write job descriptions without giving role outcomes, responsibilities, requirements, compensation range, and hiring process.
Accepting polished wording before checking the pasted notes, concrete examples, hard limits, and reviewer judgment.
Using the same prompt for every recruiter task instead of changing the output shape and review lens.
Forgetting to name a candidate, employee, hiring panel, or HR reviewer, which makes tone and detail level drift.
Ignoring the task-specific focus: role outcomes, required skills, compensation clarity, and inclusive wording.
Skipping the review pass for job description quality, role outcomes and required skills, and fairness and policy fit.
Pasting private or sensitive details when a summarized version would work.

Before you share

Prompts must support fair review and human judgment, not automated employment choices.
Ask ChatGPT to label assumptions and verification needs before using a job description.
Do not paste private names, identifiers, account details, student records, customer records, or confidential strategy when a summarized version is enough.
Check that role outcomes, required skills, compensation clarity, and inclusive wording is supported by the source material and not invented.
Have a human review job description checkpoint before sharing the output with a candidate, employee, hiring panel, or HR reviewer.

FAQ

What is the best prompt for hr and recruiters to write job descriptions?

Use a prompt that names role outcomes, responsibilities, requirements, compensation range, and hiring process, asks for copy options grouped by angle, audience, supporting detail, and revision note, and ends with a review pass for job description quality, role outcomes and required skills, and fairness and policy fit.

What should I paste into ChatGPT first?

Paste sanitized source notes, the intended audience, constraints, and the choice the output must support. For this task, the key input is role outcomes, responsibilities, requirements, compensation range, and hiring process.

How do I make the answer less generic?

Ask ChatGPT to use only the supplied material, show assumptions, and revise the answer against the pasted notes, concrete examples, hard limits, and reviewer judgment and a candidate, employee, hiring panel, or HR reviewer.

What should a human check before using the output?

Check facts, tone, privacy, unsupported claims, and the task-specific lens: job description quality, role outcomes and required skills, and fairness and policy fit.

Next workflows

ChatGPT Prompts for HR and RecruitersReturn to the role guide to choose by situation, output, and reviewer.
Prepare interview questionsUseful next step when this workflow needs a related hr and recruiters output or review pass.
Build interview scorecardsUseful next step when this workflow needs a related hr and recruiters output or review pass.
Plan onboardingUseful next step when this workflow needs a related hr and recruiters output or review pass.
Write employee surveysUseful next step when this workflow needs a related hr and recruiters output or review pass.
Write performance review promptsUseful next step when this workflow needs a related hr and recruiters output or review pass.

Write Job Descriptions: use the public role post where vague wording context

Start with the note you actually have1/3 ready

Copy this after checking the notes

Check the answer before saving it

Pick accept, repair, or reject before reuse

Save the answer, problem, and next try

Save the final answer, human edit, and variables

Set up the first run

Write job descriptions for recruiter Evidence-Aware Working Copy Prompt

Variable Builder

Copy this filled version

Run this page in four moves

Start from the real note, not a blank prompt

Check the answer against your note

Real use plan for treating the prompt like a work note

Before copying

After ChatGPT answers

Reject the answer if

Choose the next move

Build The Asset

Know when the answer is ready

Ready signal

First run action

Second pass before the answer becomes reusable

Source line

Human check note

the rough note "Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check" as the visible source line for a job description

any confident claim about the pasted notes, concrete examples, hard limits, and reviewer judgment that the pasted note does not prove

the missing audience, owner, or review detail needed before a candidate, employee, hiring panel, or HR reviewer uses the answer

the first polished paragraph so it shows role outcomes, required skills, compensation clarity, and inclusive wording before tone improvements

Why this feels hand-edited

Run the second pass

Task actions for the next useful move

Before you use the answer, make the call

Working case file: Write Job Descriptions working case for HR and Recruiters

Rough note

Constraint to keep visible

What the user brought

What is still missing

Who accepts the answer

What gets saved

Before copying

Checks before sharing

Run this case first

Input triage before running ChatGPT

Missing context

Notes to save before reusing this prompt

Facts the prompt can safely use

Unknowns the model must not hide

Rules the answer must obey

Details to summarize before reuse

Reusable fields for the next run

Iteration loop: run the prompt as a working thread

Thread goal

First version

Question pass

Risk pass

Reusable version

Prompt readiness check before you copy

Collect context first

Session handoff: finish the run without losing the thread

Collect working context

Work note: what the rough note changes

Original working note

Questions before reuse

Who checks it

Usable output

Prompt run from pasted notes

Pasted notes

Why this input is messy

First prompt move

Questions ChatGPT should ask

Usable answer shape

Human revision

Save or discard

Choose the right workflow for this job

Work moment

Why this workflow

Do first

Next best workflow