# 💎 Growth & Development
We use the Engineering Growth Framework as a tool for growth and development, this helps us evaluate where we are and how to progress, build goals and development objectives, and ensure consistency in our approach to this.
This framework will act as a guideline and evolve over time as we get more familiar with it, please feel free to contribute with comments and improvements.
guideline [noun]: a general rule, principle, or piece of advice
# 🚀 Delivery & Approach
Our growth framework is split into two sections; Delivery and Approach. This balances:
- What is necessary for a team to deliver on their specified purpose
- To what extent an individual can impact the team’s delivery
By thinking about Delivery and Approach and taking into account feedback throughout the last year on our current growth framework, we've been able to redefine and make a lot of expectations clearer, while making big improvements 🙌.
However, you'll see most of the Delivery and Approach categories are similar to Actions and Abilities, but with some additions and combinations.
Delivery: Engineer 📦
Delivery: Tech Lead 📦
Coding & Testing 💻🔬
Design & Architecture 📐
Debugging & Troubleshooting 🐛🔫
Hiring & Reputation 🌟
Developer Experience ⚒
Problem Solving 🤔
# 🔀 Delivery and Engineering Tracks
There are two Delivery categories that represent the different engineering tracks available:
- Delivery: Engineer
- Delivery: Tech Lead (Previously known as Tech Lead)
These categories reflect the importance of delivery to Engineering, RnD, and Attest, and we explicitly call out the expectations for each level here.
Delivery has expectations from Level 1 to 4
Delivery: Engineer and Delivery: Tech Lead have expectations from Level 5 to 7.
To reach level 5 Delivery and beyond, you will be looking at expectations from the Engineer or the Tech Lead category, but usually not both. The different tracks reflect your core focus, acknowledging there will be some overlap in places and some expectations will be common across tracks. In some scenarios it will make sense to be across both tracks.
# Engineering Tracks
The split of delivery into three categories represents the different engineering tracks available. This allows you to choose how you can make the most impact possible within Engineering and in which track you'd like to progress.
We acknowledge that one track and route of progression does not suit everybody and impact comes from a variety of responsibilities.
From level 5 and beyond you will choose a track to formally progress in, within Delivery. There will be flexibility to move between tracks, to explore different career paths.
This is the default track that most Engineers will feel at home in. Those who progress along the Engineering track will typically be expert coders, they understand deeply the business context and problem space they're working in and may have a seat across more than one squad. They make significant contributions directly to our OKRs or drive chapter work that improves our ability to deliver. They possess and build on a deep level of technical capability and domain knowledge, whilst being accountable for upskilling others and distributing knowledge across the whole engineering team and wider company.
The Engineer track is represented by the Delivery - Engineer category in the growth framework.
Tech Leads take on technical leadership and delivery responsibilities within a squad and beyond. This track sees a high degree of product knowledge and enables the squad to work efficiently towards their goals, while embracing a culture of continuous improvement. Those in this track drive regular feature delivery and are responsible for the engineering output of the squad.
The Tech Lead track is represented by the Delivery - Tech Lead category in the growth framework.
Those in the Engineering Management track are responsible for the growth & development of our engineers, strategy, and driving high-performance squads. Engineering managers build on their people skills and leadership, finding innovative ways to level up our team, creating a culture of trust, experimentation, and innovation, whilst acting as a force multiplier to our team.
The skills you can develop and the impact you create as an Engineering Manager is quite different to other roles in engineering, therefore a separate growth framework exists and can be found here:
The Engineering Growth Framework has flexibility built in. You are never committed to one track and if you decide that actually you would prefer to be in a different role and progress down a different track, you are free to make that choice and we will work to accommodate that.
# 📈️ Levels
# 🔭 Scope
When looking at the various Delivery and Approach levels, it's important to recognise at which scope each level applies to.
Level 1 - Small pieces of well-defined work within a squad, with the assistance of others
Level 2 - Independently works on small tasks within a squad
Level 3 - Feature / deliverable
Level 4 - Squad
Level 5 - Squad and chapter
Level 6 - Across more than one squad and chapter
Level 7 - Across the whole company
# 🗒️ Reviews
Between you and your manager, you agree on where you are on the growth framework. But the more inputs you have into this the more accurate and fairer this will be, that's where peer review comes in.
In Q1/Q3 we do an 'on/off track review' while in Q2/Q4 we do a 'Career Growth Review'. See below for more details on the difference between these review types.
# ⚖️ Pay Bands
The pay bands are calculated using salary benchmarking data and will be updated in the future if appropriate, for example when further levels and concepts are added to the growth framework.
# 🧠 Things to Remember
This framework acts a guideline, not a box ticking exercise. You can progress without meeting every single ability and action in a level.
Some flexibility will be required when using this, since we cannot eliminate all ambiguity from career progression in Engineering.
There are improvements to be made! Please give your feedback.