AI Prompts for Job Descriptions That Attract the Right Candidates

A Series B startup posted a Head of Growth job description. It was comprehensive: 15 bullet points of requirements, a salary range, and a "competitive benefits" section. They received 400 applications in the first week.

Their head of recruiting spent three days screening. She found two candidates worth a phone call. Neither proceeded past the first interview.

The job description had attracted people who could check the boxes — not people who could do the actual job. The difference: the description described requirements but not the role's real challenges, success criteria, or the specific type of person who thrives in that environment.

AI prompts job descriptions done right doesn't just help you write faster. It helps you write more honestly — which is what attracts the right candidates instead of the most candidates.

Quick-Start (Copy This Right Now)

For a job description that attracts qualified, aligned candidates:

You are a talent acquisition specialist writing a job description for [role title] at [company type/stage].

Role context:
- What this person will actually spend 80% of their time doing: [be specific — not generic job duties]
- The biggest challenge this person will face in the first 90 days: [honest answer]
- What "excellent" looks like in this role after 12 months: [specific outcomes, not traits]
- Who this person will work with most closely: [teams, reporting structure]
- What kind of candidate will NOT thrive in this role: [honest answer about culture/pace/style]

Company context:
- Stage: [startup/growth/enterprise]
- Culture descriptor (one honest sentence, not marketing copy): [describe it]
- Salary range: [include it — describe your comp philosophy if relevant]

Write a job description that:
1. Opens with what makes this role important and interesting — not the company's mission statement
2. Describes what the person will actually DO (active language, specific tasks)
3. Lists requirements as "you'll need" rather than "required qualifications" — and only includes things that are truly necessary to do the job
4. Includes a "what success looks like" section with measurable outcomes at 30/60/90 days
5. Includes one honest sentence about who this role is NOT right for
6. Uses inclusive language — avoid "ninja," "rockstar," and language that skews toward one demographic

Length: 400-600 words. No corporate filler.

What this does: The "what kind of candidate will NOT thrive" field is the most unusual and most valuable — it self-selects out candidates who would be wrong for the culture before they apply, saving everyone time. Most job descriptions are written to attract as many people as possible; this one is written to attract the right people.

Understanding the Variables

"What this person will actually spend 80% of their time doing" is the most common gap in job descriptions. Companies write what the job covers; candidates need to know what the job IS. There's a big difference between a marketing role where 80% of time is content creation and one where 80% is campaign analytics, even if both descriptions would include "content strategy" and "data analysis" in the requirements list.

"What excellent looks like after 12 months" converts vague role descriptions into specific success criteria — and helps candidates self-assess honestly. If the 12-month bar is "launched three new markets and established partnerships with five enterprise distributors," a generalist marketer knows this isn't for them. That's good. That saves time for everyone.

⚡ Pro tip: Share a draft job description with your best current employee in a similar role and ask: "Would the 22-year-old version of you have applied for this? Would you have gotten the job based on this description?" Their answer often reveals what the description is missing or inflating.

Step-by-Step: Writing Job Descriptions by Role Type

For technical roles:

Write a job description for [technical role — e.g., Senior Backend Engineer] that: explains the technical stack without assuming it's inherently appealing, describes the type of engineering problems this person will work on (not just the technologies), and includes a realistic picture of code review practices, deployment frequency, and on-call expectations. Technical candidates have been burned by job descriptions that hide operational complexity — be upfront about it.

What this does: Technical candidates are more skeptical of job descriptions than almost any other group — because they've read too many that overpromised. Specificity and honesty about the actual work environment builds credibility.

For leadership roles:

Write a job description for a [leadership role — e.g., VP of Sales]. This role requires building a team from [current state] to [target state]. Be specific about: the maturity of the current team, what's working and what isn't, the authority this leader will have (budget, hiring, strategy), and what "fixing" looks like. Do not describe this as a "greenfield opportunity" unless it genuinely is — candidates hear this as either exciting or a warning sign depending on their experience level.

What this does: Leadership job descriptions need to be honest about the state of what the person is inheriting — candidates who've been in leadership roles know that "opportunity to build" can mean anything from exciting to chaotic.

For specialist roles:

Write a job description for [specialist role] at a company where this function is being built for the first time. The first hire will need to: [describe the foundational work]. They will NOT have [resources they might expect — existing tools, team support, established processes]. In 12 months, success means [specific outcome]. Be honest about the "building from scratch" nature — candidates who thrive in this are looking for it; candidates who need established infrastructure should self-select out.

What this does: First-hire-in-a-function roles require a specific personality type — autonomous, comfortable with ambiguity, energized by building rather than optimizing. This description finds those people and tells everyone else this isn't their role.

Pro-Level Variations

Inclusive language audit:

Review this job description for language that might discourage qualified candidates from applying: [paste JD]. Flag: requirements that are inflated beyond what the role actually needs, language that implies a specific physical capability not required by the role, gendered language or phrases that research shows discourage women from applying, experience requirements that screen out candidates with non-traditional backgrounds who could do the job. Suggest specific rewrites for each flagged item.

What this does: Catches the systematic biases that reduce your candidate pool unnecessarily — including the research-backed finding that women apply when they meet 100% of requirements, while men apply when they meet 60%. Inflated requirements have a measurable demographic effect.

Troubleshooting Common Issues

"We're getting under-qualified applicants." Your requirements list isn't specific enough. Replace "5+ years experience" with "5+ years experience specifically in [specific domain] — experience in adjacent fields won't be sufficient for day one."

"We're not getting enough applicants." Your salary range is either too low, missing entirely, or your description reads as unappealing. Add the range, and remove one-third of your requirements list — research consistently shows that long requirements lists reduce applications without improving quality.

⚠️ Common mistake: Writing job descriptions by copying and modifying a previous job description. Job descriptions copy-pasted from prior versions inherit outdated requirements, inflated credentials, and the wrong framing for what the role actually needs today. Start from the role context, not the previous description.

Your Turn

Take your next open role and answer the four honest-context questions before you touch the job description: What will this person do 80% of the time? What's the hardest challenge in the first 90 days? What does excellent look like after 12 months? Who will not thrive here?

Answer those four questions, paste them into the Quick-Start prompt, and you'll have a job description better than 90% of what's on the market.

Save your job description templates in PromptABCD organized by role family — engineering, sales, marketing, operations. Update the specific context for each hire; the framework stays constant. You'll spend your time on the things that vary by role, not rebuilding the structure from scratch.

After You Post: Using AI to Screen and Sort

The job description is the beginning of the hiring process, not the end. Once applications come in, AI prompts can help you screen consistently and fairly.

Here are the requirements for [role]: [paste key requirements from JD]. Here are three candidate applications: [paste summaries or key details]. For each candidate, assess: which requirements they clearly meet, which are uncertain based on available information, and which appear to be gaps. Do not make a hire/no-hire recommendation — provide an assessment that helps me decide which candidates warrant a first conversation, and what questions I should ask to resolve the uncertain areas.

What this does: Creates a consistent screening framework across candidates — which reduces the unconscious bias that comes from evaluating applications sequentially with different mental frames.

⚠️ Common mistake: Using AI to make final screening decisions. AI should inform your process, not replace judgment. Use it to organize and highlight; keep the decisions with humans who understand the full context of the role and team.

The job description and screening prompts together, saved in PromptABCD by role type, create a repeatable hiring process that gets faster and more consistent with every use.

⚡ Pro tip: After each hiring cycle, run a retrospective on your job description. Which candidates who looked great on paper underperformed in the role — and was that gap predictable from the description? Update the JD for the next hire accordingly.

⚡ Pro tip: Before posting any job description, have someone outside your team read it and tell you what kind of person they picture applying. If their description doesn't match who you're actually looking for, the description is doing the wrong job. Revise before posting.

⚡ Pro tip: Post your job description on at least two platforms and track which produces better-fit applicants. Over multiple hires, this data tells you where your target candidates actually look — which is often different from where most companies default to posting.