Skip to content

How the match score works

Either how close the whole posting is to your whole CV, or the share of the posting's named skills that your CV mentions. The panel says which.

Needs a free account

Save a CV and every job gets a match percentage, the skills you already have, and a ranked list of the ones the posting asks for and your CV does not mention.

Two different mechanisms produce that number

  • Semantic, where we have it. How close the whole posting is to your whole CV, as a similarity between the two, computed inside our own database.
  • Keyword, in your browser, as the fallback. The share of the skills named in the posting that also appear in your CV. The denominator is the skills we extracted from the full posting when we stored it, so a row and the detail panel cannot disagree.

The panel always says which of the two produced the number, because they are not the same claim. Common aliases are matched on both sides, so K8s on your CV matches Kubernetes in the posting, and Postgres matches PostgreSQL.

What the colours mean

Strong from 70, fair from 40, and weak below that. A weak score is grey, not red: a posting whose skills you mostly lack is not an error, and colouring it like one is a judgement we are not entitled to make.

The match score is computed in our own database or in your browser. Your CV is not sent to any third party to produce it. The writing tools are the only features that send it anywhere, and they say so.

Where it stops: This is keyword and similarity matching, not judgement. It does not know that your three years of Postgres outweigh a missing bullet point, and it cannot see anything a posting did not write down. Treat a low score on a job you want as a prompt to read the posting, not as a verdict.

Did this answer your question?

Still stuck? Ask us directly, and mention this article so we know where to start.