E1: Engineer I

FOCUS:
Within Task

Role Expectations
Critical Thinking
  • Holistic Thinking Approaches tasks with a view to develop an understanding on how the task fits into the feature, the users impacted, the flows impacted and developing the understanding of the feature's purpose
  • Technical Analysis Collaborates with team members to produce smaller scope designs.
    Aims to think about what technical changes are needed for a task, acceptance criteria, and seeks to follow best practice.
    Understands how a few systems fit together at a high level and each team's responsibility for their piece of functionality
Business Impact
  • Understand "WHY" Has a basic understanding on the team's domain and how work in this domain relates to the team's objectives and deliverables
  • Defining Strategy Understands the organisation's company strategy and how the engineering aligns to this.
Product Impact
  • Understands or grasps how the product works and the overall purpose and impact of the product
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Asked questions on a project to understand the purpose of the project
  • Asked for help in defining the GraphQL API for a task and checks if best practice is being followed
  • Broke down a task and the ordered these sub-tasks for delivery
  • Identified additional scenarios to cover on a task
E2: Engineer II

FOCUS:
Within Epic

Role Expectations
Critical Thinking
  • Holistic Thinking Understands the tasks that fits into a feature, the users impacted, the flows impacted and understands of the feature's purpose.
    Developing an ability to analyse the bigger picture and identify non-happy paths.
  • Technical Analysis Keeps context in mind when defining technical design for a feature or change.
    Thinks about what technical changes are needed for a set of tasks, acceptance criteria, seeks to follow best practice and impact of their design on other parts of the system.
    Designs are pragmatic, simple and recommend the most appropriate technology.
    Understands the team's context, how the overall system fits together at a high level and each team's responsibility for their piece of functionality
Business Impact
  • Understand "WHY" Understands the team's domain, how work in this domain relates to the team's objectives and deliverables and how it contributes to overall business strategy and how technical strategy maps to this.
  • Defining Strategy Understands the organisation's company strategy and how the engineering strategy aligns to this.
    Attempts to feed into squad OKRs that align to these strategies when the team is setting squad OKRs
Product Impact
  • Understands product area of focus, how it fits into the overall business, and sometimes makes improvement suggestions for it.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Suggested refactoring a module as part of an epic
  • Analysed the data in the database for the epic and noted different cases to handle
  • Found code that was re-used on a few flows and added these to regression tests for an epic
  • Suggested MVP version of their task to test a feature earlier with customers
  • Created a spike to quickly prototype a feature to better understand the impacts and flows
E3: Senior
Engineer

FOCUS:
Within Team

Role Expectations
Critical Thinking
  • Holistic Thinking Has a thorough understanding of a feature, the users impacted, the flows impacted and feature's purpose.
    Has the ability to analyse the bigger picture, identify and prioritise non-happy paths.
    Aims to consider more than one domain in this analysis.
  • Technical Analysis Creates project proposals and design that have considerable impact, or touch multiple systems.
    Technical designs are clear, well thought out, and considers dependencies, failure states, maintainability, testability and ease of support.
    Business context is kept in mind when proposing architectural decisions.
    Also considers scalability, reliability and performance of systems/contexts affected when defining technical designs.
Business Impact
  • Understand "WHY" Has a thorough understanding of the team's domain, how work in this domain relates to the team's objectives and deliverables and how it contributes to overall business strategy and how technical strategy maps to this.
    Has a basic understanding of adjacent teams' business domains.
  • Defining Strategy Understands the organisation's company strategy and how the engineering strategy aligns to this.
    Usually involved in discussions about the implications for their team. Feeds into defining and measuring OKRs for their squad when the squad are setting OKRs.
    May participate in discussions and providing input into technical direction of parts of the engineering strategy.
Product Impact
  • 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.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Researched the effort to migrate from one framework to another framework, considering pros, cons and effort.
  • Created a migration plan for legacy data and broke this into phases to avoid impact on production
  • Considered the options and effort of work and long term strategy when building a feature in their domain.
  • Asked for more context on the upcoming projects in the roadmap
  • Added dashboards to measure and monitor behaviours of customers
E4: Development Lead

FOCUS:
Within Team and Stakeholders

Role Expectations
Critical Thinking
  • Holistic Thinking Has a thorough understanding of a feature, the users impacted, the flows impacted and feature's purpose.
    Leads the team in analysing the bigger picture, identifying and prioritising non-happy paths. Considers across domains when analysing the bigger picture.
  • Technical Analysis Creates and guides the team on project proposals and design that have considerable impact, or touch multiple systems.
    Technical designs are clear, well thought out, and considers dependencies, failure states, maintainability, testability and ease of support.
    Business context is kept in mind when proposing architectural decisions.
    Also considers scalability, reliability and performance of systems/contexts affected when defining technical designs.
    Seeks alignment on overall technical architecture direction.
Business Impact
  • Understand "WHY" Has a thorough understanding of the team's domain, strategy, how it maps to overall market trends, and how it contributes to overall business strategy and how technical strategy maps to this.
    Has a thorough understanding of adjacent teams' strategies and how they map to their team and interaction points.
  • Defining Strategy Collaborates and decides on their team's engineering work and measuring these based on organisation's engineering strategy, together with their teammates and senior engineers. Sometimes involved in work on organisational engineering strategy.
Product Impact
  • 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.
Examples
+ show examples - hide examples
  • Led the team to consider the impact of a feature on each user persona.
  • Identified when there was a gap in the technical design of the squad, where security implication had been missed.
  • Guided the team to consider the implications to legacy data and flows when refactoring an area of the codebase.
  • Guided the team to think about Key Results of a feature and how this could be measured.
  • Analysed the upcoming epics and highlighted risks to be researched by the team upfront
E5: Engineering Manager

FOCUS:
Across Several Teams

Role Expectations
Critical Thinking
  • Holistic Thinking Guides across teams on developing a thorough understanding of a feature, the users impacted, the flows impacted and feature's purpose.
    Guides across teams in analysing the bigger picture, identifying gaps and dependencies across domains when analysing the bigger picture and aligning to the company goals.
  • Technical Analysis Guides teams on technical designs for larger and more complex technical initiatives and projects that consider dependencies, maintainability, failure states, testability, ease of support, performance and reliability across systems and contexts with alignment on the technical architecture design.
    Sets and champions best practice within the company.
    Identifies and prioritizes major areas of improvement in the architecture.
    Simplifies architecture to address complex problems.
Business Impact
  • Understand "WHY" Has a thorough understanding of several team's domains, and how they contribute to overall business strategy and alignment to the technical strategy.
  • Defining Strategy Works with VP Engineering and VP Product on strategic organisational decisions and plans.
    Leads cross-team strategic efforts, influencing decisions to achieve cross-team alignment on major goals.
Product Impact
  • Recognises 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.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Lead and align engineering team with the company's vision
  • Improve engineering quality and efficiency (e.g. improve workflow, code review, etc.)
  • Create positive team culture (e.g. curious, mutually challenging, collaborative)
E6: VP Engineering

FOCUS:
Across Organisation

Critical Thinking
  • Holistic Thinking Analyses the bigger picture aligning to the company goals and strategy.
    Guides the engineering organisation on thinking across the entire platform.
  • Technical Analysis Has a view across the majority of the architecture and sets direction on how engineering can align to the company's vision and growth.
    Takes a long term view of the architecture direction. Brings awareness where processes, architecture, organisation are not optimal and drives the team and leadership to make changes proactively to address them.
Business Impact
  • Understand "WHY" Has a thorough understanding of the entire business, including individual domains, and how they contribute to the overall business strategy and mapping technical strategy to this.
  • Defining Strategy Leads strategic organisational decisions and plans.
    Contributes to organisation strategic planning.
    Provides expertise and recommendations to CEO and other leaders
Product Impact
  • Works with VP Product and LT to define the product roadmap.
    Identifies technical complexities or limitations that may impact product long-term product plans
    Brings engineering and security considerations to product and strategic planning discussions
    Leads the establishment of the engineering and platform roadmap
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Lead and align all of engineering with the company's vision
  • Contributed to company strategy via strategy business cases and planning discussions.
  • Put in place measures to ensure all parts of the engineering organisation operate at their best productivity and efficiency.