Overview

A recruiter spends two hours writing a job description. It reads like a legal document written by committee. Nobody applies. An HR manager asks AI to write the same job description in two minutes. It's still bad, generic, tone-deaf, focused on "10+ years of experience" when they'd hire someone with 3 years of passion. Both failed. The difference isn't AI. It's the question being asked.

Most HR professionals treat prompts like they treat Google: type a few words, hope for the best. That doesn't work. A vague prompt produces vague, useless output. A precise prompt produces output you can actually use, or at least, output worth improving.

This lesson is about the anatomy of a good prompt. Not "good for AI lovers", good for HR professionals who have real work to do. You'll learn why specificity is your only lever. You'll see exactly how the same task, asked five different ways, produces five wildly different outputs. By the end, you'll have a framework for asking AI anything and knowing whether the answer is worth your time.

Why This Matters for HR Professionals

You don't have unlimited time to rewrite AI output. Every minute spent fixing a prompt is a minute you're not spending on strategy. So precision up front saves you hours on the back end.

More importantly: the way you ask a question shapes the assumptions baked into the answer. A vague job description prompt produces AI output that sounds like every other AI-generated JD. A specific prompt, one that includes your company's voice, your role level, your actual audience, produces output that feels like it came from a human who knows your business. The same is true for recruiting emails, policy language, and performance feedback.

Your job isn't to become a prompt engineer. It's to become precise about what you actually need. When you're precise, AI becomes useful. When you're vague, you're just wasting time.

Core Anatomy: The Four Elements of a Strong Prompt

Every effective prompt has four components. Not all four are always explicit, but they're always there.

Context: What's the situation? What's the background? What does AI need to know to understand why you're asking?

Task: What specifically do you want? What's the output?

Constraints: What are the boundaries? Length, tone, format, audience, restrictions?

Format: How should the answer be structured?

Here's a weak prompt:
"Write a job description for a marketing manager."

Here's the same task, strong:
"Write a job description for a Senior Marketing Manager at a 250-person B2B SaaS company. This person will lead a team of three and report directly to the CMO. We're a data-driven, fast-moving company. The role combines strategic planning with hands-on execution. Our marketing team is collaborative but independent. Tone: direct, warm, no corporate jargon. Length: 400-500 words. Format: headline, overview paragraph, 4-5 key responsibilities (use bullet points), required qualifications section, nice-to-haves, about us paragraph. Avoid generic phrases like 'fast-paced environment' or '10+ years required.'"

The second prompt works because:
- Context: You've explained the company size, reporting structure, and culture.
- Task: It's crystal clear you want a job description, and specifically for a Senior role, not an entry-level one.
- Constraints: You've set tone boundaries ("direct, warm, no corporate jargon"), length, and what to avoid.
- Format: You've specified the exact structure, which means less rewriting later.

Why Vague Prompts Fail in HR Contexts

AI is a mirror. It reflects back what you put in. If you're vague, it defaults to corporate templates. If you're specific, it adapts.

Here's a recruiter's actual weak prompt: "Help me write an outreach email to a candidate."

The AI output will be generic, salesy, and applicant-tracking-system-speak. It will sound like 100 other recruiting emails. Candidates get them constantly. They delete them constantly.

Now here's a specific version of the same task:
"Draft a personalized LinkedIn message to a prospective candidate. Context: We're a 30-person software consulting firm. The candidate (imagine her name is Sarah) is a Senior Product Manager with 8 years at a Fortune 500 company. I found her through a mutual connection. We're hiring for a Director of Product role, the first product director role in our company. We want ambitious product leaders who want ownership and want to help us scale. Tone: genuine, not salesy. Length: 80-120 words. Format: conversational, as if from a human colleague. What to avoid: generic 'excited to connect,' overused LinkedIn phrases, mentioning our size as a benefit to HER (she's leaving a big company, so scale isn't the draw)."

The second version works because you've given AI:
- Why you're reaching out (mutual connection, role fit)
- Who she is (what matters about her background)
- What you actually have to offer (ownership, not a title)
- The tone you want (genuine, not corporate)

The Iterative Loop: It's Not One-and-Done

The best prompts aren't perfect the first time. They evolve.

Here's how it actually works:

• First prompt: You ask a question, maybe it's 80% right. You fix the 20%.
  - Second iteration: You refine based on what worked and what didn't. You ask AI to adjust the tone, cut 50 words, make it less corporate.
  - Third iteration: You might realize you need a different structure entirely. You ask AI to reorganize.

This is normal. Professional. Expected.

The mistake is thinking you wasted time if the first output isn't perfect. You didn't. You got output in two minutes that would take an hour to write from scratch. Now you're tweaking, not starting over.

Here's a concrete example from performance review writing:

First prompt (weak):
"Write a performance review for an employee who had a good year but struggled with communication."

AI output (generic):
"[Employee name] has made solid contributions to the team this year. [He] demonstrates strong technical skills and has completed all assigned projects on time. However, [he] should focus on improving communication with team members and stakeholders. Overall, [he] is a valued member of the team."

Your reaction: This could apply to anyone. It says nothing specific. It's useless.

Refined prompt (better):
"Write a performance review for Marcus, a senior engineer who shipped three major features on time but has a pattern of not updating the team Slack during development. His work is high quality, but his communication during the process creates surprises for project managers. He's direct and sometimes abrupt in team meetings. He's receptive to feedback and made improvements mid-year. Overall, we want to keep him and see him grow into a leadership role. Tone: balanced, specific, constructive. Include one concrete example. Avoid generic praise. Highlight the growth area as something learnable, not a character flaw."

AI output (better):
"Marcus delivered strong technical work this year, three features shipped on schedule, all meeting our quality standards. His engineering judgment is mature and reliable. Where Marcus has an opportunity to grow is in proactive communication. During the Q2 feature release, Marcus didn't update the project Slack until he was finished, which created last-minute surprises for the PM and marketing team. He recognized this pattern and adjusted mid-year, which we appreciated. As Marcus moves toward a potential tech lead role, this skill, keeping collaborators informed without waiting for a finish line, will be critical. This is entirely learnable, and Marcus has already shown he can adapt. Let's build on this momentum."

Better? Yes. Specific? Yes. Actionable? Yes.

Next iteration (if needed):
You might ask: "That's good, but can you make it shorter? It's too formal in tone. Can you sound more like a direct peer giving feedback?" And you'd get another version. This is normal. This is workflow.

The Before-and-After Pattern: Job Descriptions

Let's walk through a real HR task: writing a job description.

Weak prompt (what most people do):
"Write a job description for a human resources manager."

Weak output:
"We are seeking an experienced Human Resources Manager to join our dynamic team. The ideal candidate will have 5+ years of HR experience and a strong background in employee relations, recruitment, and compliance. You will be responsible for managing HR operations, recruiting new talent, overseeing employee benefits, and ensuring compliance with employment law. Must have excellent communication skills and be detail-oriented. We offer a competitive salary, benefits package, and opportunities for career growth."

This is a copy-paste template from a resume database. It's forgettable. It doesn't tell the candidate anything about who you are or why they'd want to work for you.

Strong prompt (what you should do):
"I need a job description for an HR Manager role at our company. Here's what you need to know: We're a 120-person IT consulting firm. We're growing fast (we hired 15 people last quarter). This HR Manager will be the second person in the HR function, reporting to the VP of People, who handles strategic stuff. This role is hands-on: you'll own recruiting end-to-end, handle employee relations, manage benefits and payroll administration, and support onboarding. The person needs to be comfortable with ambiguity (we're still building our systems) and be a problem-solver. Our culture is collaborative, direct feedback is normal, and people work hard but we respect boundaries. We're remote-first. Tone: authentic, warm but not cheesy, honest about the role being scrappy in some ways. Length: 500-600 words. Structure: compelling opening paragraph that captures why someone would want THIS job (not just any HR job); list actual responsibilities with brief context; required qualifications (be realistic. We'd rather have 3 years of actual HR experience than 10 years of title inflation); nice-to-haves; why you'd love working here (again, be honest). Avoid: corporate buzzwords, 'fast-paced environment,' generic HR templates."

Strong output (examples):
"We're hiring our second HR person, and we're looking for someone who actually enjoys solving real problems. [Continues with specific, authentic, compelling language about the role and company.] This is a chance to build something from the ground up, not to manage someone else's system, but to shape how we support and develop people as we scale."

Notice what changed:
- Context (company size, growth stage, reporting structure) shapes the output
- Specificity (naming the growth rate, the reporting structure) makes it believable
- Honest tone (acknowledging the scrappiness) builds trust
- Constraints (length, tone, structure) mean less rewriting

Advanced: Providing Examples (The Few-Shot Technique)

Once you're comfortable with the anatomy of a prompt, here's a pro move: show AI examples of what you want.

Say you want to draft recruiting emails in a specific style. Instead of describing your style in words (which often sounds dumb when you try to articulate it), just show examples.

Prompt with examples:
"I'm going to share three recruiting emails that landed interviews with strong candidates. Study the tone, the level of personalization, the length, the structure. Then draft a similar email to a Senior Data Engineer I found through our alumni network. Here are the examples: [paste three real emails that worked]. Now draft one to David, who worked at TechCorp and graduated from State in 2020."

By showing three real examples, you've taught AI your style better than you could describe it. This is called "few-shot prompting," and it's incredibly powerful in HR contexts.

Tip: Keep a "swipe file" of good HR outputs, recruiting emails that got responses, policies that felt clear, review feedback that hit the mark. When you need something new, include an example of the style you want. AI learns from examples faster than from descriptions.

Constraints: The Often-Forgotten Fourth Element

Many HR professionals skip constraints because they seem optional. They're not. Constraints are what transform a mediocre output into a usable one.

Constraints include:
- Length: "under 250 words," "1-2 paragraphs," "no more than 3 bullet points"
- Tone: "warm but professional," "direct, no jargon," "formal and compliant"
- Audience: "for non-technical employees," "for executive leadership," "for a 22-year-old entry-level candidate"
- What to avoid: "no corporate speak," "don't mention salary," "don't assume experience level"
- Format: "bullet points," "table with three columns," "Q&A format"

Example: "Write an email to employees announcing a benefits change. Constraints: We're removing a benefit employees loved. The email must be honest about why (budget, utilization was low). Tone: transparent, empathetic, not defensive. Length: under 200 words. Structure: explain what's changing, explain why, explain what we're doing instead, invite questions. Avoid: corporate spin, vague language, lengthy justifications that read as excuses."

Constraints force AI to produce usable output instead of verbose corporate-speak.

Important: If you don't set constraints, AI will produce the longest, most formal version possible. Constraints move output toward usable.

Try This Now: Three Exercises

Exercise 1: Rewrite a Weak Prompt

You're hiring a Customer Success Manager. You ask AI: "Write a job description for a Customer Success Manager."

Take 10 minutes and rewrite this prompt using the four-element framework. Include:
- Context (company, size, what does this person report to)
- Task (what output do you want)
- Constraints (length, tone, what to avoid)
- Format (how should it be structured)

Write it as if you're explaining the role to a smart friend. That's your prompt.

Exercise 2: From Template to Specific

Recruiting email template (weak): "We'd like to reconnect with you about a new opportunity we think matches your background."

Rewrite this as a specific prompt for AI. Include:
- Why you're contacting this person
- What the role actually is
- What you want the tone to feel like
- What length makes sense
- One example of something you DON'T want

Exercise 3: The Iterative Loop

• Step 1: Ask AI a vague HR question (write a diversity statement, draft a layoff email, create a 30-60-90 plan template). Copy the first output.
  - Step 2: Read it. What's missing? What's too generic? What's off-tone? Write down 2-3 things you'd change.
  - Step 3: Go back to AI and ask it to adjust based on your feedback. Notice what happens.

This is the workflow you'll use every day. The first output is never final. The iteration is where your time goes, and where quality comes from.

Practical Application - "What to Do Monday Morning"

• 
  Audit one HR task you do repeatedly (job descriptions, recruiting emails, performance review templates, onboarding checklists). Notice how vague your current approach is.
• 
  Write out the four elements for that task: What context does AI need? What's the exact task? What constraints matter? What format makes sense?
• 
  Save this as a template. Next time you do this task, start with this template instead of a blank page.
• 
  Test it. Paste the prompt to AI. If the output is 80%+ usable, keep the prompt. If it's not, refine it and test again.
• 
  Collect your best prompts. Over the next month, save 3-5 prompts that produce output you actually use. These become your library.

Key Takeaways

• Specify context: AI can't read minds. Tell it what it needs to know about your company, role, and situation.
  - Be explicit about task and constraints: Vague prompts produce vague output. Be specific about length, tone, and format.
  - Iterate, don't expect perfection: The first output is a draft. Refine based on what's missing or off.
  - Show examples when you can: Providing 2-3 good examples teaches AI your style better than descriptions.
  - Test with real work: If a prompt produces usable output, save it. Build a library of working prompts.

FAQ

Q: How long should my prompt be?
A: As long as it needs to be, but usually 150-400 words. You're not writing a novel. You're being specific. If your prompt is over 600 words, you're probably overthinking it.

Q: Should I always follow this four-element structure?
A: It's a framework, not a law. Some prompts need all four elements emphasized. Some are simpler. But when output is bad, it's usually because you're missing one of these elements.

Q: What if I don't know how to describe what I want?
A: Show examples instead. "Here are three recruiting emails I liked, draft one like these" is often clearer than trying to describe your tone.

Q: Does the AI remember previous prompts?
A: Only within a conversation thread. Each new conversation starts fresh. If you want consistency, you need to include the context and constraints every time (or use system prompts, that's a later lesson).

Q: What if my prompt is perfect but the output is still bad?
A: The AI has limits. Some tasks are outside its competency (analyzing your specific company data, knowing your internal policies, making decisions that require judgment). This is covered in Lesson 1.4 (When to Trust and When to Override).

What's Next

Now that you can ask clear questions, Lesson 1.2 is about recognizing what "useful" actually means in HR contexts. A technically correct job description can still be tone-deaf. A grammatically perfect recruiting email can still get deleted. You'll learn how to evaluate whether AI output is actually ready to use, or just a starting point.