CREATING AN INCLUSIVE ENVIRONMENT ROLE LEVELS MATRIX GUIDE

CREATING AN INCLUSIVE ENVIRONMENT ROLE LEVELS MATRIX: GUIDE [YOUR LOGO HERE] OVERVIEW A roles and levels matrix (tech) gives employees clarity around the skills, knowledge and behaviours required for their current and aspirational roles. It removes ambiguity and makes hiring, performance management and career development simpler and fairer. Having these identifiers for roles and levels throughout your employee lifecycle helps performance evaluation and subsequent decisions to be made on data and reduces potential for bias. Linking the matrix to salary bands provides transparency and reduces the potential for pay gaps to occur. CLOSING THE GENDER GAP IN TECHNOLOGY 1

CREATING AN INCLUSIVE ENVIRONMENT ROLE LEVELS MATRIX: GUIDE [YOUR LOGO HERE] HOW TO MAKE SKILLS LEVELS MATRIX Create a table with technology role levels for your teams - Eg. Software Developer: Junior/Level 1, Mid/Level 2 etc Define for each of these, what you would expect to see in terms of; ● Skills (list the key skills will they employ) ● Knowledge (detail the specific knowledge they should have and would use) ● Behaviours (define what behavioural competencies are essential) Then for each role and level, set a salary range. HOW TO USE IT Firmly embed the matrix in the following processes for technology teams; 1. 2. 3. 4. Recruiting Setting salaries Performance management Career development CLOSING THE GENDER GAP IN TECHNOLOGY 2

CREATING AN INCLUSIVE ENVIRONMENT ROLE LEVELS MATRIX: GUIDE Example (taken from http: //eng-skills-matrix. expert 360. com/ [YOUR LOGO HERE] ) This is a great example taken from a comprehensive framework. You can start yours simple and add to it as your team grows. Other examples can be found HERE and HERE. Software Engineer Skills & Knowledge Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] Senior (Level 3) [Salary Range] Lead (Level 4) [Salary Range] Manager (Level 5) [Salary Range] Understanding Code Gains context within team's domain with help from more senior engineers. API Design Understands API interfaces for Graph. QL and REST APIs. Understands different formats used in an API. Able to query and update data via an API. Design Patterns Developing an understanding of different patterns used in the codebase Software Architecture Aware of domain architecture and designs basic functions to avoid code duplication and interface -breaking changes. Understanding Code Understands a portion of the team's domain, can gain sufficient context to work productively in that portion. API Design Understands different API interfaces and formats and creates APIs for consumption. Understands some best practices when designing APIs and deepening this understanding. This can include response sizes, security, error handling, rate limiting, performance, REST & Graph. QL best practices. Design Patterns Considers and understands how to apply applicable patterns within the context of the codebase. For example understanding pub-sub pattern or circuit breaker pattern for different scenarios that are applicable for work being undertaken. May seek help from others on which patterns to apply. Software Architecture Designs functions considering how this fits into the overall architecture. Understanding Code Understands their team's domain and can gather sufficient context to work productively within it. Has expertise in a portion of their team's domain. API Design Consistently considers best practice when designing APIs Design Patterns Consistently considers and applies applicable patterns across several contexts/codebases, in accordance to agreed best practices and standards. Software Architecture Consistently designs code that fits with the overall architecture. Utilizes abstractions and code isolation effectively. Understanding Code Has expertise in their team's domain, including the breadth of services, how they interact, and data flows between systems. Understands adjacent domains and impact on their domain. API Design Consistently considers best practice when designing APIs and ensures the work in the team meets these Design Patterns Leads the team in applying applicable and relevant design patterns in the team's work and contexts, in accordance to agreed best practices and standards with pragmatism Software Architecture Works with the team to ensure architecture and technical approaches are aligned to the broader engineering goals (e. g. scaling or validation mode, continuous deployment etc) and the architectural roadmap Understanding Code Has expertise in a set of related team's domains, including the breadth of services, how they interact, and data flows between systems. API Design Consistently considers best practice when designing APIs and ensures the work across teams meets best practices Design Patterns Works across the teams to foster a culture of applying applicable and relevant design patterns, in accordance needs of the company and guides several teams in anticipation of future use cases. Software Architecture Works with teams to ensure architecture and technical approaches are aligned to the broader engineering goals (e. g. scaling or validation mode, continuous deployment etc) Contributes to and drives the architectural roadmap Guides the team on knowing when to invest in tech or focus on delivery. CLOSING THE GENDER GAP IN TECHNOLOGY 3

CREATING AN INCLUSIVE ENVIRONMENT ROLE LEVELS MATRIX: GUIDE [YOUR LOGO HERE] Software Engineer Behaviours Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] Senior (Level 3) [Salary Range] Lead (Level 4) [Salary Range] Manager (Level 5) [Salary Range] Teamwork Helps their teammates when requested, volunteers themself for team tasks. Gives or shares credit where due. Demonstrates a positive attitude, learns from mistakes and does not place blame on others. Feedback Actively seeks feedback through pull requests and pairing, and uses feedback from others as a tool for growth. Effective Communication Communicates effectively, clearly, concisely and in an audience -oriented way, in written and verbal form. Communicates progress of work, escalates issues, rubber-ducks approaches to their work with a team member, and asks for help where needed. Actively listens to others and ensures they are understood. Asks questions for clarification. Pays attention to nonverbal communication. Teamwork When requested, helps their teammates overcome obstacles, resolve blockers, and complete work tasks. Volunteers for team tasks. Developing a sense where they fit into the team's progress and where they can provide assistance. Gives or shares credit where due. Actively demonstrates a positive attitude, learns from mistakes. . Feedback Actively seeks feedback through pull requests and pairing, seeking from relevant domain experts. Provides constructive, respectful feedback to other developers through PRs and pairing, uses feedback from others as a tool for growth and actively follows up on feedback given. Effective Communication Usually communicates effectively, clearly, concisely and in an audience-oriented way in written and verbal form, for both technical and non technical subjects, to their teammates. Communicates progress of work, escalates issues early and reaches out to a diverse set of people to get other perspectives on a complex design. Actively listens to others and ensures they are understood. Asks questions for clarification. Pays attention to nonverbal communication. Teamwork Helps their teammates overcome obstacles, resolve blockers, and complete work tasks without impacting their own work. Aware of team's progress and reaches out to teammates if they notice someone has been stuck for a while. Gives or shares credit where due. Actively demonstrates a positive attitude, takes responsibility for mistakes. Feedback Actively seeks feedback through pull requests and pairing, seeking from relevant domain experts. Effective Communication Communicates effectively in written and verbal form both technical and non technical subjects. Communicates progress of work, escalates issues early and reaches out to a diverse set of people to get other perspectives on a complex design. Demonstrates how to effectively communicate an idea, proposal, decision or counterpoint. Offers solutions to problems rather than just communicating a problem. Actively listens to others and ensures they are understood. Asks thoughtful and considered questions in a respectful way. Pays attention to nonverbal communication. Teamwork Consistently helps their teammates overcome obstacles, resolve blockers. Aware of team's progress and unblocks members of the team. Gives or shares credit where due. Actively demonstrates a positive attitude, does not place blame on others, assumes responsibility for mistakes, leads resolution and ensures the team follow this example. Feedback Works within their team, relevant domain experts and with its business stakeholders to foster a culture of seeking out feedback and using it as a tool for growth. Effective Communication Is able to communicate effectively with a diverse team. Fosters a culture of clear, concise, effective, audience-oriented communication on their team Asks thoughtful and considered questions in a respectful way and ensures their team demonstrates this. Communicates status, project updates and relevant sharing of information across interested groups. Takes the lead on driving conversations within the team to navigate complicated technical problems. Actively demonstrates these behaviours. Pays attention to nonverbal communication. Teamwork Consistently works across teams to help them resolve blockers. Ensures team leads have the tools they need to unblock their teams. Ensures that credit is shared and given. Actively demonstrates a positive attitude, assumes responsibility for mistakes, leads resolution and ensures this is followed across teams. Feedback Works across several teams, domains and with their business stakeholders to foster a culture of seeking out feedback and using it as a tool for growth. Actively demonstrates these behaviours. Effective Communication Is able to communicate effectively with a diverse set of teams. Fosters a culture of clear, concise, effective, audience-oriented communication across several teams, ensuring teammates actively listen to others and are understood. Ensures their teams ask questions are asked in a respectful way. Provides input to discussions on areas of strategy. Reaches out to teams and groups beyond their own, and outside engineering, to gather information from stakeholders. Uses a variety of communication methods to communicate and drive others to excel. CLOSING THE GENDER GAP IN TECHNOLOGY 4

CREATING AN INCLUSIVE ENVIRONMENT ROLE LEVELS MATRIX: GUIDE [YOUR LOGO HERE] The below template reflects 5 typical levels per role in tech teams, put in the role title (eg. Software Engineer. Net, Software Engineer in Test, i. OS Developer, Product Manager etc) then use this salary guide and any other market data you would like to use, along with your company pay philosophy (if you have one) to create your ranges. Role Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] Senior (Level 3) [Salary Range] Lead (Level 4) [Salary Range] Manager (Level 5) [Salary Range] Role Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] Senior (Level 3) [Salary Range] Role Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] CLOSING THE GENDER GAP IN TECHNOLOGY Senior (Level 3) [Salary Range] 5

CREATING AN INCLUSIVE ENVIRONMENT ROLE LEVELS MATRIX: GUIDE [YOUR LOGO HERE] Role Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] Senior (Level 3) [Salary Range] Lead (Level 4) [Salary Range] Manager (Level 5) [Salary Range] Role Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] Senior (Level 3) [Salary Range] Role Junior (Level 1) [Salary Range] Mid (Level 2) [Salary Range] CLOSING THE GENDER GAP IN TECHNOLOGY Senior (Level 3) [Salary Range] 6