Claude for recruiters: CV review, interview notes and reports

By Screened · Updated 13 October 2026

A CV says “supported renewals”. The role needs someone who can lead renewal negotiations. Those statements are not equivalent, but a rushed shortlist might treat them as though they are.

Claude can help a recruiter read source material more carefully. Give it the approved job requirements and relevant, permitted application details, then ask it to separate what the candidate actually describes from what remains unclear. That produces a useful follow-up question, not a made-up qualification.

The same approach helps when a hiring brief has changed but the interview plan has not, when screening notes need a handover, or when an ATS report makes a stronger claim than its numbers justify.

Follow one account-manager vacancy through CV review, role documents, interview preparation and reporting. It includes the source material, prompts, example outputs and checks a recruiter should make before using the result. Claude assists the review; the recruiter remains responsible for the evidence and hiring recommendations.

What is Claude, and where does it fit in recruiting?

Claude is an AI assistant from Anthropic. It can work in conversations, read files, organise material in Projects and use connected tools where those features are available.

Some accounts still use the name Cowork for longer file-and-tool tasks, while Anthropic is moving toward a more unified Claude experience. You do not need to understand that product history to begin. A normal conversation is enough for the first exercises.

For recruiters, Claude becomes particularly useful when there is a source pack rather than one isolated sentence:

• a current role brief and several older drafts;
• a CV plus screening notes;
• an interview plan and scorecards;
• an ATS export whose fields need to be understood before calculation;
• several candidate messages that need consistent but factual replies.

A Project is useful when you will keep returning to the same role and documents. A connection becomes useful when the task needs current ATS records rather than a dated file. Anthropic’s current overview is in its getting-started guide.

Read one CV passage without changing its meaning

Consider this sample CV passage:

I scheduled customer-training sessions using dates supplied by account managers. I checked attendance and sent reminders. When customers asked to change their subscription terms, I passed the request to the account manager. I did not negotiate renewals.

The role requires experience leading renewal negotiations.

Prompt

Review this sample CV passage against the job requirement provided.

Job requirement
The person must have experience leading customer-renewal negotiations.

CV passage
“I scheduled customer-training sessions using dates supplied by account managers.

I checked attendance and sent reminders.

When customers asked to change their subscription terms, I passed the request to the account manager.

I did not negotiate renewals.”

Show:
- what the applicant says they did
- what the account managers did
- what the passage establishes about the requirement
- what it does not establish
- one neutral follow-up question

Quote the words supporting each important point. Do not turn support work into leadership or make a hiring recommendation.

Example output

What the passage establishes

The applicant has customer-coordination experience connected to accounts and renewals.

What it does not establish

Experience leading renewal negotiations.

Possible follow-up

Have you led renewal or contract discussions in another role? What were you responsible for?

Now change the final sentence to:

I supported renewals.

The interpretation should change. The applicant no longer explicitly says they did not negotiate. Their responsibility is unclear.

A useful summary says “not established,” not “never did it.”

That distinction is central to good recruiting work:

A question you still need to ask is not the same as negative evidence.

Expand the task to several requirements

Use one row per current requirement.

For each row, quote the strongest passage, explain the applicant’s personal responsibility and state what remains unknown.

Do not force every requirement into match or miss.

Use screening notes instead of the CV

Use the transcript or checked notes as the source. Keep the candidate’s exact statement separate from the recruiter’s interpretation.

Compare two apparently similar applicants

Use the same current requirements and the same output structure for both applicants. Do not create a ranking. Show where one source is clearer than the other.

The comparison can reveal that one CV is easier to interpret without proving that the person is a better candidate.

Check the source pack before asking for a polished answer

Recruiting documents change.

A manager updates the brief. The advert retains an older requirement. The interview plan still tests the previous version of the role. An applicant’s PDF contains an image-only page Claude cannot read.

A polished answer can still be wrong when it starts from the wrong source.

Suppose you have:

• role-brief-v3.pdf — approved 1 October;
• job-advert-draft-v4.docx — proposed 4 October;
• interview-plan-v2.docx — approved 28 September;
• manager-notes-7-oct.txt — discussion, not approval;
• application-A331.pdf.

Prompt

Before preparing an interview brief for job J-20, inspect the files in this source pack.

Current source of truth
role-brief-v3.pdf, approved 1 October 2026

Files
- role-brief-v3.pdf
- job-advert-draft-v4.docx
- interview-plan-v2.docx
- manager-notes-7-oct.txt
- application-A331.pdf

Return a source map showing:
- each file you can read
- its visible date or version
- what it contributes
- whether it is approved, proposed or unclear
- unreadable pages or missing attachments
- conflicts with the current role brief

Do not prepare the interview brief yet. Do not treat the newest file as approved automatically.

Example output

This answer prevents Claude from producing a beautiful interview brief from the wrong version of the role.

Make the source map useful over time

When the vacancy will be used repeatedly, create a Claude Project and keep the approved documents easy to identify. Add a short decision log rather than expecting Claude to infer approval from file dates. See Claude Projects.

When files conflict:

Do not merge the conflicting wording. Show the exact difference and ask which version should govern the task.

When a document is unreadable:

Name the unreadable page or attachment and explain which part of the requested output may be incomplete because of it.

The source check is not administrative filler. It protects every answer that follows.

Draft a clearer job description without quietly changing the job

Claude can turn a rough role brief into readable candidate-facing language.

The risk is that it “improves” the role by adding qualifications, outcomes or benefits that were never approved.

Suppose the approved brief says:

• lead customer renewals;
• identify account risks early;
• involve product specialists where needed;
• work within pricing authority;
• product knowledge can be taught.

The manager adds:

Make it sound senior. We want someone commercial and strategic.

Prompt

Draft a clear job description from the approved role brief and manager notes below.

Approved role brief
- Lead customer-renewal discussions.
- Identify account risks early.
- Involve product specialists when product issues affect the account.
- Work within agreed pricing authority and seek approval for exceptions.
- Product knowledge can be taught after joining.

Manager notes
“Make it sound senior. We want someone commercial and strategic.”

Write:
- a short role summary
- responsibilities
- genuine day-one requirements
- skills the team has agreed to teach

Use plain English and describe the actual work.

Do not invent salary, benefits, location flexibility, qualifications or years of experience. Put unresolved questions outside the candidate-facing draft.

Example output

Role summary

You will lead renewal planning for a portfolio of enterprise customers. You will identify risks early, coordinate the right internal specialists and lead customer discussions within agreed commercial limits.

Responsibilities

• Review account evidence and identify renewal risks before the contract end date.
• Build and coordinate a renewal plan.
• Lead renewal discussions with customers.
• Involve product or support specialists when an issue affects the renewal.
• Make commercial decisions within agreed authority and prepare recommendations for exceptions.
• Keep account handovers and renewal records current.

Day-one requirements

• Experience leading customer or contract discussions.
• Evidence of identifying account risk and coordinating other teams.
• Judgement about when to decide independently and when to seek approval.
• Clear written and spoken communication in customer-facing work.

We can teach

• The company’s product.
• Internal systems and CRM.
• The organisation’s pricing and approval process.

Decisions still needed

• Portfolio size and contract complexity.
• Exact commercial authority.
• Whether people management is part of the role.

The output sounds senior because the responsibility is senior—not because Claude added tenure or prestige.

Change the output for another purpose

For a shorter advert:

Keep the summary to 80 words and the responsibilities to six bullets. Do not remove the decision boundaries.

For an intake meeting:

Do not draft the advert. Return only the unresolved decisions that would change sourcing or assessment.

For a job-board version:

Use candidate-facing language and remove internal process terminology. Keep every factual promise tied to the source brief.

Turn rough screening notes into evidence another person can use

A screening call produces notes such as:

Did renewals, enterprise, worked with product. Account director handled pricing. Good communicator. Not sure how much owned.

A fluent rewrite could hide the uncertainty:

Led enterprise renewals and coordinated cross-functional stakeholders.

Claude is useful when you ask it to separate the roles rather than write a stronger story.

Prompt

Rewrite these screening notes for application A-331.

Current role requirements
- lead renewal discussions
- identify account risk early
- involve product specialists when needed
- work within commercial authority

Source notes
“Did renewals for enterprise accounts.

Mostly prepared usage data and joined customer calls.

Account director handled pricing.

Candidate said they flagged a product issue once and got product involved.

Not sure how much owned.

Good communicator.”

Organise the record into:
- relevant experience described
- candidate’s own actions
- colleagues’ actions
- limits on the candidate’s authority
- what remains unclear
- useful follow-up questions

Keep the candidate’s statements separate from interpretation. Do not turn “joined” into “led,” invent an outcome or assign a rating.

Example output

Relevant experience described

• Worked on enterprise-account renewals.
• Prepared usage data.
• Participated in customer calls.
• Described flagging a product issue and involving the product team.

Candidate’s own actions

• Prepared usage information.
• Joined customer calls.
• Identified at least one issue that needed product-team input.

Colleagues’ actions

• The account director handled pricing.

Limits on authority

• Commercial authority was not described.
• The example suggests the account director owned pricing.

Still unclear

• Whether the candidate led a renewal conversation.
• Whether they decided when to involve product specialists.
• What happened after the product issue was escalated.

Follow-up questions

1. “Tell me about a renewal call you personally led.”
2. “How did you decide product input was needed?”
3. “What commercial decisions could you make yourself?”

“Good communicator” disappears because the source does not explain the work behind the impression.

Turn the note into a manager handover

Use three headings: Why continue the conversation, What is still unclear, What to ask next. Keep the source references.

Turn it into a concise ATS note

Keep the note under 180 words. Include the job and application ID. Put unresolved questions in the final sentence.

Preserve contradictions

When two notes disagree, quote both. Do not blend them into a compromise statement.

Build a screening call that fits the time

A 20-minute recruiter call cannot contain 15 behavioural questions, role history, logistics and candidate questions.

Claude can help turn a long list into a realistic conversation.

Prompt

Prepare a 20-minute screening guide for the Senior Account Manager role.

Current requirements
- lead renewal discussions
- identify risk early
- coordinate internal specialists
- work within commercial authority

Later stages will assess:
- detailed account strategy
- written handover
- technical product judgement

Create a practical call plan with:
- opening and role context
- no more than four assessment questions
- neutral follow-ups
- practical questions
- time for the candidate’s questions

For every assessment question, explain what it is trying to establish.

Do not repeat later interviews without a clear reason. Do not claim the questions are validated.

Example output

Question 1

“Tell me about a renewal discussion you personally led.”

Establishes: direct responsibility for the core work.

Follow-up: “What did you decide, and what needed approval?”

Question 2

“Describe a renewal risk you noticed before the customer raised it.”

Establishes: early risk identification.

Follow-up: “What evidence made you concerned?”

Question 3

“Tell me about a time a product or service issue affected an account.”

Establishes: judgement about involving specialists.

Follow-up: “Why did you involve that team at that point?”

Question 4

“What commercial decision could you make yourself in your last role?”

Establishes: understanding of authority and escalation.

The guide fits the available time. That is more useful than a comprehensive-looking question bank nobody can finish.

Understand an unfamiliar role without turning every term into a requirement

A recruiter working on a new technical or specialist role may not know which words are essential and which are merely common in one company.

Claude can create a plain-English glossary tied to the role brief.

Prompt

Explain the following terms from this implementation-consultant role:
- data migration
- API integration
- solution design
- UAT
- stakeholder mapping

For each term:
- explain it in plain English
- give one realistic work example
- say what a recruiter could ask the hiring manager to clarify
- list related terms that may appear on a CV

Use the role brief below to distinguish what this employer actually requires from common industry usage.

Do not add a tool or credential to the requirements merely because it appears in a source.

Example excerpt

User acceptance testing (UAT)

The stage where business users test whether a system works for their real processes before launch.

Work example

An implementation consultant prepares test scenarios, coordinates customer users, records defects and confirms which issues must be fixed before launch.

Clarify with the manager

Does the consultant own the UAT plan, facilitate sessions or only resolve product issues raised during testing?

Related CV language

Business acceptance testing, test coordination, go-live readiness, defect triage.

The recruiter gains useful vocabulary without pretending that the glossary defines the employer’s role.

Write candidate messages that answer the real question

Candidate messages are often easy to draft and easy to get subtly wrong.

Suppose the candidate asks:

Has the team made a decision? I have another process moving this week.

The confirmed state is:

• no decision;
• a discussion may happen Friday;
• Friday is not confirmed;
• no response date is approved.

Prompt

Draft a reply to this candidate message.

Candidate message
“Has the team made a decision? I have another interview process moving this week.”

Confirmed facts
- The team has not made a decision.
- A discussion may happen Friday, but it is not confirmed.
- No response date has been approved.

Write a warm, direct reply under 90 words.
Answer the candidate’s question first.
Do not mention the tentative Friday discussion or promise a date.
Ask whether the candidate has a deadline we should know about.

Example output

Hi Jordan,

The team hasn’t made a decision yet. Thanks for letting me know about your other process. Is there a date by which you need an answer? I’ll make sure the team is aware.

Best,

Maya

The answer is short because the situation is simple. The value is that it avoids converting an internal possibility into a candidate-facing promise.

Change the message for a missed update

Acknowledge in the first two sentences that our update is late. Do not hide the delay behind “thanks for your patience”.

Change it for an interview-format question

Use the approved interview plan. Explain the length, attendees and exercise in plain language. Do not add preparation advice that is not in the plan.

Change it for a rejection draft

Use only the decision and feedback approved for communication. Do not invent developmental feedback to make the message feel more complete.

Analyse an ATS export without inventing history

A spreadsheet can look complete while lacking the events needed to answer the question.

Consider this export:

Across both jobs, there are three applications and two people.

For J9, there are two applications: one currently in Screen and one currently in Interview.

The file does not show when either application entered a stage or whether they passed through the same previous stages. It cannot establish a screening conversion rate.

Prompt

Inspect this ATS export before calculating a report.

Export date
13 October 2026

Question
What is the screening conversion rate for job J9?

Data
application_id,person_id,job_id,current_stage
A201,P11,J9,Screen
A202,P11,J10,Interview
A203,P12,J9,Interview

Show:
- what one row represents
- number of applications
- number of people
- records in scope for J9
- calculations the data supports
- fields or events missing for the requested conversion rate
- a clear explanation for the manager

Do not infer stage history from current stage.

Example output

Row unit

One application.

Counts

• Three applications across both jobs.
• Two people across both jobs.
• Two applications in scope for J9.

What can be said

The current J9 snapshot contains one application in Screen and one in Interview.

What cannot be calculated

Screening conversion. The file lacks screening-entry events, progression events, dates and completed outcome status.

Manager explanation

Half of the current J9 applications are in Interview, but this is pipeline composition—not a conversion rate. We need stage-history events to calculate how many screened applications progressed.

This is a good example of a useful answer being incomplete on purpose.

Change the analysis when you have history

Define the screening cohort, screening-completion event, progression event, observation period and treatment of open cases before calculating the rate.

Change it for time in stage

Use stage-entry timestamps. Do not substitute a generic last-updated date.

Connect Claude to an ATS only when the task needs current records

An approved export is often enough for a one-time analysis. A connection becomes useful when you need live application state or repeated access.

Ashby and Greenhouse publish supported connection instructions and available tool details. Follow the provider’s current setup rather than assuming every AI client exposes the same actions.

After connecting, retrieve one known application and compare:

• candidate ID;
• application ID;
• job ID;
• current stage;
• available notes;
• available feedback.

Reading one record does not prove the connection can read the entire interview panel or write to the application.

Prepare a note before writing it

Prepare a proposed screening note for candidate C-118, application A-331, job J-20.

Use the checked screening source below.

Show:
- supported note destination
- existing similar content
- proposed text
- source reference
- anything ambiguous

Do not write the note or change the stage.

If the connection supports only a candidate-profile note, include the job and application ID in the text. One person may have several applications.

Turn a successful document workflow into a reusable method

Suppose the CV-evidence workflow consistently preserves responsibility, quotes the source and exposes missing information.

You can save a short instruction file or Project guidance for colleagues.

Draft reusable instructions for the “CV evidence review” workflow we checked.

Include:
- required inputs
- how to identify the current requirements
- source-citation format
- how to separate described, unclear and explicitly absent experience
- output structure
- stop conditions for unreadable files or missing criteria

Use sample placeholders, not live candidate information.

Return the proposed instructions and one sample test case.

A reusable method should be short enough to inspect. It should preserve the corrections you learned. It should not contain the history of one particular candidate.

Schedule a report only when its sources can run in that environment

A cloud task can continue without your laptop. A task that depends on a local folder, desktop browser or local connector cannot.

Before scheduling, ask Claude to list the runtime dependencies.

Prepare a recurring version of the checked weekly recruiting report.

Scope
Jobs J-20 and J-21.

Schedule
Monday at 8:30am Singapore time.

Sources
- current ATS connection
- approved role documents in the Project
- candidate commitments from the connected mailbox

Destination
Private recruiting-operations Project.

Before scheduling, state which sources are cloud-accessible and which require the desktop to remain available.

Keep the task read-only. If a source fails, label the report incomplete. Show the full task and schedule before saving it.

Anthropic documents scheduled tasks and their environment requirements in its scheduled-task guidance.

Where to begin

Claude is most useful in recruiting when the hard part is not generating words. It is reading carefully.

Start with one permitted source whose meaning you understand:

• a CV passage;
• a role brief and a proposed edit;
• rough screening notes;
• a small ATS export.

Ask Claude to show its evidence, preserve responsibility and expose what remains unknown.

The career opportunity is not to hand your judgement to Claude. It is to raise the quality of the judgement you bring to every handover.

Start with one document whose meaning you understand well. Compare Claude’s interpretation with the source. Then add the next layer: the current requirements, the screening notes, the interview plan or the report definition.

You will know the workflow is useful when the next person starts from something clearer and more honest—without the source sounding stronger, cleaner or more complete than it really is.

That is where Claude can make a recruiter feel unusually prepared: not because it knows the candidate better than you do, but because it helps you see the evidence before the story hardens around it.