Is candidate-to-job scoring based on an unweighted Boolean filter, or does RChilli use relevance-based and fuzzy matching?

RChilli Search & Match is not limited to standard SQL, exact-keyword matching, or a single hard-coded Boolean filter. It uses configurable, relevance-oriented matching across structured recruitment entities.

Depending on the enabled features and configuration, matching can combine:

• Exact matching
• Partial matching
• Taxonomy- and ontology-assisted matching
• Semantic matching
• Configurable entity weightage
• Mandatory matching criteria

Customers can configure parent and child entity weightage for areas such as:

• Job Profile
• Skills
• Degree
• Experience
• Location
• Employer/Organization
• Other supported matching fields

Dynamic Weightage can also be supplied at the request level and can override the default index-level weightage. Required Match Fields can be used to impose mandatory AND-type criteria.

Therefore, the most accurate description is configurable relevance-based scoring with optional mandatory constraints, rather than a purely unweighted Boolean filter.

The final match score does not need to be characterized as a statistical probability to provide relevance-based matching.

Relevant Help Documents:

• Dynamic Weightage
• Search & Match Features

For more information, contact RChilli Support