The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
From Staff Blockchain Engineer (L4)
3-5 years as a Staff EngineerSkills to master
- At this stage, you'll have mastered complex system design, led multiple critical projects, and demonstrated strong mentorship. You'll need to develop a broader strategic perspective, deeper understanding of business impact, and the ability to influence executive-level stakeholders.
You're ready to move on when
- Successfully architected and delivered at least two major, high-value blockchain protocols from end-to-end.
- Consistently identified and mitigated significant security risks before they became incidents.
- Mentored and elevated at least 2-3 senior engineers to take on more significant technical leadership roles.
- Demonstrated the ability to translate complex technical concepts into clear, concise strategic recommendations for product and business leaders.
- Established a reputation as a go-to expert for the most challenging technical problems within the organisation.
- 2
From Technical Lead / Engineering Manager (Blockchain Focus)
4-6 years in a lead/management roleSkills to master
- You'll have strong people leadership skills and project delivery experience. You'll need to deepen your technical architecture expertise, particularly in security and protocol design, and develop a more comprehensive understanding of the entire blockchain ecosystem and its strategic implications.
You're ready to move on when
- Successfully led and delivered multiple high-stakes blockchain engineering projects, managing technical risks and team performance.
- Demonstrated deep technical understanding of smart contract security and decentralised system design, even if your primary role was management.
- Proven ability to attract, hire, and develop top-tier blockchain engineering talent.
- Effectively managed cross-functional dependencies and driven alignment on complex technical initiatives.
- Actively contributed to architectural discussions and influenced technical direction in previous roles.