For sourcing and talent search products
One skill vocabulary for every profile your users source
Profiles reach your product from job boards, referrals, CV databases and uploads, each worded differently. HireLayer parses attached CVs, resolves skills and recruiter queries to one taxonomy, and ranks the longlist a recruiter is about to read.
Why sourced profiles are hard to search
Your product is good at finding people. The trouble starts when a recruiter tries to compare what was found.
- 01
Every source words skills differently
“K8s”, “Kubernetes admin” and “container orchestration” overlap. Keyword search treats them as unrelated.
- 02
Recruiter queries are free text too
A query typed between two calls rarely matches the labels stored on profiles.
- 03
Attached CVs stay unread
The most detailed information sits in PDFs that nobody opens until a candidate is already shortlisted.
- 04
Longlists have no reading order
A search returns dozens of plausible profiles; the recruiter needs to know where to start.
What a recruiter types, and what your search runs
The query goes through /skills/normalize as one text and comes back as taxonomy skills in the order typed, each with the words it came from. Parts that match no skill are listed in unresolved, never guessed. Values below come from real responses.
Recruiter types
Your backend sends
POST /api/v4/skills/normalize { "text": "react js", "language": "en" }
skills[], in the order typed
1React
reactsoftware · from “react js”
Frontend development
unresolved: []
Your search filters on
No scores to tune: each part of the query is resolved or listed in unresolved, never guessed.
Enrichment after discovery
Discovery, provenance and outreach stay in your product. HireLayer works on profiles you have already captured, and does not source candidates itself.
- Your system
Step 1, your system: A profile is captured
From any channel your product supports, with or without an attached CV.
- HireLayer
Step 2, HireLayer API: Parse the CV, if there is one
Adds work history, education, languages and typed skills to the record.
POST /
api/ v4/ resumes/ parse - resume.work_experiences[]
- resume.skills[]
- HireLayer
Step 3, HireLayer API: Normalize profile skills in one call
All of a profile’s skill strings as one text, up to 5,000 characters. Keep the original label for display and the skill id for search.
POST /
api/ v4/ skills/ normalize - skills[].id
- mention
- HireLayer
Step 4, HireLayer API: Normalize the recruiter’s query
Resolve what the recruiter typed to taxonomy skills before your search engine runs.
POST /
api/ v4/ skills/ normalize - HireLayer
Step 5, HireLayer API: Rank the longlist
Send the role description and the profiles the recruiter will read first, with precise_ranking on.
POST /
api/ v4/ resumes/ score - scores[].rank
- scores[].ranking_reason
- Your system
Step 6, your system: The recruiter reaches out
Outreach, sequences and consent stay in your product.
The whole skills taxonomy is one call away, with families and domains for your filters.
See the Skills Normalizer docsNormalize a profile’s skills in one call
A Python sketch for an enrichment worker. One request takes the profile’s whole skill list, up to 5,000 characters, and counts as one credit.
- text
- One free text up to 5,000 characters: a skill, a list or a skills section.
- skills[].mention
- The part of the text each skill came from, in the order of the text.
- unresolved[]
- Parts that match no taxonomy skill, with family_hints. Nothing is guessed.
import requests
resp = requests.post(
"https://hirelayer.co/api/v4/skills/normalize",
headers={"X-API-Key": API_KEY},
json={"text": "React, Node, Cobol, project management", "language": "en"},
timeout=65,
)
resp.raise_for_status()
result = resp.json()
for skill in result["skills"]:
profile.add_skill(
raw=skill["mention"],
skill_id=skill["id"], # store and filter on the id
name=skill["name"],
)
for part in result["unresolved"]:
profile.flag_for_review(part["text"]) # never guessed
profile.taxonomy_version = result["taxonomy_version"]{
"language": "en",
"skills": [
{
"id": "react",
"name": "React",
"type": "software",
"mention": "React",
"families": [
{
"id": "frontend_development",
"name": "Frontend development",
"domain_id": "software_development"
}
],
"domains": [
{ "id": "software_development", "name": "Software Development" }
],
"broader": null
},
// type, families, domains and broader left out below
{ "id": "node_js", "name": "Node.js", "mention": "Node" },
{ "id": "cobol", "name": "COBOL", "mention": "Cobol" },
{
"id": "project_management",
"name": "Project management",
"mention": "project management"
}
],
"unresolved": [],
"taxonomy_version": "v1",
"credits_used": 1
}The HireLayer APIs behind this workflow
Start with the core APIs, add the others when a feature needs them. All six products share one API key and one credit balance.
- HireLayer Skills Normalizer
Skills Matching API
Core to this workflowDocs for HireLayer Skills NormalizerResolves profile skills and recruiter queries to one taxonomy.
- HireLayer Resume Parser
Resume Parsing API
Core to this workflowDocs for HireLayer Resume ParserReads attached CVs into structured history and typed skills.
- HireLayer Resume Scorer
Candidate & Job Matching API
Core to this workflowDocs for HireLayer Resume ScorerChecks one profile criterion by criterion before outreach; its precise_ranking option orders the profiles a recruiter will read first, each with a ranking reason.
- HireLayer Job Criteria Extractor
Job Parsing API
Add when neededDocs for HireLayer Job Criteria ExtractorTurns an assignment brief into criteria when you need them.
- HireLayer Talent Pool Search
Talent Pool Search API
Add when neededDocs for HireLayer Talent Pool SearchSearches the profiles saved in your product for the ones closest to a job.
What recruiters using your product notice
Search that survives synonyms
Queries and profiles meet on skill ids rather than on spelling.
Richer profiles, no manual entry
Attached CVs become structured fields as soon as they are captured.
A reading order for longlists
Recruiters open the most relevant profiles first, with a rationale for each position.
Facets you can group
Each skill has families and domains, the primary one first, to build skill clusters and filters.
Sourcing tools: frequently asked questions
Does HireLayer find candidates?
How do we normalize skills on profiles imported in bulk?
Can recruiters filter search by the same skill vocabulary?
What if a recruiter’s query maps to the wrong skill?
How does ranking fit a long list of search results?
Send a real recruiter query
Create an account and send your own query or skill list to /skills/normalize. One credit covers a whole text of up to 5,000 characters. The free plan includes 50 credits a month, shared by all six products.