A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Themes | Skills | Level 0 | Level 1 | Level 2 | Level 3 | Level 4 | Level 5 | |||||||||||||||||||
2 | Titles | Junior Engineer | Engineer | Senior Engineer | Staff Engineer | Senior Staff Engineer | Principal Engineer | ||||||||||||||||||||
3 | Detail | You are learning quickly, and your new knowledge is benefitting your team. You're building software that is succeeding at the organization and your code is consistently of high quality. Deployments with your features are largely uneventful. You've established good working relationships with your peers and other members of the organization. You're working towards expanding your understanding of the companies procedures and products and adhere to the organizations cultural principles and values. | You are a solid contributor on your team with a solid grasp of the breadth and depth of the team's codebaseYou have built/owned features that were successful at The Company's. Your work is consistently high quality; you are active in contributing to insuring your team's work is high qualityYou have established good work relationships with people throughout The Company's. You are participating in the design and implementation of medium-sized features or subsystems. You drive discussion of and decisions regarding technical topics important to your team. You participate in technical discussions constructively You support The Company's tech culture principles | You are consistently productive and reliable You have a broad understanding of The Company's technologies and business You play a leading role in the design, development, deployment of a successful system Your experience is sought out by others, and you are held up as a role model in your division You continually better the solutions of others and think in terms of architecture, not just code You distill the essence of conflicts, harmonize views, find the best way forward, and lead people to that outcome You actively mentor junior team members and better your peers and work to make other people more productive You support and foster The Company's tech culture principles through recruiting, employee mentoring, and team participation | You stand out from your peers in the efficiency with which you solve problems and the comprehensive solutions you provide You play a leading role in the design, development, deployment of multiple systems or products You think in terms of optimal technical solutions for business problems You are effective in working on business problems with non-technical peers in the organization You actively advocate, improve, and stand up for The Company's tech culture principles | You have a broad and deep understanding of The Company's's business and how technology fits into making them great You play a leading role in the design, development, deployment of critical, large scale projects and or the launch of new products You think in terms of optimal solutions for business problems and applicable technology You distill the essence of conflicts, harmonize views, find the best way forward, and lead people to that outcome when working with cross functional teams, not just engineers You are skilled in working on business problems with non-technical peers in the organization You actively advocate, improve, and stand up for The Company's's tech culture principles | You stand out from your peers in the application of technology to business problems by anticipating upcoming trends, potential problems, and emerging technologies You have successfully led the architecture and development of the most complex and critical systems in the company and support others through mentorship You coach and advised others in their leading role in the design, development, deployment of critical, large scale projects and or the launch of new products through the use of new technologies and methodologies You distill the essence of conflicts, harmonize views, find the best way forward, and lead people to that outcome working with leadership teams across the company and seek senior leadership alignment You actively advocate, improve, and stand up for The Company's's tech culture principles | ||||||||||||||||||||
4 | Collaboration | Teamwork | Helps teammates when asked. Gives and takes credit when due. Collaborates to deliver high quality work. Builds stable relationships internally. | Actively participates in meetings and events. May assist with technical interviews. | Acts as a technical resource and sounding board. Participates in technical interviews for engineering team hires. | Defines delegates and tracks project level work while maintaining transparency in a way that aligns with cultural values | Leads cross department technical projects; defines and oversee multiple projects for teams while ensuring visibility to the business | Leads organization technical projects; defines and oversee multiple projects for teams while ensuring visibility to the business | |||||||||||||||||||
5 | Collaboration | Communication | Can clearly articulate thoughts during synchronous and asychronous events in both written and verbal form. | Communicates clearly, consicely, and effectively on both technical and non-technical topics to their teammates. Practices active listening. Contributes to the teams documentation. | Can identify non-verbal queues when listening. Speaks with an audience-oriented mindset. Recognizes conflict and tension. | Promotes a culture of clairty and competence of thought. Works well with all teammates and all team stakeholders. Can adjust style and language based on the situation in a dynamic fashion. | Can communicate with all team stakeholders at varying levels of detail using different and appropriate styles. Can adjust to nonverbal communication queues. | Can communicate appropriately scoped information across multiple teams using different styles. Acts as a representative both internally and externally for the team and organization where appropriate. | |||||||||||||||||||
6 | Collaboration | Feedback | Understands constructive feedback and can solicit feedback from peers and managers in an effective and polite manner. Incorporates feedback into their ongoing process for personal growth. | Can provide praise and feedback to teammates and managers in a helpful manner. | Can provide praise and feedback to stakeholders in a helpful and collaborative manner. | Actively fosters a culture of constructive feedback within their team and between their team and stakeholders. | |||||||||||||||||||||
7 | Leadership | Mentoring & Learning | Seeks out opportunities for mentorship and education to improve their craft. | Seeks out opportunities for mentorship and education. Occasionally helps their teammembers in an open collaborative manner in accordance with cultural values. | Mentors team members in an open, collaborative, and patient manner in accordance with cultural values. | Proactively mentors other team members. Designs and facilitates technical interview procedures. Represents the organization in synchronous and asynchronous events and other industry functions. | Proactively mentors other team members. Fosters a culture of education and personal growth. Collaborates with other mentors, and educates other mentors on the team. | Proactively mentors members across teams. Interviews technical leadership roles and other team hires. Mentors senior technical staff across the organization. Actively promotes a culture of growth and continuous education. | |||||||||||||||||||
8 | Leadership | Alignment & Mediation | Shares thoughts and opinions with their teammates when appropriate. Adheres to cultural principles regarding conflict resolution. | Has conversations based on organizational strategy and principles with their teammates when appropriate. Strongly oriented towards goals and works towards their team's goals. | Has conversations based on organizational strategy and principles with their teammates when appropriate to ensure team alignment. Strongly oriented towards goals and ensures their team is continuously working towards their shared goals. | Fosters a culture within their team of having conversations based on organizational strategy and principles to create alignment. Strongly oriented towards goals and ensures their team is continuously working towards their goals. | Fosters a culture across several teams of of having conversations based on organizational strategy and principles to create alignment. Strongly oriented towards goals and ensures several teams are continuously working towards their goals. | Fosters a culture across the organization of of having conversations based on organizational strategy and principles to create alignment. Ensures goals are understood and continuously worked towards across the organization. | |||||||||||||||||||
9 | Leadership | Culture | Understands and can articulate the principles and values of the team and organization. | Adheres to the principles and values of the team without guidance. | Understands principles and values and can clearly articulate how they apply to their domain. Uses values as tools to determine how to design software with empathy. | Works with management and peers to establish appropriate principles and values for their particular team. Sets a good example for all staff. | Works with management to establish and articulate good values and principles for the appropriate software domains across several teams | Works with management to establish and articulate good values and principles for the appropriate software domains across the entire organization. Educates and solicits feedback from peers. | |||||||||||||||||||
10 | Leadership | Influence | Receives direction on tasks including their designs and technical acceptance criteria from their engineering lead. | Receives direction from their lead. Owns smaller features. | Oversees & owns entire features including their architecture. Can clearly articulate tradeoffs. Works with senior staff and managers to achieve meaningful results. | Leads technical projects. Collaborates with managers on product led initiatives. | |||||||||||||||||||||
11 | Delivery | Cadence & Predictability | Can self identify challenges with progress. Communicates proactively and is forthright asking for assistance when required. | Clarifies expectations with their team. Commits to an achievable amount of work and sets expectations accordingly. | Works actively with product managers to clarify scope and capabilities of the project or initiative. Can break down work into reasonable packets of value. Eliminates risk by identifying challenging aspects of the initiative during the design process. | ||||||||||||||||||||||
12 | Delivery | Quality & Risk | Recognizes and analyzes technical problems. Escalates problems to senior engineers and managers. Understands quality metrics of the team. Production releases are uneventful. | Can identify dependencies and technical problems. Can handle many issues while following the proper escalation procedures. Communicates with senior engineers and managers. | Ensures tasks are prioritized properly and that all dependencies are mapped and resolved. Anticipates any delays and proactively communicates with stakeholders. | ||||||||||||||||||||||
13 | Delivery | Process | Learns and understands the organization and team SDLC. Escalates problems to senior teammates and managers. | Understands priorities and acts accordingly. Adheres to the defined SDLC. | Works towards milestones with little to no supervision. Identifies and adopts engineering best practices that make sense for the organizations engineering team. | Delivers process improvements that increase the velocity and quality of the entire team. Contributes to the development, build, deployment, and monitoring processes with an emphasis on realibility and performance. | Delivers process improvements that increase the velocity and quality of the entire organization. Contributes to the build, deployment, and monitoring processes with an emphasis on reliability and performance. | ||||||||||||||||||||
14 | Strategy | Budget | Awareness of budget guidelines provided for the team | Awareness of budget guidelines provided for the team. Can control costs related to their own work | Understands milestones in projects from a time + resource perspective. | Understands budget consequences. Can forecast costs for projects and compare them to business constraints to determine viability. | Leads the resources and budgets from a techincal resource perspective on entire projects. | ||||||||||||||||||||
15 | Strategy | Product | Understands the basic value and utility of the product. Owns tasks and technical components. | Understands product area of focus, how it fits into the overall business, and sometimes makes improvement suggestions for it. | Thoroughly understands the business model in relation to their current product focus area. Sometimes participates in roadmap feedback with product team. Looks for opportunities to simplify product & technical design. | Evaluates and creates new product features in collaboration with the product team. Regularly participates in the creation of the team roadmap and ensuing feedback. Simplifies product and technical design through proactive conversations. | Oversees and owns midsized projects and mission critical subject matter. Seen as a subject matter expert on the technical implementation of projects. Understands the product behaviour and can provide suggestions on long-term product viability from a maintenance and technical perspective. Recognizes product opportunities and differentiators in relation to the competition. Often helps refine roadmaps across teams based on technical strategy & constraints. Helps to define & create new product abilities by changing technical strategy or constraints. | Actively seeks to create or redefine roadmaps across the organization with product & business counterparts. | |||||||||||||||||||
16 | Technology | Design & Architecture | Is aware of overall design patterns and architecture in use within the team. Adheres to standards within the codebase. | Understands patterns and architecural decisions in use within the team and can articulate the tradeoffs between these patterns and alternatives. Adheres to the team standards. | Provides technical leadership and direction in the implementation of large new product features. | Provide technical guidance and leadership through the implementation and delivery of large technical projects that cross-cut products (e.g. upgrading system versions and refactoring integral product components); conduct directed research and development and provide technical analysis of new candidate technologies that fill an engineering team business or technical need | (+) and (e.g. adoption of replacement technologies and protocols); maintain a personal research and development program, intended to identify ways in which The Company's can benefit from industry innovations | (+) and provide new technology insights to remainder of engineering department and senior leadership team | |||||||||||||||||||
17 | Technology | Security | Understands the importance of security. Adheres to the teams security policies. | Is proficient with common vulnerabilities applicable to the technology stack of the team and codebase in question. Can prevent introducing new security issues during the design and development phase of a project. | Understands and is proficient at preventing OWASP top 10 style issues. Familiar with the types of security concerns throughout the technologies used in the stack. Does not introduce any new security issues, and proactively identifies and rasies security concerns with the team during technical reviews. | ||||||||||||||||||||||
18 | Technology | Tradeoffs & Technical Debt | Maintains established standard of reliability, performance, and quality in delivered tasks. | Maintains and occasionally improves performance within the constaints of the SLA of the service or application in question. Can articulate trade-offs during design and implementation phases. | |||||||||||||||||||||||
19 | Technology | Privacy & Compliance | Understands the concepts of PII | ||||||||||||||||||||||||
20 | Technology | Testing | Writes unit tests. Understands basics of testing and the test pyramid. | Methods are appropriately sized and easy to test in isolation with no side-effects. | |||||||||||||||||||||||
21 | Technology | Clarity & Comprehension | Code is easy to read. Follows cultural conventions that suit the language, style, codebase with architectural guidance from senior staff. | Code adheres to the conventions of the codebase. Patterns are adhered to and convetions like DRY are used when appropriate. Opportunities for refactors are identified and raised during technical meetings. | |||||||||||||||||||||||
22 | |||||||||||||||||||||||||||
23 | |||||||||||||||||||||||||||
24 | |||||||||||||||||||||||||||
25 | |||||||||||||||||||||||||||
26 | |||||||||||||||||||||||||||
27 | |||||||||||||||||||||||||||
28 | |||||||||||||||||||||||||||
29 | |||||||||||||||||||||||||||
30 | |||||||||||||||||||||||||||
31 | |||||||||||||||||||||||||||
32 | |||||||||||||||||||||||||||
33 | |||||||||||||||||||||||||||
34 | |||||||||||||||||||||||||||
35 | |||||||||||||||||||||||||||
36 | |||||||||||||||||||||||||||
37 | |||||||||||||||||||||||||||
38 | |||||||||||||||||||||||||||
39 | |||||||||||||||||||||||||||
40 | |||||||||||||||||||||||||||
41 | |||||||||||||||||||||||||||
42 | |||||||||||||||||||||||||||
43 | |||||||||||||||||||||||||||
44 | |||||||||||||||||||||||||||
45 | |||||||||||||||||||||||||||
46 | |||||||||||||||||||||||||||
47 | |||||||||||||||||||||||||||
48 | |||||||||||||||||||||||||||
49 | |||||||||||||||||||||||||||
50 | |||||||||||||||||||||||||||
51 | |||||||||||||||||||||||||||
52 | |||||||||||||||||||||||||||
53 | |||||||||||||||||||||||||||
54 | |||||||||||||||||||||||||||
55 | |||||||||||||||||||||||||||
56 | |||||||||||||||||||||||||||
57 | |||||||||||||||||||||||||||
58 | |||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||
100 |