Reporting lines are anchored around technology disciplines. The following teams report into the CTO. Operationally people tend to work in squads as detailed in the Delivery section.
- Product Engineering
- Builds the apps, microservices, libraries and web frontends
- A small team that guides teams to design their own architectures
- Cyber Security & Risk
- Keeps our systems safe and secure
- Data & ML
- Provides data and BI solutions
- Cloud Infrastructure
- Builds, runs and scales our cloud infra
- Corporate IT
- Manages our workspace technology
The different career levels for people in Technology.
|#||Individual Contributor||People Leader|
|4||Staff Engineer||Team Lead|
|5||Principal Engineer||Engineering Manager|
Career pathways can go:
- Vertical, e.g. Engineer to Senior Engineer
- Horizontal, e.g. Staff Engineer to Team Lead
- Diagonally, e.g. Principal Engineer to Head
Other roles such as Data Scientist, are levelled in the same way, except “Engineer” is replaced with that domain-specific title.
- ‘✅’ – focus areas for each role
- ’–’ – optional areas for each role
|Individual Contributors||People Leaders|
|KRAs||Associate Engineer||Engineer||Senior Engineer||Staff Engineer||Principal Engineer||Team Lead||Engineering Manager||Head|
|Line manage people||✅||✅||✅|
|Lead multiple teams||✅||✅|
|Risk and compliance||✅|
When to use what type of talent?
We always prefer to hire permanent staff and provide them a career pathway.
Contractors are great for defined pieces of work and fixed deadlines. They give teams breathing space whilst they recruit a permanent team member. Only experts (senior or above) are considered as they need to start running on day one.
Consultants are used where a larger piece of work is to be completed that requires multiple resources for which we don’t have the skill set. For example an Infra architectural review.