Recruitment: first automations in Claude Code

Situation

A recruitment specialist spent a lot of time on manual work around meetings and candidates. After every meeting the transcript had to be found, copied into a chat and turned into a summary. Requirements for candidates were kept in email threads, and CVs were checked against them by eye. The client came with a list of tasks to automate and wanted to learn to do it themselves.

Format

Training on your tasks. The client built the solution themselves, on their own computer. The consultant prepared a plan for each session from the client's materials, explained and corrected.

What was done

1. The tasks on the list were reviewed and put in order. Role criteria came first, since the other tasks rely on them.
2. A project folder with a CLAUDE.md rules file and a register with fixed fields.
3. Ready-made commands for a meeting summary from a transcript and for search across collected materials.
4. A loop for refining criteria: role criteria, a check on a CV with personal data removed, a one-line refinement in the criteria file. The system improves by editing the file; the prompt wording stays the same.

5. The question of candidates' personal data was worked through: CVs do not go to the cloud as they are. Options considered: anonymisation before sending, a plan with a data processing agreement, and a local model.

What changed

A meeting summary takes one command instead of a manual chain. Role criteria are written down in files and checked against real CVs. The client uses the ready-made commands on their own.

How it was measured

Time savings were not measured. The client plans to measure them once the remaining tasks on the list are in place.

Status and next step

The work continues. Next: refining the CV check, moving to a plan with a data processing agreement, then a solution with a local model on the client's own hardware.