Most organizations beyond 100 employees have a job architecture problem, even if they do not name it that way. The symptoms are familiar: inconsistent job titles across teams doing similar work, grade inflation as managers promote valued employees because compensation budget is constrained, compensation inequities that appear during audits because the same work is classified differently in different business units, and career conversation impasses because there is no clear definition of what it means to progress from one level to the next. Job architecture is the solution to all of these problems. It is also a prerequisite for pay transparency, which is now legally required in over a third of US states for job postings.

The Core Components of a Job Architecture

A complete job architecture has four structural elements:

  • Job families. Groups of related jobs that share common skill requirements and career pathways. Examples: Engineering, Product, Sales, Marketing, Finance, HR, Operations. Job families are the broadest organizing unit and typically map to functional areas of the organization.
  • Job functions. Sub-categories within job families that distinguish meaningfully different specializations. Within Engineering: Software Engineering, Data Engineering, Platform Engineering, QA. Within Sales: Account Executive, Sales Development, Customer Success, Sales Engineering. Job functions are the career tracks within which employees typically progress.
  • Job levels. The relative seniority and complexity tiers within a job function. Most organizations use 4 to 8 levels, typically including: Entry/Associate, Professional, Senior, Staff or Specialist, Principal or Expert, Manager, Senior Manager, Director. Each level should have a clear, behavioral definition of the scope, complexity, and independence expected.
  • Job grades. The compensation bands attached to levels. Multiple job functions at the same level may share a grade (all Level 3 professional roles), or may have different grades if market pricing supports a premium or discount. Grades are the link between job architecture and compensation.

Job architecture vs. job evaluation

Job architecture (designing the framework) and job evaluation (assessing specific roles against the framework) are related but distinct activities. Building the architecture is an HR design project done once and maintained over time. Evaluating roles against the architecture is an ongoing operational activity done when roles are created or significantly changed. The architecture is the measuring stick; job evaluation is the act of measuring. Conflating the two leads to architecture projects that get stuck in endless evaluation debates rather than framework design decisions.

Designing Level Definitions That Actually Work

The most critical element of a job architecture is the quality of level definitions. Weak level definitions produce grade inflation and inconsistent application. Strong level definitions are:

  • Behavioral and observable, not credential-based. "Operates independently on complex problems with minimal direction" is a better level descriptor than "requires 5+ years of experience." Experience is a proxy for capability. The architecture should describe the capability directly.
  • Differentiated enough to be practically distinguishing. If a manager cannot determine from the definition whether a specific employee belongs in Level 3 or Level 4, the definitions need more precision. A useful test: can a manager who reads the Level 3 and Level 4 definitions correctly place 90% of their team without asking HR for clarification?
  • Consistent across job functions within the same level. A Level 4 in Software Engineering and a Level 4 in Marketing should reflect genuinely comparable scope, complexity, and independence. This consistency is what allows a single pay band to cover multiple job functions at the same level.

Sample level definition structure

Level 3 (Senior Professional): Independently manages projects of moderate scope and complexity. Applies advanced knowledge in their domain to solve non-routine problems. Provides guidance to more junior colleagues on technical approaches. Work is reviewed periodically rather than continuously. Produces high-quality outputs with limited revision required. Identifies improvements to existing processes and practices within their area. Level 4 (Staff / Specialist): Manages complex, ambiguous projects that span multiple teams or systems. Recognized as a domain expert within the organization. Actively drives improvements that have significant impact beyond immediate team. Influences technical or functional direction at the team and occasionally broader organizational level. Can independently define the approach to novel problems in their domain.

Building Pay Bands on Top of Job Architecture

Once the job architecture is complete, pay band design connects the structural framework to compensation data. The standard approach:

  • Gather market pricing data for benchmark roles. For each job function and level, identify 3 to 5 benchmark roles — roles that are clearly defined, commonly found in the external market, and representative of the work. Price these roles using salary surveys (Radford, Willis Towers Watson, Mercer, or accessible sources like Levels.fyi for tech roles).
  • Select your market positioning policy. Most organizations target the 50th percentile (market median) as the midpoint of their pay bands. Organizations competing for top talent in tight labor markets target the 65th to 75th percentile. Non-profit and government-adjacent employers may target the 40th to 45th percentile with stronger non-monetary benefits.
  • Set band ranges. A standard pay band spans 80% to 120% of the midpoint, creating a 50% range (minimum to maximum). Wider ranges (70% to 130%) give more room for tenure and performance differentiation within a level. Narrower ranges create tighter control but may feel constraining to employees and managers.
  • Validate against your current population. Map all current employees to their grade and check their current salary against the new band. Identify employees below the minimum (to be remediated immediately), employees near the midpoint (appropriately placed), and employees above the maximum (red-circled).

Governance: Making the Architecture Stick

A job architecture that is not governed deteriorates quickly. The essential governance mechanisms:

  • Grade change approval process. All changes to an employee's grade level require HR review and approval, not just manager discretion. This prevents grade inflation through unilateral manager promotions.
  • Annual architecture review. Annually review whether new roles created in the past year have been correctly classified, whether market pricing movements require band adjustments, and whether grade distribution across the organization has shifted in ways that indicate systemic issues.
  • New role classification process. When a new role is created, the hiring manager and HRBP complete a job evaluation together before posting, using the architecture criteria to determine the correct level and grade. This prevents new hires from being posted at inflated grades to attract candidates.
Related Reading Helpful Calculators

Frequently Asked Questions

What is a job architecture framework?

A job architecture framework is a structured system that organizes all roles in an organization into job families, job functions, levels, and grades. It defines the criteria that distinguish one level from another, establishes consistent titling conventions, and creates the foundation for pay band design, career pathing, and succession planning. It is the operating system that makes consistent, defensible compensation and career decisions possible at organizational scale.

How many job levels should a mid-sized company have?

A company of 100 to 500 employees typically needs 6 to 8 levels: 2 to 3 individual contributor levels such as associate, professional, and senior; 1 to 2 specialist or expert levels; and 2 to 3 management levels including manager, senior manager or director, and senior director or VP. Adding more levels than the organization needs creates grade inflation and title escalation. The goal is the minimum number of distinct levels that reflect meaningful differences in scope, complexity, and market value.

What is the difference between a job level and a job grade?

Job levels describe the relative complexity, scope, and seniority of a role within a career progression. Job grades are the compensation bands associated with those levels. Multiple job families with the same level may share the same grade and compensation band, or may have different grades based on market pricing. The level defines the career architecture; the grade defines the pay structure. They work together but serve different purposes in people management.

When should a company build a formal job architecture?

The inflection point for building formal job architecture is typically around 75 to 150 employees. Below this size, informal systems can work with high management attention. Above this size, inconsistent titles, grade inflation, and compensation inequities begin compounding. The business catalysts that frequently trigger job architecture projects are a decision to implement pay transparency, an equity analysis that reveals compensation inconsistencies, or the organization reaching a headcount where career pathing conversations become unmanageable without a formal framework.

How do you prevent grade inflation after launching a job architecture?

Grade inflation prevention requires governance mechanisms: a defined process for grade change requests that requires HR review and approval, annual calibration sessions where managers across a business unit review grade distributions and identify outliers, and a clear policy that manager requests to upgrade an employee's grade require either a change in role scope or a documented business case. Without governance, grade inflation resumes within 12 to 18 months of framework launch as managers seek to reward valued employees through promotions when compensation budget is constrained.