- a
sourcewhich indicates the source of the information - a
data_typewhich indicates the type of the information, currently a Job Family supports thejob_family_descriptiontype and a Job supports thejob_description,job_title,vacancyandskill_notestypes - a
datafield which contains the actual information
/job_architecture/jobs/{job_external_id}/profile_data and
/job_architecture/job_families/{job_family_external_id}/profile_data endpoints
respectively. In this way, a suggested skill profile can be created where a clear
distinction can be made between the skills coming from the Job and the skills
coming from the Job Family.
Example
Assume that a Job Family with ID 101 is created, which represents a Software Developer. Additionally, a Job with ID 1 is created, which represents a Junior Software Developer. The following Profile Data can be added to the Job Family by calling/job_architecture/job_families/101/profile_data with the following body:
/job_architecture/jobs/1/profile_data with the following body: