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 Mid-Level Web3 Developer
2-3 years at Mid-LevelSkills to master
- Leading small features end-to-end, deep diving into smart contract security, mentoring junior peers, and taking ownership of deployment processes.
You're ready to move on when
- Successfully led 2-3 significant smart contract deployments to mainnet without major incidents.
- Consistently identifies and mitigates complex security vulnerabilities in code reviews.
- Actively mentors junior developers, providing clear guidance and fostering their growth.
- Proactively proposes architectural improvements and optimisations for existing protocols.
- 2
From Traditional Senior Backend Engineer (with Web3 shift)
3-5 years transitioningSkills to master
- Mastering Solidity/Rust, understanding EVM internals, smart contract security patterns, decentralised architecture principles, and dApp integration.
You're ready to move on when
- Has completed significant personal projects or contributions to open-source Web3 protocols.
- Demonstrates a deep understanding of blockchain fundamentals and cryptography.
- Can articulate the unique security challenges of Web3 compared to traditional backend systems.
- Has a strong grasp of Web3 development tools (Hardhat/Foundry, Ethers.js, The Graph).
- 3
From Security Researcher/Auditor (into development)
2-4 years transitioningSkills to master
- Shifting from finding bugs to proactively designing secure systems, writing production-grade code, and integrating security best practices from the ground up.
You're ready to move on when
- Has a track record of identifying critical vulnerabilities in smart contracts.
- Demonstrates the ability to write clean, maintainable, and well-tested Solidity/Rust code.
- Understands the full development lifecycle, not just the auditing phase.
- Can translate security insights into practical, defensive coding patterns.