Write a Job Description That Attracts the Right Candidates

Turns a role scorecard into a job post that describes the actual work, states the pay, and filters honestly — instead of a requirements list that deters the people you want. Use it once you know what the role is for.

0 likes 0 dislikes
Sign in to rate this prompt

Prompt

    You are a hiring manager writing a job post that a strong, employed, not-desperate candidate would read to the end.

The role and what it's for: {{role_and_mission}}
What this person will actually do and accomplish: {{outcomes_and_work}}
What they genuinely need to be able to do: {{real_requirements}}
The team, the manager, and how they work: {{team}}
Compensation range, location, and work arrangement: {{comp_and_location}}
What's genuinely good about this job, and what's hard: {{honest_pitch}}
Our company, in plain terms: {{company}}

Write the post:

**Opening.** What this person will work on and why it matters, in three or four sentences. Specific to us — if this paragraph would fit any company in our industry, rewrite it. No mission-statement language, no "we're a fast-paced team."

**What you'll do.** The real work, framed as outcomes from {{outcomes_and_work}}. Concrete enough that a candidate can picture their Tuesday.

**What we're looking for.** From {{real_requirements}} only. Keep it short, describe capabilities rather than credentials, and cut anything that's a proxy for something you could assess directly. Long requirement lists disproportionately deter qualified candidates who don't match every line — including strong ones you want. If a nice-to-have is genuinely optional, put it in a separate, clearly-labeled short list or leave it out.

**Compensation.** State the range. A post without one gets fewer and worse applicants, and it wastes everyone's time through three rounds.

**The honest part.** From {{honest_pitch}}, what's hard about this job — the legacy system, the travel, the ambiguity, the on-call. This is the highest-trust paragraph in the post and it filters better than any requirement.

**Process.** What the interview process actually is, how many stages, and roughly how long. Candidates choose partly on this.

Rules: no "rockstar," "ninja," "wear many hats," or "work hard play hard." No unpaid-overtime euphemisms. Write in plain second person. Aim for 400–600 words.

Then flag any language that could deter qualified candidates unnecessarily or that risks running into hiring-discrimination rules — age-coded terms like "digital native" or "recent graduate," gendered phrasing, unnecessary physical requirements, or citizenship wording. Employment law varies by jurisdiction; have HR or counsel review the final post.

Like this prompt?

Create an account to copy this prompt, create your own, and find the best prompts to scale your business.