Engineering Ladders

Introduction

This framework allows software engineering managers to have meaningful conversations with their direct reports around the expectations of each position and how to plan for the next level in their career ladder.

The framework relies heavily in radar charts to show visually the different perspectives and expectations of a given position:

Career Ladders

The framework has 3 different ladders:

• Developer: role also known as programmer or software engineer, requires a deep level of technical expertise
• Tech Lead: role also known as dev lead, is the owner of the system and requires a unique balance between hands-on development, architecture knowledge and production support
• Engineering Manager: role also known as dev manager, is responsible for the consistent delivery, career growth and level of happiness of the team

Level	Seniority	Developer	Tech Lead	Engineering Manager
1	Junior	D1
2	Junior	D2
3	Junior	D3
4	Senior	D4	TL4
5	Senior	D5	TL5	EM5
6	Senior	D6	TL6	EM6
7	Senior	D7	TL7	EM7

Axes

The chart shown above has the following 5 axes:

• Technology: knowledge of the tech stack and tools

• System: level of ownership of the system(s)

• People: relationship with the team(s)

• Process: level of engagement with the development process

• Influence: scope of influence of the position

The influence axis can be seen as a different dimension since it is orthogonal and applies to all the other axes.

Each axis has 5 different levels of performance. It is important to highlight that every level includes the previous one(s). For example, someone that evangelizes technology, specializes and adopts it as well.

Keep reading to better understand each level.

Levels

Technology

1. Adopts: actively learns and adopts the technology and tools defined by the team

2. Specializes: is the go-to person for one or more technologies and takes initiative to learn new ones

3. Evangelizes: researches, creates proofs of concept and introduces new technologies to the team

4. Masters: has very deep knowledge about the whole technology stack of the system

5. Creates: designs and creates new technologies that are widely used either by internal or external teams

System

1. Enhances: successfully pushes new features and bug fixes to improve and extend the system

2. Designs: designs and implements medium to large size features while reducing the system’s tech debt

3. Owns: owns the production operation and monitoring of the system and is aware of its SLAs

4. Evolves: evolves the architecture to support future requirements and defines its SLAs

5. Leads: leads the technical excellence of the system and creates plans to mitigate outages

People

1. Learns: quickly learns from others and consistently steps up when it is required

2. Supports: proactively supports other team members and helps them to be successful

3. Mentors: mentors others to accelerate their career-growth and encourages them to participate

4. Coordinates: coordinates team members providing effective feedback and moderating discussions

5. Manages: manages the team members’ career, expectations, performance and level of happiness

Process

1. Follows: follows the team processes, delivering a consistent flow of features to production

2. Enforces: enforces the team processes, making sure everybody understands the benefits and tradeoffs

3. Challenges: challenges the team processes, looking for ways to improve them

4. Adjusts: adjusts the team processes, listening to feedback and guiding the team through the changes

5. Defines: defines the right processes for the team’s maturity level, balancing agility and discipline

Influence

1. Subsystem: makes an impact on one or more subsystems

2. Team: makes an impact on the whole team, not just on specific parts of it

3. Multiple Teams: makes an impact not only his/her team but also on other teams

4. Company: makes an impact on the whole tech organization

5. Community: makes an impact on the tech community