Match!

In CandidateClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. Search, Match! takes an external jobClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement. posting or job description and finds candidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. in the Org matching the job requirements. In Job Search, Match! works with a candidate resume instead to find jobsClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement. in the Org that might be a good match.

To use Match!, either paste an external job post URL into the search box or click the upload button within the search box and choose a file containing a job description (or resume, for Job Search) then press the Search button.

Textkernel interprets information from the job posting (or resume, for Job Search) and creates a query to find candidates (or jobs) in the Org who are a potential match. The Match! query created by Textkernel is based on these fields:

  • Job title
  • Years of experience
  • Skills
  • Education level
  • Location
  • Full-text keywords (extracted from the record based on the context)

If any of the fields do not have a value, they will not be displayed in the breadcrumbs. For example, if a candidate does not have any skills indexed, there won’t be a skills breadcrumb in the generated query.

The Match! button also appears on the search result detail view. Selecting a candidate and clicking on Match! will show the jobs in the Org the candidate is suitable for.

The Match! button can also be added directly to the contact record page layout to start searches from a candidate's record.

Job Titles in Match! Queries

When using Match!, the jobtitle field is not a single field, but instead is the sum of several different fields. This is to ensure the query covers a large enough range of potential matches. Here’s what’s taken into account for the query:

For Candidate Match

  • Raw job titles from the last three years, taken from the employment history fields
  • The normalized version of those job titles
  • Job group and Job class

A hierarchical table is used to normalize job titles, which consists of three levels: classes, groups, and codes. Each of these levels can be used in matching.

For a Job Match

  • The job title from the Job record.
  • The three normalized fields: classes, groups, and codes.

Breadcrumb labels will be different between candidate and job search. For example, users will see Job Title when using Match! from a candidate (looking for a matching job) but Recent PositionsClosed A job (vacancy, position, role) is an opening for which a customer's client needs a placement. when matching from a job (looking for a candidate).