Talent search over profiles that asked to be found
Search real candidate profiles by role, capabilities, country, remote share and day rate — every profile in the index belongs to someone who opted into being found, and every one meets the same minimum standard: a summary, a role, a dated position, skills and a country of work.
{
"titles": ["Platform Engineer"],
"skills": ["Kubernetes", "Terraform"],
"countries": ["DE", "AT"],
"remoteMin": 60,
"dayRateMax": 950
}Capability matching, not keyword bingo
The search scores candidates on the role and the capabilities a job actually needs, with related skills understood — someone who administrates Kubernetes matches a container requirement without having typed the exact word. You see for each candidate what is covered and what is genuinely missing.
A floor under the data
Profiles below the minimum standard never enter the index. That floor costs some volume and buys something better: a results list where every entry can actually be evaluated.
Shortlist and reach out in the same place
Keep candidates on a per-job shortlist with status and notes, and contact them through the platform — candidates who opted out of outreach are respected automatically.
For teams, from the chat too
Team workspaces can run candidate search, manage shortlists and publish openings via MCP — the same operations, driven from Claude or any connected assistant.
Frequently asked questions
Whose profiles appear in the talent search?
Only people who explicitly made their profile discoverable. Nobody is indexed by default, and personal contact details stay masked on published profiles.
What can I filter on?
Role, capabilities, countries, minimum remote share and maximum day rate. Scoring explains per candidate which requirements are met, related, or missing.
Do I need a job posting to search?
A posting gives the search its requirements and enables matching against a concrete role. Free-form searching works by naming the capabilities you are looking for.