E1: Engineer I

FOCUS:
Within Task

Role Expectations
Software Development Lifecycle
  • Participates and developing an understanding on Scrum and the importance and purpose of cadences of the methodology.
    Understands how the flow of work gets delivered to production.
Reliability & Accountability
  • Able to contribute to planned sprint work with guidance.
    Has daily conversation with the team about the progress of their work.
    Delivers on commitments with a sense of urgency and cares about the value of what they are working on and impact on the business.
Technical Planning
  • Able to contribute to planning and estimation with guidance.
    Works on prioritised tasks first and with a bias to action.
    Understands value of rightsizing and breaking down tasks to enable continuous integration and incremental delivery.
    Developing an understanding of weighing cost and value in decision making.
Dealing with Ambiguity
  • Works to clarify ambiguity in tasks and asks questions for clarification.
    Works on defining and handling risks with help from others.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Took ownership of a tasks, ensuring it is well tested from obvious errors and regressions
  • Observed a bug in production from their change and asked for help to resolve errors in production.
  • Asked questions to clarify ambiguity in a task before coding
  • After merging code, and checked the build pipeline when there errors in tests and deployments
E2: Engineer II

FOCUS:
Within Epic

Role Expectations
Software Development Lifecycle
  • Actively participates and understands Scrum, understands the importance and purpose of cadences of the methodology.
  • Understands how the flow of work gets delivered to production, will participate in improving the delivery process (e.g. fix configuration in the CI/CD pipeline).
  • Usually considers how the feature will be deployed with minimal disruption to production (e.g. when to delete columns in the database).
Reliability & Accountability
  • Commits to a realistic amount of work, and works with their teammates both to ensure they understand priority and urgency, and to deliver upon them accordingly.
    Cares about the value of what they are working on and impact on the business.
    Escalates any blockers, delays, and cost ballooning to their team daily. Clarifies expectations with their teammates.
Technical Planning
  • Before beginning work, ensures that tasks are appropriately sized for continuous integration and incremental delivery, weighs cost and value to make pragmatic decisions with help from teammates and manager.
    Understands and acts according to task prioritisation. Identifies dependencies.
Dealing with Ambiguity
  • Usually handles risk, change, and uncertainty within their personal scope of work effectively.
    Takes initiative to clarify ambiguity in work and communicates risk early.
    Usually decides and acts responsibly without having the total picture, and when in high pressure situations, seeking help from others early.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Understands the value of work to the business
  • Contributed to sprint work mostly autonmously
  • Edited build pipeline configuration to make improvements
  • Articulated to stakeholders clearly and early if they are blocked on a task
  • Realised a task was too big and broke this down
  • Identified when there was an impact or dependency to legacy data and flows
E3: Senior
Engineer

FOCUS:
Within Team

Role Expectations
Software Development Lifecycle
  • Actively participates and understands Scrum, understands the importance and purpose of cadences of the methodology, developing a point of view on a good software delivery process.
  • Understands how the flow of work gets delivered to production, acts to improve the delivery process.
  • Considers how the feature will be deployed with minimal disruption to production and how the feature will be monitored.
Reliability & Accountability
  • Ensures their commitments are realistic, understands their priority and urgency, and delivers upon them accordingly.
    Anticipates and communicates blockers, delays, and cost ballooning for their work before they require escalation.
    Cares about the value of what the team is working on and impact on the business.
    Ensures expectations within their team are clarified between all parties involved.
Technical Planning
  • Reviews tasks critically and ensures they’re appropriately sized for continuous integration and incremental delivery, weighs cost and value in order to take the most pragmatic action.
  • Uses this thinking in their own work, and to make suggestions to teammates.
  • Ensures tasks are prioritised correctly, dependencies are noted early and frontloads these items as part of prioritsation.
Dealing with Ambiguity
  • Handles risk, change, and uncertainty within their personal scope of work effectively.
  • Takes initiative to clarify ambiguity in a project and communicates risk early and offers possible solutions.
  • Decides and acts responsibly without having the total picture and when in high pressure situations, assisting others and communicating early.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Unblocked others with pragmatic decisions, e.g. spends time on a good GraphQL interface then stubs the response so others in the team can use the interface while logic is being built
  • Identified blockers early and makes suggestions on solutions to their team lead
  • Helped others in the team to resolve production outages
  • Identified where there is an impact on legacy flows and suggests solutions to deal with this
E4: Development Lead

FOCUS:
Within Team and Stakeholders

Role Expectations
Software Development Lifecycle
  • Motivates the team on Scrum process, understands the importance and purpose of the methodology, has a clear point of view on a good software delivery process and employs methods to refine and improve.
    Understands how the flow of work gets delivered to production, promotes improvements to the delivery process.
    Considers and prompts the team to consider how the feature will be deployed with minimal disruption to production and how the feature will be monitored.
Reliability & Accountability
  • Anticipates and communicates blockers, delays, and cost ballooning within their team’s projects, before they require escalation.
    Cares about the value of what the team is working on and impact on the business.
    Ensures expectations with their team and external stakeholders are clarified between all parties involved.
    Rallies and motivates the team on the team goals and commitments.
Technical Planning
  • Reviews epics and projects critically and ensures they’re appropriately broken down and prioritised, and well understood by the team.
    Ensures dependencies are identified early and well understood by the team, at both the task and epic level.
    Works within their team to foster a culture of priority setting and urgency in alignment with organisational strategy.
Dealing with Ambiguity
  • Effectively handles risk, change, and uncertainty within their team.
  • Takes initiative to guide and clarify ambiguity and frontloads risks.
  • Decides and acts responsibly in their work with their team without having the total picture, as well as when in high pressure situations, assisting others and communicating early.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Motivated the team on a goal by explaining why and set clear objectives
  • Guided the team to identify risks with legacy architecture and prompted for different solutions to make pragmatic decision
  • Scoped a project into milestones and increments for delivery
  • Defined a release plan that considered risks to deployment to production
  • Added improvements to standups to encourage engagement and awareness of each other's work
  • Provided transparency on issues with a project early
E5: Engineering Manager

FOCUS:
Across Several Teams

Role Expectations
Software Development Lifecycle
  • Deep understanding of agile and delivery principles.
    Motivates and teaches the Scrum process across teams, on the importance and purpose of the methodology, has a clear point of view and employs methods to refine and improve across teams.
    Defines the principles of the SDLC and coaches teams on meeting expectations for deployment, continuous integration and releases.
    Promotes improvements to the delivery process. Guides teams to consider how the feature will be deployed with minimal disruption to production and how the feature will be monitored.
Reliability & Accountability
  • Successfully manages cross-team commitments, their progress, and roadmap to delivery.
    Anticipates and communicates blockers, delays, and cost ballooning across teams, before they require escalation.
    Cares about the value and impact on the business of initiatives across teams.
    Ensures expectations across teams and stakeholders are clarified between all parties involved.
    Rallies and motivates across teams on their goals and commitments.
Technical Planning
  • Reviews cross-team work critically and ensures it’s appropriately broken down and prioritised, and well understood by all involved teams.

    Ensures cross-team dependencies are noted early and well understood by all teams involved and other relevant stakeholders. Works across teams to foster a culture of priority setting and urgency in alignment with organisational strategy.

    Understanding of the return-on-investment of key projects and ability to challenge the approach to align to business goals
    Works with VP Engineering and VP Product to establish team Objectives, coaches teams on defining key results
Dealing with Ambiguity
  • Effectively handles risk, change, and uncertainty across several teams. Takes initiative to guide and clarify ambiguity and teach teams to frontload risks.
    Decides and acts responsibly in their work across teams without having the total picture, as well as when in high pressure situations, assisting others and communicating in a timely manner.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Led an initiative on improving the review process
  • Guided a team lead on breaking down the scope of a project into milestones
  • Unblock a team on a cross-context dependency/risk by assisting, providing guidance on alternatives
  • Encouraged teams to identify blockers early during planning phase
  • Communicated expected delivery timeframes and potential delays for initiatives to stakeholders
E6: VP Engineering

FOCUS:
Across Organisation

Software Development Lifecycle
  • Sets the direction of the delivery process across the organisation, on the importance and purpose of the methodology, has a clear point of view and guides the organisation on improvement improvements to the delivery process.
    Promotes a culture amongst engineering of delivering features with minimal disruption to production.
Reliability & Accountability
  • Responsible for executing product roadmap on-time and within budget
    Responsible for ensuring security and relevant compliance of core systems
    Responsible for meeting relevant customer SLAs and SLOs.
    Successfully manages organisation-wide commitments, their progress, and roadmap to delivery.

    Ensures expectations across the organisation and external stakeholders are clarified between all parties involved.
Technical Planning
  • Identifies dependencies across the organisation and works with individual teams to resolve them before they become an issue, and installs preventative measures to mitigate repeat occurrences.
    Works across the organisation to foster a culture of priority setting and urgency in alignment with organisational strategy.
    Coaches the team on making trade-offs, prioritisation and managing technical debt
Dealing with Ambiguity
  • Identifies and manages technical and business risks
    Manages changes in scope, remit, strategy or business structure across the engineering organisation
    Identifies ambiguities in strategy and seeks to provide clarity to team and stakeholders
    Guides engineering to identify and frontload risks.
+ Show All Competencies + Hide Other Competencies
Examples
+ show examples - hide examples
  • Considers external contraints and business objectives when planning
  • Communicated expected delivery timeframes and potential delays for initiatives to the organisation
  • Led the prioritisation process on the technical roadmap
  • Provided guidance on the OKRs of the implementation of a migration