PromptWork
Write a job description from role facts
Turn rough notes about a role into a job description built around outcomes rather than a requirements laundry list, with must-haves clearly separated.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Write a job description for Senior Product Designer on the Growth team using the facts below.
Structure it as: a 2-3 sentence overview of the role and why it exists, "What you'll be responsible for" written as outcomes ("own the checkout funnel's conversion rate"), not a laundry list of tasks ("attend meetings, write code"), then "Must-have" and "Nice-to-have" as two clearly separated lists — anything that would actually block a hire belongs in must-have, everything else goes in nice-to-have, even if the notes lumped them together. Keep the tone direct, no corporate filler like "fast-paced environment" or "wear many hats" unless the notes specifically support it. If the notes don't give you enough to write the compensation or location section, leave it as a placeholder rather than inventing a number or policy.
Role facts:
need someone to own end-to-end design for the signup and onboarding flow, working closely with a PM and 3 engineers. must have shipped a consumer product used by at least 100k people. figma required, experience with a design system a plus. would like someone comfortable presenting to execs but that's not a dealbreaker. remote OK if in a US timezone.
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →Requiring responsibilities to be written as outcomes rather than tasks makes the JD describe what success looks like, which is also what a good candidate actually screens themselves against.
- →Forcing a hard split between must-have and nice-to-have, with an explicit rule for which bucket a blocking requirement belongs in, fixes the common failure where every requirement gets marked "required" and qualified candidates self-select out.
- →Banning filler phrases unless the notes support them, and leaving compensation as a placeholder rather than a guess, keeps the JD from padding out gaps in the input with generic corporate language or a fabricated number.