Trên GitHub, jorgef/engineeringladders đã đạt 8.6k sao. A framework for Engineering Managers
Tóm tắt dựng từ metadata GitHub của chính dự án — chưa có bài review TopGit. Trang sẽ tự động cập nhật khi bài review đầy đủ được xuất bản.
VÌ SAO CHƯA CÓ REVIEW
TopGit viết bài đầy đủ cho repo có nhiều sao nhất và được yêu cầu nhiều nhất. Trang này là snapshot trong thời gian chờ — xem README gốc ở tab READ ME.
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.
Although the framework uses roles and levels that are somewhat standard in the US tech industry, every company is different. Please use the information provided as a baseline and feel free adjust it to your needs.
The framework relies heavily on radar charts to visually represent the different perspectives and expectations of a given position:
Career Ladders
The framework has 4 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
Technical Program Manager: role responsible for coordinating and driving to completion initiatives that span multiple teams
Engineering Manager: role also known as dev manager, is responsible for the consistent delivery, career growth and level of happiness of the team
If you are confused about the difference between a Tech Lead and an Engineering Manager, please refer to the Tech Lead vs Engineering Manager page for a detailed comparison.
Level
Senior
Developer
Tech Lead
Technical Program Manager
Engineering Manager
1
No
D1
2
No
D2
3
No
D3
4
Yes
D4
TL4
TPM4
5
Yes
D5
TL5
TPM5
EM5
6
Yes
D6
TL6
TPM6
EM6
7
Yes
D7
TL7
TPM7
EM7
(click on position name for more details)
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
Adopts: actively learns and adopts the technology and tools defined by the team
Specializes: is the go-to person for one or more technologies and takes initiative to learn new ones
Evangelizes: researches, creates proofs of concept and introduces new technologies to the team
Masters: has very deep knowledge about the whole technology stack of the system
Creates: designs and creates new technologies that are widely used either by internal or external teams
System
Enhances: successfully pushes new features and bug fixes to improve and extend the system
Designs: designs and implements medium to large size features while reducing the system's tech debt
Owns: owns the production operation and monitoring of the system and is aware of its SLAs
Evolves: evolves the architecture to support future requirements and defines its SLAs
Leads: leads the technical excellence of the system and creates plans to mitigate outages
People
Learns: quickly learns from others and consistently steps up when it is required
Supports: proactively supports other team members and helps them to be successful
Mentors: mentors others to accelerate their career-growth and encourages them to participate
Coordinates: coordinates team members providing effective feedback and moderating discussions
Manages: manages the team members' career, expectations, performance and level of happiness
Process
Follows: follows the team processes, delivering a consistent flow of features to production
Enforces: enforces the team processes, making sure everybody understands the benefits and tradeoffs
Challenges: challenges the team processes, looking for ways to improve them
Adjusts: adjusts the team processes, listening to feedback and guiding the team through the changes
Defines: defines the right processes for the team's maturity level, balancing agility and discipline
Influence
Subsystem: makes an impact on one or more subsystems
Team: makes an impact on the whole team, not just on specific parts of it
Multiple Teams: makes an impact not only his/her team but also on other teams
Company: makes an impact on the whole tech organization
Community: makes an impact on the tech community
FAQs
What if some of the people don't meet all the points?
That is very normal, people are usually stronger in some areas and weaker in others. The framework should not be used as a checklist to promote people but instead as guidance to have meaningful career conversations.
What if my organization's career ladder is different?
Since the framework is open source, you have the opportunity to adapt it to your organization. Feel free to use the chart template to define your own levels.
When is a person ready to move to the next level?
Companies usually expect a person to be performing at the next level consistently for several months before formalizing a promotion.
How do I collect evidence to support the discussion with my direct reports?
Different teams collect evidence in different ways. A recommended approach is to use a combination of:
1:1 conversations
Feedback from peers and other teams
Self-evaluation
Could the framework provide more specific examples of behavior to support each level?
Specific examples of behavior require knowledge about the way that the team works, the system architecture and its technology stack. It is recommended to allow each team to define their own examples.
Why does the framework stop at level 7?
Levels 8 and above vary drastically from company to company. Organizations of different sizes tend to assign a diverse level of scope to positions so high in their structure.
Do you have any additional resources about the topic?
The Manager's Path: Camille Fournier does an excellent job at describing the expectations and challenges of many engineering positions. Also, she provides good advice about writing a career ladder in chapter 9.
How to Be Good at Performance Appraisals: Dick Grote explains in simple terms how to define job responsibilities and how to evaluate performance (results and behaviors).
Trang TopGit này là một snapshot — tab "Readme" hiển thị nguyên văn README của repo (đã bỏ link, giữ ảnh). Repo GitHub ở github.com/jorgef/engineeringladders là nguồn chính thức.
jorgef/engineeringladders có bao nhiêu sao?
jorgef/engineeringladders có 8.6k sao GitHub — tải lại trang để xem số mới nhất, hoặc xem trực tiếp github.com/jorgef/engineeringladders. TopGit phản chiếu số sao của GitHub nhưng không cam kết đến từng phút.
jorgef/engineeringladders có phải mã nguồn mở không?
Có — jorgef/engineeringladders phát hành theo license Apache-2.0, nghĩa là mã nguồn mở để đọc, fork và (tùy license) tái sử dụng. Mã: github.com/jorgef/engineeringladders.
jorgef/engineeringladders còn đang phát triển không?
Commit gần nhất trên jorgef/engineeringladders là 4.1 năm trước (theo timestamp GitHub). Repo có 595 fork — một chỉ báo về mức độ quan tâm của cộng đồng.
jorgef/engineeringladders là gì?
jorgef/engineeringladders (jorgef/engineeringladders) là dự án đa ngôn ngữ trên GitHub. Theo mô tả gốc: A framework for Engineering Managers
Đọc đầy đủ README ở tab phía trên.
engineeringladders có đáng để bạn bỏ thời gian?
ChatGPT, Claude và Perplexity đều đọc được trang này. Hỏi thử xem họ nghĩ gì về engineeringladders.