Why a job shows no match score
Because the posting names too few skills to judge. A confident 0% would be a much stronger claim than the truth, which is that we cannot tell.
Needs a free account
When a posting names fewer than three recognisable skills, no percentage is shown at all and the panel says the posting is too thin to judge.
That is deliberate. A one-skill posting can only ever score 0% or 100%, and a confident 0% reads as "you match nothing", which is a different and far more discouraging claim than "we cannot tell". The first is a verdict we have not earned.
This is the common case, not an edge case
Several boards cap the description they send us at a few hundred characters. A large share of the index therefore arrives too thin to score against, and no amount of work on our side recovers text the source never sent.
The other reasons a score is absent
- No CV saved yet, or none marked as the default.
- A semantic score that comes out at the floor is withheld rather than shown as a zero, for the same reason as above.
Where it stops: We will not pad a thin posting out to make it scoreable. A number computed from one skill would look identical to a number computed from thirty, and there is no way to show the difference on a row.
Related
- How the match score worksEither 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.
- Reading a listingThe full description, the skills we pulled out of it, where it came from, and a direct link to the employer's own posting.
- Uploading a CVUpload a PDF or paste plain text, keep as many CVs as you need for different kinds of role, and mark one as the default.
Did this answer your question?
Still stuck? Ask us directly, and mention this article so we know where to start.