Roles

How do you source candidates for a specific role?

Every role has its own vocabulary, channels and reasons to move. A software engineer wants the stack and salary range; a nurse wants the roster; an electrician wants to know about travel and the van. These playbooks cover title variants, signals versus noise, a boolean string, an outreach example and common mistakes per role.

What is the difference between a role page and an industry page?

A role page is about the person you are looking for: how they describe their work, which qualifications matter, where they are online and what makes them reply. An industry page is about the market and the employer side: hiring conditions, regulation and how recruitment teams in that sector work. Use both. For sector context, start at industries.

The six roles have one thing in common: good candidates rarely apply, so the work is in sourcing and outreach. They also differ sharply. Developers and salespeople are easy to find on LinkedIn and flooded with messages, so the message decides. Nurses, electricians and technicians are thin on LinkedIn, so channel mix, qualification checks and patient follow-up decide. Degree-level engineers sit in between, and the word engineer itself needs untangling first.

Each playbook ends with how AIcruiters automates the repetitive part: vacancy intelligence that splits hard requirements from preferences, search and ranking with reasons, and personal outreach with follow-up. Your team sets the rules and approves what it wants to approve. For the search syntax behind the examples, see the boolean search guide.

Last updated:

Try it on a role you are hiring for now

A 30-minute demo on one of your own vacancies: search strategy, ranked candidates and draft messages.

Book a demo on your own vacancy30 minutes · your vacancy · your numbersCalculate the business case