For job boards and career sites
Let candidates build their profile from the CV they already have
One upload prefills experience, education, languages, location and skills. Candidates review instead of typing, employers get profiles they can filter, and job pages can show which requirements a candidate covers.
What stands between a visitor and a complete profile
A job board lives on two numbers it cannot fake: candidates who finish signing up, and employers who find them.
- 01
Signup forms lose candidates
Every field between the CV upload and the first application is a reason to leave, especially on a phone.
- 02
Free-text skills make poor filters
Employers filter on “React”, candidates write “ReactJS”, “React.js” or “front-end (React)”. Exact-match facets miss most of them.
- 03
Suggestions without reasons get ignored
A “jobs for you” block that cannot say why does little to convince a candidate to apply.
- 04
Uploads are not always CVs
ID scans and blank pages arrive in the CV field and leave half-empty profiles behind.
Prefilled, confirmed, then explained
Three mobile screens built on the API. HireLayer supplies the data; the layout, the wording of each status and the consent flow are yours.
01 · Upload
Start from a file
PDF, Word or a photo of a paper CV. Files that are not CVs get a clear message instead of an empty profile.
POST /
api/ v4/ resumes/ parse 02 · Confirm
Review, don’t retype
Fields arrive prefilled and editable. Raw skills resolve to taxonomy skills with stable ids for employer filters.
POST /
api/ v4/ skills/ normalize 03 · Apply
Show what the candidate covers
On a job page, criterion status values become your own wording. The candidate sees strengths and gaps before applying.
POST /
api/ v4/ resumes/ score
From upload to application on your board
Signup, consent and profile editing stay in your product. HireLayer runs behind the upload button and the job page.
- Your system
Step 1, your system: A candidate uploads a CV
At signup or from the apply button, on desktop or mobile. Photos of a paper CV work too (JPG, PNG, BMP).
- HireLayer
Step 2, HireLayer API: Parse it
Returns candidate details, history, education, languages and skills. A file that is not a CV returns a 422 code you can show as a message.
POST /
api/ v4/ resumes/ parse - resume.info_candidate
- resume.work_experiences[]
- resume.skills[]
- Your system
Step 3, your system: The candidate confirms
Render the prefilled form. Nothing is saved until the candidate validates it.
- HireLayer
Step 4, HireLayer API: Normalize skills into facets
Send the profile’s skills as one text of up to 5,000 characters. Keep the original wording for display and the skill id for filters.
POST /
api/ v4/ skills/ normalize - skills[].id
- families[]
- domains[]
- HireLayer
Step 5, HireLayer API: Explain fit on a job page
When a signed-in candidate opens a job, compare the profile with the job’s criteria and show what is covered.
POST /
api/ v4/ resumes/ score - scores[].criteria[].status
Upload any CV to see exactly what your signup form would receive.
Try the parser demoWhat the signup form receives
The request your backend sends after an upload, and an abridged response showing the fields that prefill a profile.
- experience_level
- One of five brackets, ready for a seniority filter.
- languages[].level
- Normalized to CEFR levels A1 to C2.
- skills[].status
- normalized skills carry their taxonomy name; send them to Skills Normalizer as one text to store their ids for facets.
curl -X POST https://hirelayer.co/api/v4/resumes/parse \
-H "X-API-Key: $HIRELAYER_API_KEY" \
-F "file=@cv_clara_jensen.pdf" \
-F "application_id=signup_7f3k2"{
"application_id": "signup_7f3k2",
"stored": true,
"already_stored": false,
"resume": {
"info_candidate": {
"full_name": "Clara Jensen",
"job_title": "Customer Success Manager",
"experience_level": "5 to 10 years",
"education_level": "Level 7",
"availability_now": true,
"location": { "city": "Lyon", "country_code": "FR" }
},
"work_experiences": [
{
"company_name": "Brightdesk",
"job_title": "Customer Success Manager",
"start_date": "2021-04-01",
"currently_active": true
}
],
"languages": [
{ "language": "English", "level": "Full Professional Proficiency (C1)" }
],
"skills": [
{
"skill_title": "Zendesk",
"skill_type": "Software skill",
"status": "normalized",
"domain": "Sales & Customer Relations",
"subcategory": "Customer service"
}
]
},
"warnings": [],
"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 Resume Parser
Resume Parsing API
Core to this workflowDocs for HireLayer Resume ParserPrefills the signup form and flags uploads that are not CVs.
- HireLayer Skills Normalizer
Skills Matching API
Core to this workflowDocs for HireLayer Skills NormalizerPuts candidate and employer wording on the same skill facets.
- HireLayer Resume Scorer
Candidate & Job Matching API
Core to this workflowDocs for HireLayer Resume ScorerPowers a “what you cover” block on job pages; its precise_ranking option orders applicants for an employer, each with a ranking reason.
- HireLayer Job Criteria Extractor
Job Parsing API
Add when neededDocs for HireLayer Job Criteria ExtractorStructures each job post into criteria when it is published.
- HireLayer Job Recommendations
Job Recommendation API
Add when neededDocs for HireLayer Job RecommendationsShows each candidate the open jobs closest to the CV they uploaded.
What candidates and employers notice
Less typing at signup
Candidates start from a filled-in profile and correct it, instead of starting from a blank form.
Facets that work on both sides
Candidates and employers land on the same taxonomy skills, with families and domains for grouping.
Fit a candidate can read
A status per requirement tells candidates what they cover and what an employer will ask about.
A cleaner database
Files that are not CVs are rejected with a reason, before they become empty profiles.
Job boards & career sites: frequently asked questions
Can job seekers sign up from a phone with their CV?
Does the candidate have to accept the parsed data?
Can HireLayer recommend jobs from our whole catalog?
How do we build skill facets?
Can our signup flow ask HireLayer not to retain CV data?
See what your signup form would receive
Drop a CV in the demo to see the full JSON, then create an account to call the API from your backend. The free plan includes 50 credits a month, shared by all six products.
Also built on HireLayer
- ATS platformsParse CVs on upload and show recruiters why a candidate fits.
- Sourcing toolsNormalize skills across sources and rank sourced longlists.
- HR software & SaaSShip CV, job and skills features under your own brand.
Implementation guides
- Parse a resume PDF into JSON with Python or Node.jsCompare PDF extraction, OCR and a parser API, with working code.
- Resume parser API integration guideSend files from your backend, map the JSON and handle errors.
- Resume parser APIs that extract the photoSix APIs compared on the candidate photo field and format.
- Convert a resume to JSON ResumeMap a parsed PDF or DOCX resume onto JSON Resume 1.7.0 in Python.