How to screen job applications and prep for interviews with Claude
Use Claude to collect applications into one table, compare candidates on the same criteria, and build interview questions tailored to each person. Step by step, with ready prompts.
Hiring drains a small team as much as sales, but the payoff is slower to show. A single opening can pull in dozens of applications, and half a day disappears just reading them to decide who is worth a call. Claude, the AI assistant from Anthropic that runs at claude.ai, helps you move through that pile faster without flattening real people into spreadsheet rows. Here is how to do it, step by step.
Why does screening applications eat so much time?
Resumes arrive in every shape: a PDF here, a plain message there, a link to a profile somewhere else. Your eye latches onto formatting instead of substance, and you quietly favor whoever laid out a pretty document over whoever actually fits. By the bottom of the stack your standards have drifted, the first candidate got judged harder than the twentieth. Claude keeps one frame for everyone, because it applies your criteria to each application the same way.
How do you turn resumes into one table in minutes?
Open Claude, attach the resume files (several at once is fine), and give it a plain prompt, which just means a text instruction for the AI:
"Here are resumes for a sales manager role. Put them in a table: name, years in sales, any experience in our niche, key achievements with numbers, salary expectations if stated. If something is missing from a resume, write a dash, do not invent it."
That last sentence matters. Without it the model may fill in things the document never said. A minute later you have a table that already shows who clearly misses on experience and who deserves a careful read.
How do you compare candidates on the same criteria?
A table is not enough, you need a judgment. Describe what matters to you and ask Claude to place candidates along those axes:
"Rate each candidate from 1 to 5 on three criteria: experience in our niche, independence (can they run a deal without hand-holding), and concreteness of results (real numbers, not vague claims). After the scores, explain in two lines why you gave them. Do not inflate, if the data is thin, score lower."
Keep one thing in mind: Claude's score is a draft, not a verdict. It sees only the text of a resume, not the person. Its job is to shrink a stack of thirty down to the five you will actually talk to.
How do you build questions for a specific person?
A generic question list off the internet tests nothing. Give Claude one candidate's resume and ask:
"From this resume, write five interview questions. Each question must test a specific claim in the resume, not a general trait. If they say they grew the team's revenue, the question should dig into what exactly they did and what was the team's credit."
Now the conversation follows what the person wrote about themselves, not a template. A rehearsed story cracks fast under questions like these.
What should you ask to test real experience, not scripts?
Ask Claude for questions that cannot be answered with generalities: about a concrete failure and the lesson from it, about a time they had to push back on a manager, about how they measured their own results. A solid prompt:
"Give three questions that separate someone with real experience from someone retelling other people's cases. The questions must demand detail: numbers, process names, the sequence of steps."
Answers to those reveal quickly whether there is practice behind the words.
How do you avoid leaking candidates' extra data?
A resume is another person's personal data. Do not paste passports, full addresses, or phone numbers into the chat if they are not needed for the assessment, experience and results are enough. Strip anything work-irrelevant from the file before you upload it. That way you respect the applicant and cover yourself at the same time.
Where do you start right now?
Take the last batch of applications you never got around to reading and run it through the three prompts above: table, scores, questions. Half an hour instead of half a day. If you want to learn to build prompts for your own tasks instead of copying someone else's, start with our free materials: the AGINE guides and the first free lesson, where in one evening you assemble a working assistant for hiring. It is easiest to work right inside claude.ai, where you can attach files and keep the whole review in a single chat.
AGINE Academy is an independent product, not affiliated with Anthropic. Claude is owned by Anthropic.
Questions
No. It works only from the resume text and never meets the person. Its role is to narrow a long list to a few candidates and flag what to check in the conversation. The decision and the interview stay with you.
It can, unless you forbid it. Add a line to every prompt like "if the data is missing, write a dash and do not guess." Then the table reflects only what the person actually wrote.
Upload only what the assessment needs: experience, results, skills. Remove passport data, full addresses, and phone numbers first, they are not part of the shortlisting.
Yes. Swap the criteria in the prompt for your role: one set of axes for an accountant, another for a designer. The table, scores, questions flow fits any opening.