Job Families, Clusters, Roles, and Levels

The Four-Layer Hierarchy

Every job architecture organizes roles into a four-layer hierarchy. Each layer serves a distinct purpose, and getting the boundaries right determines whether the architecture is usable or bureaucratic.

Job Families

A job family groups roles that share similar knowledge domains, competencies, and functional purpose. Families are the broadest category — typically 8–20 per organization.

Design principles:

• Families should map to recognizable functional areas. Employees should immediately understand which family their role belongs to.
• Avoid both over-splitting (30+ families creates navigation overhead) and under-splitting (5 families hides meaningful distinctions).
• Each family should contain at least 3 distinct roles. If a family has only 1–2 roles, it likely belongs as a cluster within another family.

Common examples: Finance & Accounting, Engineering & Technology, Human Resources, Commercial & Sales, Operations, Legal & Compliance, Marketing & Communications, Research & Development, Customer Success, Data & Analytics.

Job Clusters (Sub-Families)

Clusters add finer granularity within a family. Not every organization needs them — they are most useful when a family contains more than 10 distinct roles.

When to use clusters:

• A family contains functionally distinct groups (e.g., Engineering → Software Engineering, Data Engineering, Infrastructure)
• Career paths within the family diverge significantly (e.g., HR → Talent Acquisition vs. Compensation & Benefits)
• Different skill sets are required despite shared family affiliation

When to skip clusters:

• The family is small (fewer than 10 roles)
• All roles within the family share the same skill foundation
• Adding clusters would create single-role clusters

Job Roles

The job role is the fundamental building block — the smallest distinct unit in the architecture. Each role has:

• Unique role code — alphanumeric identifier (e.g., ENG-SWE-003)
• Standardized title — consistent across regions and departments
• General description — 2–3 sentences summarizing the role's purpose
• Detailed tasks — specific activities the role performs (10–20 tasks per role)
• Required skills — discrete capabilities with proficiency levels
• Qualifications — education, certifications, experience requirements
• Equal pay criteria — factors for determining comparable work

Common mistake: creating a new role for every slightly different job description. Role proliferation defeats the purpose of architecture. Target: 80% of employees should map to existing roles. Only create new roles when tasks and skills genuinely differ.

Job Levels

Levels define seniority within each role. They determine compensation bands, decision-making authority, and career progression expectations.

How Many Levels?

Distinguishing Levels

Each level must be objectively distinguishable from the one above and below. The criteria:

• Scope of responsibility — Individual tasks → Team outcomes → Department strategy → Business unit P&L
• Complexity of problems — Well-defined → Ambiguous → Novel → Transformational
• Autonomy — Guided → Independent → Strategic → Sets direction
• Impact — Task output → Project delivery → Function performance → Organization strategy
• Skills depth — Basic → Qualified → Advanced → Professional → Domain Expert

If two adjacent levels cannot be clearly distinguished on at least three of these dimensions, they should be merged.

Level Matrices by Industry