Loading page content
Preparing content…
SOC 15-1211
Computer systems analysts analyze business and technical problems, turn requirements into implementable system solutions, and take responsibility for solution evidence, change records and deployment results.
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.
One-sentence summary: this work centers on translating business problems into system solutions that can be implemented, verified and maintained, and suits people willing to clarify requirements, coordinate stakeholders and take responsibility for delivery results.
Note: if your goal is to write code, develop security policies or design network architecture over the long term, this occupation is a useful adjacent direction but a different role; those directions require additional coding, security or architecture abilities and corresponding qualifications.
Boundary: the exercises and judgments on this page are only for self-checking. They do not constitute hiring criteria, qualification recognition or authorization to operate or deploy real systems; work involving real systems and data must follow your organization's rules.
Computer systems analysts analyze business and technical problems and design and integrate system solutions. They produce requirements and design documents and testing and change records, and are responsible for the basis of solutions and deployment results.
The official occupation analyzes data-processing problems in science, engineering, business and other areas, and develops or implements complex applications, systems management or network solutions. The editorial grouping has three work areas: requirements/solutions; integration/testing; support/improvement. Work may involve programming, code correction and cost-benefit analysis; verify actual responsibilities and authority with the organization.
Career direction comparison
The table below compares computer systems analysts with five adjacent occupations using the same dimensions: each direction first describes core work and outputs, then key differences from this occupation, and finally when choosing that direction may be more suitable.
| Career direction | Core work and output | Key differences | Best-fit choice |
|---|---|---|---|
| Computer Systems Engineers and Architects | Design and integrate computer systems and overall architecture, producing system architecture, integration plans and technology selection recommendations. | Engineers and architects are responsible for overall system architecture and integration design; this occupation focuses on turning business requirements into specifications and implementation plans and usually does not bear final responsibility for architecture decisions. | If you prefer architecture decisions and technology selection, explore engineers and architects; if you prefer clarifying business requirements and implementing solutions, explore this occupation. |
AI impact on this career
Materials, cases, code and logs are candidates for assistance to be tested; occupational reliability, adoption and net efficiency have not been established. Do not equate tool capabilities with actual effects. AI Impact Score 67% is an editorial estimate. 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.The three tasks, ratings and sources are listed in the FermatMind method source record on this page.
FermatMind AI Impact Score estimation method v1
FermatMind / 费马测试 · 2026-10-18
Chinese mainland salary reference
GT4754-2017 categories 651 software development (PDF70/printed page 64), 6531 systems integration/6540 operations and maintenance/6560 IT consulting (PDF71/printed page 65) match context by a unit's main business; they do not cover every internal analyst role in other industries or establish equivalence between Chinese and U.S. occupations.
GT4754-2017 categories 651 software development (PDF70/printed page 64), 6531 systems integration/6540 operations and maintenance/6560 IT consulting (PDF71/printed page 65) match context by a unit's main business; they do not cover every internal analyst role in other industries or establish equivalence between Chinese and U.S. occupations.
248,752 yuan per year, non-private IT industry context, not systems analyst median or starting pay.
U.S. Wage Reference
The 2025 national annual wage percentiles are 67,340/82,860/105,850/134,110/167,710 dollars; hourly values are 32.37/39.84/50.89/64.48/80.63. BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change; overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
| Wage Statistical Position | Annual Wage Reference | Conversion Boundaries | How to Understand This Position |
|---|---|---|---|
| 10th Percentile | 67,340 dollars per year (10th percentile) | No Conversion Into Individual Monthly Income | The 10th percentile means 10% of workers have annual wages no higher than that value; it is not an entry-level or minimum wage. |
| 50th Percentile |
Occupational Suitability Guide
Focus more on the ability to clarify requirements, confirm with business and technical stakeholders, document solutions and changes in reviewable records, and take responsibility for deployment results. Personality and interest assessments serve only as references for self-observation, not entry requirements.
You May Be More Suited： Willing to map workflows and data, able to write requirements as verifiable specifications, accustomed to recording changes and tests, and willing to confirm uncertainty with business stakeholders before proceeding.
These Situations Require Caution： Unwilling to document and confirm requirements, accustomed to changing systems without review, unable to accept concurrent projects and frequent communication, or entirely unwilling to take responsibility for deployment results.
Try an Entry Exercise： Complete a requirements-to-deployment cycle in a fictional scenario: write requirements and acceptance criteria, describe interfaces and data, and list test cases and deployment and rollback steps; then assess whether you are willing to repeat that process over the long term.
Work Pressure, Risks and Occupational Boundaries
Editorial advice is to check requirements/definitions, interfaces/data, testing and recovery, with responsibilities determined by the actual organization; no ranking of most needed or most common is made.
Tasks/context: O*NET15-1211; wages and current overall employment: BLS. Specific employer policies have not been obtained; data, approval, deployment and other measures are editorial suggestions.
Typical scenario：Treating a single complaint in an interview directly as a requirement, without checking current workflows and data, causes deployed solutions to diverge from business expectations.
Roles most affected：Analyst and Business Stakeholders
Possible consequence：High rework costs, damaged business trust and possible delays to other projects.
Entry, Qualifications and Career Development
Requirements/implementation/data exercises are editorial preparation routes, not prevalence proportions or uniform promotion paths. O*NET's current education information for new hires only lists some positions requiring an associate degree, a bachelor's degree or some college without a degree; it provides no verifiable proportions and is not the educational composition of current workers. Zone4/SVP7 to below 8 is a preparation level, not a fixed duration for an individual; BLS lists a bachelor's degree/no related experience/no OJT as typical, not requirements for China or every employer. 146 U.S. certifications and 5 apprenticeship names are not places or mandatory requirements in China.
Occupational Outlook and Transitions to Related Occupations
BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change; overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded. For 2025, urban non-private units in information transmission/software/IT services average 248,752 yuan per year, and private units 128,166 yuan per year. Read these separately as before-tax industry context, not a wage range, median, starting pay or personal quote for systems analysts.
United States · United States; O*NET-SOC 15-1211.00 Precise Occupational Scope
Growth 7.9%; published +42,900; average annual openings 32,900 (2025–2035)
Employment Growth Rate and Average Annual Openings
Clarify business requirements and workflows, write requirements and design documents, confirm interfaces and data definitions with development and operations teams, participate in testing and deployment, and address post-deployment faults and improvements.
This occupation is responsible for requirements, design and integration, with coding only one means of implementation; programmers are responsible for code correctness and maintainability. They collaborate closely but have different responsibilities and deliverables.
Choose a real task from this page for a small practice project or a conversation with someone in the field. Use the planning guides to set a date, an output and feedback questions before deciding whether to continue.
Before starting, confirm that you can organize vague business requests into verifiable fields, workflows and acceptance criteria, and document them.
Trial method: write a one-page requirements brief for a fictional business scenario, such as redesigning an expense reimbursement workflow, including the current workflow, proposed changes, fields and rules, acceptance criteria and two risks.
Requirements briefs and system design documents
Integration implementation records and testing and acceptance results
This page compares computer systems analysts with adjacent occupations across six dimensions: core purpose, main objects and evidence, core process, main outputs, accountable parties, and entry requirements and licensing. Tasks and tools may overlap, but system design authority, architecture decisions, operations and maintenance responsibilities, and resource allocation authority do not transfer merely because tasks are similar.
| Dimension | Primary track | Comparison track |
|---|---|---|
| Core Purpose | Analyze business and technical problems and design, integrate and improve systems so existing systems better support business objectives. | Core purposes of adjacent occupations: computer and information systems managers coordinate departmental resources and delivery; computer systems engineers and architects design systems and architecture; network and computer systems administrators ensure operation; computer network architects design network solutions. |
| Main Objects and Evidence | Business workflows and data, existing systems and interfaces, users and job tasks; evidence consists of interview and observation records, workflow and data documents, system logs and requirements confirmation. | Objects and evidence for adjacent occupations: departmental resources and budgets (managers), system and architecture specifications (systems engineers and architects), and network and server operation (administrators and network architects). |
| Core Process | Interviews and observation → organize workflows and data → define objectives and specifications → design and integrate → test and deploy → train and improve. | Management, architecture, operations and analysis tasks may overlap; verify workflows with the actual organization rather than impose a fixed sequence for all roles based on titles. |
| Main Outputs | Requirements briefs, system design and interface documents, testing and change records, user instructions and training materials, and deployment and rollback records. | Outputs of adjacent occupations: departmental plans and budgets, system and architecture design documents, and operational monitoring and incident resolution records. |
| Accountable Parties | Analysts and project leads are responsible for the completeness of requirements confirmation, design evidence, and testing and change records. Data permissions and deployment approvals must follow the organization's rules; this page does not replace employer policies or legal advice. | Accountable parties in adjacent occupations: managers are responsible for resources and delivery; systems engineers and architects for system design; administrators for operational availability. |
| Entry Requirements and Licensing | O*NET's current education information for new hires only lists some positions requiring an associate degree, a bachelor's degree or some college without a degree; it provides no verifiable proportions and is not the educational composition of current workers. Zone4/SVP7 to below 8 is a preparation level, not a fixed duration for an individual; BLS lists a bachelor's degree/no related experience/no OJT as typical, not requirements for China or every employer. The current 146 U.S. certification candidates and 5 registered apprenticeship names are not mandatory in China or actual available places. | This page does not provide preparation levels or qualification requirements for adjacent occupations; check each occupation's official page and the target employer's announcements for the relevant year individually. |
| Limits of Conclusions | For these nine modules, read U.S. 2025 employee wages and 2025–2035 overall projections separately from China's 2025 industry context and precise evidence gaps. | Similar tasks do not make roles interchangeable: responsibility for system design authority, architecture decisions, operations and maintenance, or resource allocation determines the scope of authorization and accountability. |
Interview clients and users and observe work tasks; identify who handles which data at each stage to produce a current-state description and list of problems.
Define system scope, inputs and outputs, processing rules and acceptance criteria from the current situation and business objectives, and assess candidate solutions' compatibility with existing systems.
Coordinate software and hardware installation and configure interfaces and data flows according to the design so systems within the organization can exchange information.
Write test cases covering normal and exceptional paths and record environments and results; after deployment, monitor performance and error logs to locate and correct problems.
Propose improvements based on operating metrics and user feedback, assess the scope of impact and schedule changes, adjusting workflows and training materials when necessary.
Write user instructions and train users; maintain design, testing and change documents so others can take over.
The six checks are editorial suggestions; the 23 tasks comprise 18 Core/4 Supplemental/1 New (writing code, importance NA), not the old 18+5 supplemental grouping. The first five are 81/76/75/74/70; programming is 68 Core and code correction 65 Supplemental, not frequency or shares of all positions.
Check one: are business objectives and the current situation clearly documented?
Check two: are definitions and data consistent?
Check three: are specifications and acceptance criteria verifiable?
| Network and Computer Systems Administrators | Install, configure and maintain networks, servers and operating systems, producing available systems and operational monitoring and incident resolution records. | Administrators are responsible for system availability and daily maintenance; this occupation is responsible for requirements, design and deployment results and usually does not provide ongoing operational coverage. | If you prefer responsibility for continuous system operation and incident response, explore administrators; if you prefer requirements and solution design, explore this occupation. |
|---|
| Computer and Information Systems Managers | Coordinate IT department personnel, budgets, projects and service levels, producing departmental plans, budgets and delivery results. | Managers are responsible for resources and delivery; this occupation is responsible for the basis of solutions and deployment results and does not hold departmental budget or personnel decision-making authority. | If you prefer coordinating resources and teams and taking responsibility for delivery results and budgets, explore management; if you prefer working closely with specific requirements and solutions, explore this occupation. |
|---|
| Computer Network Architects | Design and implement LAN, WAN and cloud network solutions, producing network designs and capacity and implementation documentation. | Network architects decide how networks are designed and expanded; this occupation uses network capabilities when designing solutions but is not responsible for network architecture decisions. | If you prefer network design and capacity planning, explore network architecture; if you prefer translating business needs into systems, explore this occupation. |
|---|
| Computer Programmers | Write, modify and test code and scripts, producing working programs and development documentation. | Programmers are responsible for code correctness and maintainability; this occupation is responsible for requirements, design and integration, with coding only one means of implementation. | If you prefer writing code and debugging over the long term, explore programming; if you prefer defining requirements and design, explore this occupation. |
|---|
| Information Security Analysts | Plan, implement and monitor security measures, producing security policies, controls and incident reports. | Security analysts are responsible for controls and incident response; this occupation must satisfy security requirements when designing solutions but does not define security policies. | If you prefer studying attack surfaces and developing security controls, explore security; if you prefer system solutions and deployment coordination, explore this occupation. |
|---|
The six adjacent directions differ in their objects, authorization and responsibilities: tasks and tools may overlap, but system design authority, architecture decisions, operations and maintenance responsibilities, and resource allocation authority do not transfer with them. Compare actual job responsibilities individually against the six dimensions in this page's comparison table.
If you are deciding between two directions, first try a small experiment using a fictional business scenario: write a one-page requirements brief and acceptance criteria, then see whether you prefer refining requirements and solutions or working on architecture, operations and maintenance, or coding.
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.
This page uses only official task lists and source explanations to identify information-processing actions that can be assisted, such as organizing, drafting and comparing; it does not infer the order of replacement.
Technical availability does not mean employer adoption: adoption depends on data scope, approval processes, allocation of responsibility and compliance requirements. This page has not obtained adoption-rate data for this occupation.
BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change; overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
| Work area | Task | Current change | Human control point |
|---|---|---|---|
| Requirements and solution design | Confirm information-processing requirements with clients and management | Can automatically organize interview and meeting records and generate requirements drafts and field lists from templates. | Confirm business definitions and priorities, assess solution tradeoffs and take responsibility for confirmed results. |
| System design and specifications | Analyze processing requirements and design systems, inputs and outputs | Generate design documents and workflow drafts from existing templates and flag missing rules. | Assess whether the design meets business and compliance requirements and take responsibility for the basis of the design. |
| Systems integration | Coordinate software and hardware installation and connect systems within the organization | Generate integration checklists and compare interface and configuration differences. | Assess interface feasibility and impacts on current operation, and schedule implementation windows. |
| Testing and monitoring | Test, maintain and monitor programs and systems | Generate draft test cases from requirements and classify anomalous patterns in logs. | Confirm test coverage and results, assess defect severity and decide whether to proceed. |
| Incident resolution | Diagnose and fix program and system faults | Aggregate records of similar faults and suggest candidate causes and handling steps. | Reproduce problems in the environment, identify root causes and perform reversible fixes. |
| Training and documentation | Train users and maintain design and testing documentation | Organize feature descriptions into draft user manuals and training summaries. | Check that instructions match reality and confirm trainees can independently perform key operations. |
| Improvement and changes | Improve systems and workflows using operating data | Summarize operating metrics and user feedback and generate initial improvement suggestions. | Decide improvement priorities and change windows, assess scope of impact and take responsibility for deployment results. |
Read official tasks, wages and employment, potential exposure, voluntary governance and job-posting terms separately; they do not prove actual employer AI deployment or policies.
Discuss assistance to be tested and responsibility by task, rather than comparing proven AI effects.
AI primarily changesAutomatically organize interview and meeting records, generate requirements drafts and workflow descriptions from templates, and flag missing fields and rules.
Human responsibility remainsConfirm definitions and priorities with business stakeholders, assess solution tradeoffs and scope of impact, and take responsibility for confirmed results.
AI primarily changesGenerate draft test cases from requirements, compare log anomalies, and summarize integration issues.
Human responsibility remainsAssess the feasibility of interface solutions and their impacts on existing systems, and decide whether to proceed to the next stage.
AI primarily changesClassify operating logs and user feedback and generate draft improvement suggestions and documentation updates.
Human responsibility remainsDecide improvement priorities and change windows, organize user training, and take responsibility for deployment results.
Use tools for information processing and leave confirmation, approval and deployment responsibility to people: the five steps below explain the division of work across a complete process.
Organize interview records, current workflows and data sources into requirements documents, retaining original records and confirmation times.
Use tools to generate requirements drafts, field lists and initial test cases, marking all as drafts.
Confirm definitions and priorities with business stakeholders and check feasibility against workflows, data and existing systems.
Record requirements changes, test results and deployment records, retaining versions and approval information.
Business stakeholders and accountable roles confirm deployment and rollback decisions and bear responsibility for the results; tool output does not constitute approval.
Treating a single statement in an interview directly as a requirement or citing outdated documents can produce systems that do not meet business needs, with high rework costs after deployment.
Control: Return to current workflows, data and business stakeholders to confirm definitions; retain versions and confirmation records in requirements documents.
Analysis work often involves business data and personal information; unauthorized data access or importing data into unapproved tools can have compliance consequences.
Control: Access data only to the minimum necessary extent and within authorization; do not process identifiable information through unapproved channels or external services.
Missing version records for documents, scripts and automation may make review or reversion harder. Recovery also requires checking actual logs, audits, backups and approved recovery paths; do not categorically assert that rollback is impossible.
Control: Record tools and versions, change ticket numbers and execution times, and retain a means of reverting.
Inconsistent amounts, times and statistical definitions can make reports and reconciliation results contradict one another, distorting the basis for decisions.
Control: Define field meanings, units and sources at the requirements stage and validate with sample data; stop and confirm when inconsistencies arise.
Without clearly accountable roles and review records for requirements, design, testing and deployment, incidents leave no evidence to refer to.
Control: Retain review and approval records at each stage; confirm rollback conditions and responsible parties before deployment.
First learn workflow mapping and requirements writing and basic data and interface concepts, then write a one-page requirements brief and acceptance criteria for a fictional business scenario; do not treat knowing how to use a particular tool as an entry requirement.
Use tools to organize interview records and generate requirements drafts and lists of test cases, but confirm every conclusion with business stakeholders and check it against documents and operating logs.
Identify which requirements confirmations and deployment decisions must be made by business stakeholders and accountable roles. Set boundaries and data scope for assistive tools to avoid tools directly producing unconfirmed specifications.
Develop architecture design, security control or coding abilities and corresponding qualifications. Demonstrate readiness through verifiable outputs, such as architecture documentation, controls or code, rather than only years in a role.
Evidence on long-term replacement or retention of the occupation as a whole and the net effects on each task has not been obtained; no guarantees are given. BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change; overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
Source: O*NET15-1211 Tasks; BLS Table 1.2 Current 2025–2035Original source ↗
Programming 68 Core, code correction 65 Supplemental and new code writing NA all appear on the task list. Verify actual coding depth and delivery responsibilities for the position; do not use the requirements-analysis label to exclude programming.
Source: O*NET 15-1211.00 Official Task ListOriginal source ↗
Interviews, documents, test cases and logs are editorial candidates; the order of impact and reliable automation have not been established, so no earlier-or-later ranking is given.
Source: O*NET 15-1211.00 Tasks and Detailed Work ActivitiesOriginal source ↗
BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change; overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
Source: BLS Table 1.2 Current Overall Employment ProjectionsOriginal source ↗
No. Deployment involves data migration, permissions, compliance and business continuity and must be confirmed by accountable roles and business stakeholders under organizational processes. Tools can assist with checklists and rollback conditions but cannot replace approval or accountability.
Source: NIST Voluntary Framework and O*NET Tasks; Actual Organizational Policies Have Not Been ObtainedOriginal source ↗
Insufficient evidence: this round did not obtain material supporting a year in which the occupation will disappear; no timeline is given.
Source: ILO, Generative AI and Jobs; O*NET Summary Page Employment TrendsOriginal source ↗
First learn business and workflow mapping, requirements and documentation writing, data and interface fundamentals, and testing and deployment processes; tools and platforms, such as SQL, Power BI and cloud platforms, come after these foundations.
Source: O*NET 15-1211.00 Tasks and Knowledge RequirementsOriginal source ↗
Editorial advice is to check the value of drafts/comparisons in an approved test environment, retaining original records, versions and criteria, then decide according to actual responsibilities; actual deployment and efficiency evidence is still missing.
128,166 yuan per year, private IT industry context, not systems analyst median or starting pay.
Insufficient evidence: this round did not obtain precise wage distributions, medians, starting pay or advertised-pay statistics for systems analysts in China.
Not obtaining precise occupational wages does not mean officials have never published them. For 2025, urban non-private units in information transmission/software/IT services average 248,752 yuan per year, and private units 128,166 yuan per year. Read these separately as before-tax industry context, not a wage range, median, starting pay or personal quote for systems analysts.
| Educational Background | Job Direction | Notes and Checking Advice |
|---|---|---|
| Junior college diploma (computing or a related subject) | Systems support, requirements organization, implementation and configuration roles | Editorial educational preparation route; actual Chinese recruitment samples have not been obtained. Check announcements for specific conditions. |
| Bachelor's degree (computing, information systems or a related subject) | Systems analyst, business analyst, implementation and integration roles | Junior college/bachelor's routes are editorial preparation suggestions; proportions for the majority of Chinese positions have not been obtained. |
| Bachelor's degree plus business background (finance, accounting, supply chain, etc.) | Business systems analyst and industry solution roles | Verify platform/design experience and recognition of education/certifications with the employer; no promises of income or promotion. |
| Master's degree or professional certification route | Data and platform analyst, architecture or consulting roles | Editorial compilation: data, architecture and consulting directions place greater emphasis on specialist depth and project experience; certifications and training serve only as evidence of ability. |
Note: not obtaining a separately listed figure for this occupation does not mean officials have never published one. This page records only the actual scope and results of searches and does not fill gaps with industry averages or U.S. data.
Main employment settings: implementation and product teams at software companies, systems integrators, and cloud and data service providers.
Common settings: business system redesign, standardization of data definitions and projects moving workflows online.
Common settings: government system development, industry consulting and outsourced delivery projects.
Evidence on occupational AI adoption in China and wage causation has not been obtained; do not infer income from tool capabilities.
| 105,850 dollars per year (median; year 2025, month 5 wage data) |
| No Conversion Into Individual Monthly Income |
| The 50th percentile is the median, meaning half of workers are above that value and half below; it does not represent a fixed wage for a particular industry or employer type. |
| 90th Percentile | 167,710 dollars per year (90th percentile) | No Conversion Into Individual Take-Home Pay | The 90th percentile describes the upper end of the wage distribution; evidence linking this position to industry, employer size or specialization has not been obtained. Do not infer high earners' characteristics or causes from percentiles. |
|---|
Wages · 10th Percentile：67,340 dollars per year (10th percentile)；The 10th percentile annual wage published on the O*NET national wage page (year 2025, month 5 wage data). This position means 10% of workers have annual wages no higher than this value； it does not represent novice starting pay. ；O*NET National Wage Page (year 2025, month 5 wage data)
Wages · 25th Percentile：82,860 dollars per year (25th percentile)；The 25th percentile annual wage published on the O*NET national wage page. This is a statistical distribution point, not an experience level. ；O*NET National Wage Page (year 2025, month 5 wage data)
Wages · Median：105,850 dollars per year (median)；The national median annual wage published on the O*NET national wage page and BLS OOH Pay page (year 2025, month 5 wage data). This is the middle of the distribution, not an individual's starting pay or take-home income. ；BLS OOH: Computer Systems Analysts (Pay)
Wages · 75th Percentile：134,110 dollars per year (75th percentile)；The 75th percentile annual wage published on the O*NET national wage page. This is a statistical distribution point, not a promotion level. ；O*NET National Wage Page (year 2025, month 5 wage data)
Wages · 90th Percentile：167,710 dollars per year (90th percentile)；167,710 dollars per year is the 90th percentile； evidence linking higher wages to industry/employer size/specialization has not been obtained. It is not a job grade.
No. The median is the statistical middle of employee occupational wages, not starting pay for newcomers. Industry, employer size and specialization conditions require specific sources; this page has no newcomer or subgroup data and cannot assert that starting pay varies significantly.
No. Percentiles are statistical positions, and individual hours and employment terms are absent, so they cannot establish an individual's monthly or after-tax take-home income. The median hourly wage (50.89 dollars per hour) is likewise a statistical position.
From BLS year 2025, month 5 wage data displayed on the O*NET national wage page and the BLS OOH Pay page; percentiles are statistical positions, not experience or professional-title levels.
Industry and business complexity, technology stack and project type, region and employer type; this page has not obtained subgroup figures for these factors. Refer to the target employer's rules for the relevant year and official regional data.
| Industry | O*NET 2025 Industry Employment Structure | How to Understand This Value |
|---|---|---|
| Professional, Scientific and Technical Services | Professional/Scientific/Technical 33% (industry employment share) | This row is an employment share from O*NET's industry distribution, not an industry median wage; this page has not obtained wage data broken down by industry. |
| Finance and Insurance | Finance and Insurance 13% (industry employment share) | As above, this is an employment share; systems redesign and compliance projects in finance are important employment settings for this occupation. |
| Management of Companies and Enterprises | Management of Companies and Enterprises 10% (industry employment share) | As above, this is an employment share; IT departments at headquarters organizations typically handle systems integration across regions. |
| Other Industries Combined (Including Government and Information) | Other 44% (including government and health and social work) | The current industry page lists professional/scientific/technical 33%, finance and insurance 13%, management of companies and enterprises 10%, and other 44% (including government and health and social work). These are not industry wages, job counts or opportunities; the page does not give an exact year. |
Verify each industry's business, data and compliance rules against the specific position. Editorial advice is to understand the target industry first, without inferring greater complexity or ability requirements from industry names. This page has not obtained occupational wages broken down by industry.
Editorial advice: if the target involves data platforms, cloud migration or systems integration, check its technical tasks and project-material requirements; no uniform ranking of technical depth is made. This page has not obtained wages broken down by technology stack.
Evidence on the causal effects of region and living costs/competition on wages has not been obtained; do not use national figures to rank regions.
BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change； overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change； overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
Published net change +42,900； average annual openings 32,900 include replacement, not net additions.
Which Holland interest types are more suitable for computer systems analysts?
Interests I90/C82/R38/E21/A16/S15 form a profile, not headcounts; activity importance is not an individual minimum threshold.
Do not use it this way: Judging suitability only by interest codes or assessment scores overlooks actual project experience.
Test My Holland Vocational InterestsWhich Big Five traits are more relevant to this work?
Associations between Big Five personality traits and job performance are a research topic; this page has no verifiable occupation-specific regression evidence. Practitioners with higher conscientiousness and emotional stability may find it easier to keep records complete amid multiple concurrent projects and repeated confirmations, but personality scores cannot replace fundamentals in requirements and design.
Do not use it this way: There is no basis for treating personality assessment scores as hiring or competence criteria.
View My Big Five Personality TraitsWhich MBTI type is best suited to computer systems analysts?
MBTI is a type-preference tool; this page has no verifiable evidence that a particular type is better suited to this occupation. Suitability depends on clarifying requirements, coordinating stakeholders and taking responsibility for delivery results, and must be assessed through actual projects.
Do not use it this way: Using four letters to limit yourself or others lacks a basis.
Understand My MBTI PreferencesWhich Enneagram type is more suitable for computer systems analysts?
The Enneagram is not an occupational suitability assessment: it describes motivations and emotional patterns, cannot determine suitability for this occupation, and does not constitute a basis for hiring or promotion.
Do not use it this way: Do not replace judgments about engagement with actual tasks with type labels.
Explore My Enneagram PatternsCan I be a computer systems analyst with low IQ or weak mathematics?
Mathematics knowledge 56/skill 50/reasoning 50/number facility 50 are occupational importance ratings, not individual IQ/minimum thresholds; verify algorithms, models and business mathematics for the position.
Do not use it this way: Treating one test score as an occupational ceiling lacks supporting sources.
Understand My Intelligence and Reasoning PerformanceDo computer systems analysts need high emotional intelligence?
Communication under requirements conflicts and deployment pressure can be observed through actual projects and collaboration. This page has not verified predictive validity or causal evidence for emotional intelligence scales in this occupation; it does not infer individual assessment effects from occupational work styles.
Do not use it this way: Treating emotional intelligence as the sole entry requirement overlooks fundamentals in requirements and design.
Understand My Emotional Intelligence AbilitiesFits better when: You are willing to make architecture decisions and technology selections and explain their tradeoffs and scope of impact.
Watch for: Only willing to organize requirements, without taking responsibility for architecture decisions and technology selection.
Explore related career: Computer Systems Engineers and ArchitectsFits better when: You are willing to take responsibility for continuous system operation and accept shifts, monitoring and responses to unexpected incidents.
Watch for: Unwilling to provide ongoing operational coverage or having difficulty responding at night or during holidays.
Explore related career: Network and Computer Systems AdministratorsFits better when: You are willing to coordinate staffing and budgets, take responsibility for delivery results and communicate with management.
Watch for: Unwilling to handle budgets, personnel and cross-department conflicts, and wanting to focus only on technical work.
Explore related career: Computer and Information Systems ManagersFits better when: You are willing to study network protocols and capacity planning in depth and take responsibility for network design.
Watch for: Unwilling to study underlying network mechanisms and capacity models over the long term.
Explore related career: Computer Network ArchitectsFits better when: You are willing to spend extended periods independently coding, debugging and maintaining code and documentation.
Watch for: Preferring to discuss requirements and solutions with business stakeholders rather than spend extended periods independently coding.
Explore related career: Computer ProgrammersFits better when: You are willing to study attack surfaces and controls and handle security incidents under organizational rules.
Watch for: Only wanting to meet security requirements in solutions without taking responsibility for security policies and incident response.
Explore related career: Information Security AnalystsMore relevant behaviors are willingness to map workflows and data, ability to turn requirements into verifiable specifications, a habit of recording changes and tests, and willingness to confirm with business and technical stakeholders. These are observable behaviors in actual projects, not personality labels.
Do not exclude people by introversion or extraversion; interview, coordination and documentation exercises are editorial suitability suggestions, without evidence of a relationship between personality and competence.
This round has no evidence of an extraversion advantage or personality-related hiring association; check through actual requirements communication/analysis task exercises.
There is no evidence that one type is best suited to this occupation. MBTI is a type-preference tool; this page gives no type conclusion and does not use types for hiring or suitability judgments.
ICR is an interest ranking of I90/C82/R38, not population proportions; the remaining E21/A16/S15 are retained.
Not on their own. Personality assessments lack predictive-validity evidence for this occupation; actual performance depends on requirements analysis, solution design and collaboration abilities and must be observed through real projects.
Mathematics knowledge 56/skill 50/reasoning 50/number facility 50 are occupational importance ratings; no blanket promise that advanced mathematics is unnecessary can be made. Cost-benefit analysis 45 Supplemental is also a task; verify the required depth separately.
This site sets no emotional-intelligence threshold; actual employer conditions have not been obtained, and communication exercises do not guarantee hiring.
No. The Enneagram is not an occupational suitability assessment and has no predictive validity for this occupation; use actual task exercises and project experience to assess suitability.
Self-check using three kinds of fictional outputs: a one-page requirements brief with fields, rules and acceptance criteria; a system design or interface description; and test cases and results records. Give greater priority to directions in which you can complete these independently and explain your judgments.
How to reduce risk：First document the current situation and problems, then move to design after requirements confirmation; business stakeholders confirm key requirements in a written version.
Evidence：O*NET 15-1211.00 Occupational Details (Tasks and Work Context) · O*NET 15-1211.00 Work Context Section
Typical scenario：Importing business data containing personal information into an unapproved online tool for convenience in analysis.
Roles most affected：Analyst and Data-Accountable Role
Possible consequence：Violations of data and personal information protection requirements may trigger compliance consequences and loss of trust.
How to reduce risk：Access data only to the minimum necessary extent and within authorization; use approved storage and analysis environments and promptly remove temporary files.
Evidence：O*NET 15-1211.00 Occupational Details (Tasks and Work Context) · O*NET 15-1211.00 Work Context Section
Typical scenario：Finance and technical teams define the same metric differently, producing contradictory reports and reconciliation results.
Roles most affected：Analyst, Business Stakeholders and Data Team
Possible consequence：Distorted decision evidence, doubts about system trustworthiness and repeated rework.
How to reduce risk：Define field meanings, units and sources at the requirements stage and cross-check with sample data.
Evidence：BLS OOH: Computer Systems Analysts (Wages and Employment) · O*NET 15-1211.00 Occupational Details (Tasks and Work Context)
Typical scenario：Failure to assess interfaces with existing systems and failure handling results in data synchronization failure after deployment.
Roles most affected：Analyst, Development and Operations Teams
Possible consequence：Business interruption requiring emergency rollback and affecting later change windows.
How to reduce risk：Document interface solutions and exception paths in design documents; complete integration testing and rollback rehearsals before deployment.
Evidence：O*NET 15-1211.00 Work Context Section · O*NET 15-1211.00 Occupational Details (Tasks and Work Context)
Typical scenario：Requirements changes are communicated only verbally and testing records are incomplete, making the source of post-deployment problems unclear.
Roles most affected：Analyst and Project Lead
Possible consequence：Difficulty locating problems, unclear responsibility and inability to provide evidence during audits or compliance checks.
How to reduce risk：Document reasons, scope of impact and versions for changes; record test cases, results and environments; retain records of key reviews.
Evidence：BLS OOH: Computer Systems Analysts (Wages and Employment) · O*NET 15-1211.00 Work Context Section
Typical scenario：Maintaining only familiar old platforms and writing practices without tracking changes in data, cloud and security tools.
Roles most affected：Analyst and Team
Possible consequence：Fewer types of projects can be handled, and solutions fall out of step with industry practice.
How to reduce risk：Regularly learn about platforms and data tools, participate in project retrospectives and apply new methods in small pilots.
Evidence：O*NET 15-1211.00 Occupational Details (Tasks and Work Context) · ILO Research on Generative AI and Job Exposure
| Editorial Preparation Directions/Adjacent Roles | Main Work Early in Employment | Ability Materials Suggested for Checking by Editors | Demonstrable Simulations or Approved Practice | Differences From Other Directions |
|---|---|---|---|---|
| Business Systems Analyst | Clarify business requirements and workflows, write requirements briefs and acceptance criteria, and work with developers and testers. | Editorial preparation advice: use fictional cases or document samples to observe requirements, workflow, business understanding and communication; verify actual employer assessment methods separately. | A requirements brief with workflows, fields and acceptance criteria. | Focuses on business requirements; participation in architecture and deployment decisions depends on the actual position and organizational authorization. |
| Implementation and Integration Consultant | Configure products, connect interfaces, migrate data and train users according to product and client requirements. | Product and interface configuration abilities, client communication and training abilities. | An implementation or interface configuration description and testing records. | Focused on delivery projects, requiring handling of issues at client sites and deployment windows. |
| Data and Reporting Analyst | Define metrics, retrieve and model data, and produce reports and data descriptions. | SQL and data modeling abilities, awareness of metric definitions and judgment of data quality. | A metric definition and data validation description. | Focuses on data, metrics and quality; the project determines the scope of system redesign, with no fixed ranking by size. |
| Product Manager (Technical) | Define product objectives and requirements priorities and coordinate development and business stakeholders to advance deployment. | Requirements prioritization, cross-team collaboration and accountability for results. | A requirements list and priority explanation. | Focuses on product objectives and priorities; participation in system design and integration details depends on organizational responsibilities. |
| Systems Engineers and Architects (Entry Level) | Participate in system and interface design and help complete integration and performance validation. | System design and integration abilities and the basis for technology selection. | An interface or integration design description. | Focuses on system components, interfaces and integration; verify technical depth, independent responsibility and entry conditions for the actual position, without uniform ranking. |
O*NET's current education information for new hires only lists some positions requiring an associate degree, a bachelor's degree or some college without a degree; it provides no verifiable proportions and is not the educational composition of current workers. Zone4/SVP7 to below 8 is a preparation level, not a fixed duration for an individual; BLS lists a bachelor's degree/no related experience/no OJT as typical, not requirements for China or every employer.
Actual Chinese employer samples on education/subjects/experience have not been obtained; do not give majority/nearly-half proportions.
Financial, healthcare and government systems may require background checks, confidentiality agreements or data compliance training.
This page has not obtained uniform mandatory qualification requirements for related positions in China. Check employer and client rules; do not treat U.S. preparation levels as Chinese entry requirements.
Workflow mapping and documentation writing, data and interface understanding, breaking problems into verifiable conditions, and proceeding through review processes (from O*NET tasks and work activities).
These are task and ability observation points, not personality labels or hiring thresholds.
Databases and queries (SQL), reporting and visualization (Power BI, Tableau), modeling and documentation (UML, flowcharts), project management and collaboration tools; more frequently appearing O*NET job-posting keywords also include Python, ServiceNow and mainstream cloud platforms.
Fictional scenario: a company's finance department wants to replace paper expense reimbursements with online approval; you are the analyst responsible for clarifying requirements.
Provided materials: current workflow (employee completes a paper form → supervisor signs → finance enters data → cashier pays, averaging 5 working days); fields (applicant, department, amount, expense type, invoice number, approver); current rules (amounts of 5000 yuan or more require second-level approval; travel expenses require an itinerary).
Missing materials: whether to integrate with the existing ERP, whether invoices need authenticity verification, and whether multiple legal entities are involved. State assumptions explicitly if your exercise requires these conditions.
Write a one-page requirements brief including current and target workflows, fields and rules, acceptance criteria including exception paths, and two major risks and responses.
The requirements brief should specify which conditions business stakeholders confirm and which require joint assessment with development or operations.
The requirements brief should include: objectives (shorten approval cycles and retain records), workflow changes (online submission and approval, automatic finance aggregation), fields and rules (amount thresholds, expense types and attachment requirements), acceptance criteria (approval can finish within 2 working days, amounts and invoice information can be exported for checking), exception paths (missing approver, excessive amount, missing attachments), risks (data consistency in ERP integration and invoice authenticity requirements) and responses (start with a small pilot and clarify definitions and accountable parties).
Deliverables: requirements briefs for two fictional scenarios, such as online expense reimbursement and automated inventory reconciliation, each including current workflows, fields and rules, acceptance criteria and exception paths.
Each brief should specify which definitions require confirmation by business stakeholders and which require assessment with developers.
Deliverable: an interface or data-flow design description including data sources, field mappings, failure handling and impact assessment for existing systems.
Include one rejected solution and the reason for rejecting it.
Deliverables: a test-case list including normal and exception paths and a deployment and rollback steps checklist.
Deliverable: a one-page description listing the tools you use for data retrieval, workflow diagrams and documentation, and their purposes; do not include real company data, accounts or client information.
| Stage | Possible Assessment Areas | Observed Evidence | Usage Boundaries |
|---|---|---|---|
| Case Analysis (On Site or Online) | Ability to break vague requirements into workflows, fields and acceptance criteria. | Case records and explanations under follow-up questioning. | One employer's interview process does not represent a uniform industry examination. |
| Requirements Document Review | Whether requirements briefs are complete, implementable and capable of acceptance testing. | Submitted requirements briefs and field rules. | Employers set their own review standards; this page provides no uniform threshold. |
Find a public requirements or product description document, mark the current situation, fields, rules and acceptance criteria, and note three points you want to confirm.
For the fictional scenario of moving travel reimbursements online, draw or write the current workflow, including roles, fields and approval rules.
Write 5 verifiable acceptance criteria for that scenario, including at least two exception paths.
List 8 core fields with meanings, sources, units and update frequencies, and mark two that may be ambiguous.
For one external dependency, such as an invoice authenticity verification service, write an interface description: data flows, failure scenarios and compensation methods.
List 6 test cases, including boundary values, and deployment steps and rollback conditions.
| Qualification/Identity | Main Intended Audience | Practical Role in Job Seeking | Whether It Is a Widespread Entry Requirement | Application/Registration Conditions | Investment Level | Important Limitations |
|---|---|---|---|---|---|---|
| Junior College Diploma/Bachelor's Degree (Computing, Information Systems or a Related Subject) | People planning to enter analysis or implementation roles | BLS lists a bachelor's degree as typical; verify specific Chinese position requirements separately | Requirements vary greatly among employers and are not a uniform national threshold | According to the target employer's recruitment announcements and subject requirements for the relevant year | Verify separately against current course/issuer/project conditions |
Typical scope：Participate in interviews and current-state mapping, organize fields and rules, and produce requirements drafts
Readiness evidence：A requirements brief with workflows, fields and acceptance criteria
Credential boundary：Education or Business Analysis Training (According to Employer Announcements)
Next moves：Confirm requirements for more business modules
Typical scope：Independently handle requirements, specifications and acceptance criteria for a business module and align with developers
Readiness evidence：A complete requirements brief and change records
Credential boundary：Business Analysis Certification or Relevant Project Experience
Next moves：Participate in workflow redesign across systems
Typical scope：Take responsibility for requirements priorities, scope and acceptance results and organize reviews
Readiness evidence：A requirements review record and priority explanation
Credential boundary：Business Analysis and Management Training (According to Employer Rules)
Next moves：Move into product management or project management
Typical scope：Take responsibility for product objectives and deployment results and coordinate stakeholder resources
Readiness evidence：A product objectives and iteration brief
Credential boundary：Product Management or Project Management Training
Next moves：Move into product owner or project manager roles
Typical scope：Perform configuration, joint interface testing and data migration support according to the design
Readiness evidence：An interface configuration description and testing records
Credential boundary：Platform or Database Training and Certification (According to Employer Announcements)
Next moves：Participate in more complex integration projects
Typical scope：Write system designs and interface solutions and assess impacts on existing systems
Readiness evidence：A system design and interface description
Credential boundary：Systems Analysis or Platform Certification
Next moves：Participate in architecture reviews and technology selection assessments
Typical scope：Take responsibility for system architecture, integration solutions and technology selection
Readiness evidence：An architecture or integration solution document
Architecture or Cloud Platform Certification and Project Experience
Typical scope：Retrieve data and produce reports according to definitions, and check data quality
Readiness evidence：A metric definition and data validation description
Credential boundary：SQL and Reporting Tool Training (According to Employer Announcements)
Next moves：Handle more metric and model work
Typical scope：Define metrics, model data and produce analytical conclusions
Readiness evidence：A metric definitions and data description
Credential boundary：Data or Statistics-Related Certifications and Courses
Next moves：Participate in data platform or governance projects
Typical scope：Participate in data platform design, data governance and access control
Readiness evidence：A data platform design or governance description
Credential boundary：Data Platform and Cloud Service Certifications
Next moves：Move into data engineering or data governance roles
Can conduct interviews and map the current situation under guidance: document workflows, data and problems clearly and distinguish facts from conjecture.
Can turn requirements into fields, rules and acceptance criteria and confirm versions with business stakeholders.
Can propose system designs, interfaces and data solutions, assess impacts on existing systems and organize testing.
Can organize deployment, rollback and training, drive improvement using operating data and conduct project retrospectives.
BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change; overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
Does not establish：Employment projections are not individual employment guarantees and do not indicate the extent of task replacement.
Global · Global; Cross-Economy Task-Level Research (Not Official Statistics for One Country)
The research provides a framework for measuring task exposure; it does not provide a score for this individual occupation, an adoption rate or a replacement date.
Task-Level Generative AI Exposure (Research Framework)
Task exposure describes the extent to which work content can be automated, not changes in job numbers.
Does not establish：Cross-economy research cannot be directly converted into employment changes for one country or a disappearance date for one role.
Mainland China · GT4754-2017 categories 651 software development (PDF70/printed page 64), 6531 systems integration/6540 operations and maintenance/6560 IT consulting (PDF71/printed page 65) match context by a unit's main business; they do not cover every internal analyst role in other industries or establish equivalence between Chinese and U.S. occupations.
For 2025, urban non-private units in information transmission/software/IT services average 248,752 yuan per year, and private units 128,166 yuan per year. Read these separately as before-tax industry context, not a wage range, median, starting pay or personal quote for systems analysts.
IT Industry Context: Read Non-Private and Private Units Separately
Precise occupational wages in China have not been obtained; industry context is labeled separately.
Does not establish：For 2025, urban non-private units in information transmission/software/IT services average 248,752 yuan per year, and private units 128,166 yuan per year. Read these separately as before-tax industry context, not a wage range, median, starting pay or personal quote for systems analysts. GT4754-2017 categories 651 software development (PDF70/printed page 64), 6531 systems integration/6540 operations and maintenance/6560 IT consulting (PDF71/printed page 65) match context by a unit's main business; they do not cover every internal analyst role in other industries or establish equivalence between Chinese and U.S. occupations.
These are capability relationships, not automatic promotions or credential waivers.
Transfers：Systems analysis and design, interface and integration experience, and cross-team collaboration.
Build next：Requires decision-making ability in system architecture design, technology selection and integration solutions, and responsibility for design.
View career profileTransfers：System and network fundamentals, change and backup processes, and troubleshooting methods.
Build next：Requires network and server installation and configuration, operational monitoring and incident resolution abilities, and responsibility for operational availability.
View career profileTransfers：Requirements and project management experience and cross-department communication.
Build next：Requires budget, personnel, project and service-level management abilities and responsibility for departmental resources and delivery.
View career profileTransfers：Knowledge of network protocols and equipment and understanding of performance and capacity data.
Build next：Requires network design and capacity planning abilities and responsibility for network architecture decisions.
View career profileTransfers：Program and data concepts, logical troubleshooting and experience collaborating with developers.
Build next：Requires coding, debugging and version management abilities, producing working programs.
View career profileTransfers：Data and permission concepts, anomaly identification and reporting under organizational rules.
Build next：Add security policies, controls and incident response according to existing experience; check certificate requirements against the specific employer and issuer's conditions, without a uniform threshold.
View career profileTransfers：SQL and data modeling, backup and recovery, and access control.
Build next：Requires database installation and configuration, performance tuning and backup and recovery abilities, and responsibility for data availability.
View career profileTransfers：System and network fundamentals, troubleshooting methods, and documentation and escalation standards.
Build next：Requires network and endpoint maintenance, ticket handling and user support abilities, and responsibility for permissions and records.
View career profileSome information-processing tasks will receive assistance, such as interview organization, document and test-case drafts, and log classification, but people remain responsible for requirements confirmation, solution tradeoffs, and deployment and rollback decisions. The O*NET summary page reports employment growth of 9% during 2024–2034 (much faster than average).
Organizing meeting and interview records, drafting requirements and design documents and initial test cases, classifying logs and summarizing issue lists; tasks requiring business confirmation, cross-department coordination and deployment decisions are difficult to automate completely.
Turning vague requirements into verifiable conditions, assessing solution tradeoffs and scope of impact, coordinating stakeholders and advancing deployment, and taking responsibility for delivery results.
The U.S. national median annual wage is 105,850 dollars (year 2025, month 5 wage data); the 10/25/75/90 percentiles are 67,340/82,860/134,110/167,710 dollars respectively. Mainland China's public wage statistics are published by industry or broad personnel category; this page has not obtained occupational figures and records only the gap.
U.S. scope: entry typically requires a bachelor's degree, commonly in computer science or information systems but not exclusively; the preparation level is Job Zone Four. Mainland Chinese requirements follow the target employer's recruitment announcements for the relevant year.
This page provides no mandatory qualification list; business analysis, vendor and platform, data and project management certifications can demonstrate ability. O*NET's national certification search lists candidates such as CompTIA Project+, Microsoft Certified: Power BI Data Analyst Associate and AWS Certified Solutions Architect – Associate. Employers and clients determine employment and data access permissions.
Yes. Common entry points include requirements organization, implementation support and data analysis roles; people with business backgrounds can draw on industry experience but need requirements and documentation methods and data and interface fundamentals.
The O*NET summary page reports 9% growth (much faster than average) and approximately 34,200 average annual openings for 2024–2034; the current BLS OOH 2025–2035 period reports 8% and approximately 32,900 average annual openings. The two projection periods cannot be mixed.
This entry's evidence route records mainland Chinese occupational wages as “not obtained”: public wage statistics are aggregated by industry or broad personnel category, without an established occupational subcategory corresponding one-to-one to O*NET-SOC 15-1211.00. This page therefore retains the visible gap rather than filling it with industry averages, a broader occupation or U.S. data.
Wage percentiles come from BLS year 2025, month 5 wage data displayed on the O*NET national wage page; employment and projections come from the O*NET summary page (2024 and 2024–2034) and BLS Occupational Outlook Handbook. Every figure on this page labels its scope and period.
No. The exercise materials and scenarios are fictional and test requirements mapping and documentation abilities. They do not constitute hiring, qualification recognition or authorization to operate or deploy real systems; work involving real systems and data must follow the organization's rules.
Read O*NET15-1211 tasks/context, 2025 employee wages and 2025–2035 overall employment separately from Chinese IT industry context and precise gaps. Current education proportions are not provided; certification/apprenticeship directories are not mandatory in China, and specific IIBA conditions are listed separately. Risks/suitability/routes and transitions are editorial suggestions.
These nine modules were read/revised on 2026-10-09; old sources not reopened retain their dates, with no claim that the whole page was updated.
Main sources are O*NET OnLine public pages (occupational details, occupational summary, industry distribution, technology lists, preparation level and education sections, certification search and national wage page); the U.S. Bureau of Labor Statistics Occupational Outlook Handbook and OEWS methods notes; International Labour Organization research on generative AI and job exposure; the NIST AI risk management framework; and National Bureau of Statistics releases on annual average wages of employed persons in urban units and information announcing the Occupational Classification Dictionary of the People's Republic of China (2022 edition).
Limitations：Supports occupational identity, 23 tasks, 26 detailed work activities, work activity and work-context percentages, preparation level and interests; does not include Chinese qualifications or specific employer requirements.
Limitations：Supports employment size (521,100 people in 2024), projected 2034 size (566,500 people), 9% growth and 34,200 average annual job openings; net change in people is not separately listed.
Limitations：The current industry page lists professional/scientific/technical 33%, finance and insurance 13%, management of companies and enterprises 10%, and other 44% (including government and health and social work). These are not industry wages, job counts or opportunities; the page does not give an exact year.
Limitations：There are currently 119 hot technologies; full-year 2025 U.S. Lightcast job postings mention SQL16%, Excel15%, Office14%, SAP13%, PowerPoint10%, ServiceNow/JIRA/Python each 6%, SharePoint/PowerBI each 5%, Outlook/Azure/AWS/Visio each 4%, and Access/Linux/Tableau each 3%. These are not adoption rates, proficiency or AI deployment.
Limitations：O*NET's current education information for new hires only lists some positions requiring an associate degree, a bachelor's degree or some college without a degree; it provides no verifiable proportions and is not the educational composition of current workers. Zone4/SVP7 to below 8 is a preparation level, not a fixed duration for an individual; BLS lists a bachelor's degree/no related experience/no OJT as typical, not requirements for China or every employer.
Limitations：Entry typically requires a bachelor's degree, commonly in computer science or information systems but not exclusively; this does not replace education or qualification requirements for Chinese positions.
Limitations：Supports median annual wages of 105,850 dollars and hourly wages of 50.89 dollars; percentiles are not experience levels and are not converted into individual take-home income.
Limitations：That page currently publishes the 2025–2035 period (growth 8%, net change +42,900 people, approximately 32,900 average annual openings, and 2025 employment 544,400 people), which differs from this page's main 2024–2034 period and cannot be mixed with it.
Limitations：For 2025, urban non-private units in information transmission/software/IT services average 248,752 yuan per year, and private units 128,166 yuan per year. Read these separately as before-tax industry context, not a wage range, median, starting pay or personal quote for systems analysts. GT4754-2017 categories 651 software development (PDF70/printed page 64), 6531 systems integration/6540 operations and maintenance/6560 IT consulting (PDF71/printed page 65) match context by a unit's main business; they do not cover every internal analyst role in other industries or establish equivalence between Chinese and U.S. occupations.
Limitations：Used for work-context and responsibility-boundary context, such as 100% using email daily, 93% working indoors in controlled conditions daily, and 54% considering accuracy extremely important; does not replace specific employer permission policies or local rules.
Limitations：Supports Chinese occupational classification context; does not establish appointment qualifications, authorization scope or individual income for precise positions.
Limitations：Discusses task-level generative AI exposure; provides no score for this individual occupation, adoption rate or replacement date.
Limitations：Suitability signals, risk rankings, exercise materials and the seven-day plan are editorial designs, not diagnoses, hiring criteria or professional practice advice.
Limitations：Voluntary Framework, Not Evidence of Mandatory Approval/Human Review or Adoption Effects
Limitations：Supports U.S. national annual wage percentiles 10/25/50/75/90 and median hourly wages; percentiles are not experience levels and are not converted into individual take-home income.
Limitations：Supports adjacent occupation comparisons and work activity checks, with related occupations including computer and information systems managers, computer systems engineers and architects, database administrators, information security analysts, and network and computer systems administrators; does not establish interchangeability or transferable qualifications.
Limitations：Explains OEWS population coverage, wage components and statistical scope; provides no specific figures for this occupation.
Limitations：BLS table 1.2, SOC15-1211 (2025–2035), projects overall employment of 544,400→587,200, with published net change +42,900/+7.9% and average annual openings 32,900 including replacement. Subtracting rounded endpoints does not replace the published net change; overall employment includes self-employment and differs from OEWS employee wages. These are not annual actuals, individual opportunities or AI causation. OOH's approximately 8% is rounded.
Limitations：GT4754-2017 categories 651 software development (PDF70/printed page 64), 6531 systems integration/6540 operations and maintenance/6560 IT consulting (PDF71/printed page 65) match context by a unit's main business; they do not cover every internal analyst role in other industries or establish equivalence between Chinese and U.S. occupations.
Limitations：Candidate List, Not Mandatory; Check Each Credential Separately
Limitations：IIBA's current ECBA has no specific application eligibility requirements but requires agreement to ethics and certification terms; CBAP requires at least five years of business analysis experience, 7,500 hours within 10 years, including at least 900 hours in each of four of six knowledge areas, 35 hours of professional development within 4 years, two references who have known the applicant for at least 6 months, and ethics/certification terms. They do not have the same threshold and neither is a uniform occupational licence in China.
Usage note: this page is an occupational information service, not hiring conditions, qualification recognition, data access authorization, deployment approval or legal and compliance advice. Specific judgments involving personal information, data security, system changes and deployment decisions must follow applicable jurisdictional rules, organizational policies and the opinions of authorized roles.
MBTI (English) · Big Five (English) · MBTI (Chinese) · Big Five (Chinese)
Check four: are interfaces with existing systems feasible?
Check five: are change and testing records complete?
Check six: is someone responsible for deployment and rollback?
There are currently 119 hot technologies; full-year 2025 U.S. Lightcast job postings mention SQL16%, Excel15%, Office14%, SAP13%, PowerPoint10%, ServiceNow/JIRA/Python each 6%, SharePoint/PowerBI each 5%, Outlook/Azure/AWS/Visio each 4%, and Access/Linux/Tableau each 3%. These are not adoption rates, proficiency or AI deployment.
The reference deliverable lists required elements only; its wording need not match the example, provided you can explain the basis for your judgments.
This exercise tests only requirements mapping and documentation abilities; it does not evaluate real project results or constitute hiring or qualification judgments.
| Data and Interface Questions |
|---|
| Understanding of data definitions, interface methods and failure handling. |
| Answer records or whiteboard reasoning. |
| Employers set assessment standards; this page makes no inference. |
| Probation Assessment | Combined assessment of requirements delivery quality, deployment support and cross-team collaboration. | Probation assessment records and samples of project documents. | Employers set assessment and confirmation conditions; this page does not constitute a hiring promise. |
|---|
Return to this page's judgment checklist and write three reasons to continue and two conditions requiring caution.
| O*NET's current education information for new hires only lists some positions requiring an associate degree, a bachelor's degree or some college without a degree; it provides no verifiable proportions and is not the educational composition of current workers. Zone4/SVP7 to below 8 is a preparation level, not a fixed duration for an individual; BLS lists a bachelor's degree/no related experience/no OJT as typical, not requirements for China or every employer. |
| IIBA Business Analysis Certifications: Check ECBA and CBAP Separately | People wanting a systematic understanding of requirements analysis methods | Has reference value in analyst roles at some employers (editorial compilation) | Not a Widespread Entry Requirement | IIBA's current ECBA has no specific application eligibility requirements but requires agreement to ethics and certification terms; CBAP requires at least five years of business analysis experience, 7,500 hours within 10 years, including at least 900 hours in each of four of six knowledge areas, 35 hours of professional development within 4 years, two references who have known the applicant for at least 6 months, and ethics/certification terms. They do not have the same threshold and neither is a uniform occupational licence in China. | Verify separately against current course/issuer/project conditions | Certifications do not replace role-specific data/deployment authorization; recognition by Chinese employers has not been obtained. |
|---|
| Vendor and Platform Certifications (Cloud, Databases, Reporting) | People needing to demonstrate abilities on specific platforms | Can serve as evidence of ability and an advantage in screening | Related to the position's technology stack, not a widespread threshold | According to each certification body's application and renewal requirements | Verify separately against current course/issuer/project conditions | Certification does not equal ability to design solutions and take responsibility for deployment. |
|---|
| Data and Statistics Certifications or Courses | People planning to move into data and reporting | Used to demonstrate data processing and modeling fundamentals | Not a widespread entry requirement | According to course or certification body requirements | Verify separately against current course/issuer/project conditions | Courses and certifications cannot replace business understanding and judgment of definitions. |
|---|
| Project Management Certifications (Such as CompTIA Project+) | People responsible for advancing projects | Has reference value for positions oriented toward project management | Not a Widespread Threshold | This round did not obtain current original application requirements for Project+ specifically; conditions for other project management certifications cannot be transferred. | Verify separately against current course/issuer/project conditions | Project management ability does not equal system design ability. |
|---|
| Background Checks and Confidentiality Requirements (Employer or Client) | People entering finance, healthcare or government projects | Check actual employer/client requirements; no uniform industry participation prerequisite has been obtained. | Set by Employers and Clients | Follow employer and client processes | Verify separately against current course/issuer/project conditions | This page provides no organization's checking standards or results. |
|---|
Any qualification and employment requirements should follow current employer and competent authority rules; this page does not constitute a hiring promise or qualification recognition opinion.
Next moves：Move into architecture lead or technical management roles
Typical scope：Take responsibility for overall system design and technology evolution and coordinate stakeholder resources
Readiness evidence：A technology evolution and risk assessment brief
Credential boundary：Architecture and Management Training
Next moves：Move toward information technology management
Typical scope：Take responsibility for data standards, quality and compliance requirements
Readiness evidence：A data governance or compliance description
Credential boundary：Data Governance and Compliance Knowledge
Next moves：Move into data governance lead or product directions
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.
