Job Description
Job Description People Can Apply To
Write a JD with a real must-have list, salary band space, and no leftover corporate fog.
The Prompt
job-description-people-can-apply-to.md
Write a job description that a strong candidate can say yes or no to. Role title: {{title}} Team / reporting line: {{team}} Location / remote: {{location}} What this person will own in 6 - 12 months: {{outcomes}} Must-have skills (true musts): {{musts}} Nice-to-haves: {{nices}} Salary band if I can share: {{salary}} Company one-liner: {{company}} Structure: 1. One-paragraph role summary (outcomes, not adjectives) 2. What you will do (6 - 8 bullets, verbs) 3. What you need (must vs nice, clearly split) 4. How we work (hours, travel, on-call - only facts) 5. Pay and benefits - use {{salary}} or [compensation range to add] 6. How to apply Rules: - No "ninja", "rockstar", or "wear many hats" without naming the hats. - Do not require a degree unless I listed it as a must. - Keep under 650 words.
Negative prompt
Included when you copy the prompt
Do not use ninja, rockstar, wear many hats, or other empty corporate fog. Do not invent degree requirements, years of experience, or salary figures not provided. Do not pad with culture buzzwords instead of outcomes. Keep under 650 words.
Fill in your details below - this prompt updates as you type, then copy it.
Fill in your details
0 of 8 filled. Preview updates as you type - then copy the finished prompt (negative prompt included when present).
job-description-people-can-apply-to.md
Prompt preview
Write a job description that a strong candidate can say yes or no to. Role title: {{title}} Team / reporting line: {{team}} Location / remote: {{location}} What this person will own in 6 - 12 months: {{outcomes}} Must-have skills (true musts): {{musts}} Nice-to-haves: {{nices}} Salary band if I can share: {{salary}} Company one-liner: {{company}} Structure: 1. One-paragraph role summary (outcomes, not adjectives) 2. What you will do (6 - 8 bullets, verbs) 3. What you need (must vs nice, clearly split) 4. How we work (hours, travel, on-call - only facts) 5. Pay and benefits - use {{salary}} or [compensation range to add] 6. How to apply Rules: - No "ninja", "rockstar", or "wear many hats" without naming the hats. - Do not require a degree unless I listed it as a must. - Keep under 650 words.
Examples
Example input
Title: Senior Backend Engineer. Team: Platform, reports to Eng Manager. Location: Remote (US). Outcomes: Own API reliability and cut p95 latency 30% in 12 months. Musts: TypeScript, Postgres, on-call experience. Nices: Kubernetes. Salary: $160 - 190k. Company: B2B logistics SaaS for mid-market carriers.
What you should get
A JD with a one-paragraph outcome summary, 6 - 8 verb-led bullets, clearly split must vs nice skills, remote/on-call facts, the $160 - 190k band, and a short how-to-apply section - no rockstar language or invented degree requirements.
When to use this prompt
Use it when
- You need help with hiring managers.
- You need help with people ops.
- You need help with founders.
Skip it when
- You only need a one-line ask with no constraints, format, or context.
- You cannot supply the fill-in details the template asks for.
- A different category or tool-specific workflow fits the job better.
How to get a good result
Done when
A JD with a one-paragraph outcome summary, 6 - 8 verb-led bullets, clearly split must vs nice skills, remote/on-call facts, the $160 - 190k band, and a short how-to-apply section - no rockstar language or invented degree requirements.
Common mistakes
- Leaving title, team, location vague - the model then invents placeholders.
- Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules.
- Stopping when the first draft appears instead of checking it against the success criteria below.
FAQ
- What do I fill in before I copy this prompt?
- Replace these placeholders with your details: title, team, location, outcomes, musts, nices, salary, company. Required fields are marked on the page. The prompt text updates as you type.
- Which AI tools is this prompt written for?
- It works best with ChatGPT, Claude, Gemini. Copy the filled prompt and paste it into the tool you already use.
- What should a good result look like?
- A JD with a one-paragraph outcome summary, 6 - 8 verb-led bullets, clearly split must vs nice skills, remote/on-call facts, the $160 - 190k band, and a short how-to-apply section - no rockstar language or invented degree requirements.
- What are common mistakes with this prompt?
- Leaving title, team, location vague - the model then invents placeholders. Asking ChatGPT, Claude, or Gemini for a shorter answer after a long structured prompt - that throws away the format rules. Stopping when the first draft appears instead of checking it against the success criteria below.
Best for
- Hiring managers
- People ops
- Founders
Related Prompts
More prompts like this — same topic and style.
