Translate real work, decision rights, outcomes, and constraints into a clear and inclusive job description. 제공할 내용: Actual role evidence, Approved role requirements, Hiring and publishing rules. 예상 결과: A review-ready job description with responsibilities, outcomes, qualifications, conditions, compensation gaps, and fairness audit.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
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.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
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.
예시 출력
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.
효과가 있는 이유
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.
결과 확인
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?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Draft a job description from actual responsibilities”?
For “Draft a job description from actual responsibilities,” prepare Actual role evidence, Approved role requirements, and Hiring and publishing rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Draft a job description from actual responsibilities” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A review-ready job description with responsibilities, outcomes, qualifications, conditions, compensation gaps, and fairness audit—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Draft a job description from actual responsibilities”?
The published test record for “Draft a job description from actual responsibilities” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
