Draft a job description from actual responsibilities
Translate real work, decision rights, outcomes, and constraints into a clear and inclusive job description
9 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Draft a job description grounded in actual role evidence and approved requirements.
Recurring work, outcomes, decisions, stakeholders, tools, workload, schedule, travel, physical demands, and boundaries:
[work]
Essential and trainable skills, credentials, experience evidence, level, location, employment type, compensation, benefits, and accommodations:
[requirements]
Jurisdiction, template, equal-opportunity language, prohibited criteria, application, privacy, approvers, and review date:
[rules]
Separate observed current work, approved future need, preference, legal requirement, and unresolved decision. Define role purpose, reporting and collaboration lines, 5-8 outcome-oriented responsibilities with realistic frequency, decision rights and escalation, success evidence for the first 6-12 months, essential qualifications tied to duties, learnable skills, work conditions, location and schedule, compensation and benefits only if approved, application process, and accommodations. Never invent salary, benefits, credential, degree, years of experience, employment status, physical demand, travel, authority, or legal language. Challenge requirements that lack a task-based reason or may act as unnecessary proxies; suggest a broader alternative for human review without deciding legality. Avoid personality stereotypes and inflated scope. End with a requirement-to-duty map, missing decisions, bias and accessibility audit, and required HR/legal approval.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Actual role evidence
Operations Coordinator on a 12-person remote software team. Weekly: triage 20-30 internal requests, confirm owner and acceptance criteria, maintain status in Linear, prepare twice-weekly handoff review, follow up on overdue dependencies, and document process changes. Coordinates Engineering, Support, and Finance; does not set product priority, approve spend, or manage staff. Handles routine operational data, not production credentials. Core hours overlap 13:00-17:00 UTC; occasional month-end meeting. No travel or physical requirement observed.
Approved role requirements
Full-time employee, remote within UK. Level approved as individual contributor. Essential: clear written communication, organizing concurrent work, spreadsheet basics, and evidence of improving a recurring process. Linear can be learned. No legally required credential. Hiring manager proposed bachelor's degree and 3 years experience but gave no duty-based reason. Compensation and benefits await approval. Accommodations available through HR process, wording pending.
Hiring and publishing rules
UK posting using company sections: purpose, responsibilities, success, essentials, helpful, conditions, compensation, application, inclusion. Do not write legal equal-opportunity language; insert explicit HR placeholder. Applications through approved careers portal, URL not supplied. HR and UK employment counsel approve before posting. Review date Aug 28 2026.
Example output
Operations Coordinator — UK remote
Purpose
Keep recurring internal requests and cross-team handoffs visible, owned, and reviewable so Engineering, Support, and Finance can coordinate decisions. This is an individual-contributor role and does not manage people, set product priorities, or approve spend.
Responsibilities
• Triage roughly 20-30 internal requests each week and confirm the owner and acceptance criteria.
• Maintain current request and dependency status in Linear.
• Prepare and facilitate two weekly handoff reviews, recording decisions and unresolved dependencies.
• Follow up on overdue dependencies without changing ownership or priority.
• Document approved process changes and keep operational instructions current.
• Coordinate routine operational information across Engineering, Support, and Finance; do not handle production credentials.
Success evidence in the first 6-12 months
Requests consistently have owners and acceptance criteria; review materials are ready for the agreed cadence; overdue dependencies and unresolved decisions are visible; at least one recurring process improvement is documented and evaluated. Numerical performance targets require approval and are not invented here.
Essential evidence
Clear written communication; ability to organize concurrent work; basic spreadsheet use; one example of improving a recurring process. A degree and three years of experience are not included as essential because no duty-based reason was supplied. Hiring should assess equivalent evidence. Linear experience is helpful but learnable.
Conditions and missing publication fields
Full-time employee, remote within the UK, with overlap from 13:00-17:00 UTC and occasional month-end meetings. No travel or physical requirement is stated. Compensation, benefits, careers URL, accommodation wording, and approved inclusion statement remain explicit HR decisions. Do not publish until HR and UK employment counsel approve them.
Why this works
1
Duty-linked qualifications reduce arbitrary filters and make selection evidence more defensible.
2
Decision rights and success evidence show candidates what the work actually requires.
Check the result
Does every essential qualification map to an actual responsibility or legal requirement?
Are compensation, conditions, authority, and legal wording confirmed rather than inferred?
Are learnable skills and reasonable accommodation paths visible?
ChatGPT