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
**Thinks outside the box and proposes solutions to technical challenges and ongoing feature development.**
13
13
14
14
**Thinks of approaches to testing based on hypotheses and proposes them to their team in order to test new ideas.**
@@ -17,14 +17,14 @@
17
17
18
18
19
19
## Vision
20
-
**When making decisions, lists the pros and cons of multiple solutions based on data and facts to determine which one is the most suitable.**
21
-
22
20
**Takes action in accordance with** their team’s goals, the company’s values, and the organizational vision.
23
21
24
22
**Autonomously considers how they can contribute to achieving their team or project’s goals and sets their own goals to do so.**
25
23
24
+
**Proactively makes efforts** to improve their work **based on investigations and discussions.**
26
25
27
-
## Priorities / Direction
26
+
27
+
## Focus on the Mission
28
28
Understands **the value that** their product and **team provide to end users and actively works on their assigned tasks while considering the impact on the user experience.**
29
29
30
30
Explains how their team’s domain **contributes to** the product **and how the product impacts the industry.**
@@ -34,23 +34,23 @@ Explains how their team’s domain **contributes to** the product **and how the
34
34
35
35
36
36
## Teamwork
37
-
**Handles disagreements with proper consideration and respect towards the** other members **involved; is open to changing their mind.**
38
-
39
37
**Understands and implements methods of delivering praise and constructive** feedback.
40
38
41
39
Listens to others, **pays attention to nonverbal communication, and builds** strong relationships with their teammates, manager, **and product counterparts.**
42
40
41
+
**When making decisions, lists the pros and cons of multiple solutions based on data and facts to determine which one is the most suitable.**
42
+
43
43
44
-
## Ownership
44
+
## Professionalism
45
45
**Not only creating documentation for their team, but improves the team's documentation as needed.**
46
46
**Understands and explains the importance of sharing knowledge and information.**
47
47
48
48
**Investigates risks discovered and escalates issues to senior members.**
49
49
50
-
**Proactively makes efforts** to improve their work **based on investigations and discussions.**
50
+
**Handles disagreements with proper consideration and respect towards the** other members **involved; is open to changing their mind.**
51
51
52
52
53
-
## Expertise
53
+
## Continued Learning
54
54
**Selects,** learns, and applies new technical knowledge/skills relevant to their work.
55
55
56
56
**Resolves bugs or issues with minimal guidance.**
Thinks outside the box and **creates** solutions **with little or no guidance.**
13
13
14
14
**Goes beyond just discussions and leads technical approaches focusing on incremental delivery as necessary;**
@@ -26,20 +26,21 @@ Fosters a blameless team culture that welcomes new challenges.
26
26
27
27
28
28
## Vision
29
-
**Predicts results and formulates hypotheses** based on data and **credible evidence to lead decision-making within their team or project.**
30
-
31
29
**Contributes to the achievement of team goals by proactively communicating team goals or supporting the engineers around them.**
32
30
33
31
**Involves themselves in creating team/project goals and formulating technical strategies.**
34
32
35
-
### [Engineering Manager Skills]
33
+
**Continuously makes improvements by investigating and discussing ways** to improve their **team’s** work.
34
+
**Addresses failures or discovered issues by making improvements focused on the process, not on individual responsibilities.**
36
35
37
-
Considers necessary trade-offs between requirements, timelines, and technical approaches when making decisions.
36
+
### [Engineering Manager Skills]
38
37
39
38
Understands the division’s goals, the company’s values, and the organizational vision, helping to move the team toward those goals.
40
39
40
+
Encourages failure analysis focused on the process, not on individuals.
41
+
41
42
42
-
## Priorities / Direction
43
+
## Focus on the Mission
43
44
Understands **thoroughly how the product is being used by** end users, **contributes to the value enhancement of the product, such as works as a counterpart of the PM to decide on technical specifications.**
44
45
45
46
**In addition to understanding the domain knowledge of their team, has a deep understanding of how their domain interacts with related domains and the importance of their assigned domain in achieving business goals. Helps those around them deepen their understanding of domain knowledge.**
@@ -57,42 +58,42 @@ Defines the resources the team needs to solve issues while making sure results a
57
58
58
59
59
60
## Teamwork
60
-
**Turns disagreements within their team/project into constructive discussions and guides these discussions to better conclusions.**
61
-
62
61
**Actively seeks feedback from those around them, utilizes** praise and constructive feedback, **and mentors new team members.**
63
62
64
63
**Makes sure that they are accountable for development and consistently earns understanding and cooperation from others.**
65
64
**Builds trust with people both inside and outside the company, and works to gather others to join them.**
66
65
67
-
### [Engineering Manager Skills]
66
+
**Predicts results and formulates hypotheses** based on data and **credible evidence to lead decision-making within their team or project.**
68
67
69
-
Values different opinions and diverse ideas, and encourages everyone in their team to do the same in order to maintain high psychological safety.
68
+
### [Engineering Manager Skills]
70
69
71
70
Delegates tasks to promote skill growth. Takes responsibility for onboarding new members.
72
71
73
72
Connects different members and projects across teams to solve issues.
74
73
74
+
Considers necessary trade-offs between requirements, timelines, and technical approaches when making decisions.
75
+
75
76
76
-
## Ownership
77
+
## Professionalism
77
78
**Uses appropriate processes, methods, and tools to share relevant and useful information about their team and related projects with other members.**
78
79
**Examples: Leverages methods such as post-incident analysis (post-mortem), pros/cons lists, decision matrices, etc.**
79
80
80
81
**Takes action to reduce risk and incidents, such as by undertaking development that considers future risk, and in the event an incident occurs, contributes to the response.**
81
82
**Examples: Considers operational processes and solutions intended to prevent problems, and creates and carries out forward-looking contingency plans within the team**
82
83
83
-
**Continuously makes improvements by investigating and discussing ways**to improve their **team’s** work.
84
-
**Addresses failures or discovered issues by making improvements focused on the process, not on individual responsibilities.**
84
+
**Turns disagreements within their team/project into constructive discussions and guides these discussions to better conclusions.**
85
+
85
86
86
87
### [Engineering Manager Skills]
87
88
88
89
Contributes to standardization of information-sharing processes and promotes knowledge sharing, to create an environment where knowledge is effectively utilized within the team.
89
90
90
91
Encourages everyone in the team to take ownership of their work.
91
92
92
-
Encourages failure analysis focused on the process, not on individuals.
93
+
Values different opinions and diverse ideas, and encourages everyone in their team to do the same in order to maintain high psychological safety.
93
94
94
95
95
-
## Expertise
96
+
## Continued Learning
96
97
**Learns about new fields to contribute to the team in order to enhance the value of the product. Shares and teaches their knowledge and technical know-how with the engineers around them. Knows the importance of tech outreach and shares useful information inside and outside the company.**
97
98
98
99
**Has deep knowledge of the code and uses that knowledge in actively doing** code reviews **for the team.**
**In development that impacts multiple teams or the goals of the product or the division,** thinks outside the box and creates **innovative** solutions.
13
13
14
14
**In development that impacts multiple teams or the goals of the product or the division,** leads **in taking on challenging issues and** technical approaches **such as** focusing on incremental delivery.
@@ -25,22 +25,21 @@ Fosters a blameless culture that welcomes new challenges **across multiple teams
25
25
26
26
27
27
## Vision
28
-
**Seeks data-backed evidence through proofs of concept (POC), tests, and external research and** leads **fact-based** decision-making **in development that impacts multiple teams or the goals of the product or the division.**
29
-
30
28
**Works with other teams to help achieve goals based on the organizational strategy, considering the interests of both their own team and teams around them.**
31
29
32
30
**Leads consensus among development teams regarding product direction and prioritization while consulting stakeholders across multiple job types and teams.**
33
31
34
-
### [Engineering Manager Skills]
32
+
**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.**
35
33
36
-
Considers necessary trade-offs between requirements, timelines, and technical approaches.
34
+
### [Engineering Manager Skills]
37
35
38
36
Understands the division’s goals, the company’s values, and the organizational vision, helping to move **multiple teams** toward those goals.
39
37
40
38
**Makes long-term team goals and a roadmap to illustrate the organizational strategy.**
41
39
40
+
Encourages **multiple teams to conduct** failure analysis focused on the process, not on individuals.
42
41
43
-
## Priorities / Direction
42
+
## Focus on the Mission
44
43
**Leads the value enhancement of the product by understanding the status, issues, and backlog of not only their team and ongoing development but also of surrounding teams and projects.**
45
44
46
45
**Understands thoroughly the domains of their team and related teams and leads specification design discussions that require complex domain knowledge.**
@@ -58,40 +57,39 @@ Knows the impact their team’s **and other team’s** work has on end users and
58
57
59
58
60
59
## Teamwork
61
-
**Addresses problems with solutions that consider concerns held by stakeholders of multiple teams, such as by encouraging engineers in their own team and others to have** constructive discussions.
62
-
63
60
**Utilizes feedback to guide members of their own team and of other teams, encouraging those member’s growth.**
64
61
65
62
**Fulfills accountability in development that impacts multiple teams or the goals of the product or the division**, and earns understanding and cooperation from those around them.
66
63
**Always focuses on building** trust with people both inside and outside the company, and works to gather **other talented individuals.**
67
64
68
-
### [Engineering Manager Skills]
65
+
**Seeks data-backed evidence through proofs of concept (POC), tests, and external research and** leads **fact-based** decision-making **in development that impacts multiple teams or the goals of the product or the division.**
69
66
70
-
**Encourages members beyond their team to** value different opinions and diverse ideas; **mediates disagreements and finds an agreeable solution for each party.**
67
+
### [Engineering Manager Skills]
71
68
72
69
**Mentors their team members in an open and respectful manner; goes beyond their team to improve onboarding for engineers.**
73
70
74
71
Connects different members and projects across **their entire division** to solve issues.
75
72
73
+
Considers necessary trade-offs between requirements, timelines, and technical approaches.
76
74
77
-
## Ownership
75
+
## Professionalism
78
76
**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
77
**Examples: Proposing improvements, presenting at meetings, and creating tools, documents or guidelines for their division**
80
78
81
79
**Investigates risks, coordinates with the relevant teams, and takes necessary measures.** Takes action to reduce risk and incidents, **such as increasing awareness of risk management across multiple teams.**
82
80
83
-
**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.**
81
+
**Addresses problems with solutions that consider concerns held by stakeholders of multiple teams, such as by encouraging engineers in their own team and others to have** constructive discussions.
84
82
85
83
### [Engineering Manager Skills]
86
84
87
85
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
86
89
87
Encourages **engineers across multiple teams** to take ownership of their work.
90
88
91
-
Encourages **multiple teams to conduct** failure analysis focused on the process, not on individuals.
89
+
**Encourages members beyond their team to** value different opinions and diverse ideas; **mediates disagreements and finds an agreeable solution for each party.**
92
90
93
91
94
-
## Expertise
92
+
## Continued Learning
95
93
**Demonstrates advanced skills and knowledge in their field of expertise and architecture. Learns and applies new knowledge beyond their specialty field** to enhance the value of the product. **Communicates high-quality technical information and encourages those around them to do the same.**
96
94
97
95
Has deep knowledge of the code and **takes responsibility for** doing code reviews for **teams or projects.**
0 commit comments