Technical & Security roadmap
People targeting technical & security roles such as Smart Contract Developer, Frontend Web3 Developer, Developer Relations.
This is a lane-level planning guide, not a role-specific curriculum or a guaranteed path to a job. Starting point: Working code, tests, audit notes, uptime evidence, and threat models matter more than tutorial screenshots.
Milestones
Stage 1 of 5
Choose a chain and development stack
Review criteria
The stack note should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.
Done when: You can produce the stack note without step-by-step guidance and could explain the decisions behind it.Stage 2 of 5
Build and test a small contract or integration
Review criteria
The repository should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.
Done when: You can produce the repository without step-by-step guidance and could explain the decisions behind it.Stage 3 of 5
Document failure states and security assumptions
Review criteria
The threat notes should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.
Done when: You can produce the threat notes without step-by-step guidance and could explain the decisions behind it.Stage 4 of 5
Deploy a working testnet project
Review criteria
The testnet demo should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.
Done when: You can produce the testnet demo without step-by-step guidance and could explain the decisions behind it.Stage 5 of 5
Publish the repository and technical write-up
Review criteria
The technical case study should be reviewable by someone else: it names its assumptions, matches the stated task, and could stand as a small piece of evidence on its own.
Done when: You can produce the technical case study without step-by-step guidance and could explain the decisions behind it.
Decision point after each milestone
After each milestone, check whether the output matches a role's proof standards on its role guide. If it does not, revisit the milestone before moving on; if a nearby role fits your evidence better, compare it before continuing.