Job families turn an unstructured collection of individual roles into a navigable map. The Engineering family typically contains Software Engineer, Senior Software Engineer, Staff Engineer, Principal Engineer, and Engineering Manager / Director / VP. The People family typically contains Recruiter, Senior Recruiter, Recruiting Manager, HR Business Partner, People Operations Specialist, and so on. Each family has internal progression rules and clear adjacencies to other families that support cross-family moves.
Defining job families requires judgment about granularity. Too few families - everyone in ‘Technology’ - obscures meaningful skill differences and produces compensation bands that are too wide to be useful. Too many - separate families for each programming language - creates artificial barriers to lateral movement and over-specifies what the architecture needs to capture. Most mid-sized organisations operate with 20-40 job families across the company.
The job family concept becomes most powerful when paired with skill profiles, allowing internal mobility programs to surface candidates from one family for opportunities in adjacent families based on shared competencies rather than identical titles.
Key Points: Job Family
- Group of related roles: Roles in the same family share core skills, knowledge, and progression criteria.
- Internal progression path: Each family has a defined level structure - typically 4-7 levels from junior IC to principal/director.
- Adjacencies to other families: Some cross-family moves are common (Recruiting to Sales, Engineering to Product) and the architecture should make them visible.
- Right-sized granularity: Most organisations operate with 20-40 families - granular enough to be meaningful, broad enough to allow mobility.
- Foundation for talent mobility: Skill-based internal mobility programs use family adjacencies to surface non-obvious candidate matches.
How Job Family Works in Treegarden
Job Family in Treegarden
Treegarden’s job catalogue tags each requisition by family, enabling internal-mobility surfacing (when a role opens in family X, employees in family X or in adjacent families with the right skills can be alerted) and family-level analytics (time-to-fill, source mix, and offer acceptance trends segmented by family for resource planning).
Related HR Glossary Terms
Frequently Asked Questions About Job Family
Function is the broader business area (e.g., ‘Engineering’, ‘GTM’, ‘G&A’); family is a more specific grouping of roles within a function (e.g., within Engineering, you might have Software Engineering, Site Reliability Engineering, and Engineering Management as three distinct families). Most architectures use both: families nest within functions, levels nest within families.
Granular enough that each family has a clear, distinguishable skill profile and progression path; broad enough to permit lateral movement and supportable comp benchmarking. Common warning signs of over-granular families: multiple families at the same level with significantly overlapping skill profiles; people with identical roles in nominally different families because of historical title accidents. Common warning signs of under-granular families: very wide compensation bands within a single family; no clear progression criteria because the family covers too much.
Most do. Edge cases include hybrid roles that span two families (Sales Engineer, who spans Engineering and GTM) and emerging roles where the architecture hasn’t caught up. Practical approach: hybrid roles are typically assigned to the family that defines their primary skill set, with explicit cross-family adjacencies documented in the architecture; emerging roles are placed in the closest existing family with a note for review at the next architecture refresh.
Yes - this is one of the core uses of job family architecture. Cross-family moves typically involve internal application, validation that the candidate has the relevant skills for the destination family, and sometimes a level adjustment (a senior IC in one family may enter the new family at a lower level until they build family-specific expertise). The architecture makes these moves more navigable by clarifying the skill bridge and any expected level change.