Leveling and Comp Bands: Structure, Calibration, and Rollout

A leveling framework defines what expertise, scope, and impact each role and career step requires.

Leveling and Compensation Bands: Building a Framework Before It Becomes an Emergency

Leveling and compensation bands are the boring, high-leverage HR infrastructure that separates companies where pay conversations are calm and predictable from companies where every offer, promotion, and raise is a bespoke negotiation and where a Glassdoor leak reveals uncomfortable disparities. The framework has two parts: (1) a leveling ladder that describes what someone at each level is expected to know, do, and impact, and (2) compensation bands that assign base salary, equity, and target bonus ranges to each level, adjusted for geography and job family. Building this at 20-30 employees is proactive; building it at 80+ is triage.

The leveling ladder

A typical engineering ladder runs L1-L2 (junior), L3-L4 (mid), L5-L6 (senior, staff), L7-L8 (principal, distinguished). Each level should specify: scope (task, feature, team, org, company), autonomy (needs direction, works independently, sets direction for others, sets direction across the org), impact (contributes to team goals, drives team goals, influences other teams, shapes company strategy), and craft depth (learning fundamentals, competent, expert, industry-recognized). Write these as observable behaviors, not adjectives — 'delivers X-scoped projects on time' beats 'is a good engineer.' Parallel ladders for engineering management (EM, Senior EM, Director, VP) and product/design should map to equivalent IC levels for comp parity.

Building bands

Sources: Radford, Option Impact, Pave, Levels.fyi, and peer-CEO benchmarking. Pick two credible sources, target the 50th-75th percentile for your comp philosophy (or 25th-50th if you're cash-constrained and lean equity-heavy), and define bands with a ~30-40% spread (min-mid-max) per level. Geography: decide the model — same-band nationwide, tiered by geography (SF/NY tier 1, other major metros tier 2, rest tier 3), or fully location-based. Publish the philosophy internally; the specific numbers can be private but the framework should not. Bands drift; recalibrate every 12 months against updated benchmarks.

Placing existing employees into the framework

The scary but essential step. Have managers propose a level for each report based on the new ladder criteria; have skip-level managers calibrate across teams to prevent grade inflation in one team and grade suppression in another; have leadership calibrate across functions. Expected outcomes: (a) 60-70% of people land where their current title implied. (b) 15-25% are under-leveled and receive a title/comp adjustment. (c) 10-15% are over-leveled and don't — instead, freeze their comp and let them grow into the level. Communicate the framework and adjustments transparently; secret ad-hoc corrections generate the exact distrust the framework is meant to prevent.

Ongoing calibration

Twice yearly, run promotion and compensation cycles simultaneously across the whole org. Each manager submits promotion cases with evidence against the level criteria; a calibration committee (skip-levels + HR + a rotating peer) reviews. Comp adjustments follow: market movement (bring below-band people to band), performance (within-band raises), and promotions (to the new level's band). Reject the temptation to negotiate outside the framework for one 'critical' hire — every exception you make is quoted in every future negotiation and erodes the framework's authority.

Common pitfalls

(1) Overengineering — a 40-page ladder with 12 competency dimensions per level. Managers ignore it. Aim for 1-2 pages per level, 4-6 competency dimensions total. (2) Copying another company's ladder without adaptation — 'we use Google's ladder' is meaningless because scope and impact differ radically. Adapt shamelessly, but adapt. (3) Publishing bands without also publishing the philosophy — creates comparison shopping without context. (4) Not budgeting for band adjustments — if 20% of your team is underpaid vs. the new bands and you can't afford to correct them, don't roll out the framework yet. (5) Failing to update bands as the company scales — Series A bands look ridiculous at Series C stage and drive attrition.

Frequently asked questions

When should we introduce this?
Roughly 25-40 employees, before ad-hoc negotiation produces visible unfairness and before an equal-pay audit surfaces problems retroactively. Earlier if you're growing very fast or making many senior hires.
Should we publish comp bands internally?
Publishing bands (not individual comp) internally builds trust and reduces the tax of secretive comp culture — 'am I underpaid?' becomes checkable. Some companies go further and publish individual comp within a level; that requires much more organizational maturity to survive.
How do we handle a critical hire who wants above-band?
First, verify the level assignment — often the request is really 'this person is level N+1, not N.' If truly above-band for the level, either grant an equity premium (bands often stretch more on equity than base) or decline. Every above-band base is a landmine for internal equity when discovered.

Related fundraising guides (40)

Investor directory · Fundraising library · Articles A–Z · Company funding database