Huneety separates two closely related concepts: role profiles and job roles. Understanding the difference keeps your setup clean and reusable.
Role profiles
A role profile is a reusable blueprint of the competencies and skills required for a type of work. Example: a “Senior engineer” profile with 10 competencies at specific Dreyfus proficiency levels. Profiles live under Profiles in the main navigation.
Profiles move through a status workflow:
- Draft — being edited.
- Under review — sent to a manager for feedback.
- HR review — final check before publishing.
- Approved — live and usable in assessments.
- Archived — no longer active but preserved for history.
Job roles
A job role is a specific position in your org: role name, department, career level, and an optional linked profile. Example: “Senior engineer — Platform team” inside the Engineering department at seniority level 3. Job roles live under Organization → Job roles.
How they link
One profile can be linked to many job roles. The profile sets the competency requirements; the role adds context (department, team, country). From the Job roles table, use “Add profile” to link an existing profile, or “Create new profile for role” if the role is unique.
When to use which
- Build profiles first, then create the job roles that use them.
- Reuse profiles across teams and departments; do not duplicate the blueprint per team.
- If a role is truly unique, create a dedicated profile for it.
Tips
- Keep profile names generic (“Senior engineer”) and role names specific (“Senior engineer — Platform”).
- Archive old profiles instead of deleting them. Historical assessments rely on them.
- Profiles without a linked role still work for framework design, but you cannot assess anyone against them until at least one job role is linked.