JobProfile Group Matching

The JobProfile Group Matching feature improves JobProfile-based matching by identifying job profiles that have different titles but belong to the same functional JobProfile Group.

For example, job profiles such as Software Engineer, Software Developer, Application Developer, and Backend Developer can have different titles but may belong to the same functional group, such as Software Developers.

When JobProfile Group Matching is enabled, Search and Match uses this group relationship as an additional matching layer. Therefore, related job profiles can contribute to the matching score even when their JobProfile titles do not match exactly.

Exact JobProfile matching continues to have the highest priority.

How JobProfile Group Matching Works

JobProfile Groups and their associated JobProfiles are maintained in the Taxonomy dataset.

During Resume and Job Description processing, the Resume Parser and JD Parser identify the applicable JobProfile Group for the extracted JobProfile. Search and Match uses this information during indexing and matching.

For example, consider the following JobProfiles:

Job Description

Software Engineer

Resume

Backend Developer

The JobProfile titles are different, so they do not provide an exact JobProfile match. However, if Taxonomy maps both JobProfiles to the following group:

Software Developers

Search and Match can identify the functional relationship between the two profiles and use the JobProfile Group as an additional contribution to the matching score.

The matching priority is:

  1. Exact JobProfile match

  2. Formatted JobProfile match

  3. JobProfile alias or JobProfile Group match

This approach preserves the higher relevance of an exact JobProfile match while allowing functionally related job profiles to contribute when their titles differ.

Usage

Use the jobProfileGroupMatch parameter to enable or disable JobProfile Group Matching.

"jobProfileGroupMatch": true

The parameter accepts the following Boolean values:

  • true — Enables JobProfile Group Matching.

  • false — Disables JobProfile Group Matching.

Default Behavior

JobProfile Group Matching is enabled by default for Search and Match version 4.0 APIs.

You can disable the feature by passing:
"jobProfileGroupMatch": false
For Search and Match version 3.0 APIs, include the following parameter in the request to enable the feature:
"jobProfileGroupMatch": true

Supported APIs

JobProfile Group Matching is supported with the following APIs:

For SimpleSearch, the feature is supported for both Resume and JD indexes.

Sample Request

The following example enables JobProfile Group Matching for a JD to Resume match:
{
  "index": {
    "indexKey": "Use your indexKey"
  },
  "matchType": "JD to Resume",
  "explainScore": true,
  "explainScoreType": "json",
  "match": {
    "resumeContent": "{{resumeContent}}",
    "resumeFileName": "text.pdf",
    "jdContent": "{{jdContent}}",
    "jdFileName": "text.docx"
  },
  "jobProfileGroupMatch": true
}

Indexing Behavior

JobProfile Group information is indexed along with the existing JobProfile information when Resume or JD data is indexed using the ParseAndIndex API.

For a Resume:

  • The Current JobProfile group is indexed in CurrentJobAlias.

  • The JobProfile group is indexed in JobAlias.

  • JobProfile Group information is also added to the JobProfileHistory object.

For a Job Description:

  • The JobProfileTitle group is indexed in JobProfileAlias.

This indexed information allows Search and Match to identify JobProfiles that belong to the same functional group.

Note: Existing indexed documents may need to be re-indexed to make JobProfile Group information available for matching.

Response

When JobProfile Group Matching contributes to the score, the explain score details include the jobProfileGroup field.

For example:
{
  "score": 31.11,
  "maxScore": 38.89,
  "entity": "CurrentJobAlias",
  "value": "abrasives other professionals",
  "sourceType": "JobProfileTitle",
  "jobProfileGroup": "Abrasives Other Professionals"
}

The jobProfileGroup value identifies the JobProfile Group that contributed to the match.

Field Description
score Score received by the matched entity.
maxScore Maximum possible score for the entity.
entity Entity that contributed to the matching score.
value Value used during matching.
sourceType Source entity from the matched document.
jobProfileGroup JobProfile Group used during matching.

Error Handling

The jobProfileGroupMatch parameter accepts only Boolean values.

If an invalid value is provided, the API returns the following error:

Error Code:2201

Message:
jobProfileGroupMatch type must have value either true or false.
For example, the following value is invalid:
"jobProfileGroupMatch": "yes"
Use either:
"jobProfileGroupMatch": true
or:
"jobProfileGroupMatch": false

Important Considerations

  • Exact JobProfile matching continues to have a higher priority than JobProfile Group matching.

  • JobProfile Group Matching works as an additional matching layer when JobProfile titles are different but belong to the same functional group.

  • JobProfile Group relationships depend on the JobProfile Group information available in the Taxonomy dataset.

  • In Search and Match version 4.0, the feature is enabled by default.

  • Existing indexed Resume and JD documents may need to be re-indexed to include JobProfile Group information.

  • If JobProfile Group information is unavailable for a JobProfile, the existing matching behavior continues to apply.