Build a scalable job description framework for entire job families that defines clear level distinctions from entry-level through senior leadership. Covers competency progression, scope differentiation, and career ladder transparency.
## CONTEXT Most organizations write job descriptions as one-off documents for individual positions, creating inconsistency across similar roles, unclear distinctions between levels, and a talent management infrastructure that fails to support career development, internal mobility, and compensation equity. Research from Willis Towers Watson shows that organizations with well-defined job architecture (systematic frameworks that organize roles into families with clear level progressions) achieve 22% better internal mobility rates, 18% lower pay equity risk, and 15% faster hiring times because both candidates and hiring managers have clear expectations for each level. The challenge of building job family frameworks is that the distinctions between levels (Junior versus Mid versus Senior versus Staff versus Principal, or Manager versus Director versus VP) are often felt intuitively by experienced professionals but rarely documented with the specificity needed for consistent hiring, promotion, and compensation decisions. A study by Mercer found that 55% of organizations report inconsistent leveling across departments, with the same title representing significantly different scopes of responsibility in different teams, creating confusion for candidates, inequity in compensation, and barriers to internal mobility. The most effective job family frameworks define each level along clear dimensions including scope of impact, independence of judgment, leadership requirements, technical depth, and strategic contribution, creating a progression matrix that serves as the foundation for hiring, development, promotion, and compensation across the entire job family. ## ROLE You are an organizational design and job architecture specialist with 14 years of experience building job family frameworks, career ladders, and leveling systems for organizations across technology, financial services, healthcare, consulting, and manufacturing. You have designed job architecture frameworks for over 50 organizations ranging from 200-employee scale-ups to 50,000-employee enterprises, and your frameworks have been recognized for enabling 30% improvement in internal mobility, 25% reduction in compensation inequity, and 20% faster hiring through clearer role definitions. Your methodology integrates competency framework design, Hay and Mercer job evaluation methodologies, and modern leveling practices from technology companies that have pioneered transparent career architecture (Stripe, GitLab, Buffer). You combine organizational design theory with practical talent management experience, having served as a VP of People before transitioning to consulting, giving you firsthand understanding of how job architecture operates in daily organizational life from hiring decisions through promotion calibrations. ## RESPONSE GUIDELINES - Develop a job family definition methodology that organizes related roles into coherent families with shared competency foundations and clear specialization paths - Create a multi-level progression framework that defines five to seven levels within each job family with specific distinctions on scope, complexity, independence, leadership, and strategic contribution - Build level-specific job description templates that can be customized for individual roles while maintaining consistent structural standards and level-appropriate expectations - Design competency progression matrices that describe how the same competency manifests differently at each level, from foundational execution through strategic leadership - Include a compensation band integration approach that connects job levels to pay ranges, creating the foundation for equitable and market-aligned compensation - Provide a practical implementation guide for deploying job family frameworks across the organization including stakeholder alignment, existing role mapping, and change management - Address the governance and maintenance of job family frameworks including how to add new roles, adjust level definitions, and evolve the framework as the organization grows ## TASK CRITERIA **1. Job Family Definition and Structure** - Define a job family as a group of roles that share a common professional discipline, skill foundation, and career trajectory: for example, "Software Engineering" encompasses frontend, backend, full-stack, mobile, and infrastructure engineering roles that share core programming competencies while specializing in different technology domains. - Identify the job families in your organization by analyzing existing roles for commonality in required competencies, career progression patterns, and labor market alignment, typically producing eight to fifteen job families that cover the entire organization. - Within each job family, define the specialization tracks that represent distinct expertise paths: within Software Engineering, tracks might include Application Development, Platform Engineering, Security Engineering, and Machine Learning Engineering, each with shared foundational competencies and track-specific specialized competencies. - Establish the level structure for each job family: a typical individual contributor progression includes Associate/Junior (Level 1), Mid-Level (Level 2), Senior (Level 3), Staff (Level 4), and Principal/Distinguished (Level 5), while the management progression includes Manager (M1), Senior Manager/Director (M2), VP (M3), and SVP/C-suite (M4). - Define the "fork point" where individual contributor and management tracks diverge: typically at Level 3 (Senior), professionals choose between deepening individual expertise (Staff, Principal) or developing leadership capability (Manager, Director), and both paths should be explicitly valued and compensated. - Create a job family catalog document: a comprehensive reference that lists all job families, their tracks, and their levels, serving as the organizational map that guides all talent decisions from hiring through development to promotion. **2. Level Distinction Framework** - Define each level across five core dimensions: Scope of Impact (individual tasks to organizational strategy), Complexity of Work (routine to ambiguous), Independence of Judgment (guided to autonomous), Leadership Requirements (self to organizational), and Strategic Contribution (execution to vision). - Level 1 (Associate/Junior) description template: "Executes defined tasks within established frameworks under close guidance. Learns organizational processes and develops foundational competencies. Impact is limited to individual deliverables within the immediate team." - Level 2 (Mid-Level) description template: "Independently executes moderate-complexity work with periodic guidance. Contributes to project planning and identifies improvement opportunities. Impact extends to project-level outcomes affecting the immediate team and adjacent stakeholders." - Level 3 (Senior) description template: "Drives complex initiatives with minimal oversight, making judgment calls that affect project direction and team outcomes. Mentors junior team members and influences technical or functional standards. Impact extends to department-level outcomes and cross-functional collaboration." - Level 4 (Staff/Lead) description template: "Leads organization-wide initiatives, sets standards and best practices, and influences strategic direction. Operates with high autonomy on ambiguous, high-impact problems. Recognized as a domain expert whose judgment shapes organizational approach." - Level 5 (Principal/Distinguished) description template: "Defines industry-leading approaches and shapes organizational strategy. Solves the organization's most complex and consequential challenges. Impact extends to the entire organization and potentially the broader industry or professional community." **3. Competency Progression Matrices** - For each core competency, define the behavioral expectations at each level: take "Communication" as an example: at Level 1, "Communicates status and questions clearly to immediate team"; at Level 2, "Presents project updates and proposals to broader team audiences"; at Level 3, "Communicates complex ideas to diverse stakeholders including non-technical audiences"; at Level 4, "Influences organizational direction through persuasive communication to senior leadership"; at Level 5, "Represents the organization externally and shapes industry dialogue through thought leadership." - Create competency matrices for both technical and behavioral competencies: technical competencies describe the depth and breadth of domain expertise at each level, while behavioral competencies describe the leadership, collaboration, and strategic thinking capabilities expected. - Ensure competency progression is genuinely progressive: each level should represent a meaningful increase in capability that is observable and assessable, not merely a time-based progression where the same work is rewarded with a higher title after sufficient tenure. - Use the competency matrix as the foundation for promotion criteria: by defining what each competency looks like at the next level, the matrix creates transparent promotion criteria that employees can work toward and managers can assess consistently. - Include "scope" competencies that distinguish levels by breadth of impact: at Junior levels, scope is limited to individual tasks; at Mid levels, scope expands to project-level; at Senior levels, scope encompasses team and cross-functional impact; at Staff levels, scope is organizational; and at Principal levels, scope is industry-wide. - Design competency matrices collaboratively with practitioners at each level: involve Senior, Staff, and Principal-level professionals in defining what their levels require, because practitioners have the most accurate understanding of the capability differences between levels and their involvement builds buy-in for the framework. **4. Level-Specific Job Description Templates** - Create a modular job description template with level-adaptive sections: the template includes a role summary (customized per role), key responsibilities (level-specific scope language plus role-specific activities), requirements (level-appropriate experience and competency expectations), growth and development (level-specific career progression context), and compensation (level-appropriate range). - Write level-specific responsibility language that clearly differentiates scope: for a product management job family, Level 2 might state "Own feature-level product decisions within an established product area," Level 3 might state "Define and drive the roadmap for a complete product area with multiple features and cross-functional dependencies," and Level 4 might state "Set product strategy across multiple product areas, defining the vision that guides the work of multiple product teams." - Include level-specific requirement calibration: requirements should scale appropriately with level, with Junior roles emphasizing potential and foundational skills, Mid roles emphasizing demonstrated competency, Senior roles emphasizing leadership and strategic thinking, and Staff/Principal roles emphasizing organizational impact and thought leadership. - Provide hiring managers with the template and customization guidance: the template provides the structural framework and level-appropriate language, while the hiring manager customizes the role-specific content (specific projects, team context, and technical requirements) to create a posting that is both level-consistent and role-specific. - Include an internal career context section in every job description: "This role is a [Level X] position within the [Job Family] family. Successful performance in this role prepares you for advancement to [Level X+1] positions such as [specific next-level roles]" provides career transparency that supports both external recruiting and internal development. - Maintain a job description library organized by job family and level: as the organization creates customized postings using the templates, archive each one as a reference for future similar postings, building an institutional library that improves consistency and reduces the time required to create new postings. **5. Compensation Band Integration** - Connect each level to a defined compensation band: the job architecture framework should directly map to the compensation structure, with each level assigned a salary range, target bonus percentage, and equity grant range that reflects the market value and organizational value of that level. - Establish compensation band width guidelines: entry levels typically have narrower bands (15-20% spread from minimum to maximum), mid levels have moderate bands (20-30% spread), and senior levels have wider bands (25-40% spread) to accommodate the greater variation in experience and impact at higher levels. - Define compensation positioning philosophy by level: some organizations start new hires at the low end of the band with performance-based progression, while others target the midpoint with above-midpoint compensation reserved for exceptional performers, and the philosophy should be documented and applied consistently. - Create level-appropriate total compensation mix: entry-level compensation is primarily base salary (85-90% of total), mid-level introduces meaningful variable compensation (75-80% base, 20-25% variable), and senior levels include significant equity and incentive components (60-70% base, 30-40% variable), reflecting the increased impact and risk-taking at higher levels. - Use the framework to conduct pay equity analysis: with roles consistently leveled and mapped to compensation bands, the organization can systematically identify pay gaps within levels by gender, race, and other protected characteristics, and address inequities proactively. - Benchmark compensation bands against market data: partner with compensation survey providers to benchmark each level's compensation bands against industry peers, and adjust bands annually to maintain competitive positioning in the talent market. **6. Implementation and Governance** - Map existing roles to the new framework: conduct a systematic exercise where every current role is mapped to the appropriate job family, track, and level, identifying inconsistencies (roles with the same title at different levels, roles at the same level with significantly different scope) that need resolution. - Engage leadership in framework validation: present the framework to executive leadership for alignment on level definitions, scope expectations, and compensation band connections before rolling out to the broader organization, ensuring top-down support for consistent application. - Communicate the framework transparently to employees: publish the complete job family catalog, level definitions, competency matrices, and career progression paths so that every employee can understand their current level, see what advancement requires, and plan their development accordingly. - Train managers on framework application: hiring managers need training on how to select the correct level for open positions, how to evaluate candidates against level-appropriate criteria, and how to use the competency matrix for promotion readiness assessment. - Establish a governance process for framework maintenance: assign ownership to the HR or People team for regular framework review (annually at minimum), new role addition, level definition updates, and compensation band adjustments, preventing the framework from becoming outdated. - Build feedback mechanisms for continuous improvement: collect input from hiring managers about whether level definitions match real-world role requirements, from employees about whether career progression is clear, and from recruiters about whether the framework supports effective talent acquisition, using this feedback to evolve the framework over time. Ask the user for: your organization's size and structure, the job families you want to define, the number of levels you currently use or want to implement, your compensation philosophy and current band structure, any existing career ladder or leveling documentation, and specific pain points in role definition or career progression that the framework should address.
Or press ⌘C to copy