Does RChilli allow scoring weights and semantic matching features to be configured or disabled, and can automated rankings be overridden? – RChilli HelpDesk

Yes. RChilli Search & Match provides multiple configuration controls that allow customers to modify scoring and matching behavior rather than relying on a fixed automated ranking.

The available controls include:

Adjust scoring weights: Dynamic Weightage allows resumeWeightage and jdWeightage to be supplied per request, overriding the default index-level entity weights. Parent and child entity weights can also be customized.
Set mandatory criteria: requiredMatchFields can require selected entities to match using AND-type logic.
Limit matching entities: dynamicMatchFields can restrict matching to selected resume and JD entities.
Control semantic Job Profile expansion: semanticSearch is an explicit request parameter. Semantic expansion is applied when semanticSearch=true and can be disabled when not required.
Control ontology/taxonomy expansion: Ontology Search requires ontologyBasedSearch=true and can therefore be disabled when not required.
Control semantic degree matching: Semantic Degree requires semanticDegreeSearch=true and can be disabled when not required.
Control skill-ranking behavior: Skill Ranking requires skillRank=true and can be disabled when not required.
Control degree-score optimization: Degree Weight Optimization requires mergeDegreeScore=true and can be disabled when not required.
Apply additional ranking controls: Filters, sorting, inclusion/exclusion, and other Search & Match features can further control which candidates are returned and how results are prioritized.

RChilli returns matching results and scores to the consuming ATS or recruitment workflow. The returned ranking can be used, ignored, re-sorted, or combined with additional workflow logic according to the customer's configured recruitment process.

Relevant Help Documents:

For more information, contact RChilli Support.