Skip to content

For recruitment agencies and search firms

Shortlists your clients can check, criterion by criterion

Turn a client brief into weighted criteria, rank the strongest profiles from your database against it, and hand over a shortlist where each requirement comes with the evidence found in the CV.

Three steps of an agency assignment. A client brief with highlighted requirements becomes four weighted criteria, two of them required, through criteria extraction. A ranked shortlist of three candidates follows, with scores.

Where consultant time goes

Agencies are paid for judgment and relationships. A lot of the week still goes to reading, re-reading and rewriting.

  1. 01

    Briefs mean different things to different consultants

    “Strong stakeholder management, ideally SaaS” gets read three ways, and the search drifts before it starts.

  2. 02

    Your database is bigger than anyone’s memory

    Strong candidates from past assignments stay in the CRM because nobody thinks to search for them.

  3. 03

    Client reports are rewritten by hand

    Consultants re-read each CV to explain why a candidate fits, for every shortlist.

  4. 04

    Clients challenge the order

    “Why is she ahead of him?” needs an answer grounded in the CV, not in an impression.

From brief to client shortlist

Your CRM holds candidates, clients and assignments. HireLayer gives each assignment a structure and each shortlist its evidence.

  1. Your system

    Step 1, your system: A client brief arrives

    Pasted into the assignment in your CRM or ATS.

  2. HireLayer

    Step 2, HireLayer API: Extract weighted criteria

    Each requirement comes back with a type, a weight from 1 to 3 and a level: required, preferred or bonus.

    POST /api/v4/jobs/extract-criteria

    • job_id
    • criteria[]
  3. Your system

    Step 3, your system: The consultant validates the brief

    Adjust weights, add what the client said on the phone, confirm with the client if needed.

  4. HireLayer

    Step 4, HireLayer API: Rank the first pool

    Send the candidates from your CRM search, past candidates included, with precise_ranking on, and get an order with a ranking reason for each.

    POST /api/v4/resumes/score

    • scores[].rank
    • scores[].ranking_reason
  5. HireLayer

    Step 5, HireLayer API: Document the finalists

    Each score already evaluates the validated criteria one by one: met, partial, missing or unknown, with the evidence and an explanation.

    • scores[].criteria[]
    • scores[].summary
  6. Your system

    Step 6, your system: Present to the client

    The consultant edits the explanations into the shortlist. Final judgment stays with the consultant.

See exactly what a criterion looks like before you map it to your CRM.

View the criteria format

Evidence a hiring manager can check

A shortlist your CRM can assemble from Resume Scorer results. Statuses and explanations come from the API, in the brief’s language; the consultant’s note is yours.

A client shortlist for a Head of Customer Success role, prepared by the agency. For two finalists it shows the weighted score, a summary, and for each of the four criteria a status with a one-line explanation from the CV, followed by the consultant's own note.

Evaluate a finalist against validated criteria

The consultant kept three extracted criteria and added a fourth. Criteria sent with the brief replace the stored ones, and the finalist is read from your stored CVs by application_id. The answer is abridged.

score
(3×1 + 2×2/3 + 1×1) / 6 = 0.89: crit_3, unknown, is left out of the mean.
status
met · partial · missing · unknown.
requirement
required: a CV that clearly lacks it loses a quarter of its score, never removed outright.
Request · cURL/api/v4/resumes/score
curl -X POST https://hirelayer.co/api/v4/resumes/score \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $HIRELAYER_API_KEY" \
  -d '{
    "job": {
      "job_id": "mission-2291",
      "text": "<client brief>",
      "criteria": [
        { "label": "Managing a Customer Success team", "type": "experience", "requirement": "required", "weight": 3 },
        { "label": "B2B SaaS experience", "type": "experience", "requirement": "preferred", "weight": 2 },
        { "label": "Fluent English", "type": "language", "requirement": "required", "weight": 2 },
        { "label": "Lyon-based or willing to relocate", "type": "location", "requirement": "bonus", "weight": 1 }
      ]
    },
    "resumes": [{ "application_id": "cand_7720" }]
  }'
Response · abridged
{
  "scores": [
    {
      "application_id": "cand_7720",
      "score": 0.89,
      "verdict": "relevant",
      "summary": "Strong on management and SaaS; English level to be confirmed.",
      "to_verify": [{ "criterion_id": "crit_3", "label": "Fluent English" }],
      "criteria": [
        { "criterion_id": "crit_1", "weight": 3, "status": "met", "score": 1,
          "explanation": "Led a team of six CSMs for three years." },
        { "criterion_id": "crit_2", "weight": 2, "status": "partial", "score": 0.67,
          "explanation": "A SaaS vendor is mentioned, with no detail on a B2B customer base." },
        { "criterion_id": "crit_3", "weight": 2, "status": "unknown", "score": null,
          "explanation": "The CV does not state an English level." },
        { "criterion_id": "crit_4", "weight": 1, "status": "met", "score": 1,
          "explanation": "The candidate lives in Lyon." }
      ]
    }
  ]
}

What changes for consultants and clients

  • A brief everyone reads the same way

    Weighted criteria, each required, preferred or bonus, replace the interpretation of a paragraph.

  • Your database back in play

    Past candidates are ranked against new assignments alongside new applicants.

  • Reports that start as a draft

    Per-criterion explanations give the consultant something to edit, not a blank page.

  • Answers when clients push back

    Every status points to what the CV says, so the order can be explained.

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.

Recruitment agencies: frequently asked questions

Does HireLayer connect to our CRM or ATS?

HireLayer is an API, not a CRM plug-in. Your CRM’s automation, your integration partner or a small service you run calls the endpoints and writes results back to the assignment and candidate records.

Can consultants adjust a client brief before shortlisting?

Yes. After the intake call, a consultant can reword, reweight from 1 to 3, remove or add criteria, for example a requirement the client only mentioned on the phone. Resume Scorer then scores the shortlist against the edited list.

How should a missed must-have appear in a client shortlist?

A required criterion the CV clearly lacks lowers the score by a quarter and is listed in required_missing; it never removes the candidate on its own. Your shortlist can highlight it so the consultant decides whether to present the candidate to the client.

What language are explanations written in?

Criteria, summaries and explanations follow the brief’s language (English, French, German, Spanish or Portuguese; English for any other), and evidence quotes the CV in its own language.

When should we turn on precise ranking?

Resume Scorer always evaluates each candidate against the criteria and explains each one, which suits finalists and client reports. Turn on precise_ranking when the order matters: the best candidates of the call are compared with each other and each gets a ranking reason, for 1 more credit per call.

Run your next brief through it

Paste a real job description, rank candidates from your database and read the evidence. The free plan includes 50 credits a month, shared by all six products.