For staffing and temporary work agencies
Fill job orders from a candidate pool you can actually search
Temp placements are decided on practical details: who is available on Monday, who holds the right licence, who can get to the site. HireLayer reads those details out of every CV so your branches can filter the pool, then ranks the shortlist for each order.
What slows down a job order
In temporary staffing, the order is often filled by whoever answers first with the right person. The bottleneck is rarely the pool; it is reading it.
- 01
Orders arrive late and need answers now
A client calls for a forklift operator tomorrow morning. The consultant has to know who is available, licensed and close, without reopening every file.
- 02
The deciding details hide in CVs
Availability dates, driving licences, certifications and the towns a candidate will travel to are written in free text, if at all.
- 03
Branches re-qualify the same people
A candidate registered at one branch is called again by another, because the record was never structured.
- 04
Shortlists depend on who is on shift
Two consultants order the same pool differently, and clients notice when quality varies.
From CV to a ranked job order
Your staffing software keeps the pool, the orders and the client relationship. HireLayer structures the CVs and orders the shortlist.
- Your system
Step 1, your system: A candidate registers
At the branch, on your website or by email. A phone photo of a paper CV works (JPG, PNG, BMP).
- HireLayer
Step 2, HireLayer API: Parse the practical details
Availability, licences, certifications, location with coordinates, mobility and ROME occupation codes come back as fields.
POST /
api/ v4/ resumes/ parse - availability_now
- availability_date
- driver_license[]
- certifications[]
- mobility.other_cities[]
- Your system
Step 3, your system: An order comes in
The consultant enters role, site, start date and required licence in your software.
- Your system
Step 4, your system: Filter with your own rules
Distance from the site using parsed coordinates, licence held, available by the start date. These rules are yours to set.
- HireLayer
Step 5, HireLayer API: Rank who is left
Send the order text and the remaining candidates, with precise_ranking on. Each comes back with a rank, a score and a ranking reason.
POST /
api/ v4/ resumes/ score - rank
- score
- ranking_reason
- Your system
Step 6, your system: The consultant calls
The consultant works down the list and records outcomes in your software.
Check what the parser reads from one of your own candidate CVs.
Try the parser demoThe details that decide a placement, as fields
What a consultant looks for when reading a CV, and where it lands in the parser response. Fields are filled when the CV mentions them, and null otherwise.
Rank the candidates left after your filters
One request per order: the order text and the candidates left, each by the application_id its CV was parsed under at registration. The answer is abridged: each score also carries a verdict, a summary and the evaluation of every criterion.
- resumes
- Stored CVs by application_id; a CV text or a file works too.
- application_id
- Your id, returned with each score so results map back to your pool.
- ranking_reason
- Written in the order’s language: English, French, German, Spanish or Portuguese, and English for any other.
curl -X POST https://hirelayer.co/api/v4/resumes/score \
-H "Content-Type: application/json" \
-H "X-API-Key: $HIRELAYER_API_KEY" \
-d '{
"job": {
"text": "Forklift operator, night shift, Roissy warehouse. CACES R489 category 3 required. Start Monday."
},
"resumes": [
{ "application_id": "cand_4812" },
{ "application_id": "cand_5530" },
{ "application_id": "cand_6107" }
],
"precise_ranking": true
}'{
"job": { "job_id": "job_8a41c2f09d7b4e6a1c3f5e2d9b0a7c64", "language": "en" },
"precise_ranking": true,
"scores": [
{
"rank": 1,
"application_id": "cand_5530",
"score": 0.9,
"ranking_reason": "CACES R489 category 3 mentioned, with night-shift warehouse experience."
},
{
"rank": 2,
"application_id": "cand_4812",
"score": 0.74,
"ranking_reason": "Confirmed forklift experience, CACES category not stated."
},
{
"rank": 3,
"application_id": "cand_6107",
"score": 0.52,
"ranking_reason": "Order picker profile, no CACES mentioned."
}
],
"credits_used": 3
}What changes at the branch
Search on the details that decide
Availability, licences, certifications and mobility become fields consultants can filter on.
One record for every branch
A candidate parsed once is searchable by every branch, on the same fields.
A consistent first pass
Every order gets the same kind of ranking and rationale, whoever is on shift.
Consultants keep the call
Resume Scorer orders the list. The consultant still decides who to call and who to send.
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 ParserExtracts availability, licences, certifications, location, mobility and ROME codes.
- HireLayer Resume Scorer
Candidate & Job Matching API
Core to this workflowDocs for HireLayer Resume ScorerPrepares the call: what the CV confirms, and what to ask about; its precise_ranking option orders the filtered candidates for an order, each with a ranking reason.
- HireLayer Job Criteria Extractor
Job Parsing API
Add when neededDocs for HireLayer Job Criteria ExtractorStructures recurring client orders into reusable criteria.
- HireLayer Skills Normalizer
Skills Matching API
Add when neededDocs for HireLayer Skills NormalizerKeeps skill and qualification labels consistent across branches.
- HireLayer Talent Pool Search
Talent Pool Search API
Add when neededDocs for HireLayer Talent Pool SearchFinds the stored candidates closest to a job order, within a radius of the client site.
- HireLayer Job Recommendations
Job Recommendation API
Add when neededDocs for HireLayer Job RecommendationsLists the open job orders closest to each new candidate.
Staffing & temp agencies: frequently asked questions
Which practical details can be extracted from a CV?
Can we filter candidates by distance from a client site?
How do we shortlist for a job order from a large pool?
Can our French branches group candidates by occupation?
Can a walk-in candidate register from a paper CV?
Test it on your next job order
Parse a few CVs from your pool and rank them against a real order. The free plan includes 50 credits a month, shared by all six products.
Also built on HireLayer
- Recruitment agenciesTurn client briefs into criteria and evidence-backed shortlists.
- RPO providersApply one screening method across every client ATS.
- AI resume screeningRank applications for a job and explain every score to recruiters.
Implementation guides
- Best resume parsing software in 2026Six vendors compared on price, output, connectors and security.
- Resume parser benchmark on 10 test resumesHireLayer, Textkernel, RChilli and Affinda scored field by field.
- Bulk resume parsing with a reliable pipelineQueues, retries, deduplication and cost controls at scale.
- Bullhorn API guideOAuth, REST login, candidate search, resume files and event polling.