How does a difference between the candidate's location and job location affect the overall match score?

The effect on the overall match score depends on the weightage configured for the applicable location entities.

If a location entity matches, its configured contribution is included in the score. If it does not match, that particular location contribution is not received.

The exact location weightage can be verified from the configuration associated with the index key or from the dynamic weightage passed in the request. Documented sample configurations use separate weights for City, State, and Country, rather than a single combined location weight.

Location proximity and partial location matching

Standard City, State, and Country matching is entity-based. Geographic proximity, such as identifying candidates within a specified number of kilometers or miles from a job location, is supported through the GeoSearch feature.

With GeoSearch:

• A location can be specified using City/State/Country or latitude/longitude.
• A minimum or maximum radius can be configured.
• Distance can be measured in kilometers or miles.
• Specific GeoLocation fields can be selected for matching.
• The GeoSearch contribution to the overall score can be controlled using geoSearchScore.

By default, when GeoSearch is included, the documented behavior allocates 50% of the overall score to GeoSearch and the remaining 50% to other matching criteria. This distribution can be changed using the geoSearchScore parameter.

Relevant Help Documents:
Dynamic Weightage
Geographical Search
Dynamic Field Matching

For more information, contact RChilli Support.