
Strategy
Level Structure for Startups and Scaleups
A leveling structure can be challenging to build at a startup / scaleup… or maybe not? Knowledge is power, so we will share what we've learned on the subject. What is a job level? It is simply a way of classifying a set of responsibilities expected of…
Published Nov 4, 2022
Building a level structure can be challenging at a startup / scaleup... or maybe not? Knowledge is power, so we will share what we've learned on the subject.
What is a job level?
It is simply a way of classifying a set of expected responsibilities for the roles in your company. It is one of the main elements for identifying the seniority of roles (note that this refers to ROLES, not PEOPLE) within an organization. The higher the level, the greater the expected complexity. This logic also applies to indicate the degree of autonomy.
Because it is a general concept for the entire organization, the elements considered when defining each level must be broad and applicable across all functions. Dimensions such as scope, responsibility and teamwork can be used for individual contributors, while people management, conflict resolution and leadership apply to managers. Others can apply to both groups.
Levels are used for many aspects of managing the company and its people, such as career plans, delegation of authority, training, performance reviews, eligibility for policies and processes, compensation, among others.
A level structure is different from a career ladder. The latter is intended for a group of roles and has more specific performance requirements. Think of the level as something more general that applies across the entire organization, while the career ladder is more detailed and directed at a functional structure.
- Illustrative scenario: among the dimensions defined for all individual contributor levels are Communication and Execution.
- For a Sales role, more precise articulation involving storytelling techniques may be expected in addition to Communication.
- In the Engineering structure, coding is an important point and something beyond Execution has become a necessity. A competency related to Analysis Structuring may be expected, aimed at identifying what was delivered and how it was done.
Why have a level structure?
There are some advantages. The main ones are:
- Career management: the fact that a startup / scaleup is not a large organization does not mean it can't have a career plan. A well-defined level structure will help make that path visible, including when hiring people (or promoting them), and can also be used as one of the parameters of performance management.
- Scalability: today the company may be small or mid-sized. But what if it grows at an unexpected speed? The need to create new roles may arise, and having a level structure will make that scenario easier to handle.
- Market alignment: in many cases, following what is considered market practice is a good governance move. Level structures are no different. Other companies have been through this too, and it is prudent to replicate market knowledge in your company. It also makes comparing internal versus external equity easier, which helps in managing people.
How to establish a level structure?
Many companies around the world strive to find the perfect formula for this. But the truth is there is no universal approach that will meet every need. A company of 10 employees is very different from one with 500. It is important to consider the scalability of the structure so that it lasts for a while.
That said, you need a starting point. If your goal is to build a simple structure, our suggestion is to start with 8 levels, as below:
| Level* | Individual Contributor Track | Management Track |
|---|---|---|
| L08 | C-level | |
| L07 | Director | |
| L06 | Senior Manager | |
| L05 | Senior Specialist | Manager |
| L04 | Specialist | Coordinator |
| L03 | Senior | Supervisor |
| L02 | Mid-level | |
| L01 | Junior | |
| L00 | Assistant / Intern |
*Variations may exist depending on company size (e.g., small structures may have fewer management levels)
This will probably be enough to serve most organizations of up to about 1,000 employees. For companies with few people it may seem like a lot, but keep scalability and growth in mind. It will vary a lot from scenario to scenario. Some companies may use this structure for a long time, while others will need to revise it sooner.
It is worth noting that it helps to establish the equivalence between the tracks of individual contributor levels (individual contributors or IC) and manager levels (managers or M).
The number of levels you will actually use in your headcount will vary with the company's needs and current moment. And this can change by area. A similar logic can be applied to defining role scope (generalist vs. specific).
- Example A: say there is an urgent need and you have to hire a software engineer. The expectation is that the person works independently to run projects, with minimal guidance from the team's manager. So a senior/staff level role may make more sense in this situation.
- Example B: we have 3 operations analysts who handle routine activities very well. But none of them has the knowledge needed to scale the processes, and the company is growing fast. Opening a manager-level position may be a viable way to prepare this team to reach the goal.
- Example C: to support the company's growth, a new senior-level position is needed on the human resources team. However, challenges are getting harder to predict. Instead of considering a professional with a specific focus (recruiting, compensation, training, etc.), it may make more sense to hire a generalist profile. Right now there may be high demand for recruiting, but a few months from now a peak in training activities. This way you keep flexibility in handling challenges and, if needed, can revisit the scope in the future.
Thinking about maintaining the structure
Like the organization, the structure is alive. That means you need to periodically assess whether it needs a review. Doing this exercise to make sure it is still adequate is crucial, but it doesn't necessarily mean changes will be made. Adapt it to the reality of your startup / scaleup.