Blockchain architect to blockchain developer
A blockchain architect already meets 71% of what the blockchain developer role asks for. The move turns on 10 required skills not yet in the profile.
43.9/ 100
1 How much of what a blockchain developer is expected to do is already part of a blockchain architect’s work. Directional: the figure for the reverse move differs, because moving into a speciality is not the same problem as moving out of one. 2 Every skill the blockchain developer role is recorded as needing, required and optional together. What these numbers mean.
Why this move works
A blockchain developer role treats 33 of its required skills as things a blockchain architect already does. You would walk in with these on day one.
- blockchain application areas
- blockchain applications
- blockchain applications security principles
- blockchain architecture
- blockchain components
- blockchain consensus mechanisms
What stands in the way is 10 required skills the profile does not yet cover. Table 3 groups them; Table 4 says which to take first.
Table 2 · What you already bring
Of the 38 skills that carry over, these are the ones fewest other occupations ask for. A blockchain developer role needs them, and most people applying for one will not have them already. This is the part of a blockchain architect background worth leading with.
- already held blockchain application areas information and communication technologies (icts)
- already held blockchain applications information and communication technologies (icts)
- already held blockchain applications security principles information and communication technologies (icts)
- already held blockchain architecture information and communication technologies (icts)
- already held blockchain components information and communication technologies (icts)
- already held blockchain design patterns information and communication technologies (icts)
All 38 carried skills, including the 33 the blockchain developer role treats as required.
Table 3 · What you may need to learn
The 22 missing skills fall into 4 areas of the ESCO skill hierarchy, numbered in the order worth working in. Areas carrying the most required skills come first, and inside each one the required skills sit above the optional ones. Nothing here is a verdict on you: it is a list of what this particular job asks for that your current one does not.
- still to learn ICT debugging tools required
- still to learn blockchain required
- still to learn smart contract programming languages required
- still to learn computer programming required
- optional, not held Angular optional
- optional, not held C++ optional
- optional, not held Java (computer programming) optional
- optional, not held JavaScript optional
- optional, not held Scala optional
- optional, not held Solidity optional
- optional, not held TypeScript optional
- optional, not held Vyper optional
- still to learn use software design patterns required
- still to learn analyse decentralised applications required
- still to learn implement smart contracts required
- optional, not held adapt to changes in technological development plans optional
- optional, not held design user interface optional
- still to learn use software libraries required
- still to learn utilise computer-aided software engineering tools required
- optional, not held implement front-end website design optional
- optional, not held use markup languages optional
- still to learn game theory required
Table 4 · Where to start
The 3 entries a blockchain developer role is least likely to hire without. The ordering is computed from the skill data, not from what pays.
- 01 ICT debugging tools study this
- 02 blockchain study this
- 03 smart contract programming languages study this
Each entry opens a course search for that skill. Career Overlap earns nothing from these links.
Appendix · The rest of the record
All 38 skills that carry over
- already held blockchain application areas knowledge
- already held blockchain applications knowledge
- already held blockchain applications security principles knowledge
- already held blockchain architecture knowledge
- already held blockchain components knowledge
- already held blockchain consensus mechanisms knowledge
- already held blockchain design patterns knowledge
- already held blockchain history knowledge
- already held blockchain mining principles knowledge
- already held blockchain openness knowledge
- already held blockchain platforms knowledge
- already held blockchain terminology knowledge
- already held blockchain-based business models knowledge
- already held blockchain-based services regulation knowledge
- already held debug software skill
- already held decentralised identifiers knowledge
- already held decentralized application frameworks knowledge
- already held design process for blockchain-based systems skill
- already held develop blockchain innovative architectures skill
- already held digital identity management knowledge
- already held distributed ledger technologies consensus protocols knowledge
- already held distributed ledger technologies vulnerabilities knowledge
- already held distributed ledger technology knowledge
- already held evaluate blockchain architectures skill
- already held explain blockchain implications skill
- already held explain distributed ledger technologies principles skill
- already held identify blockchain innovation opportunities skill
- already held interpret technical requirements skill
- already held outline blockchain-based identity management skill
- already held recognise blockchain application areas skill
- already held recognise blockchain risks skill
- already held smart contract knowledge
- already held software components libraries knowledge
- already held ICT encryption knowledge
- already held cloud technologies knowledge
- already held cryptocurrency knowledge
- already held data analytics knowledge
- already held service-oriented modelling knowledge
12 supplementary skills, helpful but not required
- optional, not held Angular optional
- optional, not held C++ optional
- optional, not held Java (computer programming) optional
- optional, not held JavaScript optional
- optional, not held Scala optional
- optional, not held Solidity optional
- optional, not held TypeScript optional
- optional, not held Vyper optional
- optional, not held adapt to changes in technological development plans optional
- optional, not held design user interface optional
- optional, not held implement front-end website design optional
- optional, not held use markup languages optional
19 held skills the blockchain developer role does not ask for
- not needed by the target role analyse ICT system skill
- not needed by the target role analyse blockchain use cases skill
- not needed by the target role blockchain concept application knowledge
- not needed by the target role blockchain signature schemes knowledge
- not needed by the target role business processes knowledge
- not needed by the target role create business process models skill
- not needed by the target role data security principles knowledge
- not needed by the target role define roadmap for blockchain in applications skill
- not needed by the target role define software architecture skill
- not needed by the target role define technical requirements skill
- not needed by the target role design cloud architecture skill
- not needed by the target role design information system skill
- not needed by the target role design thinking knowledge
- not needed by the target role develop blockchain technology skill
- not needed by the target role develop software prototype skill
- not needed by the target role digital systems knowledge
- not needed by the target role implement cryptographic constructs skill
- not needed by the target role statistics knowledge
- not needed by the target role systems development life-cycle knowledge
13 gaps that are knowledge rather than practice
Knowledge gaps usually close through study. Practical skill gaps usually need something you can point at.
- still to learn ICT debugging tools required
- still to learn blockchain required
- still to learn smart contract programming languages required
- still to learn computer programming required
- still to learn game theory required
- optional, not held Angular optional
- optional, not held C++ optional
- optional, not held Java (computer programming) optional
- optional, not held JavaScript optional
- optional, not held Scala optional
- optional, not held Solidity optional
- optional, not held TypeScript optional
- optional, not held Vyper optional
Common questions about this move
Can a blockchain architect become a blockchain developer?
Yes, and it is a moderate move. A blockchain architect already covers 71% of what a blockchain developer is expected to do: 38 skills carry over, 33 of which the blockchain developer role treats as required.
What skills does a blockchain architect need to become a blockchain developer?
10 required skills are missing, plus 12 optional ones. They fall into 4 areas of the ESCO skill hierarchy, led by information and communication technologies (icts). The single most important is ICT debugging tools.
How hard is the move from blockchain architect to blockchain developer?
Its learning distance is 43.9 out of 100, which is the moderate band. That accounts for both how much is missing and how specialised those skills are.
How this record was compiled
Both occupations are taken from ESCO, which lists the skills and knowledge each occupation is expected to have and marks every one required or optional. Nothing here is a prediction about hiring, and nothing here knows that a particular employer wants a particular certificate. Treat Table 3 as a starting point for your own research rather than a syllabus. The full method states what these figures can and cannot tell you.