You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/MG3.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,8 @@ Connects different members and projects across teams to solve issues.
74
74
75
75
76
76
## Ownership
77
-
**Responds to small-scale incidents within their team and actively creates** post-mortem reports **that other engineers can use to prevent the incident from reoccurring.**
77
+
**Uses appropriate processes, methods, and tools to share relevant and useful information about their team and related projects with other members.**
78
+
**Examples: Leverages methods such as post-incident analysis (post-mortem), pros/cons lists, decision matrices, etc.**
78
79
79
80
Investigates risks **and creates and carries out contingency plans for the future.**
80
81
@@ -83,15 +84,15 @@ Investigates risks **and creates and carries out contingency plans for the futur
83
84
84
85
### [Engineering Manager Skills]
85
86
86
-
Comes up with suggestions to improve systems and processes at the team scale, enabling people to handle technical incident more efficiently.
87
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized within the team.
87
88
88
89
Encourages everyone in the team to take ownership of their work.
89
90
90
91
Encourages failure analysis focused on the process, not on individuals.
91
92
92
93
93
94
## Expertise
94
-
**Shares knowledge and techniques they learn with engineers around them. Knows the importance of tech outreach and shares useful information inside and outside the company.**
95
+
**Shares knowledge with and teaches techniques to engineers around them. Knows the importance of tech outreach and shares useful information inside and outside the company.**
95
96
96
97
**Has deep knowledge of the code and uses that knowledge in actively doing** code reviews **for the team.**
97
98
**Suggests new guidelines and ways to improve systematic debugging; resolves technical issues and bugs with large impact.**
Copy file name to clipboardExpand all lines: en/MG4.md
+4-3
Original file line number
Diff line number
Diff line change
@@ -75,16 +75,17 @@ Connects different members and projects across **their entire division** to solv
75
75
76
76
77
77
## Ownership
78
-
**Shares post-mortem reports and makes sure that all stakeholders (both within and outside of their team) understand the impact and can take action** to prevent the incident from reoccurring.
78
+
**Contributes to standardization of information-sharing processes, or uses them to document and share high-impact information that is used across multiple teams or projects.**
79
+
**Examples: Proposing improvements, presenting at meetings, and creating tools, documents or guidelines for their division**
79
80
80
81
Investigates risks, **coordinates with relevant teams, and takes necessary measures.**
81
82
**Boosts risk management awareness among their team.**
82
83
83
-
**Investigates and discusses** ways to improve their team **and other teams, taking the lead to implement work/process improvements in projects involving multiple teams.**
84
+
**Investigates and discusses** ways to improve their team **and other teams, taking the lead to implement work/process improvements & best practices in projects involving multiple teams.**
84
85
85
86
### [Engineering Manager Skills]
86
87
87
-
Comes up with suggestions to improve systems and processes at **the multiple teams**, enabling people to handle technical incident more efficiently.
88
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized **across multiple teams or projects.**
88
89
89
90
Encourages **engineers across multiple teams** to take ownership of their work.
Copy file name to clipboardExpand all lines: en/MG5.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -72,16 +72,16 @@ Connects different members and projects across their entire **company** to solve
72
72
73
73
74
74
## Ownership
75
-
**Encourages other members of their company to share** post-mortem reports and makes sure that **other engineers** can take action to prevent the incident from reoccurring.
75
+
**Promotes documentation and process standardization**, information and knowledge sharing, and **fosters a culture of applying these practices across the company.**
76
+
**Examples: Proposes and implements best practices for the entire company and contributes to the projects and committees related to them**
76
77
77
78
Investigates risks, coordinates with relevant teams **across their company**, and takes necessary measures.
78
-
**Creates and promotes the organization's best security practices.**
79
79
80
-
Investigates and discusses ways to improve **work in company-level development; takes** the lead to implement improvements **across the company.**
80
+
Investigates and **proposes** ways to improve **development efficiency and practices at the company level; Leads the implementation of improvements & best practices across the company.**
81
81
82
82
### [Engineering Manager Skills]
83
83
84
-
Comes up with suggestions to improve systems and processes at the **company scale**, enabling people to handle technical incident more efficiently.
84
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized **within the company.**
85
85
86
86
Encourages engineers across **their company** to take ownership of their work.
Copy file name to clipboardExpand all lines: en/MG6.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -74,15 +74,15 @@ Encourages **engineers across the group** to value different opinions and divers
74
74
75
75
76
76
## Ownership
77
-
Encourages other members **across companies** to share post-mortem reports and makes sure that other engineers can take action to prevent the incident from reoccurring.
77
+
Promotes documentation and standardization, information and knowledge sharing, and fosters a culture of applying these practices across the **group.**
78
78
79
79
Investigates risks **in development across companies and is recognized as a risk management expert in the group.**
80
80
81
81
**Encourages engineers across the group to focus on the process, not on individual responsibilities, and leads efforts to solve issues involving multiple companies.**
82
82
83
83
### [Engineering Manager Skills]
84
84
85
-
Comes up with suggestions to improve systems and processes at the **group** scale, enabling people to handle technical incident more efficiently.
85
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized within the **group.**
86
86
87
87
Encourages engineers across **the entire group** to take ownership of their work.
Copy file name to clipboardExpand all lines: en/engineering_ladder.csv
+18-14
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,8 @@ Examples: Source control, editors, the build system, best practices for testing"
17
17
18
18
Explains that praise and feedback are useful when delivered in a kind manner.
19
19
20
-
Listens to others and makes their best effort to understand them, in order to build strong relationships with their teammates and manager.","Tries to understand the reason why a bug occurs and also can explain the importance of sharing post-mortem reports.
20
+
Listens to others and makes their best effort to understand them, in order to build strong relationships with their teammates and manager.","Can find and leverage the knowledge required for their work.
21
+
Creates documents relevant to their team for information sharing.
21
22
22
23
Explains the importance of security and risk management.
23
24
@@ -45,7 +46,8 @@ Explains how their team’s domain **contributes to** the product **and how the
45
46
46
47
**Delivers** praise and **constructive feedback.**
47
48
48
-
Listens to others, **pays attention to nonverbal communication, and builds** strong relationships with their teammates, manager, **and product counterparts.**","**Follows incident handling procedures and contributes to** post-mortem reports.
49
+
Listens to others, **pays attention to nonverbal communication, and builds** strong relationships with their teammates, manager, **and product counterparts.**","**Not only creating documentation for their team, but improves the team's documentation as needed.**
50
+
**Understands and explains the importance of sharing knowledge and information.**
49
51
50
52
**Investigates risks discovered and escalates issues to senior members.**
51
53
@@ -104,7 +106,8 @@ Values different opinions and diverse ideas, and encourages everyone in their te
104
106
105
107
Delegates tasks to promote skill growth and takes responsibility for onboarding new members.
106
108
107
-
Connects different members and projects across teams to solve issues.","**Responds to small-scale incidents within their team and actively creates** post-mortem reports **that other engineers can use to prevent the incident from reoccurring.**
109
+
Connects different members and projects across teams to solve issues.","**Uses appropriate processes, methods, and tools to share relevant and useful information about their team and related projects with other members.**
110
+
**Examples: Leverages methods such as post-incident analysis (post-mortem), pros/cons lists, decision matrices, etc.**
108
111
109
112
Investigates risks **and creates and carries out contingency plans for the future.**
110
113
@@ -113,11 +116,11 @@ Investigates risks **and creates and carries out contingency plans for the futur
113
116
114
117
[Engineering Manager Skills]
115
118
116
-
Comes up with suggestions to improve systems and processes at the team scale, enabling people to handle technical incident more efficiently.
119
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized within the team.
117
120
118
121
Encourages everyone in the team to take ownership of their work.
119
122
120
-
Encourages failure analysis focused on the process, not on individuals.","**Shares knowledge and techniques they learn with engineers around them. Knows the importance of tech outreach and shares useful information inside and outside the company.**
123
+
Encourages failure analysis focused on the process, not on individuals.","**Shares knowledge with and teaches techniques to engineers around them. Knows the importance of tech outreach and shares useful information inside and outside the company.**
121
124
122
125
**Has deep knowledge of the code and uses that knowledge in actively doing** code reviews **for the team.**
123
126
**Suggests new guidelines and ways to improve systematic debugging; resolves technical issues and bugs with large impact.**
@@ -180,16 +183,17 @@ Knows the impact their team’s **and other team’s** work has on end users and
180
183
181
184
**Mentors their team members in an open and respectful manner; goes beyond their team to improve onboarding for engineers.**
182
185
183
-
Connects different members and projects across **their entire division** to solve issues.","**Shares post-mortem reports and makes sure that all stakeholders (both within and outside of their team) understand the impact and can take action** to prevent the incident from reoccurring.
186
+
Connects different members and projects across **their entire division** to solve issues.","**Contributes to standardization of information-sharing processes, or uses them to document and share high-impact information that is used across multiple teams or projects.**
187
+
**Examples: Proposing improvements, presenting at meetings, and creating tools, documents or guidelines for their division**
184
188
185
189
Investigates risks, **coordinates with relevant teams, and takes necessary measures.**
186
190
**Boosts risk management awareness among their team.**
187
191
188
-
**Investigates and discusses** ways to improve their team **and other teams, taking the lead to implement work/process improvements in projects involving multiple teams.**
192
+
**Investigates and discusses** ways to improve their team **and other teams, taking the lead to implement work/process improvements & best practices in projects involving multiple teams.**
189
193
190
194
[Engineering Manager Skills]
191
195
192
-
Comes up with suggestions to improve systems and processes at **the multiple teams**, enabling people to handle technical incident more efficiently.
196
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized **across multiple teams or projects.**
193
197
194
198
Encourages **engineers across multiple teams** to take ownership of their work.
195
199
@@ -254,16 +258,16 @@ Encourages members **across** their **company** to value different opinions and
254
258
255
259
Mentors their team members **and other EMs** in an open and respectful manner; improves onboarding for engineers **on the company level.**
256
260
257
-
Connects different members and projects across their entire **company** to solve issues.","**Encourages other members of their company to share** post-mortem reports and makes sure that **other engineers** can take action to prevent the incident from reoccurring.
261
+
Connects different members and projects across their entire **company** to solve issues.","**Promotes documentation and process standardization**, information and knowledge sharing, and **fosters a culture of applying these practices across the company.**
262
+
**Examples: Proposes and implements best practices for the entire company and contributes to the projects and committees related to them**
258
263
259
264
Investigates risks, coordinates with relevant teams **across their company**, and takes necessary measures.
260
-
**Creates and promotes the organization's best security practices.**
261
265
262
-
Investigates and discusses ways to improve **work in company-level development; takes** the lead to implement improvements **across the company.**
266
+
Investigates and **proposes** ways to improve **development efficiency and practices at the company level; Leads the implementation of improvements & best practices across the company.**
263
267
264
268
[Engineering Manager Skills]
265
269
266
-
Comes up with suggestions to improve systems and processes at the **company scale**, enabling people to handle technical incident more efficiently.
270
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized **within the company.**
267
271
268
272
Encourages engineers across **their company** to take ownership of their work.
269
273
@@ -330,15 +334,15 @@ Encourages **engineers across the group** to value different opinions and divers
330
334
331
335
**Works to train new mentors across the organization and provides other EMs with opportunities to grow their career and learn new skills.**
332
336
333
-
**Communicates appropriately to achieve goals in development across companies.**","Encourages other members **across companies** to share post-mortem reports and makes sure that other engineers can take action to prevent the incident from reoccurring.
337
+
**Communicates appropriately to achieve goals in development across companies.**","Promotes documentation and standardization, information and knowledge sharing, and fosters a culture of applying these practices across the **group.**
334
338
335
339
Investigates risks **in development across companies and is recognized as a risk management expert in the group.**
336
340
337
341
**Encourages engineers across the group to focus on the process, not on individual responsibilities, and leads efforts to solve issues involving multiple companies.**
338
342
339
343
[Engineering Manager Skills]
340
344
341
-
Comes up with suggestions to improve systems and processes at the **group** scale, enabling people to handle technical incident more efficiently.
345
+
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized within the **group.**
342
346
343
347
Encourages engineers across **the entire group** to take ownership of their work.
0 commit comments