Around 30 to 35 skills, with 10 to 15 of them flagged as critical. That is the range we recommend for a job profile, and it is where most customers land once they have worked it through in a design session.
The split matters more than the total
Critical skills are the ones used for hiring, performance, and matching, and they are the only ones we infer proficiency levels on, because that is where there is enough evidence to do it reliably. The rest of the profile stays as contextual skills with no level attached.
Criticality is decided by task, not by opinion. Our model breaks a job down into the tasks it is made of, drawing on job descriptions, vacancies, and market data, then marks a skill critical when most of those tasks need it. A skill required for five of a role’s ten tasks is more critical than one that appears in a single task.
Both ends of the range have a failure mode
- Under 15 to 20 skills, a profile gets too generic to tell two candidates apart or to support more than one use case.
- Past 50 skills, the profile stops being maintainable and the matching gets worse. Several customers who pushed to 50 later walked it back.
- Above roughly 10 critical skills, the cost lands downstream. In SAP SuccessFactors and Workday, only critical or required skills sync automatically into an employee’s profile, so a loose definition of critical pollutes every employee record.
These are starting points, not limits
You can accept, reject, or add skills and redefine what critical means for your own roles. Leadership profiles, for instance, usually pull the critical set toward leadership skills. How we break a role into its tasks in the first place is covered on our task intelligence page.