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.

Get your free API key Try the parser demo

Built with

The problem

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
Cover letters and blank scans arrive in the CV field and leave half-empty profiles behind.

Candidate experience

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/v3/parser
02 · Confirm
Review, don’t retype
Fields arrive prefilled and editable. Raw skills are mapped to your catalog for employer filters.
POST /api/v1/skills/match
Lyon · Full-time
Customer Success Lead
What you cover
Lead a Customer Success team
Covered
B2B SaaS background
Partly
Spanish
Not on your CV
Apply with my profile
03 · Apply
Show what the candidate covers
On a job page, match_status values become your own wording. The candidate sees strengths and gaps before applying.
POST /api/v1/matching/job-candidate

How it fits

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).
2
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/v3/parser
- info_candidate
- work_experiences[]
- skills[]
Your system
Step 3, your system: The candidate confirms
Render the prefilled form. Nothing is saved until the candidate validates it.
4
HireLayer
Step 4, HireLayer API: Normalize skills into facets
Send the profile’s skills in one batch of up to 100. Keep the original wording for display and the catalog term for filters.
POST /api/v1/skills/match
- skill
- domain
- subcategory
5
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/v1/matching/job-candidate
- evaluated_criteria[].match_status

Upload any CV to see exactly what your signup form would receive.

Try the parser demo

Technical example

What 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: raw labels are the ones to send to Skills for facets.

HireLayer CV Extract docs About HireLayer CV Extract

Request · cURL/api/v3/parser

curl -X POST https://onlineresumeparser.com/api/v3/parser \
  -H "X-API-Key: YOUR_API_KEY" \
  -F "file=@cv_camille_laurent.pdf" \
  -F "application_id=signup_7f3k2"

Response · abridged

{
  "status": "success",
  "info_candidate": {
    "full_name": "Camille Laurent",
    "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": "raw" }
  ]
}

APIs used

The HireLayer APIs behind this workflow

Start with the core APIs, add the others when a feature needs them. All five share one API key and one credit balance.

Compare all products

HireLayer CV Extract
Resume Parsing API
Core to this workflow
Prefills the signup form and flags uploads that are not CVs.
Docs for HireLayer CV Extract
HireLayer Skills
Skills Matching API
Core to this workflow
Puts candidate and employer wording on the same skill facets.
Docs for HireLayer Skills
HireLayer Match
Candidate & Job Matching API
Core to this workflow
Powers a “what you cover” block on job pages.
Docs for HireLayer Match
HireLayer Job Extract
Job Parsing API
Add when needed
Structures each job post into criteria when it is published.
Docs for HireLayer Job Extract
HireLayer Rank
Candidate Ranking API
Add when needed
Orders applicants for an employer, up to 10 per request.
Docs for HireLayer Rank

Outcomes

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 catalog terms, with a domain and subcategory 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.

FAQ

Job boards & career sites: frequently asked questions

Can job seekers sign up from a phone with their CV?

Yes. Your signup screen passes the file, whether a PDF, a Word document or a JPG, PNG or BMP photo, to your backend, which calls the parser and prefills the new profile. Each request must stay under 6 MiB.

Does the candidate have to accept the parsed data?

Your product decides. We recommend showing the prefilled fields for confirmation before saving, which also gives candidates a chance to complete anything the CV did not mention.

Can HireLayer recommend jobs from our whole catalog?

No single call searches your catalog. Use your own search to pick candidate jobs, then call Match for each job you want to explain. Each match is one credit.

How do we build skill facets?

Send parsed skills to /api/v1/skills/match in batches of up to 100 and store the top catalog term. GET /api/v1/skills lists the catalog with domains and subcategories for your facet tree.

Can our signup flow ask HireLayer not to retain CV data?

Yes. Add do_not_store_data, set to true, to the parsing call your signup backend makes; it defaults to false. The parsed fields still come back for the job seeker to review before the profile is saved.

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 five APIs.

Get your free API key Try the parser demo

All solutions

Software platforms

Recruiting firms

Let candidates build their profile from the CV they already have

What stands between a visitor and a complete profile

Signup forms lose candidates

Free-text skills make poor filters

Suggestions without reasons get ignored

Uploads are not always CVs

Prefilled, confirmed, then explained

Start from a file

Review, don’t retype

Show what the candidate covers

From upload to application on your board

Step 1, your system: A candidate uploads a CV

Step 2, HireLayer API: Parse it

Step 3, your system: The candidate confirms

Step 4, HireLayer API: Normalize skills into facets

Step 5, HireLayer API: Explain fit on a job page

What the signup form receives

The HireLayer APIs behind this workflow

What candidates and employers notice

Less typing at signup

Facets that work on both sides

Fit a candidate can read

A cleaner database

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

Implementation guides

Let candidates build their profile from the CV they already have

What stands between a visitor and a complete profile

Signup forms lose candidates

Free-text skills make poor filters

Suggestions without reasons get ignored

Uploads are not always CVs

Prefilled, confirmed, then explained

Start from a file

Review, don’t retype

Show what the candidate covers

From upload to application on your board

Step 1, your system: A candidate uploads a CV

Step 2, HireLayer API: Parse it

Step 3, your system: The candidate confirms

Step 4, HireLayer API: Normalize skills into facets

Step 5, HireLayer API: Explain fit on a job page

What the signup form receives

The HireLayer APIs behind this workflow

What candidates and employers notice

Less typing at signup

Facets that work on both sides

Fit a candidate can read

A cleaner database

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

Also built on HireLayer

Implementation guides