Talent · How matching works
A percentage you can audit
Most "match scores" are unexplainable rankings. The ELAREH match is arithmetic: stated requirements, visible weights, verified credentials. Here is the whole formula — there is nothing else in it.
Worked example · Senior Backend Engineer
| Requirement | Weight | Status | Contribution |
|---|---|---|---|
| Python ≥ 85 | 30% | 94 | 30% |
| SQL ≥ 80 | 20% | 89 | 20% |
| System design ≥ 80 | 25% | 88 | 25% |
| English C1 | 16% | C1 | 16% |
| Kubernetes ≥ 75 | 9% | not verified | 0% |
Three rules keep it honest
- Only stated requirements count. If it isn't on the job's requirement list, it can't move the number.
- Only verified evidence counts. Self-ratings, keywords and CV claims contribute exactly zero.
- Both sides see the same math. Candidate and employer read one identical breakdown.
Explicitly excluded, by design: name, photo, age, gender, nationality, accent, address, employment gaps, and which jobs you looked at. None of these exist in the formula.
Read the trust centreA missing requirement shows a path — the assessment, its duration, who pays. Close the gap, and the match updates the moment the credential is issued.
Employers set minimum scores per skill. Meeting the bar counts fully — the formula rewards sufficiency, not endless one-upmanship.
Credentials carry validity windows. Expired proof drops out of the match — honestly, and visibly to you first.