Best Practices for Leveling

How many levels to have, how to distinguish them, and how to build career bands and matrices.

Why Leveling Matters

Job levels define the vertical structure of careers. They determine compensation bands, decision-making authority, performance expectations, and progression criteria. Get leveling wrong and organizations face: undifferentiated pay (everyone at the same level earns the same regardless of contribution), promotion inflation (levels created to give raises rather than reflect real differences), or excessive bureaucracy (too many levels with meaningless distinctions).

How Many Levels

Organization SizeRecommendedRationale
<200 employees5–7Fewer layers keep decisions fast. Every level should represent a meaningful step in scope and pay.
200–2,0007–10Add Principal/Staff IC tracks. Separate IC and Management at senior levels.
2,000–10,0008–12Full career bands. Align with grading frameworks (WTW, Korn Ferry).
10,000+12–25Multiple career bands, regional variations, executive tiers. WTW GGS supports up to 25.

The golden rule: if two adjacent levels cannot be clearly distinguished on at least three of the five differentiation dimensions (see below), they should be merged.

Five Dimensions for Distinguishing Levels

  1. Scope of responsibility — Individual tasks → Team outcomes → Department strategy → Business unit P&L → Enterprise strategy
  2. Complexity of problems — Well-defined → Ambiguous → Novel → Cross-functional → Transformational
  3. Autonomy — Guided → Independent → Strategic → Sets direction → Defines vision
  4. Impact — Task output → Project delivery → Function performance → Business unit results → Market/industry influence
  5. Skills depth — Basic → Qualified → Advanced → Professional → Domain Expert

Career Bands and Tracks

Career bands group multiple levels into broader categories. Common structure:

BandLevelsTypical TitlesCharacteristics
Individual Contributor1–6Analyst, Specialist, Senior, Staff, Principal, DistinguishedIncreasing technical depth, no people management required
Management3–6Team Lead, Manager, Senior Manager, Director, VP, SVPPeople leadership, organizational scope
Executive1–3VP, SVP, C-suiteEnterprise strategy, P&L accountability

Dual-track systems are essential for retaining technical talent. Without an IC track that reaches Senior Director-equivalent compensation, organizations lose their best engineers and scientists to management roles they do not want.

Level Matrices by Industry

IndustryIC LevelsMgmt LevelsNotable Pattern
Technology6–84–6Deep IC track (Staff → Principal → Distinguished). Fewer management layers.
Financial Services5–76–8Heavily regulated — precise leveling for compliance. More management tiers.
Manufacturing4–65–7Shift-based roles need work-mode leveling. Technician tracks distinct from office tracks.
Professional Services4–55–6Partner track as separate band. Revenue generation as primary differentiator.

Common Mistakes

  • Level inflation — Creating new levels to give raises. If the work does not change, the level should not change.
  • Title-driven leveling — Basing levels on title prestige rather than actual scope, complexity, and impact.
  • One-size-fits-all — Applying the same level structure to all functions. Engineering and Sales may need different level definitions even if the number of levels is the same.
  • Ignoring the matrix — Defining levels in isolation without considering how they interact across families and career tracks.

Need help building your Job & Skill Architecture? Talk to our team.

Talk to Hanns