How to level employees at a startup
Level the roles the company will need next year, not the people it happens to have today.
Short answer: To level employees at a startup, start from the work each role does and the roles the company will need as it grows, not from who holds them, how long they have stayed or what they are paid. Early titles and salaries were set in a rush. Leveling that copies them only makes past deals look official. The hard part is the people the new levels do not fit.
This is general information, not legal advice. Laws and data are summarized as checked on 20 and 21 October 2026; each one links to its source below.
Sixty people and four vice presidents
Take a typical software startup eight months after its first large funding round. It has 60 people and a plan to hire 40 more within a year. It has never had levels. Titles were agreed one hire at a time, by whichever founder made the offer.
The result looks normal from the inside and strange from the outside. There are four vice presidents, two of whom manage nobody. The first engineer, hired three years ago, is a "Principal Engineer" and earns less than a senior engineer who joined last spring with a competing offer. Two customer success managers do the same job under different titles, with salaries $18,000 apart. Nobody is sure whether the gap is about the work or about who asked.
Three things push the founders to act at once. A recruiter needs pay ranges for the next wave of job ads and has nothing to set them against. A strong engineer asks what she has to do to be promoted and gets a different answer from each founder. And a new board member asks how the company will keep pay consistent while doubling its headcount.
The founders agree to "do levels". The first draft follows the people: Each person gets a level close to their current title and salary, so that nobody is upset. It takes a weekend. It also writes every past negotiation into the structure the next 40 hires will be measured against.
This company is a composite of a common situation, not a client. Its details and numbers are illustrative.
Why leveling a startup is harder than it looks
Leveling means placing each role on a job level: A step on a ladder that describes the size of a job through its scope, its impact and how much direction it needs. In a large company the roles already exist and leveling is mostly sorting. In a startup two things make it harder.
The first is that the people and the roles are tangled. Early employees shaped their jobs around themselves. The first engineer may be doing the work of three roles that will exist separately in a year. A founding sales hire may carry a title that once meant "the only person in sales". Separating what the role is from who holds it is the core of the work and it is uncomfortable, because the people concerned are often the ones the company owes the most.
The second is that the company is about to change shape. A ladder that fits 60 people may not fit 100. The roles the company needs next year, such as the first engineering managers, the first specialists or the first people managing other managers, are not on today's chart. If the ladder only describes today, the next wave of hires will either not fit or will be squeezed into levels that were not written for them.
Those two facts create the tension. One goal is continuity: Keep early people whole, honor what was promised and avoid a demoralizing reset. The other is a fair structure for what comes next: Levels that describe work, so that the next 40 hires are placed on the same standard as the first 60. Leaning too far toward continuity freezes past deals. Leaning too far toward the clean structure can feel like a betrayal to the people who built the company.
The stakes have also gone up. Pay transparency laws in several US states turn levels into pay ranges that appear on job ads and that current employees can ask about. In the EU, employers must make the criteria for pay progression accessible to workers. A startup's first leveling is no longer a private exercise.
Five traps when a startup levels its people
Each of these feels like the kind or practical choice at the time. Each one makes the structure harder to defend later.
"Level the person, not the role"
What it looks like: People are placed according to how valued they are: Loyalty, tenure, how hard they would be to replace. The longest-serving engineer goes to the top level because she has been there the longest, whatever her current role involves.
Why smart teams fall into it: Founders know their early people well and want to recognize them. Placing them high looks like gratitude and avoids a hard conversation.
What it costs: The level then describes a person, not a job. When the next hire into the same role asks why they sit two levels lower, there is no answer based on the work. Under US equal pay law that is the answer that counts. The EEOC states that job content, not job titles, determines whether jobs are substantially equal. Recognition for early contribution is real and can be honored in other ways, such as equity or a recorded promise. Folding it into the level makes the level mean less for everyone else.
"Let current pay decide the level"
What it looks like: People are sorted by salary and the levels drawn around the clusters. Whoever earns the most lands on the highest level. No one's pay looks wrong because the levels were built to fit the pay.
Why smart teams fall into it: It is fast, it avoids awkward pay questions and it produces a tidy chart on the first try. It feels objective because it uses numbers.
What it costs: Startup salaries record who negotiated, who had a competing offer and what the market looked like the month someone joined. Building levels on top of them writes all of that into the structure. Gaps that came from negotiation now look like gaps in the work. The company loses the one chance it had to see which pay differences have a reason and which do not. The EU directive asks employers for pay structures built on objective, gender-neutral criteria such as skills, effort, responsibility and working conditions. Pay that set the levels cannot then be justified by them. Placing roles first and looking at pay afterward is what makes the gaps visible.
"Protect every early title"
What it looks like: Every current title is kept and mapped to a level, even when the work behind it does not match. The vice president with no reports stays a vice president, mapped to a level below other vice presidents. Titles and levels drift apart from day one.
Why smart teams fall into it: Titles matter to people, both inside the company and on their résumés. Taking one away feels like a demotion even when pay does not change.
What it costs: Inflated titles become a problem as soon as the company hires above them. The first real vice president arrives and finds peers who manage nobody. External candidates compare titles with their own and either expect too much or decline. Titles also carry into pay ranges: Washington's posting guidance asks for a range for each possible title when one ad covers several. A company that keeps titles which do not match levels ends up explaining the gap in public. Our guide on grade vs band vs level looks at why titles should follow levels.
"Level only for today's team"
What it looks like: The ladder has exactly the levels needed to place the current 60 people. There is no level for the first manager of managers, because there is none yet. The specialist track stops where the most senior current specialist sits.
Why smart teams fall into it: Writing levels for jobs nobody holds feels speculative. Leveling the people in front of you seems like the honest scope.
What it costs: The next 40 hires include roles the ladder cannot describe. Each one becomes an exception. Exceptions in the first year of a structure usually set its real rules. The company ends up adding levels in a rush for whoever is hired first, which is the pattern our guide on how many job levels you need warns against. Leveling the role the company will need next year, with a short written description, costs little and spares that scramble.
"Wait until something forces it"
What it looks like: Leveling is put off until a trigger arrives: A posting law, a pay complaint, a departing engineer citing unclear promotion, a board question. Then it is done in a few weeks under pressure.
Why smart teams fall into it: A startup has more urgent work than structure. Levels feel like a large-company habit that can wait.
What it costs: Every month adds hires and pay decisions made without a standard, each one another case to reconcile later. Leveling under pressure also tends to follow the people, because there is no time to do anything else. Meanwhile, the law has moved the trigger forward. Massachusetts lets a current employee ask for the pay range of the job they hold. California gives employees the right to the pay scale for their own position. Both assume the company has one. People also do not wait long for progress. ADP Research's analysis of payroll records for more than 51 million US workers found that nearly 75% left an employer before ever being promoted.
What a sound first leveling looks like
There is no single right ladder for a startup. What sound first levelings share, in our view, are these qualities.
- Roles were placed before people. Each role has a level based on what it does today. People were then matched to roles. Where someone does a bigger or smaller job than their title suggests, that is recorded rather than smoothed over.
- Pay was looked at last. Salaries were reviewed only after placement, so the company can see which gaps the levels explain and which they do not.
- The ladder reaches next year. It includes the levels the hiring plan needs, such as the first managers or senior specialists, even if nobody holds them yet.
- Levels mean the same across teams. A level in engineering and the same level in customer success are jobs of similar weight, even if they pay differently.
- Every placement has a reason in writing. A short note on the evidence of scope and impact, so the decision can be explained to the employee and to the next manager.
- Mismatches have a plan. People whose title or pay does not fit their level know what happens next and when.
- People can see the standard. Employees can read what each level means and what would move them up, even if individual placements stay private.
- One person owns it. One founder or leader decides placements and later changes, so the ladder does not drift back to one-off deals.
A useful sign that it worked: When the next hire for an existing role arrives, the level, the title and the pay range follow from the role without a negotiation about any of them.
The calls only you can make
These choices sit with the founders. Nobody outside the company can make them.
What happens to inflated titles. Change them now, keep them for current holders only or let them lapse at the next role change. Each option trades short-term goodwill against a clean structure. The choice matters more than which one is picked, as long as it is the same for everyone.
What happens to people paid above or below their level. Pay below the level's range can be raised at once or over a set period. Pay above it can be held while the range catches up. These are budget calls as much as fairness calls.
How to recognize early contribution. Early people took risks that later hires did not. Whether that is recognized through equity, a one-off award, a title kept as a courtesy or not at all is a values decision. It is better made openly than folded into the levels.
How much to show. Some startups publish the whole ladder and each person's level. Others share the level definitions and keep placements private. Aon's 2025 study found 61% of organizations had salary ranges but did not share them with employees. Where the company lands sets what people can compare.
When to start. Leveling before the next hiring wave is easier than leveling in the middle of it. The trade is founder time now against more cases to reconcile later.
The law and the numbers
As of 20 and 21 October 2026, these are the points we checked that bear on a startup's first leveling.
US equal pay law looks at the work. The EEOC states that jobs compared under equal pay law need not be identical but must be substantially equal. Job content, not job titles, decides that [1].
Employees can ask about their own range. In California, an employee can ask for the pay scale for the position they hold and the employer must keep each employee's title and wage history for the length of employment plus three years (FAQ 46 and 77) [2]. In Massachusetts, covered employers must give a current employee the pay range for their position on request (FAQ 9) [3].
Job ads need a range per title. Washington's guidance asks for a range set before posting and, where one ad could be filled at several titles, a range for each [4]. Illinois expects employers to tell current employees about promotion opportunities within 14 days of posting externally (FAQ 23 and 23A) [5].
The EU asks for clear criteria. Directive (EU) 2023/970 requires pay structures that compare jobs on skills, effort, responsibility and working conditions (Article 4) and requires employers to make the criteria for pay, pay levels and pay progression easily accessible to workers (Article 6). Member states may exempt employers with fewer than 50 workers from the pay progression part. Workers can ask for their own pay level and the average pay for the same work or work of equal value (Article 7) [6].
Most people leave before a promotion. ADP Research reports that, in its analysis of 2023 payroll records for more than 51 million US workers, nearly 75% left an employer before ever being promoted [7]. The figure is ADP's own.
Most ranges stay internal. Aon's 2025 Global Pay Transparency Study found 61% of organizations used salary ranges without communicating them to employees and 8% did not use ranges at all [8].
Our view
We think a startup's first leveling should start from the roles, including the ones it will need next year. Only then should it turn to the people and their pay. That order is what makes the result fair to the next hire as well as the current team.
The hard part is not writing level definitions. It is deciding what to do about the people the new levels do not fit: The early employee with a big title, the engineer paid below her level, the vice president with no team. Those calls deserve to be made deliberately and the same way for everyone, rather than hidden by drawing the levels around them.
Done this way, the first leveling is a one-time adjustment. Done by following the people, it becomes a permanent record of every early negotiation.
Where we help
We help startups do their first leveling in the right order: We write level definitions with your founders for the roles you have and the ones your hiring plan needs, place today's roles on them and flag the titles and placements that need a decision from you. The smallest starting point is our Leveling Starter Kit, which writes levels for up to three job families. If you would like to talk it through first, Book a free call.
Sources
- US Equal Employment Opportunity Commission, Equal Pay/Compensation Discrimination, checked 2026-10-20
- California Labor Commissioner, Equal Pay Act FAQ (questions 46 and 77), checked 2026-10-20
- Massachusetts Attorney General's Office, Pay Transparency in Massachusetts (FAQ 9), checked 2026-10-20
- Washington L&I, Administrative Policy ES.E.2, Job Posting Requirements (issued 3 December 2025), checked 2026-10-20
- Illinois Department of Labor, Equal Pay Act salary transparency FAQ (questions 23 and 23A), checked 2026-10-20
- Directive (EU) 2023/970 on pay transparency, Articles 4, 6 and 7 (EUR-Lex), checked 2026-10-20
- ADP Research, People at Work 2025: A Global Workforce View, checked 2026-10-21
- Aon, 2025 Global Pay Transparency Study, checked 2026-10-20