Job Architecture: Designing Roles, Levels, and Career Paths

Job Architecture: Designing Roles, Levels, and Career Paths

Every organisation has roles, titles, and some notion of hierarchy. But few organisations have a coherent job architecture — a structured framework that defines how roles relate to each other, what distinguishes one level from the next, and how employees can progress in their careers. Without this architecture, organisations face a predictable set of problems: title inflation, pay inequity, unclear career paths, inconsistent expectations, and difficulty benchmarking roles against the market.

Job architecture is the structural backbone of talent management. It connects role design to compensation, career development, workforce planning, and organisational design. Getting it right is foundational; getting it wrong creates systemic dysfunction.

What Job Architecture Consists Of

A well-designed job architecture typically includes four components:

1. Job families: Broad groupings of roles that share a common function or discipline — for example, Engineering, Finance, Human Resources, Sales, or Operations. Within each family, there are sub-families. For instance, within Engineering, there may be Software Development, Quality Assurance, and DevOps.
2. Job levels (or grades): A defined hierarchy of levels within each job family, from entry-level to senior leadership. Each level is distinguished by scope of responsibility, complexity of work, decision-making authority, and the degree of supervision required. A typical structure might include: Associate, Specialist, Senior Specialist, Lead, Manager, Senior Manager, Director, Vice President.
3. Job profiles: Descriptions for each role at each level that specify the purpose, key responsibilities, required competencies, and expected outcomes. These are more concise and structured than traditional job descriptions.
4. Career paths: Defined routes for progression — both vertical (promotions within a family) and lateral (movement across families or sub-families).

Job Evaluation and Grading Systems

To create a consistent and defensible levelling framework, many organisations use formal job evaluation methodologies. The two most widely adopted globally are:

• Hay Method (Korn Ferry Hay Group): Developed by Edward N. Hay in the 1940s, this is the oldest and most established job evaluation system. It evaluates roles on three factors: know-how (the knowledge, skills, and experience required), problem solving (the thinking challenges involved), and accountability (the impact of the role on organisational outcomes). Each factor is scored, and the total score determines the job grade. The Hay method is used by a large number of Indian conglomerates, public sector enterprises, and multinational companies operating in India.
• Mercer International Position Evaluation (IPE): Mercer's IPE system evaluates roles across five factors: impact, communication, innovation, knowledge, and risk. It uses a 48-grade structure that facilitates global comparisons and is particularly popular among organisations that need to benchmark roles across multiple countries. Many Indian IT and pharmaceutical companies use Mercer IPE for their global workforce.

Both systems aim to achieve the same outcome: an objective, consistent basis for comparing roles that is independent of the individual holding the role. This is essential for pay equity, market benchmarking, and organisational clarity.

Career Ladders vs. Career Lattices

Traditional career models assume a linear, upward trajectory — the career ladder. An analyst becomes a senior analyst, then a manager, then a senior manager, and so on. While simple and intuitive, the ladder model has significant limitations:

• It assumes everyone wants to manage people, which is not true for many technical specialists.
• It provides limited options for lateral growth, cross-functional experience, or career pivots.
• It creates bottlenecks at senior levels where fewer positions exist.

The career lattice model, advocated by Cathy Benko and Molly Anderson in their book The Corporate Lattice (2010, Harvard Business Review Press), offers a more flexible alternative. A lattice allows movement in multiple directions — up, across, or even temporarily down (for example, an employee moving from a management role to an individual contributor role in a new domain to build expertise). The lattice model better reflects how modern careers actually unfold and supports organisational agility.

In practice, many Indian organisations are adopting hybrid approaches: defined vertical levels with explicit lateral pathways, dual career tracks (management and technical/specialist), and project-based assignments that allow cross-functional exposure without permanent role changes.

Integration with Compensation and L&D

Job architecture achieves its full value only when it is integrated with other talent systems:

• Compensation: Each job grade is mapped to a salary band with a defined minimum, midpoint, and maximum. This creates internal pay equity (roles of similar value are paid similarly) and external competitiveness (bands are benchmarked against market data). Without job architecture, pay decisions are ad hoc, leading to unexplainable disparities that undermine trust and increase legal risk.
• Learning and development: Each job level should have defined competency expectations. The gap between an employee's current competencies and the requirements of the next level defines their development plan. This makes L&D investments targeted and career-relevant rather than generic.
• Workforce planning: Job architecture enables the organisation to analyse its talent distribution — how many people are at each level, where the demographic concentrations are, and where succession gaps exist.
• Recruitment: Standardised job profiles ensure that hiring managers and recruiters share a common understanding of what a role requires, reducing ambiguity and improving candidate assessment.

Job architecture is invisible when it works well — people understand their roles, see a path forward, and trust that the system is fair. When it is absent or poorly designed, the symptoms are everywhere: frustration, attrition, pay grievances, and a pervasive sense that career progression is arbitrary.

Building Job Architecture: Practical Steps

For Indian organisations that lack a formal job architecture, the following approach is recommended:

1. Begin with a role inventory — catalogue all existing roles, titles, and reporting relationships across the organisation.
2. Group roles into job families and sub-families based on functional similarity.
3. Define the levelling framework — determine how many levels are appropriate (typically six to ten for most mid-sized organisations) and articulate what differentiates each level.
4. Evaluate and grade roles using a consistent methodology. External support from a compensation consultancy can accelerate this step.
5. Map compensation bands to each grade using market data.
6. Communicate the architecture to employees with clarity and transparency. People need to understand where they sit today and what is required to progress.

Job architecture is not a one-time project. As the organisation grows, enters new markets, or adopts new technologies, the architecture must evolve. Annual reviews — particularly at the time of compensation benchmarking — ensure the framework remains current and credible.