Supporting Use Cases

AdeptID offers the following functionality to support the matching use cases described above. This functionality may also be deployed in isolation.

Occupation Classification

Developers seeking to categorize job postings or work experiences into standard groupings can use the Occupation Classification endpoint. Note that AdeptID offers two occupation taxonomies, O*NET 2019 as published by the US Bureau of Labor Statistics and O*NET 2019 Simplified, which removes some occupations to create a more user-friendly taxonomy.

Occupation Data Enrichment

Developers seeking information about an occupation such as typical salaries, demographics, or talent supply may use Occupation Metadata. These data can be used to inform employers selecting an occupation to recruit from or job seekers selecting a future career.

Resume and Job Parsing

Developers seeking to transform documents (e.g., .doc, .pdf) into the structured format used in AdeptID’s Matching endpoints may use the Extract Skills, Parse Resume, and Parse Job endpoints. These accept a resume or job description document and extract and structure fields such as name, email, telephone, job title, employer name, education, and skills.

AdeptID matching endpoints require a Candidate and/or Job to be represented in a specific format; to support the processing of resumes and job postings, Parse Resume and Parse Job can be used to generate the required format. An example Recipe (code) is provided on each parser's API Reference page.

Taxonomy Search

Developers seeking to standardize user-entered free text for locations, skills, and educational programs of students for use by AdeptID’s matching context can use our taxonomy search endpoints. These endpoints can power type-ahead UI elements or standardize short strings. Taxonomy search endpoints are offered for locations, skills, certifications, educational programs of study, job titles, and employers.