Preparing content…

Blockchain engineers

SOC 15-1299 · O*NET 15-1299.07

O*NET 15-1299.07 · Bright Outlook · security and release responsibilityDistributed ledgers, cryptographic protocols, and node and deployment securityU.S. wages and employment use parent group 15-1299 · Mainland employer notices
67%AI Impact ScoreFermatMind / 费马测试

Blockchain engineers design, implement and test distributed ledgers, nodes, smart contracts or applications that connect on-chain and off-chain work. They document permissions, failure handling, tests and release evidence. Roles may focus on protocols, integration or platform operations. BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

Model impact index for three equally weighted representative core tasks; not a measured share of working time or a job-loss probability. floor((50+75+75)/3+0.5)=67; fermatmind-ai-impact-v1; 2026-10-18.

116,580 USD per year (median)U.S. median annual wage (Computer Occupations, All Other definition)O*NET / U.S. Bureau of Labor Statistics
5.1% (2025—2035, parent category definition)U.S. employment growth (2025—2035, parent category definition)BLS
471,200 people (2025, parent category)U.S. employment (2025, parent category definition)BLS
27,000 per year (parent category)U.S. annual job openings (2025—2035, parent category definition)BLS
No data availableMainland China salary reference (no occupation-level statistic obtained)

Quick judgment

What kind of person suits being a blockchain engineer?

Try both BC-83 versions to see whether you like tracing permission changes, failure paths and release evidence.

Try BC-83 in section 09: trace two ledger versions on paper or in local memory and write one page for a reviewer.

Who is more likely to fit Blockchain engineers?

Conditions for pausing major investment: you have not yet completed, in a controlled environment (a testnet or a self-built environment), one full closed loop of requirements, design, implementation, testing, deployment, monitoring, and emergency response; or you only want to copy an existing template into a system that can be demonstrated and are unwilling to bear responsibility for keys, permissions, and change records; also, do not treat knowing one smart contract language or having taken a few online courses as proof that you can independently take responsibility for production environment funds and data security.

When should you be cautious about choosing Blockchain engineers?

In one sentence: blockchain engineers are not about buying coins or issuing a token; they maintain and support distributed, decentralized blockchain networks or blockchain applications, design and deploy secure blockchain design patterns and cryptographic protocols, and test their security, performance, and failure boundaries before and after deployment. The U.S. counterpart is O*NET-SOC 15-1299.07, marked Bright Outlook and listed as Job Zone Four (considerable preparation needed, SVP 7.0 to less than 8.0). The core boundary is that you can decide technical approaches at the protocol and implementation level, but you cannot make compliance, funding, or external disclosure decisions for the institution, and you cannot treat the chain running normally as meaning that business and compliance risks are already resolved.

How can a small experiment test your fit for Blockchain engineers?

Signals to keep exploring: you are willing to first write what needs to be solved as verifiable requirements and a threat list and only then write code; you can accept having your contracts, node configurations, and deployment scripts reviewed line by line by others; when key management, access control, exception handling, or performance bottlenecks arise, you are willing to stop and do small-scale testing and recording rather than getting the feature running and shipping it; and your interest in under what conditions the system fails and how large the consequences are exceeds your interest in whether the feature was built.

Career profile

Blockchain engineers design, implement and test distributed ledgers, nodes, smart contracts or applications that connect on-chain and off-chain work. They document permissions, failure handling, tests and release evidence. Roles may focus on protocols, integration or platform operations.

Quick career answers

What categories can the work of blockchain engineers be divided into?

The work of blockchain engineers falls into three categories: first, design and protocol tasks (discussing and planning systems with solution architects, systems engineers, or cybersecurity experts, designing and validating cryptographic protocols, and designing blockchain design patterns that make transactions secure, transparent, and tamper-resistant); second, implementation and deployment tasks (writing maintainable code using object-oriented design principles, updating client and server applications, designing data repositories, and automating deployment of updates across geographically distributed nodes); third, testing and risk tasks (testing the security and performance of blockchain infrastructure, assessing threats such as untested code and unprotected keys, running infrastructure tests to examine the behavior of large peer-to-peer networks, and implementing failure handling and logging). All three share the same reviewable chain of evidence.

Design and protocol tasks:

Design and protocol tasks

  1. 01Clarify client or business requirements
  2. 02determine system boundaries and the threat model with architects and systems and security personnel
  3. 03design blockchain design patterns and cryptographic protocols
  4. 04define the data and permission model
  5. 05review the control matrix and risk assessment results
  6. 06produce implementable specifications and a deployment plan.

Implementation and deployment tasks:

Implementation and deployment tasks

  1. 01Write maintainable code according to object-oriented design principles
  2. 02update integration and business logic in client and server applications
  3. 03design and implement data repositories
  4. 04implement logging and monitoring
  5. 05automate deployment of updates across geographically distributed nodes through CI and configuration management
  6. 06retain version, configuration, and rollback records.
Testing and risk tasksTest the security and performance of blockchain infrastructure in a controlled environment, run infrastructure tests to examine peer-to-peer network behavior at scale, assess threats such as untested code and unprotected keys, implement catastrophic failure handlers to identify security intrusions promptly, review assessment processes and risks based on security assessments or the control matrix, and finally write the conclusions and limitations clearly.

Where are the boundaries between blockchain engineers and adjacent positions?

Blockchain engineers center on the technical implementation of distributed ledgers and cryptographic protocols: information security analysts (15-1212.00) face broader information system security protection and compliance and do not take ledger protocols as their default subject; computer systems analysts (15-1211.00) focus on analyzing and improving business systems and do not necessarily handle cryptography and consensus; database administrators (15-1242.00) work around data storage and queries; computer programmers (15-1251.00) mainly write and test code, and their official definition does not include blockchain protocol and consensus design by default; penetration testers (15-1299.04) center on authorized attack simulation. Similar job titles do not mean responsibilities are interchangeable. Database administrators 15-1242.00 and the architect classification are different, and the two are not combined into one precise occupation for wages or duties.

DimensionPrimary trackComparison track
Core purposeKeep distributed networks and blockchain applications running stably on a secure, transparent, and verifiable basis, and make every transaction and change traceable.Core purpose
Main subjects and basisThe subjects are distributed ledger networks, nodes, smart contracts and client and server applications, and key and permission configurations; the basis is system requirements and the threat model, protocol and design pattern specifications, security assessments and the control matrix, and applicable regulations and platform rules.Main subjects and basis
Core processClarifying requirements and threats, designing protocols and design patterns, implementing coding and data models, distributed deployment and automation, security and performance testing, monitoring and failure handling, and change and rollback records.Core process
Main outputsMaintainable code and contracts, protocol and design pattern descriptions, deployment and configuration scripts, testing and security assessment records, monitoring and logging plans, and technical documentation including limitations and rollback notes.Main outputs
Responsible partyThe protocol and implementation level is the responsibility of trained and authorized engineering personnel; funding, compliance, and external disclosure decisions are the responsibility of the institution and its compliance, risk control, and legal roles; when work exceeds your authorization (for example production release, key custody, or external statements) you should escalate rather than decide on your own.Responsible party
Admission and licensingWhether you may access the production environment and mainnet, whether you may hold or custody keys, and whether you may release and upgrade contracts are determined jointly by the institutional authorization chain, change approval, and applicable regulations, and do not arise automatically from technical ability or job grade.Permissions and approval
Conclusion boundariesTesting and assessment conclusions describe the properties the system exhibits and the known limitations under a given configuration and test conditions; they are not the same as absolute security and do not replace compliance, funding, or legal judgment, and are affected by test coverage, environment differences, and version changes.Conclusion boundaries

Core responsibilities

  1. 01

    Discuss and plan systems with solution architects, system engineers, or cybersecurity experts to meet customer requirements.

  2. 02

    Implement catastrophic failure handlers to identify security breaches and prevent serious damage.

  3. 03

    Test the security and performance of blockchain infrastructures.

  4. 04

    Assess blockchain threats, such as untested code and unprotected keys.

What must be verified item by item before starting?

Before starting, verify at least six items: the occupation definition and the job entity, the education and training pathway, the actual languages and toolchains used, access authorization for the production environment and keys, the review mechanism for code and changes, and the real pay structure and on-call arrangements.

  1. 01

    Item 86 of the 2026 public notice by the Fuzhou Human Resources and Social Security Bureau actually lists blockchain engineering technicians (2-02-38-08); when the Cyberspace Administration of China republished it in 2020 the code was 2-02-10-15, describing architecture, underlying technology, applications, testing, deployment, and operations. The original 2022 code entry returned no body text this round, and no claim is made that the full text was read. Classification is not the same as an individual license, and a same-named Chinese position does not prove one-to-one correspondence with U.S. 15-1299.07.

    Occupation definition

  2. 02

    O*NET lists it as Job Zone Four (SVP 7.0 to less than 8.0), and respondents consider a bachelor's degree necessary at 38%, some college education without a degree at 19%, and a master's degree at 13%; coursework and training in computer science, software engineering, cryptography, and information security are common foundations, and the O*NET education and training information is not a list of occupational licenses; entry conditions must be verified separately by the target jurisdiction, service content, and employer requirements.

    Education and training pathway

  3. 03

    The O*NET technology list groups software and tools into 21 categories and marks 34 Hot Technologies and 20 In-Demand skills; common areas include containers and orchestration (Docker, Kubernetes), development languages and runtimes (Go, C and C++, Java, C#, TypeScript, Node.js), cloud and configuration management (AWS, Azure, Terraform, Ansible), databases and messaging (MySQL, PostgreSQL, MongoDB, Kafka), and version control and collaboration (Git, JIRA, Confluence); the labels indicate frequency of appearance in job postings, tools are only means of implementation, and protocol choices and security conclusions still rest with people.

    Methods and tools

  4. 04

    On-chain data is hard to delete once written, and keys and credentials are hard to revoke once leaked; verify key custody and rotation rules, environment isolation, access control, and audit logs, and confirm whether the cloud services or third-party tools used are permitted to process the relevant data.

    Key and data authorization

  5. 05

    Editorial suggestion: bring code, contracts, configurations, and deployment scripts under version control, and arrange review, staged release, and failure handling suited to the actual system. It was not verified that all employers have a two-person review system; distinguish reversible code and configuration changes from transactions already written to the ledger, and do not use release records to promise reversal of on-chain results.

    Records and review

  6. 06

    The same job title may be paid by annual salary, by project, or under a service contract; when comparing, include production permissions and key responsibilities, on-call and emergency response arrangements, the change approval burden, continuing learning costs, and whether there is mentoring by senior personnel in the written agreement.

    Pay and working hours

Work reality

Communication
94% of respondents use email every day, 50% make phone calls every day, and 71% have face-to-face discussions once a week or more but not daily.
Team collaboration
47% say work group teamwork is extremely important and 33% very important; 38% say they have contact with others most of the time.
Accuracy and detail
63% say precision or accuracy is extremely important and 19% very important.
Sitting and location
69% sit continually or almost continually and 19% more than half the time; 60% work indoors in a controlled environment every day.
Decision freedom
25% have a lot of decision freedom and 56% some freedom; 36% need to make decisions every day.
Working hours
50% work more than 40 hours a week and 44% work 40 hours a week.
Time pressure
38% face time pressure every day and 25% once a week or more but not daily; 40% say competition is high.
Responsibility for results
56% consider their decisions to have an important effect on the results of colleagues or the organization; 33% say the consequences of error are extremely serious.
Physical exposure
38% use their hands to handle tools or controls continually or almost continually, and 31% do repetitive motions continually or almost continually.

O*NET structured fields and use boundaries

O*NET OnLine 15-1299.07 (precise occupation)BLS 2025 wage percentiles shown by O*NET (Computer Occupations, All Other definition)National Bureau of Statistics 2025 urban unit wages (this occupation not listed separately)BLS employment and projections (2025—2035, SOC 15-1299 parent category)O*NET industry distribution and employer job posting technology signals
O*NET OnLine 15-1299.07 (precise occupation)
O*NET occupational identity and tasks: O*NET-SOC 15-1299.07 Blockchain Engineers, Bright Outlook, updated 2026, Job Zone Four (SVP 7.0 to less than 8.0). The official duty is to maintain and support distributed and decentralized blockchain networks or blockchain applications and to design and deploy secure blockchain design patterns and solutions across geographically distributed networks; there are 18 tasks in total, of which 17 are Core with importance ratings, and the new API task has an unpublished importance rating rather than 0; the high-importance tasks include discussing and planning systems with architects, systems engineers, or cybersecurity experts (92), implementing catastrophic failure handlers to identify security intrusions (91), testing the security and performance of blockchain infrastructure (91), assessing threats such as untested code and unprotected keys (88), and designing and deploying design patterns that make transactions secure, transparent, and tamper-resistant (85).
BLS 2025 wage percentiles shown by O*NET (Computer Occupations, All Other definition)
U.S. wage distribution: the 2025 BLS occupational employment and wage statistics (OEWS) shown by O*NET, under the Computer Occupations, All Other (SOC 15-1299) definition — annual wage 55,940 USD at the 10th percentile, 79,370 USD at the 25th percentile, 116,580 USD at the median, 157,500 USD at the 75th percentile, and 188,470 USD at the 90th percentile; the corresponding median hourly wage is 56.05 USD. This definition is not a separate 15-1299.07 statistic.
National Bureau of Statistics 2025 urban unit wages (this occupation not listed separately)
Precise Chinese occupation wages are still missing; the authorized salary section adds matched NBS2025 industry and broad personnel category pre-tax annual average references, which cannot replace this occupation's wages.
BLS employment and projections (2025—2035, SOC 15-1299 parent category)
In the BLS 2025—2035 projections table, the parent category Computer Occupations, All Other (SOC 15-1299) grows from 471,200 to 495,300 employed, a 5.1% increase, with a listed net gain of 24,200 and 27,000 annual openings; this is not a separate blockchain engineer statistic and is not a personal employment guarantee.
O*NET industry distribution and employer job posting technology signals
O*NET2025 U.S. SOC15-1299 other computer occupations parent category industry distribution: professional, scientific, and technical services 26%, government 22%, information 10%, and other 42% (including finance and insurance and administrative support); all are items published by the source, not a separate blockchain 15-1299.07 figure, a Chinese distribution, or industry wages. The detail page lists 21 software categories, 34 Hot labels, and 20 In-Demand labels; of the 34 items on the Hot single page, 17 have percentages and 17 are unpublished, and the denominator is unique U.S. job postings in 2025, not an adoption rate.

Career direction comparison

How do the career directions of blockchain engineers compare with adjacent occupations?

The table below compares blockchain engineers with adjacent occupations and the pathways for moving in from adjacent positions; the basis for judgment is the main output, the object of responsibility, and the required training, not how similar the job titles are.

How do the career directions of blockchain engineers compare with adjacent occupations?
Career directionCore work and outputKey differencesBest-fit choice
If you want to cover broader security operations and compliance work, consider information security analysis first; if your interest is concentrated in ledger protocols, keys, and contract security, consider blockchain engineering first.Both focus on security, but information security analysts cover protection and compliance for the entire information system, while the default subject of blockchain engineers is the implementation and deployment security of distributed ledgers, cryptographic protocols, and smart contracts; protocol-level cryptographic design and testing are the more concentrated part of the latter.Information Security Analysts (15-1212.00)Directed at organizational information system security protection, with outputs mainly being security policies, monitoring alerts, vulnerability handling, and compliance assessments.
If you would rather do business process analysis and system planning, compare systems analysis first; if you would rather work on protocol and code implementation, consider blockchain engineering first.Computer systems analysts center on business system analysis and improvement and usually do not go deep into cryptography and consensus implementation; blockchain engineers center on the technical implementation and deployment of protocols, nodes, and contracts and must handle distributed consistency and key management.Computer Systems Analysts (15-1211.00)Study an organization's existing systems and design improvements, with outputs mainly being requirements analysis, system design, and implementation recommendations.
If you would rather work around data storage, queries, and backups, consider the database direction first; if you want to handle the constraints created by immutability and multi-party consensus, consider blockchain engineering first.Both care about data integrity and access control, but database administrators work around centrally manageable storage systems, while blockchain engineers face distributed ledgers that are hard to modify after the fact and are maintained jointly by multiple parties; immutability and consensus mechanisms are constraints specific to the latter.Database Administrators (15-1242.00)Design, organize, and protect data storage systems, with outputs mainly being data models, backup and recovery, and access control.
If you would rather focus on coding and implementation, consider the programmer direction first; if you are willing to take on design, deployment, and security responsibility at the same time, consider blockchain engineering first.Computer programmers center on writing and testing code and usually are not responsible for system-level protocol design, key management, and distributed deployment; blockchain engineers must take on protocol and deployment security responsibility at the same time, and code is only one part of it.Computer Programmers (15-1251.00)Write and test code to specification, with outputs mainly being runnable software modules and tests.
If you enjoy the process of finding and exploiting vulnerabilities more, compare penetration testing first; if you would rather design and maintain systems that run over the long term, consider blockchain engineering first.Penetration testing assesses systems from an attacker's perspective within authorized boundaries, while blockchain engineers design and deploy systems from a builder's perspective and do security and performance testing in a controlled environment; the directions of responsibility and the authorization boundaries differ.Penetration Testers (15-1299.04)Simulate attacks within an authorized scope, with outputs mainly being vulnerability discovery, exploitation validation, and remediation recommendations.
If you are willing to build up the cryptography and distributed systems foundations and accept code review, you can consider moving in; if you only want to change the job title without building security and protocol training, the gap will be large.The gap is usually not programming ability but cryptographic protocols, consensus and distributed systems, key management, smart contract security, and change and rollback discipline; writing code that runs is not the same as being able to bear responsibility for production funds and data security.Moving in from software development or operations positionsYou already have coding, deployment, or operations experience and want to move toward distributed ledgers and cryptographic protocols.

How to choose

This page compares blockchain engineers with six adjacent directions on the same set of dimensions: career direction, core work and output, key differences, and which direction better fits each preference. Adjacent directions are described according to their own official occupational descriptions and do not mean job titles are interchangeable.

Conclusion: the basis for choosing a direction is the main output, the object of responsibility, and the required technical training, not how similar the names are; once the direction is set, verify item by item the target direction's education requirements, the actual languages and toolchains used, access authorization for the production environment and keys, and the review mechanism for code and changes, and keep written confirmation.

AI impact on this career

Will AI replace blockchain engineers?

Use fictional inputs to draft tests and handoffs. People review permissions, failures, state changes and release evidence. Actual keys and releases follow organizational authority.

AI assessment method and sources

FermatMind AI Impact Score estimation method v1

FermatMind / 费马测试 · 2026-10-18

  • Model impact index for three equally weighted representative core tasks; not a measured share of working time or a job-loss probability. floor((50+75+75)/3+0.5)=67; fermatmind-ai-impact-v1; 2026-10-18.
  • Anchors: 0 negligible; 25 preparation or record assistance; 50 substantial assistance; 75 most information output can be formed by AI with review; 100 almost all of the selected task can be done by AI and independently verified.
  • Protocol and design | Design and validate cryptographic protocols, and design blockchain design patterns that make transactions secure, transparent, and tamper-resistant | Reviewable protocol and design pattern descriptions. — 50/100; weight=1/3
  • Implementation and data model | Write maintainable code using object-oriented principles, update client and server applications, and design and implement data repositories and logging | Code and data models that others can reproduce and review. — 75/100; weight=1/3
  • Testing and risk assessment | Test the security and performance of the infrastructure, run peer-to-peer network tests, and assess threats such as untested code and unprotected keys | A testing and assessment report including coverage and limitation statements. — 75/100; weight=1/3

Editorial ratings use the existing occupational responsibilities and AI task analysis on this page. They are not adoption rates, measured effects, job-disappearance or personal-unemployment probabilities, or official scores from Stanford or another external institution. No measured time weights or future robot deployment are assumed.

Which blockchain engineering tasks can AI handle?

Editorial suggestion: trial AI-assisted search, code drafts, test samples, and log organization on fictional data, recording the time, errors, and manual changes, and only then judge whether time is saved; a speed-up must not be treated as already verified in advance. Output must be checked item by item against the actual threat model, permissions, and rollback requirements.

Which steps will actually be adopted?

It depends on the knowledge scope and confidentiality requirements for code and contracts, access control for the production environment and keys, and the change review and release approval arrangements. Technical feasibility does not mean it is permitted for the production environment or real assets, nor that the team has adopted it.

Will AI reduce blockchain engineer positions?

Task exposure, team adoption, and employment counts are different measures. In the BLS 2025—2035 projections table, the parent category Computer Occupations, All Other (SOC 15-1299) grows from 471,200 to 495,300 employed, a 5.1% increase, with a listed net gain of 24,200 and 27,000 annual openings; this is not a separate blockchain engineer statistic and is not a personal employment guarantee. The projection does not measure AI effects separately, so it cannot be used to infer that AI causes job gains or losses.

Task impact matrix

Comparison of AI impact across career tasks
Work areaTaskCurrent changeHuman control point
System planning and protocol designDiscuss and plan the system with solution architects, systems engineers, or cybersecurity experts, and design design patterns that make transactions secure, transparent, and tamper-resistant.Editorial task suggestion: dependency and interface document search, design pattern examples, and configuration snippets can be generated with assistance.Judge whether the protocol and design patterns match the requirements and threat model, whether the permission and key design exceeds boundaries, and whether the deployment plan can be rolled back.
Implementation and data modelWrite maintainable code using object-oriented design principles, update the integration and business logic of client and server applications, and design and implement data repositories and logging.Editorial task suggestion: code completion, syntax conversion, and boilerplate code can be generated with assistance.Check dependencies and versions, whether keys and permissions are minimized, and whether exception and failure paths are covered.
Threat identification and failure handlingImplement catastrophic failure handlers to identify security intrusions and prevent serious harm, and assess threats such as untested code and unprotected keys.Editorial task suggestion: anomaly pattern screening and log clustering can be automatically pre-screened.Judge whether an alert is a false positive or a real intrusion signal, and decide whether to isolate nodes or roll back changes.
Security and performance testingTest the security and performance of blockchain infrastructure, and run infrastructure tests to examine the behavior of large peer-to-peer networks at scale.Editorial task suggestion: test cases and first drafts of load testing scripts can be generated with assistance.Check whether the test coverage and limitation statements match the analysis goals and confirm that the conclusions are not over-extrapolated.
Deployment and release controlAutomate deployment of updates across geographically distributed nodes through configuration management and pipelines, and retain version, configuration, and release records.Editorial task suggestion: pipeline configuration and template reuse can be assisted.Decide whether a change may enter production and when to roll back, and take responsibility for release and rollback decisions.
Technology assessment and requirement clarificationEvaluate new blockchain technologies and vendor products, and determine technical requirements by discussing data needs with engineers, product managers, or data scientists.Editorial task suggestion: material search and comparison organization can be assisted.Judge whether a new technology or vendor product suits the current requirements and security boundaries, and explain its assumptions and limitations.
Code review, mentoring, and retrospectivesEditorial task suggestion: review others' code and contracts, guide junior engineers, take part in design reviews and retrospectives, and turn the experience into standards and documentation.Editorial task suggestion: document and checklist drafts can be generated with assistance.Editorial task suggestion: be responsible for team output quality, code review standards, and developing new staff.

Why does employment evidence reach different conclusions?

The five evidence cards explain the source, the research object, the conclusion, and the limits on use; they support the official duties, task definitions, technology signals, general employment projections for the BLS computer and IT occupational group, and task exposure research, and are not AI replacement rates or predictions of AI-caused job gains or losses; the IT group openings are not the number of blockchain sub-occupation positions.

O*NET-SOC 15-1299.07 occupation summary

View source ↗
Subject
U.S. occupational identity and official duties
Finding
Maintain and support distributed and decentralized blockchain networks or blockchain applications and design and deploy secure blockchain design patterns and solutions across geographically distributed networks. This occupation is marked Bright Outlook and the page was updated in 2026.
Limitation
This is a U.S. definition and cannot be extrapolated to mainland China; official duties are not the same as a specific employer's job description.

O*NET-SOC 15-1299.07 detailed information (tasks and work activities)

View source ↗
Subject
Official 18 tasks and 41 work activities
Finding
Tasks include discussing and planning systems with architects, systems engineers, or cybersecurity experts (92), implementing catastrophic failure handlers to identify security intrusions (91), testing the security and performance of blockchain infrastructure (91), assessing threats such as untested code and unprotected keys (88), designing and deploying design patterns that make transactions secure, transparent, and tamper-resistant (85), and designing and validating cryptographic protocols (83); the main work activities are using computers (98), processing information (88), and updating and using relevant knowledge (87).
Limitation
The task list describes the work content of the occupational group and does not mean every position performs all 18 tasks.

O*NET-SOC 15-1299.07 technology list (employer job posting technology signals)

View source ↗
Subject
Technologies and tools appearing in employer job postings
Finding
The actual Hot single page lists 34 items: 17 have job posting percentages and 17 are unpublished; Python24%, Go17%, Docker/AWS15%, Node.js/JavaScript13%, Java/Kubernetes12%, and TypeScript/SQL11%. The detail page separately lists 21 software categories and 20 In-Demand labels, which are not mixed into the same table; the shares are the single unique U.S. job posting of 2025, not an adoption rate.
Limitation
Technology labels indicate frequency of appearance in job postings and do not mean the institution has deployed the tool or that the position has already been replaced or cannot be replaced.

BLS Computer and Information Technology Occupations Occupational Outlook Handbook

View source ↗
Subject
Wages, employment, and 2025—2035 projections for the computer and information technology occupational group
Finding
May 2025 median annual wage for this group is 109,470 USD (50,980 USD for all occupations); overall employment is projected to grow faster than the average for all occupations from 2025—2035, with about 280,000 job openings per year, and the typical entry-level education for most occupations is a bachelor's degree.
Limitation
This is a BLS computer and information technology occupational group comparison, not the SOC 15-1299 parent category or a 15-1299.07 sub-occupation statistic; the group trend cannot be used to infer blockchain position counts.

International Labour Organization (ILO) Working Paper 140

View source ↗
Subject
Global occupational task exposure to generative AI
Finding
The ILO 2025 methodology built an exposure gradient from a representative sample of 29,753 occupational tasks, a survey of 1,640 people, and 52,558 data points; the report notes that most occupations consist of tasks requiring human input, that the most likely impact is job transformation rather than wholesale replacement, and that the index does not provide job count predictions for a single occupation.
Limitation
The index measures exposure at the task level, not adoption, automation, or unemployment predictions, and it cannot be used to derive job counts for a single occupation.

Why does impact differ by work direction?

Editorial task suggestion: the table below compares three groups of work directions in terms of automation impact: which steps can be assisted and which judgments and responsibilities still rest with people.

System planning and protocol design

AI primarily changesEditorial task suggestion: dependency and interface document search, code drafts, and test samples and configuration snippets can be generated with assistance.

Human responsibility remainsEditorial task suggestion: decide the protocol and design patterns, the key and permission model, and consensus and deployment trade-offs, and take responsibility for system security and availability.

Implementation and data model

AI primarily changesEditorial task suggestion: code completion, syntax conversion, regular expressions, and log formatting can be screened automatically.

Human responsibility remainsEditorial task suggestion: check dependencies and versions, confirm whether permission and key configurations exceed boundaries, retain reproducible build and deployment records, and bear responsibility for traceable results.

Testing, deployment, and documentation

AI primarily changesEditorial task suggestion: document drafts, comments, change notes, and first drafts of runbooks can be generated by tools.

Human responsibility remainsEditorial task suggestion: model output must not be treated as a security conclusion or compliance statement; it must be checked item by item against the actual code and test results and signed by the responsible person.

Accountability must remain intact when AI enters professional workflows

The following five steps are editorial suggestions; the specific adoption, review, and release rules are set by the actual institution and are not a uniform statutory process. The reversibility of code configuration does not mean confirmed ledger transactions can be reversed.

  1. Confirming requirements and boundaries

    Editorial task suggestion: first confirm this task's requirements, threat model, environment boundary (test or production), and institutional rules.

  2. Tool handling scope

    Editorial task suggestion: give only rollback-capable, reviewable assistive steps to tools, such as code drafts, test drafts, and document organization.

  3. Human review

    Editorial task suggestion: review tool output item by item against the code repository, dependency list, and test results, and judge whether it introduces vulnerabilities, privilege overreach, or version inconsistency.

  4. Record keeping

    Editorial suggestion: retain code, configuration, build and deployment logs, and reasons for manual changes; verify code and configuration recovery and business compensation plans against the actual mechanism, and do not infer from complete records that on-chain transactions can be rolled back.

  5. Authorization and responsibility

    Editorial task suggestion: protocol and permission design, security conclusions, and production release are signed and owned by trained and authorized people.

Professional risks of using AI

Tool output treated as a confirmed security conclusion

Unreviewed generated code or configuration may introduce vulnerabilities or privilege overreach and enter the production environment when testing is insufficient.

Control: Editorial task suggestion: mark tool output as a draft and adopt it only after code review, static checking, and controlled environment testing.

Keys and user data sent out improperly

Keys, credentials, and undisclosed business or user data, once sent out or leaked, may cause asset losses and violate compliance requirements.

Control: Editorial task suggestion: handle according to least knowledge and least privilege; before uploading, confirm the processor, storage location, retention period, and feasibility of deletion, and keep keys out of external prompts.

Tool and dependency versions that cannot be traced

Editorial risk analysis: builds and deployments that are hard to reproduce or review add difficulty to troubleshooting and incident investigation; whether they may run is determined by the actual environment and authorization process and is not uniformly denied here.

Control: Editorial task suggestion: record the tool name and version, the input scope, dependency changes, the reasons for manual changes, and the decision maker.

Mixing conclusions from test and production environments

Editorial risk analysis: extrapolating test environment conclusions directly to production, or failing to control version and configuration differences, weakens the validity of comparisons; verify the applicable conditions against the actual object.

Control: Editorial task suggestion: fix the version and configuration baseline in the plan; when changing them, record the reasons and scope of impact and repeat the security and performance testing.

Missing review leading to unclear accountability

Changes with unclear responsibility cause delays in incident retrospectives and compliance checks and may let unreviewed code enter production.

Control: Editorial task suggestion: confirm the reviewer and escalation chain before the change begins; stop and report when work exceeds your training and authorization.

How should different audiences respond?

Students or career changers preparing to enter this occupation

Editorial task suggestion: first complete, on a testnet or in a self-built environment, one closed loop from the requirements and threat list through design, implementation, testing, deployment, and rollback, and only then discuss tools and certificates; at the same time, verify whether the target position belongs to software and information technology services, financial technology, an internet platform, or blockchain information services, because the four differ in data permissions, release approval, and compliance requirements.

Working blockchain engineering personnel

Editorial task suggestion: use generative tools for rollback-capable steps such as code drafts and completion, first drafts of unit tests, log and document organization, and contract comments and examples; protocol and design pattern choices, the key and permission model, deployment and rollback plans, and security conclusions must remain with people.

Institutions and engineering teams

Editorial task suggestion: before introducing tools, clarify the usable steps, the knowledge scope and confidentiality requirements for code and contracts, access control for the production environment and keys, the review and source verification process for generated content, error escalation paths, and the responsible person for human review, so that any output returns to a version-controlled code repository.

Education and training

Editorial task suggestion: focus training on cryptographic protocols and consensus, distributed systems, keys and access control, code review and change discipline, and test design and fault injection, while also training vulnerability identification in generated code, dependency risk checking, and the ability to express uncertainty.

Common questions about AI and career development

Will blockchain engineers be replaced by AI?

The sources consulted for this page cannot assert that this occupation will be wholly replaced or will never be replaced. Engineering personnel must still verify requirements, protocols, permissions, testing, and release conclusions within their authorization; task assistance capability and final employment counts must be verified separately.

Source: O*NET occupation summary and detailed informationOriginal source ↗

Do I need to know how to code to enter the field now?

O*NET tasks include object-oriented programming and automated deployment, and the detail page lists 21 software categories and 34 Hot labels; editorial suggestion: train on reviewable, reproducible code, and do not set knowing a few languages, one piece of work, or a checklist as a uniform threshold for all employers.

Source: The actual link is the detail page and supports the programming and deployment tasks; the job posting technology shares are on the Hot single page.Original source ↗

Which tasks are most affected by AI?

Dependency and interface search, code drafts and completion, test samples and configuration snippets, and log and document organization; these steps are rollback-capable and reviewable.

Source: The actual link is the Hot job posting signals; the ranking of tasks by AI assistance is an editorial analysis, and there is no measured replacement ranking for this occupation.Original source ↗

Will this occupation shrink by 2035?

In the BLS 2025—2035 projections table, the parent category Computer Occupations, All Other (SOC 15-1299) grows from 471,200 to 495,300 employed, a 5.1% increase, with a listed net gain of 24,200 and 27,000 annual openings; this is not a separate blockchain engineer statistic and is not a personal employment guarantee.

Source: BLS 2025—2035 occupational projections table (SOC 15-1299 parent category)Original source ↗

Can AI sign a security assessment or release decision?

No. Signing security conclusions, production release, and compliance statements are determined by institutional authorization and regulations; tools can neither bear professional responsibility nor obtain compliance approval.

Source: O*NET occupation summary and this page's method noteOriginal source ↗

In which year will this job disappear?

The O*NET, BLS, and ILO sources consulted for this page give no disappearance year for this occupation; task exposure, adoption rates, and employment counts differ, and this page makes no year prediction.

Source: The actual custom entry point is used to select occupation fields and does not provide a job disappearance year.Original source ↗

What should I learn first now?

Prioritize learning distributed systems and cryptographic protocol foundations, at least one systems-level language, testing and debugging, and keys and access control, and complete one reviewed full deployment; tool skills come after reviewable engineering ability.

Source: The actual link is the detail page and supports tasks, education, and skills; the training directory is under localtraining and cannot be conflated with real-time enrollment.Original source ↗

Directional differences within this occupation are mainly reflected in the subject matter and responsibility setting: public chains and protocols, consortium chains and industry applications, financial technology and payments, and blockchain information services and infrastructure each have different data permissions, release approvals, and compliance requirements; when choosing a direction, verify the actual permissions and review mechanism rather than looking only at the job title.

Chinese mainland salary reference

Mainland China salary reference: official statistical definitions and gaps

The 2022 edition of the mainland China occupational classification code lists blockchain engineering technicians (2-02-38-08), covering architecture, underlying technology, applications, testing, deployment, and operations; when published in 2020 the code was 2-02-10-15. Occupational classification is not the same as an individual practice license, and it does not prove that a same-named recruitment position corresponds one-to-one with U.S. 15-1299.07.

Mainland China salary reference: official statistical definitions and gaps

The 2022 edition of the mainland China occupational classification code lists blockchain engineering technicians (2-02-38-08), covering architecture, underlying technology, applications, testing, deployment, and operations; when published in 2020 the code was 2-02-10-15. Occupational classification is not the same as an individual practice license, and it does not prove that a same-named recruitment position corresponds one-to-one with U.S. 15-1299.07.

Mainland China (national definition)

Insufficient evidence: no national occupation monthly wage distribution precisely corresponding to blockchain engineers was obtained.

First-tier cities (Beijing, Shanghai, Guangzhou, Shenzhen)

Insufficient evidence: no verifiable city-level occupation monthly wage data were obtained, and this page presents no city rankings.

Other cities

Insufficient evidence: no official or verifiable source supports blockchain engineer monthly wage ranges for other cities.

Which job directions correspond to different education backgrounds?

Precise occupation wages are still missing; matched broad-category pre-tax annual average references have been added and cannot be used to set individual monthly wage bands.

Education background, job directions, and notes (editorial compilation, not salary statistics)
Education backgroundJob directionsNotes and verification suggestions
Bachelor's degree in computer science, software engineering, information security, or a related field (current students and new graduates)Entry-level development or testing positions at software and information technology services companies; entry-level back-end or infrastructure positions at internet platforms.Usually does not independently take charge of production release and key management; verify the mentoring arrangement, code review process, and access permissions.
Master's level (computer science, cryptography, or information security direction)Engineering positions involving distributed ledgers, cryptographic protocols, or security in financial technology institutions and research and development teams.Systems involving funds, user data, or external services must be checked against the institution's security and compliance requirements; activities providing blockchain information services to others must additionally comply with the filing and security assessment requirements of the Provisions on the Administration of Blockchain Information Services.
Has existing development or operations experience and has received security trainingBack-end, infrastructure, or security engineering positions at software and information technology services companies.Production release, key custody, and external disclosure authority are still determined by the institutional authorization chain and do not arise automatically from technical ability.
Overseas degrees or professional certificationsEngineering positions at multinational institutions or cross-border projects.Overseas degrees and certifications can serve as ability materials; activities providing blockchain information services to others in mainland China must still comply with filing, security assessment, and content management requirements.

When comparing opportunities, confirm the nature of the institution, production and key permissions, change approval responsibility, and the pay method (annual salary, project-based, or service contract), and do not treat an industry average as an individual wage expectation.

Which industries and directions use this occupation?

Information transmission, software, and information technology services

NBS2025 information transmission, software, and IT services: urban non-private 248,752 and private 128,166 yuan per year; above-scale enterprises in this industry: 242,019 overall, 275,504 for professional and technical, and 472,496 for middle management and above, yuan per year. Match only by the actual unit industry and scale and your own duties; these are pre-tax annual averages, not the blockchain occupation median, starting salary, or city monthly wage.

Financial industry

Match by the actual financial institution industry: NBS2025 financial industry non-private 211,164 and private 140,451 yuan per year, an industry-wide pre-tax annual average and not blockchain engineering wages.

Scientific research and technical services

Match by the actual technical service institution: NBS2025 scientific and technical services non-private 182,064 and private 83,560 yuan per year, and 172,877 yuan per year for professional and technical staff at above-scale enterprises; these are not blockchain wages.

Will AI affect blockchain engineer wages?

Editorial reasoning from the tasks: AI may assist coding, testing, and documentation; AI materials do not fill this occupation's wage gap.

U.S. salary reference

How much do U.S. blockchain engineers earn?

The 2025 U.S. SOC 15-1299 parent category median annual wage is 116,580 USD and the median hourly wage is 56.05 USD; annual wages range from 55,940 to 188,470 USD from the 10th to the 90th percentile. In the BLS 2025—2035 projections table, the parent category Computer Occupations, All Other (SOC 15-1299) grows from 471,200 to 495,300 employed, a 5.1% increase, with a listed net gain of 24,200 and 27,000 annual openings; this is not a separate blockchain engineer statistic and is not a personal employment guarantee.

U.S. wage distribution

U.S. wage distribution
Wage statistical positionAnnual wage referenceConversion boundariesHow to understand this position
10th percentile55,940 USD per year (10th percentile)Official conversion, not an individual monthly incomeThe 10th percentile is an annual wage of 55,940 USD; this is the low end of the distribution, does not represent all newcomers, and is not a starting salary promise.
50th percentile116,580 USD per year (median)Not an individual monthly incomeThe median is an annual wage of 116,580 USD; it describes the midpoint of the entire distribution, not an individual take-home income.
90th percentile188,470 USD per year (90th percentile)Official conversion, not an individual take-home wageThe 90th percentile is 188,470 USD per year; it describes the high end of the 2025 parent category distribution and does not represent a common level or a personal high-pay guarantee.

Wage · 10th percentile:55,940 USD per year (10th percentile);The corresponding 10th percentile hourly wage is 26.89 USD; this is a percentile point at the low end of the distribution, 10% of workers earn this amount or less, and it is not a minimum wage or a promise of an entry-level starting salary;BLS 2025 wage percentiles shown by O*NET

Wage · 25th percentile:79,370 USD per year (25th percentile);The 25th percentile hourly wage under the same definition is 38.16 USD;BLS 2025 wage percentiles shown by O*NET

Wage · median:116,580 USD per year (median);The corresponding median hourly wage is 56.05 USD, and the median is not the entry wage;BLS 2025 wage percentiles shown by O*NET

Wage · 75th percentile:157,500 USD per year (75th percentile);The 75th percentile hourly wage under the same definition is 75.72 USD;BLS 2025 wage percentiles shown by O*NET

Wage · 90th percentile:188,470 USD per year (90th percentile);The 90th percentile hourly wage under the same definition is 90.61 USD; editorial suggestion: verify seniority, industry, duty requirements, and pay with the actual employer; this round obtained no estimate of how these factors relate to wages in this sub-occupation;BLS 2025 wage percentiles shown by O*NET

How should U.S. blockchain engineer wages be understood?

Is the median the entry-level wage?

The median is not the entry wage: it means half of practitioners earn above and half below that value; the 10th and 25th percentiles are closer to the low end of the distribution but are still affected by employer, industry, and region.

Can the hourly wage be used to derive an individual annual salary?

Hourly and annual wages are two presentations of the same OEWS definition (that statistic is converted on a standard work year), and individual take-home or overtime income cannot be derived from them.

Where do the percentiles and median come from?

The figures come from the BLS 2025 OEWS wage data shown by O*NET, under the Computer Occupations, All Other (SOC 15-1299) definition; the projection period and other statistical definitions follow the original O*NET and BLS pages.

Which conditions affect actual income?

Editorial suggestion: compare education, duties, industry, and regional conditions and actual pay with the employer; this round did not verify occupation-specific causal effects of these factors.

How much do U.S. wages differ across industries?

How much do U.S. wages differ across industries?
IndustryMedian wage for this occupation within the industryHow to understand this value
Professional, scientific, and technical servicesInsufficient evidence: the sources consulted for this page did not obtain a separate within-industry median wage for 15-1299.07.2025 parent category professional, scientific, and technical services 26%, not a blockchain sub-occupation or industry wage.
GovernmentInsufficient evidence: the sources consulted for this page did not obtain a separate within-industry median wage for 15-1299.07.2025 parent category government 22%, not a blockchain sub-occupation or industry wage.
InformationInsufficient evidence: the sources consulted for this page did not obtain a separate within-industry median wage for 15-1299.07.2025 parent category information 10%, not a blockchain sub-occupation or industry wage.
Other industries (including finance and insurance and administrative support)Insufficient evidence: the sources consulted for this page did not obtain a separate within-industry median wage for 15-1299.07.2025 parent category other 42%, an item published by the source, and there is still no blockchain sub-occupation industry wage.

Which factors actually affect blockchain engineer wages?

Education and training

Editorial job requirement check: O*NET lists this occupation as Job Zone Four (SVP 7.0 to less than 8.0), and among respondents 38% consider a bachelor's degree necessary, 19% consider some college education without a degree necessary, and 13% consider a master's degree necessary. These are new-entrant education requirement responses and do not prove the effect of education or training on starting pay; actual positions and pay should be verified with the employer.

Industry and employer type

O*NET2025 U.S. SOC15-1299 other computer occupations parent category industry distribution: professional, scientific, and technical services 26%, government 22%, information 10%, and other 42% (including finance and insurance and administrative support); all are items published by the source, not a separate blockchain 15-1299.07 figure, a Chinese distribution, or industry wages.

Scope of duties and level of responsibility

Editorial suggestion: compare the protocol and security responsibilities, release authority, emergency on-call, and management duties and pay in the actual contract; this round did not verify their causal effect on wages for identical positions or a relative ranking of contributions against tool ability.

U.S. employment prospects

Employment · employment size

471,200 people (2025, SOC 15-1299 parent category definition)

BLS parent category employment base, not the precise 15-1299.07 headcount, projected at 495,300 in 2035 with a listed net gain of 24,200;BLS 2025—2035 occupational projections table

Employment · annual job openings

27,000 per year (2025—2035 projections, parent category definition)

Annual job openings over the projection period include growth and separation replacement demand and cannot be treated as net new positions or a personal employment guarantee;BLS 2025—2035 occupational projections table

Career fit guide

Which interests, abilities, and work styles matter more for being a blockchain engineer?

Editorial self-check signals: turning requirements and threats into reviewable designs and code, checking dependencies and permissions, and accepting review; use these only to discuss training gaps, not to prove hiring or competence.

You may be better suited to: You can press for use scenarios and threat boundaries when requirements are unclear, and write the design, permissions, and rollback plan in a form others can check; you are willing to report honestly when testing reveals serious problems rather than shipping first and fixing later.

These situations require caution: You treat the feature running as system reliability, are unwilling to review dependencies and permissions, resist code review or change records, or push for release despite insufficient testing; choices that only want to write code without bearing operations and security responsibility also require caution.

Do an entry exercise: In a self-built or testnet environment, write a one-page design note (requirements, threats, permissions, deployment, and rollback plan), implement a minimal runnable system, write test cases, and complete one code review; ask an experienced person to challenge your permission and exception handling design, and then judge whether you are willing to do this kind of work long term.

Do not let one test decide your career

Holland occupational interest model (RIASEC)

Evidence strength: O*NET explicitly gives the interest code, which is official occupational material; it describes the interest characteristics of the occupational group, not an individual fit conclusion.

Which Holland interest type is closer to blockchain engineers?

The Holland interest code is CI (Conventional and Investigative): Conventional corresponds to organizing information and data according to established processes and standards, with specific fields including information technology and mathematics and statistics; Investigative corresponds to researching and analyzing abstract problems, with the specific field being mathematics and statistics.

  • The combination of Conventional and Investigative matches the job tasks: you must both handle code, configuration, and records according to established processes and standards and analyze protocols and threat models.
  • If you only want to write new code and are completely unwilling to follow processes, records, and code review, the interest code is not enough to support choosing this occupation.

Do not use it this way: Note: a match between interest test results and the occupational interest code only indicates that the direction is close; it does not mean you already have the practical ability needed for cryptographic protocols, distributed systems, and security testing.

Test my Holland career interests

Five-factor personality model (Big Five)

Evidence boundary: the personality prompts on this page are editorial compilations, not an occupation-specific prediction model; verify with reviewable work samples.

Which Big Five traits are more relevant to this job?

Editorial suggestion: observe your own way of working by whether you complete testing and change records to standard, whether you keep communicating during failures, and whether you accept cross-team review. You can combine this with Big Five self-reflection, but this page has no occupation-specific personality validity research for blockchain positions.

  • Editorial suggestion: record whether you consistently complete testing, accept code review, and leave change records, and do not treat conscientiousness scores as ability evidence.
  • Editorial suggestion: when exploring a new protocol, record the assumptions, controlled tests, and retrospective results at the same time, and do not infer technical judgment ability from openness scores.

Do not use it this way: Note: treating personality scores as ability conclusions is a common misuse; this page provides no score thresholds or personality type lists.

View my Big Five personality traits

Myers-Briggs Type Indicator (MBTI)

Evidence boundary: the occupational materials read on this page provide no result on MBTI predicting competence or hiring for this position, so no type recommendation is made.

Can MBTI be used to judge whether I suit being a blockchain engineer?

The O*NET and BLS occupational materials consulted for this page give no MBTI type list or hiring threshold for blockchain engineers. Editorial suggestion: use types to discuss communication preferences and check them against code, tests, and review feedback, and do not decide investment or screening on type alone.

  • If MBTI is used as a starting point for discussing communication preferences, it should be tested at the same time by code, tests, and review feedback.
  • Treating type labels as ability boundaries hinders accepting code review and security advice.

Do not use it this way: Note: this page lists no best-suited type and does not endorse using it to screen candidates.

Understand my MBTI preferences

Enneagram

Evidence boundary: the occupational materials read provide no result on the Enneagram predicting competence or hiring for this position.

Can the Enneagram tell me whether I suit this occupation?

The O*NET and BLS occupational materials read on this page provide no mapping between the Enneagram and blockchain positions. Editorial suggestion: it can be used to organize motivations and stress responses and then checked against actual tasks, and training or hiring should not be decided on type alone.

  • If you use it to organize your own motivations and stress responses, the conclusions should be tested against real engineering practice.
  • Treating a type interpretation as a basis for technical judgment is a typical boundary-crossing risk.

Do not use it this way: Note: this page provides no mapping between types and positions.

Explore my Enneagram pattern

Intelligence quotient (IQ) and numerical reasoning

Evidence strength: the official O*NET skills list gives the importance ratings above; this is an occupational characteristic description and does not correspond to a specific score threshold.

If I am not good at math, can I be a blockchain engineer?

O*NET basic skills are critical thinking 69, reading 75, and mathematics 53; activities are using computers 98 and analyzing 78. They describe the occupational group, and individual competence cannot be inferred directly from a mathematics grade or a single debugging session; editorial suggestion: verify actual logic, systems analysis, and programming training.

  • Being able to understand the basic concepts of distributed systems and cryptography is the prerequisite for understanding protocol and security design.
  • If you clearly avoid debugging, log analysis, and troubleshooting, evaluate whether this will affect system reliability.

Do not use it this way: Note: this page does not use any test score as a basis for admission or elimination.

Understand my intelligence and reasoning performance

Emotional intelligence (EI, often called emotional quotient)

Evidence boundary: O*NET work styles describe attention to detail, integrity, and dependability; the materials read on this page provide no predictive validity or thresholds of emotional ability tests for blockchain positions.

Do blockchain engineers need high emotional intelligence?

Editorial observation suggestion: observe communication, stress response, and help-seeking behavior during failures or reviews; this round did not verify occupation-specific predictive validity of emotional test scores for blockchain competence or hiring, and scores are not used in place of technical training.

  • Editorial observation: whether the person can keep communicating when the system is abnormal or a review is challenging, and can acknowledge test limitations and seek help promptly.
  • No occupation-specific comparison of the predictive validity of behavioral versus emotional test scores was verified.

Do not use it this way: Note: this page provides no emotional ability thresholds and does not equate high scores with competence.

Understand my emotional intelligence abilities

Which adjacent direction are you more likely to suit?

Direction leaning toward information system security operations

Fits better when: You like doing security monitoring, vulnerability handling, and compliance assessment, covering the entire information system rather than a single ledger.

Watch for: You need to build up security operations and compliance knowledge; the scope widens but is no longer focused on protocol implementation.

Explore related career: Information security analysts

Direction leaning toward business system analysis and planning

Fits better when: You are willing to communicate directly with business stakeholders, map processes, and design system improvements.

Watch for: You need to build up business analysis and requirements management; understanding the business does not replace protocol and security implementation.

Explore related career: Computer systems analysts

Direction leaning toward data storage and data governance

Fits better when: You want to work around data models, backup and recovery, and access control.

Watch for: You need to build up database and data governance training; centralized storage and distributed ledgers have different constraints.

Explore related career: Database administrators

Direction leaning toward programming implementation and testing

Fits better when: You are willing to write, modify, and test code to specification, locate errors, and maintain software modules.

Watch for: You need to build up languages, debugging, and testing ability for the target position; programming positions do not by default bear blockchain protocol, consensus, and production release responsibility.

Explore related career: Computer programmers

Direction leaning toward authorized attack simulation

Fits better when: You are willing to identify vulnerabilities, simulate attacks, validate exploitation paths, and propose remediation within a written authorization scope.

Watch for: You need to build up penetration testing methods, reporting, and authorization boundaries; system building experience does not automatically equal attack simulation ability.

Explore related career: Penetration testers

Direction leaning toward computer network architecture design

Fits better when: You are willing to plan local area networks, wide area networks, and communication infrastructure and compare capacity, reliability, network security, and cost.

Watch for: You need to build up network protocols, topology design, capacity planning, and failure recovery; ledger application experience is not the same as network architecture ability.

Explore related career: Computer network architects

Career fit questions

What kind of personality is better suited to being a blockchain engineer?

More than a personality type, it is a way of working: being able to accept having your code reviewed line by line, being willing to write assumptions and limitations clearly, and insisting on not releasing when testing is insufficient. O*NET work styles include features such as attention to detail, integrity, and dependability.

Are introverts suited to being blockchain engineers?

O*NET group figures of 94% email, 50% telephone daily, 71% face-to-face weekly but not daily, and 47% rating teamwork extremely important support the communication requirement; they do not support inferring a predictive ranking of expression against extroversion scores or drawing admission conclusions about introversion or extroversion.

Can extroverts do well as blockchain engineers?

You can explore further. Editorial suggestion: express yourself clearly in reviews while checking code, logs, and evidence item by item; observe yourself by whether you accept feedback and revise judgments, and do not use the degree of extroversion as a competence standard.

Which MBTI type is best suited to blockchain engineers?

The occupational materials read on this page provide no best-suited MBTI type. Editorial suggestion: use it to organize preferences and raise verification questions, then test with work samples; this page provides no type list or hiring prediction.

Which Holland interest type is better suited to this occupation?

O*NET lists this occupation's interest code as CI (Conventional and Investigative): Conventional corresponds to organizing information and data by process and standard, and Investigative corresponds to analyzing abstract problems. The interest code describes the characteristics of the occupational group, not an individual fit conclusion.

Can personality trait scores predict job performance in this occupation?

You cannot judge on test results alone. Editorial suggestion: combine the work samples on this page, reviewed development practice, and the target position's qualification requirements; the materials read on this page give no personality test hiring threshold for the position.

Can someone who is not good at math be a blockchain engineer?

A weak mathematics foundation does not automatically exclude you from this occupation. First complete the permission, exception, and ledger record exercises on this page and check whether you can understand the rules, locate errors, and explain the results; if you consistently avoid reasoning and debugging, then compare adjacent directions.

Do blockchain engineers need high emotional intelligence?

Editorial observation suggestion: observe communication, stress response, and help-seeking behavior during failures or reviews; this round did not verify occupation-specific predictive validity of emotional test scores for blockchain competence or hiring, and scores are not used in place of technical training.

Can the Enneagram be used to judge whether I am suited?

You cannot decide on the Enneagram alone. The occupational materials read give no mapping between type and competence in blockchain positions; you can use it to organize self-reflection and then decide on investment based on actual tasks and training conditions.

How do I use deliverables to judge which direction suits me?

Editorial suggestion: use designs, code reviews, and testing records with limitations to identify training gaps; being able to write the basis and uncertainty clearly is not the same as having reached basic competence, production permissions, or hiring conditions.

Work pressure, risks, and career boundaries

What pressures, risks, and career boundaries come with being a blockchain engineer?

Article 2 of the blockchain information services rules covers services offered to the public in mainland China through websites, apps and similar channels. Article 11 requires covered providers to file within ten working days after starting the service. Check personal data, production access, keys and public release under the relevant rules and organizational authority.

Evidence scope: the O*NET tasks and context support the work subjects, the NIST CSF2.0 and AI RMF1.0 official entry points support the general governance background, and the actual clauses of the Chinese provisions support specific public information service obligations. The six categories of consequences and controls are an editorial risk analysis, not an incident rate, an institutional approval process, or a risk conclusion provided by a training directory.

01

Improper key and credential management

Typical scenario:Private keys or access credentials are hardcoded, shared, or not rotated, and production and test environments are not isolated.

Roles most affected:The institution, users, and the engineering team

Possible consequence:Leakage of keys or credentials or overly broad permission configurations may cause asset losses and data leakage.

How to reduce risk:Editorial control suggestion, with specific authorization and rules to be verified separately: adopt least privilege, key custody and rotation rules, environment isolation, and access auditing, and review them periodically. Distinguish code and configuration recovery from ledger results, and do not promise reversal of confirmed transactions.

Evidence:O*NET full tasks and context · NIST Cybersecurity Framework 2.0

02

Contract or protocol defects being exploited

Typical scenario:Insufficiently reviewed contract logic, reentrancy, or permission defects are deployed directly to mainnet.

Roles most affected:Users, the client, and the engineering team

Possible consequence:Contract or protocol defects may be exploited, causing irreversible asset or data consequences.

How to reduce risk:Editorial control suggestion, with specific authorization and rules to be verified separately: perform threat modeling and formal review at the design stage, and conduct code review and dedicated security testing after implementation. Distinguish code and configuration recovery from ledger results, and do not promise reversal of confirmed transactions.

Evidence:O*NET full tasks and context · NIST Cybersecurity Framework 2.0

03

Vulnerabilities introduced by dependencies and configuration

Typical scenario:Using unverified third-party dependencies or templates directly without checking versions and licenses.

Roles most affected:The engineering team and operations personnel

Possible consequence:Vulnerabilities in dependencies or configuration enter production and are hard to locate and roll back quickly.

How to reduce risk:Editorial control suggestion, with specific authorization and rules to be verified separately: fix version and configuration baselines, use dependency scanning and controlled environment validation, and retain rollback-capable release records. Distinguish code and configuration recovery from ledger results, and do not promise reversal of confirmed transactions.

Evidence:O*NET full tasks and context · NIST Cybersecurity Framework 2.0

04

Releasing to production with insufficient testing

Typical scenario:Treating demonstrably usable as ready for release, and skipping load testing and failure drills.

Roles most affected:Users and the institution

Possible consequence:Releasing with insufficient testing means failures or attacks can cause service interruptions and irreversible losses.

How to reduce risk:Editorial control suggestion, with specific authorization and rules to be verified separately: complete security and performance testing on a testnet or canary environment, and specify the rollback conditions and responsible persons. Distinguish code and configuration recovery from ledger results, and do not promise reversal of confirmed transactions.

Evidence:O*NET full tasks and context · NIST Cybersecurity Framework 2.0

05

Unclear filing and compliance boundaries for external services

Typical scenario:Providing a public information service without filing beyond the specified period, developing and launching new products, applications, or functions without reporting security assessment to procedure, or failing to retain log backups as required.

Roles most affected:The platform operator and the compliance owner

Possible consequence:Providing blockchain information services to the public in mainland China without fulfilling filing, security assessment, and content management obligations may result in an order to rectify or a penalty.

How to reduce risk:The Provisions on the Administration of Blockchain Information Services apply to entities, nodes, and related technical support organizations that provide blockchain information services to the public; filing is required within ten working days from the date the service is provided, security assessment must be reported to procedure when developing and launching new products, applications, or functions, and real-name authentication, content management, and log backups of no less than six months must be implemented. Filing is not an individual occupational license, and not all internal ledger development should be treated as a public information service.

Evidence:O*NET occupation summary · Provisions on the Administration of Blockchain Information Services

06

Missing review and unclear accountability

Typical scenario:In cross-team collaboration, code review or release approval is missing and no one reviews key changes.

Roles most affected:The client and the engineering lead

Possible consequence:When responsibility is unclear, unreviewed changes may enter production with no one accountable.

How to reduce risk:Editorial control suggestion, with specific authorization and rules to be verified separately: specify deliverables, reviewers, release approval, and the escalation chain in the contract and process, and retain version and signing records. Distinguish code and configuration recovery from ledger results, and do not promise reversal of confirmed transactions.

Evidence:O*NET full tasks and context · NIST Cybersecurity Framework 2.0

Getting started, qualifications, and career development

How do you become a blockchain engineer? Education, qualifications, and career path

Article 2 of the blockchain information services rules covers services offered to the public in mainland China through websites, apps and similar channels. Article 11 requires covered providers to file within ten working days after starting the service. Check personal data, production access, keys and public release under the relevant rules and organizational authority. The Beihang and Huawei Cloud examples differ in education, experience and development scope.

How new graduates or career changers can verify and get started

Comparison of entry directions

Entry positionWhat you mainly do at the startAbility materials editors suggest verifyingHow to prove yourself without experienceDifferences from other directions
Back-end or testing positions at software and information technology services companiesImplement and test modules under mentoring, read logs, and troubleshoot defects; first become familiar with version management, code review, and the release process.Ability materials editors suggest verifying (uniform employer requirements were not verified): a computing-related degree, programming ability, and project or internship experience.Submit a small runnable, testable service or contract, with code, tests, and deployment notes.This pathway does not independently take charge of production release and keys; verify access permissions, review arrangements, and the mentoring owner.
Engineering and security positions at financial technology institutionsTake part in the development and testing of internal systems or ledger-related modules, and keep records in line with compliance and risk control requirements.Ability materials editors suggest verifying (uniform employer requirements were not verified): engineering ability, sensitivity to funds and data security, and communication ability.Submit a design document including the permission model and exception handling notes, with the corresponding test records.Funds and compliance judgments are the responsibility of the relevant institutional roles; engineering personnel must not make compliance conclusions in their place.
Infrastructure or platform engineering positions at internet platformsTake charge of engineering tasks related to deployment, monitoring, and capacity, and take part in failure drills and retrospectives.Ability materials editors suggest verifying (uniform employer requirements were not verified): distributed systems fundamentals, scripting and automation ability, and operations experience.Submit a deployment note including the rollback plan and drill results.Platform stability responsibility and security conclusions must be confirmed jointly by the team and cannot be concluded from personal testing alone.
Engineering positions at blockchain information service or protocol teamsImplement protocol-related modules on a testnet or in a self-built environment and take part in security and performance testing.Ability materials editors suggest verifying (uniform employer requirements were not verified): protocol and cryptography fundamentals, code quality, and security testing experience.Submit an assessment record including threat modeling and test scope and limitations.Providing information services to the public requires verifying filing and security assessment requirements; technical ability does not replace compliance obligations.
Moving in from adjacent positions (back-end development, operations, security operations)Take on coding, deployment, or security monitoring tasks and become familiar with version, configuration, and change processes.Ability materials editors suggest verifying (uniform employer requirements were not verified): a relevant background and engineering experience, and check whether distributed and security fundamentals are present.Submit reviewable outputs organized from your existing job tasks and explain the gaps relative to protocols and cryptography.Adjacent position experience is not the same as protocol and key responsibility; a transfer requires building up distributed systems and security training.

What evidence employers usually look for

Education and admission

U.S. side: O*NET lists this occupation as Job Zone Four (SVP 7.0 to less than 8.0), and among respondents 38% consider a bachelor's degree necessary, 19% consider some college education without a degree necessary, and 13% consider a master's degree necessary. The O*NET education and training information is not a list of occupational licenses; entry conditions must be verified separately by the target jurisdiction, service content, and employer requirements, and actual requirements follow the employer and client.

Study suggestion: prioritize programming, algorithms, distributed systems, networks, and cryptography fundamentals; this is not a verified list of institutions and does not constitute degree recognition or a hiring guarantee.

Authorization and service scope

Editorial suggestion: access production systems and keys within a written authorization scope and adopt least privilege; the Provisions on the Administration of Blockchain Information Services apply to entities, nodes, and related technical support organizations that provide blockchain information services to the public; filing is required within ten working days from the date the service is provided, security assessment must be reported to procedure when developing and launching new products, applications, or functions, and real-name authentication, content management, and log backups of no less than six months must be implemented. Filing is not an individual occupational license, and not all internal ledger development should be treated as a public information service.

When personal information is involved, verify the lawful processing basis, notice, and least necessity requirements separately; do not reduce all processing to obtaining consent, and do not write raw personal information directly into a ledger that is hard to delete.

Task and ability evidence

The official skills profile centers on reading comprehension (75), active listening (69), critical thinking (69), and active learning (63); transferable skills include complex problem solving, judgment and decision making, programming, and systems analysis. The main work activities are using computers (98), processing information (88), and updating and using relevant knowledge (87).

The interest code is CI (Conventional and Investigative); these fields describe the characteristics of the occupational group and do not constitute an individual competence threshold.

Tools and job posting signals

The O*NET technology list groups software and tools into 21 categories and marks 34 Hot Technologies and 20 In-Demand skills. Common areas include containers and orchestration (Docker, Kubernetes), cloud and configuration management (AWS, Azure, Terraform, Ansible), databases and messaging (MySQL, PostgreSQL, MongoDB, Kafka), and version control and collaboration (Git, JIRA, Confluence).

Before using tools on the production environment or real data, confirm whether access authorization, environment isolation, and change approval cover that use.

BC-83: Two fictional ledger traces

BC-83 is a fictional local ledger. Start with ledger=[], writer_epoch=1 and no committed IDs. A writer can only append, an admin can only rotate, and a reader can only read. W1 and W2 stand for epochs 1 and 2. A is a fictional admin tag.

Process E1=(r1,writer,W1,append,10), E2=(r1,writer,W1,append,10), E3=(r2,reader,R,append,20), E4=(r3,admin,A,rotate,2), E5=(r4,writer,W1,append,20), E6=(r5,writer,W2,append,20), and E7=(r6,writer,W2,append,30, with an injected failure before commit).

Restart from the same initial state for the variant. Change only E6 from W2 to W1. All other events stay the same.

Check the role first. Unauthorized actions return DENIED and raise an alert. For append, a stale epoch returns STALE with an alert, then a committed ID returns DUPLICATE. Otherwise commit the integer and ID together and return APPENDED. A failure before commit returns FAILED with an alert and writes neither. A valid rotate returns ROTATED and updates only the epoch.

For each version, record the return code, ledger, epoch, committed IDs and alerts for E1–E7. Retry E7 with the same r6 and without the injected failure.

Send one page to a change reviewer naming the input that changed, the output differences and the limits of the local model.

Trace each version separately, using the state from the previous row.

Check permissions, failure without a write and retry behavior separately.

Submit both traces and the handoff before opening the reference.

Use paper or local memory only. No network, real funds or keys.

The fictional tags do not authenticate anyone. The model does not implement persistence or distributed consensus.

Source: FermatMind|Fictional exercise|2026-11-10|Editorial design

Work and evidence preparation

Permission table

List three roles and their permitted actions.

Distinguish exercise rules from real authority.

Two traces

Show E1–E7 and the E7 retry.

Complete them before viewing the reference.

One-page handoff

Record the one change, output differences and limits.

Name the next reviewer.

Reproduction notes

Provide a paper trace or in-memory function.

No mainnet or real keys.

Source: FermatMind|Fictional exercise|2026-11-10|Editorial design

Recruitment, probation, and authorization boundaries

StagePossible assessmentObservational evidenceScope of use
Before applyingVerify the job duties, institutional nature, production and key permissions, and the code review process, and prepare work from a self-built environment.A work statement noting purpose and version; be able to explain the difference between a protocol implementation position and back-end development or security operations positions.Do not treat coursework as proof that you can independently take charge of production systems, and do not promise responsibilities beyond your authorization scope.
During the interviewScenario question: how to handle key rotation or a privilege overreach alert, or how to decide whether to roll back when a serious defect is found.Be able to first give a threat judgment and a least privilege approach, and then discuss release and rollback plans; be able to state your own uncertainty clearly.Do not promise unverifiable permissions, credentials, or achievements in the interview.
ProbationComplete design and implementation under review, and accept item-by-item checking of code, dependencies, and configuration.Code passes tests and static checks, permissions are minimized, and changes and rollbacks are recorded.Do not independently operate production environments or keys beyond the authorized scope, and do not change an approved release plan without authorization.
First 90 days on the jobCheck to plan whether production permissions, review arrangements, and training are in place, and assess code quality and ways of collaborating.Able to independently complete routine tasks and proactively seek help or escalate when uncertain.Authorization and responsibility must be confirmed in writing; verbal assurances are not a substitute.

BC-83 seven-day trial

  1. 01

    Roles and state

    Read the roles and initial state rules.

  2. 02

    Original events

    List the original events and check order.

  3. 03

    Original trace

    Trace the original one event at a time.

  4. 04

    One change

    Restart from the initial state and change only E6.

  5. 05

    Variant and retry

    Trace the variant and both E7 retries.

  6. 06

    Submit first

    Submit both traces and a one-page reviewer handoff. Leave the reference closed.

  7. 07

    Open the reference

    Open “BC-83 reference (open after submitting)” and check permissions, state, alerts and limits.

Source: FermatMind|Fictional exercise|2026-11-10|Editorial design

Judgment questions after seven days

  • Continue: you can complete all outputs within seven days and are willing to accept item-by-item review of the design and code.
  • Pause: you can complete the implementation but find it hard to accept review corrections to the design and permissions, or you are unwilling to invest time in testing and records.
  • Change direction: you enjoy writing code or tuning performance more than bearing security and release responsibility; compare back-end development or platform engineering directions.
  • Verify authorization: if the target position involves the production environment, keys, or external services, first verify institutional permissions and filing and security assessment requirements.
  • Fill in the evidence: organize the seven-day outputs into reviewable engineering work for course applications or job interviews.
  • Cost assessment: include tuition, training time, and possible regional differences in the written plan.
  • Next step: based on the verification results, decide whether to first build up education, first build up reviewed development experience, or first enter an adjacent position to accumulate engineering experience.

Qualification choices

Qualification and statusWho it mainly suitsRealistic role in job seekingWhether it is a universal entry thresholdExamination, regulatory, and ethics conditionsLevel of investmentImportant limitations
Computer-related bachelor's degree (United States)People planning to enter U.S. engineering positions38% of respondents choose a bachelor's degree; this is a group description and does not prove it is a common requirement at all employers38% of respondents choose a bachelor's degree; it is not a uniform threshold for all employers.Verify the school's actual courses, degree recognition, and position requirements; including programming, algorithms, operating systems, and networking fundamentals is suggested.Specific program length, tuition, and recognition conditions follow the school; individual total cost was not verified this roundThe degree itself is not the same as institutional authorization or production environment permissions.
Master's or higher degree (computer science, cryptography, or information security direction)People who wish to work in protocol, cryptography, or security researchIt can serve as evidence of research ability; whether a higher degree is required follows the specific position.Whether a higher degree is required should be verified by the target position and is not a uniform conclusion for all entry positionsRelevant coursework and research experience must be completed.Specific program length, research time, and tuition follow the program; individual total cost was not obtainedThe degree does not replace institutional authorization, compliance approval, or release permissions.
Vendor or industry technology certifications (cloud, containers, security, and others)People who want to demonstrate a specific toolchain abilityEditorial suggestion: verify whether the target employer recognizes the specific certificate; the appearance of a Hot tool does not prove a certificate's recruitment valueIt is not a universal legal threshold.The specific issuing body's examinations or programs and eligibility conditions must be verified separately; uniform conditions were not verifiedTraining and assessment costs vary by pathway.Tool certification is not the same as distributed systems and cryptographic protocol ability and does not constitute release or key permissions.
Code and key access authorization (internal to the institution)All personnel who come into contact with the production environment or keysDetermines whether production systems and keys may be accessed and the scope of access.Verify by the actual institution and system access scope; this is not a survey of the proportion at most institutionsVerify permissions, training, and signing by the actual internal rules, and do not claim a uniform processTraining and approval time.Authorization does not create the power to disclose externally or to replace compliance judgment.
Mainland China public blockchain information service obligationsEntities, nodes, and technical support organizations that provide the relevant information services to the publicFulfilling the service management responsibilities legally applicable to them, not an individual engineer's ability certificate.A service obligation, not a universal individual entry license.Filing within ten working days from the start of service; new products, applications, and functions must be reported for security assessment to procedure.Time for materials, assessment, and ongoing management.Whether internal ledger development applies must be verified under the service definition in Article two; filing does not prove technical security.
Network and data security compliance requirements (mainland China)Systems that process user data and provide services to othersDetermines whether data may be collected, used, and provided externally.This is a statutory requirement: providing blockchain information services to the public requires implementing information content security management responsibilities and real identity information authentication.The applicable conditions must be verified under the Provisions on the Administration of Blockchain Information Services and related laws and regulations.Compliance and corrective action time.Compliance materials are not an ability evaluation and do not replace engineering and security responsibility.
EC-Council CBP (a related U.S. third-party certification)People who want to build blockchain technology knowledge and first verify the current registration conditionsProof of relevant knowledge, not a verified hiring benefitNot a universal occupational license or a uniform threshold for all employersThe O*NET related directory lists 1 item, EC-Council Certified Blockchain Professional (CBP), which requires an examination, and the directory Q and A states recertification through CEUs every 3 years; it is not an entry license for all engineers. The vendor's current page presents CBP together with BDC, BFC, and BBLC, and BDC recommends object-oriented, asynchronous JavaScript, and front-end and back-end development foundations; this cannot be used to determine the CBP examination branch. CBP's specific eligibility, examination fee, total training cost, recertification hours and fees, and current registration availability remain insufficient evidence, and other certificates with the same abbreviation are not conflated.The O*NET related directory lists 1 item, EC-Council Certified Blockchain Professional (CBP), which requires an examination, and the directory Q and A states recertification through CEUs every 3 years; it is not an entry license for all engineers. The vendor's current page presents CBP together with BDC, BFC, and BBLC, and BDC recommends object-oriented, asynchronous JavaScript, and front-end and back-end development foundations; this cannot be used to determine the CBP examination branch. CBP's specific eligibility, examination fee, total training cost, recertification hours and fees, and current registration availability remain insufficient evidence, and other certificates with the same abbreviation are not conflated.The 3-year CEU is directory information; specific eligibility, fees, and recertification hours were still not verified and are not conflated with C4 or BDC.

Qualification and exercise boundaries

Two mainland blockchain development notices

Protocol and infrastructure direction

01

Back-end or infrastructure entry position

Typical scope:Complete module implementation, testing, and deployment preparation under review.

Readiness evidence:Reviewed module implementation and testing records.

Credential boundary:Complete coursework and training in computer science or a related field.

Next moves:Editorial pathway: specific institutional division of labor and authorization and requirements must be verified separately; do not independently take charge of production release, and each item must be reviewed.

02

Distributed systems or infrastructure engineering position

Typical scope:Take on the design, implementation, and maintenance of routine services or nodes; complex protocols require review.

Readiness evidence:A design document including the permission model and rollback plan.

Credential boundary:Editorial pathway: specific institutional division of labor and authorization and requirements must be verified separately; obtain the relevant degree or complete equivalent training.

Next moves:Deploy within the institutional authorization scope and do not operate keys beyond it.

03

Protocol or infrastructure lead

Typical scope:Lead protocol and permission model design, and take responsibility for system security and availability conclusions.

Readiness evidence:Complete protocol design, testing, and release records.

Credential boundary:Possess institutional authorization to independently take on protocol and security design.

Next moves:Editorial pathway: specific institutional division of labor and authorization and requirements must be verified separately; bear responsibility within the authorized scope and retain review and release records.

04

Engineering team lead

Typical scope:Review others' designs and code, establish standards, and mentor junior personnel.

Readiness evidence:Review records and standards improvement evidence.

Credential boundary:Editorial pathway: specific institutional division of labor and authorization and requirements must be verified separately; possess review and development capability and institutional authorization.

Next moves:Be responsible for the team's development and change standards.

Smart contracts and industry applications direction

01

Contract development or application development entry position

Typical scope:Implement and test contracts and business logic under mentoring.

Readiness evidence:Runnable, testable contract modules.

Credential boundary:Programming and data structure fundamentals.

Next moves:Editorial pathway: specific institutional division of labor and authorization and requirements must be verified separately; do not bear independent security conclusion responsibility.

02

Smart contract or application engineering position

Typical scope:Take on the implementation, testing, and deployment preparation of routine contracts and applications.

Readiness evidence:An assessment record including threat modeling and limitation statements.

Credential boundary:A degree in a related field or equivalent training.

Next moves:Editorial pathway: specific institutional division of labor and authorization and requirements must be verified separately; implement and test within the plan authorization scope, and external conclusions require review.

03

Contract or application technical lead

Typical scope:Lead contract architecture and permission design, and be responsible for security conclusions and release.

Readiness evidence:Complete design, review, and release records.

Credential boundary:Possess institutional authorization and security review responsibility.

Next moves:Be responsible for contract security and change boundaries.

04

Technical lead or architect

Typical scope:Establish contract and security review standards, review others' work, and develop personnel.

Readiness evidence:Review and training records.

Credential boundary:Editorial pathway: specific institutional division of labor and authorization and requirements must be verified separately; possess review and development qualifications.

Next moves:Be responsible for the team's security and review standards.

Platform security and compliance direction

01

Security operations support position

Typical scope:Take part in security monitoring, log analysis, and vulnerability tracking.

Readiness evidence:Monitoring and handling record templates.

Credential boundary:Security and networking fundamentals.

Next moves:Do not treat a monitoring alert as a resolved conclusion.

02

Security engineering or compliance engineering position

Typical scope:Take on security assessment, permission review, and change review.

Readiness evidence:A security assessment report including scope and limitations.

Credential boundary:Security training and operations experience.

Next moves:Work involving production and user data requires verifying compliance requirements and access authorization.

03

Security or compliance technical lead

Typical scope:Lead security and compliance plans, and be responsible for release and corrective action conclusions.

Readiness evidence:Complete security assessment and corrective action records.

Credential boundary:Possess project authorization and release review responsibility.

Next moves:Be responsible for security conclusions and compliance boundaries.

04

Security governance lead

Typical scope:Establish platform security and compliance governance standards and review cross-team projects.

Readiness evidence:Governance standards and review records.

Credential boundary:Possess cross-disciplinary review capability.

Next moves:Be responsible for the platform's security and compliance governance.

Capability ladder: what demonstrates readiness?

  1. 01

    Entry point: able to complete implementation and testing under review

    Able to implement and test modules to design specifications under review, correctly record versions and configurations, and identify situations requiring escalation.

  2. 02

    Advanced: able to independently take on routine design and release

    Able to independently complete the design, implementation, testing, and deployment of routine services or contracts, and proactively request review when permissions, exceptions, or dependency conflicts arise.

  3. 03

    Mature: able to bear responsibility for design and security conclusions

    Able to lead protocol and permission model design, take responsibility for system security and availability conclusions, and explain technical trade-offs in cross-team reviews.

  4. 04

    Responsibility: technical oversight and team development

    Able to review others' designs and code, establish team development and change standards, and train junior engineering personnel.

Career prospects and moving to related occupations

What are the prospects for blockchain engineers? Which related occupations can I move into?

BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

Three sources, three different measures

BLS 2025—2035 occupational projections (SOC15-1299 parent category)

2025

United States · parent_occupation_proxy

471,200 people (parent category)

Employment size

It is the parent category employment base for Computer Occupations, All Other (SOC 15-1299) and includes the sub-occupations within that group.

Does not establish:This describes a parent category statistical classification rather than the precise headcount for 15-1299.07, and cannot be used to estimate the size of the sub-occupation.

BLS 2025—2035 occupational projections (SOC15-1299 parent category)

2025—2035

United States · parent_occupation_proxy

Growth of 5.1% with 27,000 annual openings (parent category)

Growth rate and annual openings

BLS Table 1.2: the SOC 15-1299 parent category grows 5.1% with 27,000 annual openings; 495,300 in 2035 with a listed net gain of 24,200.

Does not establish:Projections under a parent category statistical classification definition cannot be used to derive the precise growth rate for 15-1299.07 and do not constitute a personal employment guarantee.

National Bureau of Statistics, 2025 average annual wages of urban unit employees

2025

Mainland China · industry_proxy

IT services non-private 248,752 and private 128,166 yuan per year; precise wages and the employment distribution for this occupation remain insufficient.

Matched industry and broad personnel category pre-tax annual average reference (not the occupation wage)

NBS2025 information transmission, software, and IT services: urban non-private 248,752 and private 128,166 yuan per year; above-scale enterprises in this industry: 242,019 overall, 275,504 for professional and technical, and 472,496 for middle management and above, yuan per year. Match only by the actual unit industry and scale and your own duties; these are pre-tax annual averages, not the blockchain occupation median, starting salary, or city monthly wage.

Does not establish:This definition mixes several job categories and cannot serve as the occupational wage or employment size of blockchain engineers.

Where can your current capabilities transfer?

These are capability relationships, not automatic promotions or credential waivers.

Information security analysts

Editorial distance fairly close, depending on existing security experience; the subject is not limited to ledgers, and this is not a hiring guarantee.

Transfers:Shared abilities: system understanding, log analysis, and risk assessment.

Build next:Editorial study-gap analysis: system security monitoring, vulnerability assessment, and compliance; verify against the target security analysis position.

View career profile

Computer systems analysts

Editorial distance moderate; specific business and organizational processes must be built up, and there is no uniform conversion period.

Transfers:Shared abilities: systems analysis, technical communication, and plan comparison.

Build next:Editorial study gap: business processes, requirements analysis, system improvement, and integration.

View career profile

Database administrators

Editorial distance depends on database administration practice; 15-1242.00 is the administrator role and is not mixed with database architects as a single listing.

Transfers:Shared abilities: data models, integrity, and access control.

Build next:Editorial study gap: database administration, performance, capacity, and scaling, and security and recovery.

View career profile

Computer programmers

Editorial distance fairly close, depending on language and application experience; consensus and key responsibility are not assumed by default.

Transfers:Shared abilities: coding, debugging, and testing; this cannot be treated as penetration testing work.

Build next:Editorial study gap: target languages and writing, modifying, and testing scripts or application code to specification.

View career profile

Information security engineers

Editorial distance depends on engineering protection experience; this is not a uniform career-change conclusion for general back-end services.

Transfers:Shared abilities: security testing, permission design, and vulnerability identification.

Build next:Editorial study gap: building and upgrading security technology, implementing controls, monitoring response, and forensics.

View career profile

Penetration testers

Editorial distance moderate; attack simulation must be built up, and security architecture governance is not treated as the whole of penetration testing work.

Transfers:Shared abilities: attack surface, system vulnerabilities, and test analysis.

Build next:Editorial study gap: simulating internal and external attacks, adversary tooling, exploitation validation, and authorized reporting.

View career profile

Computer systems engineers and architects

Editorial distance depends on architecture and integration experience; it is not merely business process analysis.

Transfers:Shared abilities: systems thinking, component evaluation, and test documentation.

Build next:Editorial study gap: solving complex application, management, and network problems, systems management and integration, and architecture adaptation.

View career profile

Computer network architects

Editorial distance depends on topology, capacity, and network implementation experience; database query optimization is not treated as the core of the target.

Transfers:Shared abilities: distributed communication and reliability analysis; specific network architecture must be built up.

Build next:Editorial study gap: design and implementation of communication networks such as LAN and WAN, capacity modeling, and hardware and network security.

View career profile

FAQ and sources

What do blockchain engineers do every day?

Blockchain engineers design, implement and test distributed ledgers, nodes, smart contracts or applications that connect on-chain and off-chain work. They document permissions, failure handling, tests and release evidence. Roles may focus on protocols, integration or platform operations.

What risks should I pay the most attention to in advance for this job?

Risks to note in advance include asset losses from improper key and credential management, exploitation of contract or protocol defects, vulnerabilities introduced by dependencies and configuration, releasing to production with insufficient testing, changes that cannot be rolled back, and unclear content and compliance boundaries for external services; control depends on least privilege, controlled environment testing, code review, and traceable change and rollback records.

How do I judge whether I am suited to being a blockchain engineer?

Try BC-83 in section 09: trace two ledger versions on paper or in local memory and write one page for a reviewer.

Source: FermatMind|Fictional exercise|2026-11-10|Editorial design
Which tasks will AI change?

Use fictional inputs to draft tests and handoffs. People review permissions, failures, state changes and release evidence. Actual keys and releases follow organizational authority.

Which steps must retain human review?

Determining requirements and the threat model, protocol and permission design, dependency and version trade-offs, exception and failure paths, deployment and rollback conditions, and the signing of external security conclusions and production releases must all be reviewed and owned by trained and authorized people.

Which qualifications must be verified to enter this occupation?

Article 2 of the blockchain information services rules covers services offered to the public in mainland China through websites, apps and similar channels. Article 11 requires covered providers to file within ten working days after starting the service. Check personal data, production access, keys and public release under the relevant rules and organizational authority.

What are the physical and environmental demands of this job?

O*NET work context shows that 69% of respondents sit continually or almost continually and 60% work indoors in a controlled environment every day; 38% use their hands to handle tools or controls continually or almost continually and 31% do repetitive motions continually or almost continually.

What are the working hours and work style like?

50% work more than 40 hours a week and 44% work 40 hours a week; 38% face time pressure every day and 40% say competition is high; 94% use email every day, teamwork is rated extremely important by 47%, and 33% say the consequences of error are extremely serious.

How should I judge career prospects and transitions?

BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

Why can't U.S. wages and mainland China figures be converted into each other?

Use these notices to compare employer requirements. They do not establish a national education threshold, occupational pay or current vacancy status.

Which languages and tools do I need to master?

The O*NET technology list groups tools into 21 categories and marks 34 Hot Technologies and 20 In-Demand skills; common areas include languages such as Go, C and C++, Java, C#, and TypeScript, and tools such as Docker, Kubernetes, AWS, Terraform, MySQL, PostgreSQL, MongoDB, Kafka, and Git; being able to write reviewable, reproducible code matters more than how many languages you know.

What should I note when handling keys and user data?

On-chain data is hard to delete and key leakage is hard to revoke: adopt least privilege and key custody, rotation rules, environment isolation, and access auditing; those providing blockchain information services to the public in mainland China must comply with the filing, real identity information authentication, security assessment, and record retention requirements of the Provisions on the Administration of Blockchain Information Services.

What are the working environment and ways of collaborating for blockchain engineers?

Mainly indoors in a controlled environment (60% work indoors in a controlled environment every day), with 69% sitting continually or almost continually; 94% use email every day and 50% make phone calls every day, teamwork is rated extremely important by 47%, and 33% say the consequences of error are extremely serious.

BC-83 reference (open after submitting)

Both versions return APPENDED, DUPLICATE, DENIED, ROTATED and STALE for E1–E5. After E5 both have [10], epoch 2, IDs {r1} and two alerts. Original E6 appends 20 and adds r5. Variant E6 is STALE, keeping [10] and {r1} and raising one extra alert. E7 fails in both, writes neither a value nor an ID, and adds one alert each. The retry succeeds: original [10,20,30], {r1,r5,r6}, three alerts; variant [10,30], {r1,r6}, four alerts. Both stay at epoch 2. Hand the differences and the untested authentication, persistence and consensus boundaries to the change reviewer.

Source: FermatMind|Fictional exercise|2026-11-10|Editorial design

Sources

Editors compiled this from the actual tasks and parent category wage projections, the 2025 China table and notes, the Chinese service clauses, and the current certificate directory; original text, matched proxies, editorial suggestions, and gaps are distinguished, and not all historical sources are treated as verified full text in this round.

Checked November 10, 2026. U.S. wages cover 2025 and projections span 2025–2035. Job notices and regulations retain their dates.

Read O*NET for tasks and the BLS parent group for wages and projections. Use the employer notices for mainland jobs and CAC’s rules for service scope.

  • O*NET-SOC 15-1299.07 detailed information (tasks and work activities)O*NET OnLine|United States|Page updated 2026; accessed 2026-09-16|Primary document
    View original source:O*NET-SOC 15-1299.07 detailed information (tasks and work activities)
    • Supports the O*NET 15-1299.07 official 18 tasks, 41 work activities, core skills, and work context fields (U.S. definition).
    • Page updated 2026; accessed 2026-09-16

    Limitations:The task list describes group work and does not mean every position performs all 18 tasks.

  • O*NET-SOC 15-1299.07 occupation summaryO*NET OnLine|United States|Page updated 2026; accessed 2026-09-16|Primary document
    View original source:O*NET-SOC 15-1299.07 occupation summary
    • Supports the occupational identity, the original official duty statement, Job Zone Four, and the respondent education composition (bachelor's 38%, some college without a degree 19%, master's 13%).
    • Page updated 2026; accessed 2026-09-16

    Limitations:A U.S. occupational classification that does not directly prove Chinese job identity or data authorization.

  • O*NET SOC15-1299 parent category industry distributionO*NET OnLine|United States|2024 distribution; accessed 2026-09-16|Primary document
    View original source:O*NET SOC15-1299 parent category industry distribution
    • Professional, scientific, and technical services 27%, government 23%, and other industries 50%; the summary lists 2024 period data.
    • 2024 distribution; accessed 2026-09-16

    Limitations:The 27%, 23%, and 50% figures are for the other computer occupations parent category, not the blockchain sub-occupation shares.

  • O*NET-SOC 15-1299.07 technology list (employer job posting technology signals)O*NET OnLine|United States|2025 U.S. job postings; accessed 2026-10-03|Primary document
    View original source:O*NET-SOC 15-1299.07 technology list (employer job posting technology signals)
    • The Hot Technologies page lists 34 software skills: Python24%, Go17%, Docker15%, and AWS15%.
    • The percentages are the share of deduplicated job postings mentioning the skill among all deduplicated postings linked to this occupation; see the separate onet-details listing for the 21 categories and 20 In-Demand labels.

    Limitations:The labels are frequency of appearance in job postings and do not represent tool adoption rates or job replacement.

  • O*NET occupation detailed information: Job Zone and educationO*NET OnLine|United States|Page updated 2026; accessed 2026-09-16|Primary document
    View original source:O*NET occupation detailed information: Job Zone and education
    • Job Zone Four, SVP7 to less than 8; respondent education is bachelor's 38%, some college education without a degree 19%, and master's 13%.
    • Page updated 2026; accessed 2026-09-16

    Limitations:The source is an occupational survey and training entry point, not specific institution recognition, a license, or a hiring guarantee.

  • U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299BLS|United States|2025–2035|Primary document
    View original source:U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299
    • BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.
    • 2025—2035 projections; accessed 2026-09-16

    Limitations:BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

  • O*NET: U.S. wages for Computer Occupations, All OtherO*NET / U.S. Bureau of Labor Statistics|United States|2025 BLS OEWS wage data displayed by O*NET OnLine|Primary document
    View original source:O*NET: U.S. wages for Computer Occupations, All Other
    • Supports the 2025 annual wage percentiles under the Computer Occupations, All Other definition: 55,940, 79,370, 116,580, 157,500, and 188,470 USD.
    • 2025 BLS OEWS wage data displayed by O*NET OnLine

    Limitations:The United States national row is cited; the NH selection and state and metropolitan area rows on the page are not used on this page; SOC15-1299 is not a separate blockchain sub-occupation statistic.

  • U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299BLS|United States|2025–2035|Primary document
    View original source:U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299
    • BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.
    • Employment is for 2024 and projections are for 2024—2034; accessed 2026-09-16

    Limitations:BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

  • National Bureau of Statistics, 2025 average annual wages of urban unit employeesNational Bureau of Statistics|Mainland China|2025; released 2026-05-15|Primary document
    View original source:National Bureau of Statistics, 2025 average annual wages of urban unit employees
    • Supports the fact that mainland China publishes average wages by industry category and broad job category but does not list this occupation separately.
    • 2025; released 2026-05-15

    Limitations:Aggregated by industry category and broad job category without listing this occupation separately; this page does not derive occupation wages from it.

  • NIST Cybersecurity Framework 2.0National Institute of Standards and Technology|United States|Framework 2.0; accessed 2026-09-16|Primary document
    View original source:NIST Cybersecurity Framework 2.0
    • Supports the general framework structure for cybersecurity risk governance (identify, protect, detect, respond, recover, and govern), used to explain the risk context.
    • Framework 2.0; accessed 2026-09-16

    Limitations:The framework provides a general structure for cybersecurity risk governance and does not constitute a compliance determination or security guarantee for any specific system.

  • Cyberspace Administration of China: Blockchain Information Services Rules, Articles 2 and 11Cyberspace Administration of China|Mainland China|2019-02-15|Primary document
    View original source:Cyberspace Administration of China: Blockchain Information Services Rules, Articles 2 and 11
    • Article 2 of the blockchain information services rules covers services offered to the public in mainland China through websites, apps and similar channels. Article 11 requires covered providers to file within ten working days after starting the service. Check personal data, production access, keys and public release under the relevant rules and organizational authority.
    • Effective 2019-02-15; accessed 2026-09-16

    Limitations:Article 2 of the blockchain information services rules covers services offered to the public in mainland China through websites, apps and similar channels. Article 11 requires covered providers to file within ten working days after starting the service. Check personal data, production access, keys and public release under the relevant rules and organizational authority.

  • ILO Working Paper 140, Generative AI and Jobs: A Refined Global Index of Occupational ExposureInternational Labour Organization|Global|Released 2025-05-20; accessed 2026-09-16|Primary document
    View original source:ILO Working Paper 140, Generative AI and Jobs: A Refined Global Index of Occupational Exposure
    • Supports the task-level measurement of generative AI exposure and the conclusion boundary of job transformation rather than wholesale replacement.
    • Released 2025-05-20; accessed 2026-09-16

    Limitations:The task exposure index does not provide job count predictions for a single occupation and is not an adoption or unemployment rate.

  • FermatMind editorial design and fictional exercisesFermatMind career content editorial team|United States|Editorial work in this round, 2026-10-03|editorial_synthesis
    View original source:FermatMind editorial design and fictional exercises
    • The fictional local ledger exercise specifies the initial state, seven events, and the exception retry answer, and tests only the permission, idempotency, and atomicity model.
    • Editorial work in this round, 2026-10-03

    Limitations:The editorial design is not measured occupational statistics, and the links point only to occupational context and cannot be passed off as external verification of the exercises.

  • NIST Artificial Intelligence Risk Management Framework 1.0National Institute of Standards and Technology|United States|Framework 1.0; accessed 2026-09-16|Primary document
    View original source:NIST Artificial Intelligence Risk Management Framework 1.0
    • Supports the general framework structure for AI risk governance (govern, map, measure, and manage), used to explain the responsibility and risk context.
    • Framework 1.0; accessed 2026-09-16

    Limitations:The framework provides a general structure for AI risk governance and does not constitute a compliance determination or security guarantee for any specific system.

  • O*NET: U.S. wages for Computer Occupations, All OtherO*NET / U.S. Bureau of Labor Statistics|United States|2025 BLS OEWS wage data displayed by O*NET OnLine|Primary document
    View original source:O*NET: U.S. wages for Computer Occupations, All Other
    • Supports the explanation that hourly and annual presentations belong to the same OEWS wage definition, and the hourly percentiles of 26.89, 38.16, 56.05, 75.72, and 90.61 USD.
    • 2025 BLS OEWS wage data displayed by O*NET OnLine

    Limitations:The United States national row is cited; the NH selection and state and metropolitan area rows on the page are not used on this page; SOC15-1299 is not a separate blockchain sub-occupation statistic.

  • O*NET-SOC 15-1299.00 Computer Occupations, All Other (parent category occupation)O*NET OnLine|United States|Accessed 2026-09-16|Primary document
    View original source:O*NET-SOC 15-1299.00 Computer Occupations, All Other (parent category occupation)
    • Supports the fact that the parent category occupation Computer Occupations, All Other (15-1299.00) is an All Other group and does not provide O*NET occupation data separately.
    • Accessed 2026-09-16

    Limitations:That page itself does not provide O*NET occupation data; its wage, employment, and projections fields apply to the parent group and do not represent a separate 15-1299.07 statistic.

  • BLS《Handbook of Methods: Occupational Employment and Wage Statistics》U.S. Bureau of Labor Statistics|United States|Method note; accessed 2026-09-16|Primary document
    View original source:BLS《Handbook of Methods: Occupational Employment and Wage Statistics》
    • Supports the OEWS statistical scope, estimation method, and definition note, used to explain the source and limitations of the parent category proxy definition.
    • Method note; accessed 2026-09-16

    Limitations:The method note describes the OEWS statistical scope and estimation definitions and does not provide specific values for a single occupation.

  • U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299BLS|United States|2025–2035|Primary document
    View original source:U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299
    • BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

    Limitations:BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

  • 2022 edition occupational classification code digital occupation listMinistry of Human Resources and Social Security|Mainland China|Published 2022-10-28|Primary document
    View original source:2022 edition occupational classification code digital occupation list
    • Blockchain engineering technicians 2-02-38-08; the old code 2-02-10-15 from the 2020 release must not be used.

    Limitations:The search results this round explicitly show the item 44 code, but opening the page directly failed; this occupational classification does not establish a national wage distribution or an individual license.

  • Notice on releasing occupational information such as blockchain engineering techniciansThree departments including the Ministry of Human Resources and Social Security; carried by the Cyberspace Administration of China website|Mainland China|Ren She Ting Fa (2020) No. 73; 2020-06-28|Primary document
    View original source:Notice on releasing occupational information such as blockchain engineering technicians
    • Architecture, underlying technology, system applications, testing, deployment, and operations and maintenance; old code 2-02-10-15.

    Limitations:The old 2020 code only explains the historical release and is not the current 2022 code.

  • O*NET 15-1211.00 Computer Systems AnalystsO*NET OnLine|United States|Occupation summary; consulted 2026-10-03 in this round|Primary document
    View original source:O*NET 15-1211.00 Computer Systems Analysts
    • Supports the official names, codes, and work subjects of the adjacent occupations.

    Limitations:Used for adjacent occupation subject and task comparison; it does not prove that a transfer is easy, wages, or individual qualifications.

  • O*NET 15-1212.00 Information Security AnalystsO*NET OnLine|United States|Occupation summary; consulted 2026-10-03 in this round|Primary document
    View original source:O*NET 15-1212.00 Information Security Analysts
    • Supports the official names, codes, and work subjects of the adjacent occupations.

    Limitations:Used for adjacent occupation subject and task comparison; it does not prove that a transfer is easy, wages, or individual qualifications.

  • O*NET 15-1242.00 Database AdministratorsO*NET OnLine|United States|Occupation summary; consulted 2026-10-03 in this round|Primary document
    View original source:O*NET 15-1242.00 Database Administrators
    • Supports the official names, codes, and work subjects of the adjacent occupations.

    Limitations:Used for adjacent occupation subject and task comparison; it does not prove that a transfer is easy, wages, or individual qualifications.

  • O*NET 15-1251.00 Computer ProgrammersO*NET OnLine|United States|Occupation summary; consulted 2026-10-03 in this round|Primary document
    View original source:O*NET 15-1251.00 Computer Programmers
    • Supports the official names, codes, and work subjects of the adjacent occupations.

    Limitations:Used for adjacent occupation subject and task comparison; it does not prove that a transfer is easy, wages, or individual qualifications.

  • O*NET 15-1299.04 Penetration TestersO*NET OnLine|United States|Occupation summary; consulted 2026-10-03 in this round|Primary document
    View original source:O*NET 15-1299.04 Penetration Testers
    • Supports the official names, codes, and work subjects of the adjacent occupations.

    Limitations:Used for adjacent occupation subject and task comparison; it does not prove that a transfer is easy, wages, or individual qualifications.

  • O*NET 15-1241.00 Computer Network ArchitectsO*NET OnLine|United States|Occupation summary; consulted 2026-10-03 in this round|Primary document
    View original source:O*NET 15-1241.00 Computer Network Architects
    • Supports the official names, codes, and work subjects of the adjacent occupations.

    Limitations:Used for adjacent occupation subject and task comparison; it does not prove that a transfer is easy, wages, or individual qualifications.

  • Full tasks, skills, context, and educationO*NET OnLine|United States|Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25|Primary document
    View original source:Full tasks, skills, context, and education
    • Full tasks, skills, context, and education
    • Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25

    Limitations:Group fields are not an individual threshold; the parent category is not a blockchain sub-occupation value; the training directory is not the same as real-time enrollment, and certification is not the same as an occupational license.

  • 2025 other computer occupations parent category industry distributionO*NET OnLine|United States|Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25|Primary document
    View original source:2025 other computer occupations parent category industry distribution
    • 2025 other computer occupations parent category industry distribution
    • Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25

    Limitations:Group fields are not an individual threshold; the parent category is not a blockchain sub-occupation value; the training directory is not the same as real-time enrollment, and certification is not the same as an occupational license.

  • U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299BLS|United States|2025–2035|Primary document
    View original source:U.S. BLS Table 1.2: Computer Occupations, All Other, 15-1299
    • BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.
    • Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25

    Limitations:BLS projects the U.S. parent group Computer Occupations, All Other (15-1299) from about 471,200 jobs in 2025 to 495,300 in 2035. The published net gain is about 24,200 (5.1%), with about 27,000 annual openings from growth and replacement. The baseline includes 4.9% self-employment. The data do not isolate blockchain engineers.

  • O*NET: U.S. wages for Computer Occupations, All OtherO*NET OnLine|United States|Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25|Primary document
    View original source:O*NET: U.S. wages for Computer Occupations, All Other
    • 2025 other computer occupations parent category national wage percentiles
    • Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25

    Limitations:Group fields are not an individual threshold; the parent category is not a blockchain sub-occupation value; the training directory is not the same as real-time enrollment, and certification is not the same as an occupational license.

  • Related training directoryO*NET OnLine|United States|Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25|Primary document
    View original source:Related training directory
    • Related training directory
    • Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25

    Limitations:Group fields are not an individual threshold; the parent category is not a blockchain sub-occupation value; the training directory is not the same as real-time enrollment, and certification is not the same as an occupational license.

  • Third-party certification directoryO*NET OnLine|United States|Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25|Primary document
    View original source:Third-party certification directory
    • Third-party certification directory
    • Updated 2026; industry and wages 2025; projections 2025—2035; training directory 2025—26 and degrees awarded 2024—25

    Limitations:Group fields are not an individual threshold; the parent category is not a blockchain sub-occupation value; the training directory is not the same as real-time enrollment, and certification is not the same as an occupational license.

  • 2025 urban unit wages and notesNational Bureau of Statistics|Mainland China|2025; released 2026-05-15|Primary document
    View original source:2025 urban unit wages and notes
    • 2025 urban unit wages and notes
    • 2025; released 2026-05-15

    Limitations:Match by the actual employer industry, unit coverage, and your own duties; pre-tax annual averages are not the occupation median, starting salary, or city monthly wage.

  • CBP certification details and the three-year CEU recertification directoryO*NET / CareerOneStop|United States|Read 2026-10-09|Primary document
    View original source:CBP certification details and the three-year CEU recertification directory
    • CBP certification details and the three-year CEU recertification directory
    • Read 2026-10-09

    Limitations:EC-Council CBP is a third-party certification, not an occupational license; it is not conflated with C4 or BDC, and precise registration eligibility, fees, and CEU hours were not verified.

  • EC-Council current blockchain program pageEC-Council|United States|Read 2026-10-09|Primary document
    View original source:EC-Council current blockchain program page
    • EC-Council current blockchain program page
    • Read 2026-10-09

    Limitations:The current page contains both CBP text and BDC, BFC, and BBLC, and the BDC prerequisite or three-month study suggestion is not treated as a uniform CBP registration condition; promotional employment claims are not independent projections.

  • Item 86 occupation code in the 2026 Fuzhou skills training public noticeFuzhou Human Resources and Social Security Bureau|Mainland China|Public notice of 2026-06-03|Primary document
    View original source:Item 86 occupation code in the 2026 Fuzhou skills training public notice
    • Item 86 occupation code in the 2026 Fuzhou skills training public notice
    • Public notice of 2026-06-03

    Limitations:Verifiable blockchain engineering technicians 2-02-38-08; the local public notice is not the full 2022 code, a national certificate license, or a real-time vacancy.

  • Blockchain task analysis and self-check suggestionsFermatMind career content editorial team|United States|2026-10-09|editorial_synthesis
    View original source:Blockchain task analysis and self-check suggestions
    • Blockchain task analysis and self-check suggestions
    • 2026-10-09

    Limitations:The links serve as occupational background; specific tool assistance, control steps, advancement, transition distance, and personal observations are editorial analyses, not causal findings or uniform employer systems.

  • Actual duty definition for information security analystsO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for information security analysts
    • Actual duty definition for information security analysts
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Actual duty definition for computer systems analystsO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for computer systems analysts
    • Actual duty definition for computer systems analysts
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Actual duty definition for database administratorsO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for database administrators
    • Actual duty definition for database administrators
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Actual duty definition for computer programmersO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for computer programmers
    • Actual duty definition for computer programmers
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Actual duty definition for information security engineersO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for information security engineers
    • Actual duty definition for information security engineers
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Actual duty definition for penetration testersO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for penetration testers
    • Actual duty definition for penetration testers
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Actual duty definition for computer systems engineers and architectsO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for computer systems engineers and architects
    • Actual duty definition for computer systems engineers and architects
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Actual duty definition for computer network architectsO*NET|United States|Updated 2026|Primary document
    View original source:Actual duty definition for computer network architects
    • Actual duty definition for computer network architects
    • Updated 2026

    Limitations:The duties support the corresponding target; transition distance and study suggestions are editorial analyses, with no uniform hiring guarantee.

  • Three representative core tasks of this occupationFermatMind / 费马测试|2026-10-18|Editorial model estimation method
    View original source:Three representative core tasks of this occupation
    • Model impact index for three equally weighted representative core tasks; not a measured share of working time or a job-loss probability. floor((50+75+75)/3+0.5)=67; fermatmind-ai-impact-v1; 2026-10-18.
    • Anchors: 0 negligible; 25 preparation or record assistance; 50 substantial assistance; 75 most information output can be formed by AI with review; 100 almost all of the selected task can be done by AI and independently verified.
    • Protocol and design | Design and validate cryptographic protocols, and design blockchain design patterns that make transactions secure, transparent, and tamper-resistant | Reviewable protocol and design pattern descriptions. — 50/100; weight=1/3; blockchain-engineers.profile.responsibilities-block.1[1]
    • Implementation and data model | Write maintainable code using object-oriented principles, update client and server applications, and design and implement data repositories and logging | Code and data models that others can reproduce and review. — 75/100; weight=1/3; blockchain-engineers.profile.responsibilities-block.1[2]
    • Testing and risk assessment | Test the security and performance of the infrastructure, run peer-to-peer network tests, and assess threats such as untested code and unprotected keys | A testing and assessment report including coverage and limitation statements. — 75/100; weight=1/3; blockchain-engineers.profile.responsibilities-block.1[4]

    Limitations:Editorial ratings use the existing occupational responsibilities and AI task analysis on this page. They are not adoption rates, measured effects, job-disappearance or personal-unemployment probabilities, or official scores from Stanford or another external institution. No measured time weights or future robot deployment are assumed.

  • Beihang University: blockchain engineer vacancy noticeBeihang University|Mainland China|2026-10-16|Primary document
    View original source:Beihang University: blockchain engineer vacancy notice
    • Beihang University’s October 16, 2026 notice lists one consortium blockchain engineer to design, develop and integrate ChainMaker systems. It asks for a related master’s degree or higher and at least three years in backend or blockchain development. It lists a labor dispatch contract, negotiable pay and a November 27, 2026 application deadline.

    Limitations:Beihang University’s October 16, 2026 notice lists one consortium blockchain engineer to design, develop and integrate ChainMaker systems. It asks for a related master’s degree or higher and at least three years in backend or blockchain development. It lists a labor dispatch contract, negotiable pay and a November 27, 2026 application deadline.

  • Huawei Cloud Blockchain Lab: experienced hiringHuawei Cloud|Mainland China|observed 2026-11-10|Primary document
    View original source:Huawei Cloud Blockchain Lab: experienced hiring
    • Huawei Cloud Blockchain Lab’s experienced-hire page lists a developer role for Shenzhen, Beijing and Xi’an with at least one year of experience. The role covers blockchain core components, decentralized identity, privacy computing and cross-chain modules, and asks for Go. The row gives neither pay nor headcount.

    Limitations:Huawei Cloud Blockchain Lab’s experienced-hire page lists a developer role for Shenzhen, Beijing and Xi’an with at least one year of experience. The role covers blockchain core components, decentralized identity, privacy computing and cross-chain modules, and asks for Go. The row gives neither pay nor headcount.

  • FermatMind BC-83: Ledger state and review handoffFermatMind|Fictional exercise|2026-11-10|Editorial design
    • Try BC-83 in section 09: trace two ledger versions on paper or in local memory and write one page for a reviewer.

    Limitations:Try BC-83 in section 09: trace two ledger versions on paper or in local memory and write one page for a reviewer.

  • O*NET® 31.0 Core Task StatementsU.S. Department of Labor, Employment and Training Administration|United States|O*NET 31.0|Primary document
    View original source:O*NET® 31.0 Core Task Statements

    Limitations:Verbatim Core Task Statements excerpted from the O*NET® 31.0 Database, used under CC BY 4.0. U.S. occupational scope.

  • O*NET® database license · CC BY 4.0U.S. Department of Labor, Employment and Training Administration|United States|O*NET 31.0|Primary document
    View original source:O*NET® database license · CC BY 4.0

    Limitations:Verbatim Core Task Statements excerpted from the O*NET® 31.0 Database, used under CC BY 4.0. U.S. occupational scope.

Usage notes: this page distinguishes the precise occupation definition from the parent category proxy definition; mainland China industry average wages serve only as a comparison; gaps are marked insufficient evidence and are not filled with speculative values.

Blockchain engineers | FermatMind