AI Prompts for HR

Business & Marketing Updated September 5, 2026 by GenPrompto
Prompt
Write a job posting for [role, described specifically]. Key requirements: [real requirements, in your own words]. What makes this role genuinely interesting: [real detail about the team, project, or growth opportunity]. Flag any requirement that seems unnecessarily restrictive or likely to discourage good candidates.

What this does

Writes job postings and onboarding plans with AI -- built around the real role and company, not generic templates.

HR tasks like job postings and onboarding plans need the real role, requirements, and company context named — a bare “write a job posting” request returns generic corporate language that could describe any role at any company.

What this produces

A job posting or onboarding plan built around the real role and genuine company context you provide — specific enough that a candidate can tell it’s describing an actual position, not a template.

Variations

Two ready-to-copy versions for common HR tasks.

Job Posting Version
Write a job posting for [role, described specifically]. Key requirements: [real requirements]. What makes this role genuinely interesting: [real detail about the team, project, or growth opportunity]. Flag any requirement that seems unnecessarily restrictive.
Onboarding Plan Version
Help me draft a first-week onboarding plan for a new [role, described specifically]. Their actual goals for week one: [real goals, e.g., “meet the team, understand the current project, ship one small task”]. Structure this plan out day by day clearly.

Who this is for

HR professionals handling recruiting and onboarding tasks — job postings, candidate outreach, onboarding plans — who want AI help built around the real role, not generic templates.

Example Output

Naming the actual role, real requirements, and company context produces a job posting or onboarding plan that sounds specific and genuine; a bare “write a job posting” request returns generic corporate language that could describe any role at any company.

Tips for better results

  • Name the actual role and real requirements, not just the job title — generic titles produce generic postings.
  • Give genuine company context — culture, what makes the role interesting — rather than boilerplate benefits language.
  • For onboarding, specify the actual first-week goals, not a generic checklist template.
  • Ask it to flag anything that sounds like unnecessary jargon or an inflated requirements list, which tends to discourage qualified candidates.

What didn’t work as well

Asking to “write a job posting” with no real role details or company context. The result is generic corporate language that could describe almost any role — naming the actual requirements and genuine company context is what produces something candidates would actually respond to.

See also: AI Prompts for Project Management and AI Prompts for Product Managers.

FAQ

How specific should I be about the role for a job posting?

As specific as possible — real requirements and genuine detail about the team or project produce a posting that attracts candidates who actually fit, rather than a flood of generic applications.

Can this help identify an inflated requirements list?

Yes — explicitly ask it to flag requirements that seem unnecessarily restrictive, since overly long lists are a known reason qualified candidates self-select out.

Should onboarding plans be the same for every role?

No — give the real, role-specific first-week goals rather than reusing a generic template, since onboarding needs vary significantly by role and team.

Related