The goal of this tutorial is to explain how you can govern Job skill profiles using the Skill Engine API.
Overview
You can provide feedback on both:
A skill profile can contain two types of skills:
A skill profile of a Job can contain Family-Specific and Job-Specific skills. A skill profile of a Job Family can only contain Family-Specific skills.
Job Family skill profile: the system aggregates the latest Job Family feedback for each skill, keeping only validated skills.
Job Governed skill profile: the system merges both Job Family feedback and Job-Specific feedback, using the latest feedback per skill, keeping only validated skills.
Key insights:
Consider a Job Family (ID: 101) representing “Software Developer” with two jobs:
After uploading the Job and Job Family data, the suggested skill profiles are:
Skill | Skill Type | Job Family | Job 1 | Job 2 |
---|---|---|---|---|
Machine Learning | Family-Specific | suggested | suggested | suggested |
Python | Job-Specific | - | suggested | - |
At this point, no skills are validated yet. Let’s validate some skills.
✅ Validating “Machine Learning” for all Jobs (via Job Family feedback).
We want to:
Job Family Feedback (API Call):
✅ Validating “Python” for Job 1 (via Job feedback)
Job Feedback (API Call):
Now, the skill profiles look like this:
Skill | Skill Type | Job Family | Job 1 | Job 2 |
---|---|---|---|---|
Machine Learning | Family-Specific | ✅ validated & critical | ✅ validated & critical | ✅ validated & critical |
Python | Job-Specific | - | ✅ validated | - |
Now, let’s assume we reject “Machine Learning” for Job 1.
Job Feedback (API Call):
Now, Job 1 no longer contains “Machine Learning”, since the latest feedback counts. The skill profiles of the Job Family and Job 2 remain unchanged:
Skill | Skill Type | Job Family | Job 1 | Job 2 |
---|---|---|---|---|
Machine Learning | Family-Specific | ✅ validated & critical | ❌ removed | ✅ validated & critical |
Python | Job-Specific | - | ✅ validated | - |
Let’s now add Job 3 (Software Developer) to Job Family 101.
Job Creation (API Call):
Automatic inheritance:
Updated skill profiles:
Skill | Skill Type | Job Family | Job 1 | Job 2 | Job 3 |
---|---|---|---|---|---|
Machine Learning | Family-Specific | ✅ validated & critical | - | ✅ validated & critical | ✅ validated & critical |
Python | Job-Specific | - | ✅ validated | - | - |
The goal of this tutorial is to explain how you can govern Job skill profiles using the Skill Engine API.
Overview
You can provide feedback on both:
A skill profile can contain two types of skills:
A skill profile of a Job can contain Family-Specific and Job-Specific skills. A skill profile of a Job Family can only contain Family-Specific skills.
Job Family skill profile: the system aggregates the latest Job Family feedback for each skill, keeping only validated skills.
Job Governed skill profile: the system merges both Job Family feedback and Job-Specific feedback, using the latest feedback per skill, keeping only validated skills.
Key insights:
Consider a Job Family (ID: 101) representing “Software Developer” with two jobs:
After uploading the Job and Job Family data, the suggested skill profiles are:
Skill | Skill Type | Job Family | Job 1 | Job 2 |
---|---|---|---|---|
Machine Learning | Family-Specific | suggested | suggested | suggested |
Python | Job-Specific | - | suggested | - |
At this point, no skills are validated yet. Let’s validate some skills.
✅ Validating “Machine Learning” for all Jobs (via Job Family feedback).
We want to:
Job Family Feedback (API Call):
✅ Validating “Python” for Job 1 (via Job feedback)
Job Feedback (API Call):
Now, the skill profiles look like this:
Skill | Skill Type | Job Family | Job 1 | Job 2 |
---|---|---|---|---|
Machine Learning | Family-Specific | ✅ validated & critical | ✅ validated & critical | ✅ validated & critical |
Python | Job-Specific | - | ✅ validated | - |
Now, let’s assume we reject “Machine Learning” for Job 1.
Job Feedback (API Call):
Now, Job 1 no longer contains “Machine Learning”, since the latest feedback counts. The skill profiles of the Job Family and Job 2 remain unchanged:
Skill | Skill Type | Job Family | Job 1 | Job 2 |
---|---|---|---|---|
Machine Learning | Family-Specific | ✅ validated & critical | ❌ removed | ✅ validated & critical |
Python | Job-Specific | - | ✅ validated | - |
Let’s now add Job 3 (Software Developer) to Job Family 101.
Job Creation (API Call):
Automatic inheritance:
Updated skill profiles:
Skill | Skill Type | Job Family | Job 1 | Job 2 | Job 3 |
---|---|---|---|---|---|
Machine Learning | Family-Specific | ✅ validated & critical | - | ✅ validated & critical | ✅ validated & critical |
Python | Job-Specific | - | ✅ validated | - | - |