AI for HR.
AI will not replace your judgment about people, your read of a team's health, or your accountability for decisions that change someone's livelihood. It will absolutely replace the hours you spend writing job descriptions, drafting the same policy for the fifth time, building an interview question bank, and turning a pile of survey responses into a readable summary. This handbook is the practical middle ground: where AI genuinely helps HR, the three rules that keep it fair and legal, and five workflows you can use this week — with anti-discrimination and the no-automated-decision line front and center, because that's where the real risk lives.
Where AI actually helps — and where it doesn't
The single most useful mental model: treat AI like a fast, tireless HR coordinator who drafts well, has no judgment about people, can quietly encode bias, and must never make a decision that affects someone's job. You'd happily hand that coordinator a job-description draft or a survey summary. You would never let it decide who gets hired, promoted, or let go.
| Task | Verdict | Why |
|---|---|---|
| Job descriptions & postings (bias-checked) | Excellent | Fast drafts; you review for inclusive, non-discriminatory language |
| First-draft policies, handbooks, process docs | Excellent | Structure and starting points you verify against law and your org |
| Interview question sets & structured rubrics | Strong | Consistent, job-relevant questions — which improve fairness |
| Internal comms & announcement drafts | Strong | Tone and clarity; you add facts and human sensitivity |
| Summarizing anonymized survey / feedback data | Strong | Themes and signals from data you provide — you sanity-check |
| Screening, ranking, or scoring candidates — unaudited | Never unaudited | Encodes and scales bias; legal exposure — see Rules 1 & 2 |
| Hire, fire, promote, or discipline decisions | Never automated | A human decides and is accountable — see Rule 1 |
The three non-negotiable rules
Rule 1 — AI never makes a consequential decision about a person. A human decides.
Hiring, firing, promotion, discipline, and pay are decisions that change people's lives, carry legal and ethical weight, and require context and accountability an AI cannot hold. AI may help you draft and organize, but it must never make — or effectively make, by producing a score or ranking you rubber-stamp — a consequential employment decision. A human evaluates, decides, and owns it. If a tool's output becomes the decision, you've handed a life-altering judgment to software that doesn't understand the person, the context, or the law.
Rule 2 — Actively guard against discrimination and bias. This is the big legal risk.
AI learns from historical data, and historical hiring data encodes historical bias — a well-known recruiting tool learned to penalize resumes containing "women's," and screening models can produce disparate impact on protected groups. The employer stays legally responsible regardless of the tool, and regulation is arriving fast: NYC Local Law 144 requires bias audits and disclosure for automated hiring tools, the EU AI Act classifies hiring AI as high-risk, and the EEOC has issued guidance. The discipline: any AI touching candidate selection must be validated, bias-audited, transparent, and human-reviewed — and job descriptions and rubrics get checked for biased or exclusionary language before use.
Rule 3 — Candidate and employee data is sensitive and protected.
HR holds some of the most sensitive data in the company — applications, salaries, health and accommodation information, performance and disciplinary records, complaints. Free and consumer AI tools may retain what you paste and train on it, and this data is protected by privacy and employment laws (and often consent obligations). The discipline: use enterprise tools with contractual no-training and retention commitments, anonymize wherever possible (summarize feedback without names), and never paste identifiable employee records — especially health, disciplinary, or complaint data — into a consumer chatbot.
Five workflows you can use this week
Each recipe: what to give the AI, what to ask, and what you must verify by hand. The prompts are starting points — keep the bias-check and data-privacy discipline.
1 · Job description (inclusive & bias-checked)
- Give the role, must-haves, and an explicit inclusivity instruction:
2 · Structured interview questions and rubric
- Give the role and the competencies you're assessing:
3 · First-draft policy or handbook section
- Give the topic, your org context, and jurisdiction:
4 · Summarize anonymized survey or feedback data
- Provide the data with names and identifiers removed (Rule 3):
5 · Draft internal communications
- Give the message, audience, and tone — no sensitive individual data:
The judgment exercise: spot the danger
Three scenarios from real practice patterns. Pick what you'd do — the point is calibrating when the rules bite.
1. A vendor's AI tool scores 400 applicants and hands you a ranked shortlist of 20. It'll save days. Do you interview the top 20 and reject the rest?
Rules 1 & 2. An AI ranking that becomes your shortlist is an automated employment decision, and screening models can produce disparate impact on protected groups that you remain liable for (see NYC Local Law 144's audit requirement, the EU AI Act's high-risk classification). "Objective" is exactly the false comfort — the tool learned from biased history. Require validation and bias audits, keep a human in the loop, and don't let the ranking be the decision.
2. To get a second opinion on a termination, you paste an employee's full performance file — with complaints and a medical note — into a free chatbot. OK?
Rules 1 & 3. Performance files, complaints, and especially medical information are among the most sensitive, regulated data you hold; a consumer tool may retain and train on it, and removing just the name rarely de-identifies a specific case. And a termination is a consequential human decision, not one to outsource to a chatbot. Use proper channels and human judgment.
3. The AI-drafted job posting asks for a "young, energetic digital native who's a great culture fit." It reads upbeat. Post it?
Rule 2. "Young" and "digital native" are age-coded language that can deter or screen out older applicants (age is protected), and "culture fit" is a well-known vector for bias. "Youthful" doesn't fix it. Describe the required skills and the actual work in neutral, inclusive terms — the model will happily produce biased language, so reviewing for it is your job.
Choosing tools: the questions that matter
You don't need to understand the technology to procure it well. You (or your legal team) need answers, in writing, to five questions:
| Question | Answer you want |
|---|---|
| Is our candidate/employee data used to train your models? | No, contractually — not "you can opt out somewhere in settings" |
| For any selection tool: is it bias-audited and validated? | Yes, with documentation you can rely on and disclose |
| How long is our data retained, and can it be deleted? | Defined, short, deletable on request |
| Compliance with hiring-AI and privacy law? | Yes, with support for your audit/disclosure obligations |
| Security posture and access controls? | SOC 2 Type II or equivalent, encryption, admin/audit controls |
General-purpose enterprise AI (Claude, ChatGPT's business tiers) covers the drafting and summarizing recipes here — none of which make decisions about people. Recruiting/HRIS AI that screens or scores candidates is a different, higher-risk category requiring bias audits, validation, transparency, and legal review before deployment. And if your org has an AI or hiring policy, it precedes everything here; if it doesn't, these three rules are a reasonable seed for one.
Quick answers
Can I use AI to screen resumes?
Only with a validated, bias-audited, transparent, legally-reviewed tool and a human in the loop — never as an unchecked filter. Employers are liable for disparate impact regardless of the tool, and regulation (NYC LL144, EU AI Act) is tightening.
Can AI write a performance review?
It can draft or structure feedback from documented notes you provide, but the assessment and any decision are the manager's — AI must not score, rank, or decide who is managed out.
What HR data can go into AI tools?
Keep identifiable employee/candidate data — especially health, disciplinary, and complaint data — out of consumer tools. Use enterprise tools with no-training terms and anonymize wherever possible.
Where should a skeptical HR pro start?
Recipe 1 — drafting an inclusive job description, then reviewing it for biased language. Immediately useful, and it builds the exact muscle (spotting bias in AI output) the rest of the work depends on.
Related on Vibe Engines
Explore the topic
See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.
More Handbooks
- The Prompting HandbookA friendly, hands-on field guide for everyday humans — learn the CRISP framework, spot bad prompts, practice with real recipes, play a drag-and-drop game, and test yourself with a quiz. No code required.Read →
- The Agentic AI Interview HandbookTwenty topics every senior AI engineer should be able to reason about live — from eval pipelines to reliability patterns for generative systems.Read →
- The Senior AI Engineer Interview Handbook60 questions across architecture, production incidents, agentic systems, RAG, evals, cost, safety, and leadership — what staff-level AI interviewers actually probe for.Read →
- 50 Angular Interview QuestionsA visual handbook covering components, change detection, RxJS, signals, routing, forms, performance, and testing — what interviewers actually probe for in senior Angular roles.Read →
- 50 Python Interview QuestionsFundamentals to advanced: data structures, OOP, iterators & generators, the GIL, asyncio, memory, testing, and the standard library — a visual walk through everything a Python interview touches.Read →
- 51 LLM Evals Interview QuestionsGolden sets, LLM-as-judge, regression testing, offline vs online evals, RAG evals, agent evals, red-teaming, and observability — demystified for interviews and production.Read →
Explore more from Vibe Engines
Get the next one in your inbox.
New handbooks, system-design walkthroughs, and tools — straight to your inbox. No spam, unsubscribe anytime.