Skip to content
Use case 02 · Staffing skill checks

Every engineer on your bench, checked against every skill.

“The client wants a shortlist by tomorrow.” Every engineer on your bench, checked against every skill the client asked for.
Try itSee the questions
  • java(cv) → noul
  • kubernetes(cv) → noul
  • german(cv) → choice
  • seniority(cv) → score
One request, 4 questions. The state is read once.
The problem

“The client wants a shortlist by tomorrow.”

  • The request

    A client asks for a handful of skills. Your bench has hundreds of engineers. Reading every CV against every skill takes days.

  • The race

    The first good shortlist wins the deal, and a weak profile costs you the client's screening.

  • With VAKYN

    Each skill becomes a question, asked of every CV: yes, no or unclear, with how sure it is. The recruiter reads only the unclear ones and approves the shortlist.

The questions

4 questions, one request.

The state is the client's request and one engineer's CV. Each question has fixed answers: noul for yes or no, choice to pick one, score for a level.

  1. 01

    java

    Does the CV show production work in Java?

    Answers with the probability of yes, from 0 to 1.

    noul
  2. 02

    kubernetes

    Does the CV show hands-on work with Kubernetes, not only the word in a skills list?

    Answers with the probability of yes, from 0 to 1.

    noul
  3. 03

    german

    What level of German does the CV show?

    • none
    • basic
    • working
    • fluent
    • not_stated
    choice
  4. 04

    seniority

    At what level does the engineer's experience fit?

    1. 0Junior
    2. 1Mid
    3. 2Senior
    4. 3Lead
    score
A sample state

A clear case and a borderline one.

One CV against every skill in the request, with the unclear skill sent to the recruiter.

state · JSON

{
  "client_request": "Backend engineer for a logistics platform: Java, Kubernetes, German B2 or better, senior.",
  "cv": {
    "name": "Andrei Pop",
    "summary": "Backend engineer, 9 years. Java and Spring since 2017.",
    "languages": [
      "Romanian (native)",
      "English (C1)",
      "German (B2, Goethe certificate 2022)"
    ],
    "experience": [
      "2021–now: Senior backend engineer, Halden Freight. Java 17 and Spring Boot services for shipment tracking; moved 14 services from VMs to Kubernetes (EKS), wrote the Helm charts and runs the cluster upgrades; on call.",
      "2017–2021: Java developer, Orsa Bank. Payment services in Java 8 and 11; daily stand-ups with the Vienna team in German.",
      "2015–2017: Junior PHP developer, a web agency."
    ]
  }
}

Answers · how sure

  • javayes0.99
  • kubernetesyes0.99
  • germanworking0.99
  • senioritySenior0.92

Acts automatically. Every answer is at least 0.70 sure. The answers go into the shortlist the recruiter approves.

Run this case in the playground

Real answers from VAKYN-4B Q8_0, 2026-10-11. The bar's line marks 0.70. The playground runs VAKYN MAX, so its numbers can differ. Names, companies and domains are made up.

The decision

Act on the sure answers.

VAKYN answers; your code decides. The rule here: act when every answer is at least 0.70 sure. Move the threshold to send more or fewer cases to a person.

  • Every answer ≥ 0.70

    The answers go into the shortlist the recruiter approves.

  • Any answer below

    The recruiter reads the CV for the unclear skill.

CVs decide people's jobs, so a recruiter approves every shortlist. VAKYN runs on your servers: the CVs stay with you.

Try it in the playgroundSign in to the console; the sample opens ready to run on VAKYN MAX and is charged like any call.