Humanity AILet's talk
← Back to all posts
Practical AI
August 21, 20266 min read

The Best Use of AI in Hiring Isn't Screening Resumes

Open a job board and read ten postings in a row. They're the same posting. "Fast-paced environment." "Wear many hats." "Competitive salary DOE." Nobody wrote those words on purpose. They got copied from the last one, which got copied from the one before that.

Now flip to the other side of the desk. Applications are arriving polished, keyword-matched, and tailored to your exact posting, because candidates have the same AI tools you do. The tell you used to rely on, that a cover letter showed effort, doesn't tell you much anymore.

So most owners do the obvious thing: they point AI at the resume pile and ask it to rank the candidates. That's the one part of hiring where AI is weakest and the stakes are highest. The real payoff sits on either side of that pile, in work that's tedious, repeatable, and invisible when it's done badly.

Why the resume pile is the wrong target

Three reasons, and they're worth understanding before you decide where to point the tool.

Resumes measure resume-writing. They always did. Now that both sides are using AI, a strong-sounding resume tells you even less about the person than it used to. Ranking them more efficiently just gets you to a confident wrong answer faster.

The model has no idea what you actually need. It hasn't met your team, doesn't know that the last three people who failed in this role failed for the same reason, and can't tell that the "unrelated" job on someone's history is exactly the experience that matters. It fills that gap with generic assumptions about what a good candidate looks like.

Automated rejection carries real risk. Screening tools that filter people out have drawn legal and regulatory scrutiny, because patterns in training data can quietly disadvantage certain applicants. Rules vary by state and are still changing. If you're going to be careful anywhere with AI, be careful about a machine deciding who never gets a call back.

None of that means close the laptop. It means aim it somewhere better.

Use AI on the parts of hiring that are writing and thinking. Keep the parts that are judging people.

Step one: write down what "good" actually means

This is the step almost everyone skips, and it's the reason the rest of the process goes sideways. If you can't describe the person you need, you'll recognize them only by vibe, and vibe is how you end up hiring someone who interviews well and struggles for six months.

AI is genuinely good here, not because it knows your business, but because it's a patient interviewer that makes you say the quiet part out loud. Try this:

"I'm hiring a [role] for my [type of business]. Interview me one question at a time until you understand what this person will actually do day to day, what would make them great versus merely fine, and what has gone wrong in this role before. Then give me a one-page scorecard: the five outcomes this person owns, the three must-have skills, and three things that are nice to have but not dealbreakers."

The value is in the questions it asks back. "What does this person do in their first ninety days?" is a question a lot of owners have never answered on paper. This is the same principle behind why you can't automate what you can't explain. Vague inputs produce vague results, whether you're building a workflow or filling a seat.

Now you have a scorecard. Everything downstream measures against it.

Step two: write a job post that repels the wrong people

A good job post isn't a sales pitch. It's a filter. You want the right forty applicants, not four hundred.

Feed your scorecard in and ask:

"Turn this scorecard into a job post that sounds like a real person wrote it. Be specific about what the work actually involves, including the unglamorous parts. No corporate filler, no 'fast-paced environment,' no 'rockstar.' Include a short section on who this job is NOT a good fit for."

That last instruction does the heavy lifting. A posting that says "if you need a highly structured week with the same tasks every day, this isn't it" saves you a dozen mismatched interviews. Being honest about the hard parts up front is not a weakness in the ad. It's the whole point.

Step three: replace resume ranking with a short work sample

Here's the swap that changes your hiring quality most. Instead of asking AI who looks best on paper, use it to build one small, realistic task that shows you how someone thinks.

"Based on this scorecard, design a 20-minute task a candidate could complete that would reveal whether they can actually do the core of this job. It should reflect real work, not a puzzle. Tell me what a strong answer looks like versus a weak one."

A twenty-minute sample tells you more than an hour of resume study. Keep it short and respect people's time. If it takes longer than half an hour, you're asking for free labor, and good candidates will pass.

And notice what AI did there. It didn't evaluate anyone. It built the ruler. You still do the measuring.

Step four: interview against the scorecard, not off the cuff

Unstructured interviews mostly measure how much the interviewer enjoyed the conversation. Structured ones, where every candidate gets the same core questions tied to the same criteria, are harder to run and much more useful.

"For each must-have on this scorecard, write two behavioral interview questions that ask for a specific past example, plus the follow-up I should ask if the answer stays vague. Then give me a simple 1 to 5 rating guide for each."

Print it. Use the same sheet for everyone. When you compare candidates a week later, you'll be comparing evidence instead of memory.

If the hiring conversation itself is the part you dread, whether that's a tough interview or the offer negotiation, you can rehearse it with AI first the same way you'd rehearse any hard conversation.

Step five: the follow-through nobody has time for

This is where AI quietly wins back hours, and it's the least glamorous part of the list.

  • Debriefs. Dump your messy interview notes in and ask for them to be organized against the scorecard criteria, with gaps flagged as questions to ask next round.
  • Candidate updates. Draft the "we're still deciding, here's our timeline" note you keep meaning to send. Silence is how you lose your second-choice candidate while you're deciding on your first.
  • Rejections that don't sting. Short, warm, specific enough to feel human. You will hire from this pool again someday.
  • The first week. Ask for a thirty-day onboarding outline based on the scorecard outcomes. Most turnover in small businesses starts with a first week nobody planned.

None of this is exciting. All of it is the difference between a hiring process that feels professional and one that feels like a scramble. It's a good example of handing off the task instead of automating it, since you're still reviewing every word before it goes out.

The line I'd draw

Let AI write, organize, structure, and prep. Do not let it decide.

Concretely, that means no auto-rejecting, no "score these fifty resumes and show me the top five," and no feeding a candidate's personal information into a tool without thinking about where that data goes. If a candidate is a maybe, that's a call for you to make, not a number to outsource. This falls squarely into the category of knowing when not to use AI, which is its own skill.

Also worth saying plainly: AI doesn't replace the hiring manager. It clears the writing and the paperwork off your desk so you have the attention left over for the ninety minutes that actually matter, which is time spent with the person in front of you.

If you only do one thing

Skip the rest and run step one. Spend fifteen minutes letting AI interview you about the role until you have a written scorecard.

Most bad hires trace back to a job nobody defined. Fix that upstream and everything after it, the posting, the questions, the decision, the first week, gets easier on its own. It's the cheapest fifteen minutes in the whole process.

If you're trying to figure out where AI actually fits in your business, hiring is a good place to start, because the work is repetitive, high-stakes, and almost never documented. That's exactly the kind of problem we help people untangle at Humanity AI.

FAQ

Should I tell candidates I used AI to write the job post?

You don't need to disclose that you drafted a posting with AI any more than you'd disclose using spell check. What matters is that the posting is accurate. If you use AI anywhere in evaluating candidates, be aware that some states now have disclosure and audit requirements, so check your local rules.

Can AI screen resumes at all?

It can organize them, pull out specific facts you ask for, and flag which ones mention a required certification. That's sorting, and it's fine. Ranking humans by overall quality is where it goes wrong, and where the legal exposure sits.

Everyone's applications look AI-polished now. How do I tell candidates apart?

Stop grading the writing and start watching the work. A short, realistic task and a structured interview both measure things a chatbot can't produce on someone's behalf.

What if I'm only hiring one person a year?

The scorecard step matters more, not less. When you hire rarely, you have no recent muscle memory, and a written definition of the role is the only thing keeping the decision honest.

Want to talk more?

Tell me what's on your mind and I'll take a look. No pressure, no obligation, just a real conversation about your business.

Let's talk