The process of assigning jobs to a hierarchy of grades or levels based on their relative value, complexity, and organizational impact, creating a structured framework that connects roles to compensation bands, career paths, and organizational hierarchy.
Key Takeaways
Job grading is the organizational scaffolding that holds your compensation system together. Every role gets a grade. Every grade has a pay range. Every pay range has a clear relationship to the grades above and below it. That's the structure. Without it, compensation decisions become arbitrary. A job grade tells you three things about a role: how senior it is relative to other roles, what salary range applies to it, and what career progression from it looks like. When an employee asks, "What's the next step in my career?" the grading structure provides the answer. When a recruiter asks, "What's the budget for this hire?" the grade determines it. When a compensation analyst runs a pay equity review, grades define the comparison groups. The term "grading" gets used interchangeably with "leveling" in many organizations, especially in tech where companies talk about "Level 5 engineer" or "L7 manager." Different vocabulary, same concept. Whether you call it a grade, a level, a band, or a step, you're talking about placing a role on a defined rung of the organizational ladder.
Organizations choose between narrow, broad, and broadband grading structures depending on their size, culture, and compensation philosophy.
| Structure Type | Number of Grades | Band Width | Best For | Trade-off |
|---|---|---|---|---|
| Narrow-grade | 15-25 grades | 20-30% spread | Government, unionized environments, hierarchical organizations | Clear progression but creates frequent reclassification requests and perceived "ceiling" at each grade max |
| Broad-grade | 8-15 grades | 40-60% spread | Mid-size to large private-sector companies | Balances structure with flexibility. Most common in corporate environments |
| Broadband | 4-8 bands | 80-150% spread | Flat organizations, tech companies, creative agencies | Maximum flexibility for managers but less perceived upward mobility and harder to maintain equity |
Building a grade structure is a multi-step process that connects job evaluation results to your compensation philosophy.
You need evaluation scores (Hay Points, custom point-factor totals, or ranking results) before you can build grades. Plot all evaluated jobs on a scale from lowest to highest score. Look for natural breakpoints where scores cluster together and gaps where scores jump. These clusters and gaps indicate natural grade boundaries. If most jobs cluster around 250 to 350 points with a gap before the next cluster at 400 to 500, that gap is likely a grade boundary.
Set point ranges for each grade. Ensure the ranges don't overlap (or overlap minimally if you want flexibility). Each grade should contain roles that are genuinely comparable in organizational value. If you find a grade with both administrative assistants and mid-level managers, the boundaries need adjustment. Aim for 15 to 30 roles per grade in a mid-size company. Fewer than 10 roles per grade suggests you have too many grades.
Each grade gets a salary band with a minimum, midpoint, and maximum. The midpoint is typically set at the 50th percentile of market data for roles in that grade. The minimum is usually 80 to 85% of midpoint. The maximum is 115 to 120% of midpoint for a 40 to 50% total spread. Midpoint-to-midpoint progression between adjacent grades is typically 15 to 20%, meaning each promotion represents a meaningful pay increase.
After building the structure, check that the salary bands are competitive. If your Grade 8 band tops out at $120,000 but the market pays $140,000 for roles in that grade, you'll lose people. Market data should inform the band positions even though the grade structure is based on internal evaluation. Adjust bands where market data diverges significantly from internal evaluation, and document the market premium as a separate pay element.
Understanding the different types of movement within a grading system is essential for both HR and employees.
Most employees spend 2 to 4 years in a grade before moving up. During that time, they progress within the band through merit increases, typically moving from the minimum toward the midpoint as they gain experience and demonstrate competency. A new hire might start at 85% of midpoint and reach 100% after 2 to 3 years of solid performance. Performance-based raises and market adjustments drive within-grade movement.
Moving from one grade to the next is a promotion. It usually comes with a 10 to 15% salary increase, positioning the employee at or near the minimum of the new grade's band. Not every employee will be promoted. Some roles are terminal grades for their function. A senior individual contributor at Grade 9 might not have a Grade 10 IC role above them, meaning the next move is either into management or a lateral shift to a different function.
Moving to a different role at the same grade. These moves are valuable for broadening experience and preparing for future promotions, but they don't come with grade increases. Some organizations offer a small "lateral bonus" (2 to 5%) to incentivize moves that benefit the company but don't represent upward mobility for the employee.
Even well-designed grading systems develop problems over time. Here are the most frequent issues.
Benchmarking data for organizations designing or updating their grading structures.
Technology companies use a distinctive grading approach that's worth understanding because it's become the standard in one of the world's largest employment sectors.
Most large tech companies use a numbered leveling system (L3 through L10 at Google, E3 through E9 at Meta, 59 through 80 at Microsoft). Each level has an explicit rubric covering technical skill, scope of impact, leadership, and autonomy. The levels map directly to compensation bands, stock grant sizes, and bonus targets. Unlike traditional grading where only HR knows the structure, tech companies often publish their leveling rubrics internally, and sites like levels.fyi have made them public externally.
Tech leveling emphasizes individual contribution over management responsibility. A Staff Engineer (L6 at Google) can earn more than an Engineering Manager (L5) because the IC track is valued as highly as the management track. Traditional grading systems often penalize ICs at senior levels because factors like "supervisory responsibility" don't apply. Tech companies solved this by using factors like "scope of influence" and "technical leadership" that reward senior ICs appropriately.