Skip to content

Commit 2f58446

Browse files
author
lestrrat
committed
Update ladder content
1 parent 6c4132b commit 2f58446

16 files changed

+76
-60
lines changed

META.json

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"description": "This file contains the metadata used to generate files in this repository",
3-
"commit_id": "e66d3b66781799b8dc6122282e834f5d2f605d19",
4-
"date": "Thu Jun 30 08:11:32 UTC 2022"
3+
"commit_id": "1ae6163d7b5aee673f3a1a4c8e3ac065cc72f3f6",
4+
"date": "Wed Jul 5 00:27:09 UTC 2023"
55
}

README.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -48,4 +48,5 @@ This repository is maintained by the Engineering Office. If you have any request
4848

4949
## License
5050

51-
This work is licensed under [CC0 license](https://creativecommons.org/share-your-work/public-domain/cc0/)
51+
WIP
52+

en/MG1.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,8 @@ Listens to others and makes their best effort to understand them, in order to bu
4343

4444

4545
## Ownership
46-
Tries to understand the reason why a bug occurs and also can explain the importance of sharing post-mortem reports.
46+
Can find and leverage the knowledge required for their work.
47+
Creates documents relevant to their team for information sharing.
4748

4849
Explains the importance of security and risk management.
4950

en/MG2.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,8 @@ Listens to others, **pays attention to nonverbal communication, and builds** str
4242

4343

4444
## Ownership
45-
**Follows incident handling procedures and contributes to** post-mortem reports.
45+
**Not only creating documentation for their team, but improves the team's documentation as needed.**
46+
**Understands and explains the importance of sharing knowledge and information.**
4647

4748
**Investigates risks discovered and escalates issues to senior members.**
4849

en/MG3.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,8 @@ Connects different members and projects across teams to solve issues.
7474

7575

7676
## 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.**
7879

7980
Investigates risks **and creates and carries out contingency plans for the future.**
8081

@@ -83,15 +84,15 @@ Investigates risks **and creates and carries out contingency plans for the futur
8384

8485
### [Engineering Manager Skills]
8586

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.
8788

8889
Encourages everyone in the team to take ownership of their work.
8990

9091
Encourages failure analysis focused on the process, not on individuals.
9192

9293

9394
## 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.**
9596

9697
**Has deep knowledge of the code and uses that knowledge in actively doing** code reviews **for the team.**
9798
**Suggests new guidelines and ways to improve systematic debugging; resolves technical issues and bugs with large impact.**

en/MG4.md

+4-3
Original file line numberDiff line numberDiff line change
@@ -75,16 +75,17 @@ Connects different members and projects across **their entire division** to solv
7575

7676

7777
## 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**
7980

8081
Investigates risks, **coordinates with relevant teams, and takes necessary measures.**
8182
**Boosts risk management awareness among their team.**
8283

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.**
8485

8586
### [Engineering Manager Skills]
8687

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.**
8889

8990
Encourages **engineers across multiple teams** to take ownership of their work.
9091

en/MG5.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -72,16 +72,16 @@ Connects different members and projects across their entire **company** to solve
7272

7373

7474
## 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**
7677

7778
Investigates risks, coordinates with relevant teams **across their company**, and takes necessary measures.
78-
**Creates and promotes the organization's best security practices.**
7979

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.**
8181

8282
### [Engineering Manager Skills]
8383

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.**
8585

8686
Encourages engineers across **their company** to take ownership of their work.
8787

en/MG6.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -74,15 +74,15 @@ Encourages **engineers across the group** to value different opinions and divers
7474

7575

7676
## 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.**
7878

7979
Investigates risks **in development across companies and is recognized as a risk management expert in the group.**
8080

8181
**Encourages engineers across the group to focus on the process, not on individual responsibilities, and leads efforts to solve issues involving multiple companies.**
8282

8383
### [Engineering Manager Skills]
8484

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.**
8686

8787
Encourages engineers across **the entire group** to take ownership of their work.
8888

en/engineering_ladder.csv

+18-14
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,8 @@ Examples: Source control, editors, the build system, best practices for testing"
1717

1818
Explains that praise and feedback are useful when delivered in a kind manner.
1919

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.
2122

2223
Explains the importance of security and risk management.
2324

@@ -45,7 +46,8 @@ Explains how their team’s domain **contributes to** the product **and how the
4546

4647
**Delivers** praise and **constructive feedback.**
4748

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.**
4951

5052
**Investigates risks discovered and escalates issues to senior members.**
5153

@@ -104,7 +106,8 @@ Values different opinions and diverse ideas, and encourages everyone in their te
104106

105107
Delegates tasks to promote skill growth and takes responsibility for onboarding new members.
106108

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.**
108111

109112
Investigates risks **and creates and carries out contingency plans for the future.**
110113

@@ -113,11 +116,11 @@ Investigates risks **and creates and carries out contingency plans for the futur
113116

114117
[Engineering Manager Skills]
115118

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.
117120

118121
Encourages everyone in the team to take ownership of their work.
119122

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.**
121124

122125
**Has deep knowledge of the code and uses that knowledge in actively doing** code reviews **for the team.**
123126
**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
180183

181184
**Mentors their team members in an open and respectful manner; goes beyond their team to improve onboarding for engineers.**
182185

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**
184188

185189
Investigates risks, **coordinates with relevant teams, and takes necessary measures.**
186190
**Boosts risk management awareness among their team.**
187191

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.**
189193

190194
[Engineering Manager Skills]
191195

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.**
193197

194198
Encourages **engineers across multiple teams** to take ownership of their work.
195199

@@ -254,16 +258,16 @@ Encourages members **across** their **company** to value different opinions and
254258

255259
Mentors their team members **and other EMs** in an open and respectful manner; improves onboarding for engineers **on the company level.**
256260

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**
258263

259264
Investigates risks, coordinates with relevant teams **across their company**, and takes necessary measures.
260-
**Creates and promotes the organization's best security practices.**
261265

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.**
263267

264268
[Engineering Manager Skills]
265269

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.**
267271

268272
Encourages engineers across **their company** to take ownership of their work.
269273

@@ -330,15 +334,15 @@ Encourages **engineers across the group** to value different opinions and divers
330334

331335
**Works to train new mentors across the organization and provides other EMs with opportunities to grow their career and learn new skills.**
332336

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.**
334338

335339
Investigates risks **in development across companies and is recognized as a risk management expert in the group.**
336340

337341
**Encourages engineers across the group to focus on the process, not on individual responsibilities, and leads efforts to solve issues involving multiple companies.**
338342

339343
[Engineering Manager Skills]
340344

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.**
342346

343347
Encourages engineers across **the entire group** to take ownership of their work.
344348

jp/MG1.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,8 @@
4343

4444

4545
## Ownership
46-
バグが発生した際に、なぜそれが起こったのかを理解しようとし、事後分析(ポストモーテム)を共有することの重要性を理解し、説明できる。
46+
自分の業務に必要な情報を探し、活用できる。
47+
情報共有のために自分のチームに関連するドキュメントを作成している。
4748

4849
セキュリティやリスクマネジメントの重要性を理解し、説明できる。
4950

jp/MG2.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,8 @@
4242

4343

4444
## Ownership
45-
**インシデント対応の手順に沿って対応できるだけでなく**、事後分析(ポストモーテム)**の作成に貢献している。**
45+
**チームのドキュメントの作成だけでなく、必要に応じてドキュメントの改善をしている。**
46+
**知識や情報を共有することの重要性を理解し、説明できる。**
4647

4748
**リスク調査を行い、発見した課題をシニアメンバーにエスカレーションできる。**
4849

jp/MG3.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -72,24 +72,24 @@ Divisionの目標、会社のバリュー、組織のビジョンを理解し、
7272

7373

7474
## Ownership
75-
76-
**チーム内の小規模なインシデントに対応でき**、事後分析(ポストモーテム)の作成**を積極的に行い、他のエンジニアが再発防止に取り組める状態を作れている。**
75+
**チームや関連するPJ内の情報を、適切なプロセスや方法、ツールを活用して他のメンバーと共有している。**
76+
**例:インシデント時の事後分析(ポストモーテム)、Pros/Consの評価、意思決定マトリクスなどの活用**
7777

7878
リスク調査を行い、**将来的なコンティンジェンシープランを考えて実行できる。**
7979

8080
**チームの課題を把握し、改善のため**調査や議論**を行い、改善への取り組みをリードしている。失敗や課題発見を元に、個人の責任ではなくプロセスにフォーカスして改善している。**
8181

8282
### [Engineering Manager Skills]
8383

84-
インシデントをより効率的に処理できるように、チーム規模でシステムやプロセスを改善するための提案を行っている
84+
情報共有プロセスの標準化に貢献し、情報・知識の共有を促進することで、チーム内で知識が効果的に活用される環境を整えている
8585

8686
チームの全員にそれぞれの業務に対してオーナーシップを持つよう促している。
8787

8888
個人ではなくプロセスに対する課題分析を奨励している。
8989

9090

9191
## Expertise
92-
**自身が学ぶだけでなく、学んだ知識や技術を周りのエンジニアに共有している。技術発信の重要性を意識し、社内外問わず有益な情報を発信している。**
92+
**学んだ知識や技術を周りのエンジニアに教えたり共有している。技術発信の重要性を意識し、社内外問わず有益な情報を発信している。**
9393

9494
**コードに対する深い知識を持ち、その知識をもって積極的にチームのコードレビューを行っている。**
9595
**新しいガイドラインや体系的なデバッグ手法の改善提案ができ、影響範囲の大きい**バグや技術的課題を解決している。

0 commit comments

Comments
 (0)