SOC 15-1211

Computer Systems Analysts AI displacement risk

Requirements documentation, system diagrams, and cost-benefit drafts are heavily AI-assisted. Needs discovery, stakeholder translation, integration judgment, and implementation troubleshooting keep the analyst function valuable.

Exposure62

Share and intensity of work current AI systems can materially affect.

Automation36%

Likely potential for exposed tasks to move to software after workflow integration.

Risk bandModerate

Documentation-heavy analyst work compresses as AI writes specs from prompts. Analysts who interview users, resolve conflicting requirements, and own system outcomes stay in demand.

Distribution

Where Computer Systems Analysts sits across 620 tracked roles

Computer Systems Analysts · 46050100

Displacement pressure 46 — higher than 76% of the 620 occupations tracked on displacement.ai.

Score version

This page uses Seed model v0.4 (seed-v0.4-2026-05), last reviewed 2026-08-08. Directional occupation-level planning model using hand-reviewed public research, task exposure estimates, wage context, and transition-pathway assumptions.

30 O*NET task statements matched to SOC 15-1211. The displayed task profile combines these official task statements with the current public score model.

Median wage context: $105,850 (May 2025, US national). The latest BLS row matched SOC 15-1211.

Scores are planning signals, not forecasts. Local hiring demand, employer-specific workflows, licensing, and credentials must be validated before making career decisions.

2030 economic stress test

How Anthropic's scenarios classify Computer Systems Analysts

SOC 15-1211 places this role in the paper's cognitive occupation group. These group-level outcomes do not change the 46/100 role score and are not an occupation forecast.

Modest change

+0.4% group wage

-0.5% cognitive employment since mid-2026; 2.9% cognitive unemployment.

Economy-wide: +1.6% GDP and 3.9% unemployment.

Substantial change

-0.3% group wage

-3.9% cognitive employment since mid-2026; 4.5% cognitive unemployment.

Economy-wide: +8.3% GDP and 4.6% unemployment.

Extreme change

-11.5% group wage

-21.5% cognitive employment since mid-2026; 17.9% cognitive unemployment.

Economy-wide: +32.4% GDP and 11.9% unemployment.

Compare the assumptions and limitations across all three scenarios. Source: The Anthropic Institute Working Paper No. 2026-02.

Official task evidence

O*NET task matches for Computer Systems Analysts

The current evidence import matched 30 task statements from Task Statements 31.0 (August 2026). These rows are used as a grounding layer for judging which parts of the occupation are repeatable, language-heavy, analytical, social, physical, or compliance-sensitive.

Dataset31.0 (August 2026)
Matched tasks30
SOC15-1211
  • Core task / ID 20950

    Troubleshoot program and system malfunctions to restore normal functioning.

  • Core task / ID 3464

    Provide staff and users with assistance solving computer-related problems, such as malfunctions and program problems.

  • Core task / ID 3465

    Test, maintain, and monitor computer programs and systems, including coordinating the installation of computer programs and systems.

  • Core task / ID 3482

    Use the computer in the analysis and solution of business problems, such as development of integrated production and inventory control and cost analysis systems.

  • Core task / ID 3468

    Coordinate and link the computer systems within an organization to increase compatibility so that information can be shared.

  • Core task / ID 3466

    Use object-oriented programming languages, as well as client and server applications development processes and multimedia and Internet technology.

Source: O*NET Resource Center, Task Statements. Raw import target: data/raw/onet/task-statements-31-0.txt.

Task profile

Where AI changes the work

analytical

Analyze needs and design systems

Exposure 60, automation 30%, augmentation 70%.

O*NET evidence: Analyze information processing or computation needs and plan and design computer system... (ID 3474)

language

Document procedures and standards

Exposure 76, automation 44%, augmentation 70%.

O*NET evidence: Develop, document, and revise system design procedures, test procedures, and quality st... (ID 3477)

technical

Test and monitor systems

Exposure 56, automation 30%, augmentation 62%.

O*NET evidence: Test, maintain, and monitor computer programs and systems, including coordinating the i... (ID 3465)

social

Consult with users and management

Exposure 30, automation 9%, augmentation 46%.

O*NET evidence: Consult with management to ensure agreement on system principles. (ID 3469)

TaskExposureAutomationAugmentation
Analyze needs and design systems6030%70%
Document procedures and standards7644%70%
Test and monitor systems5630%62%
Consult with users and management309%46%

Transition pathways

Adjacent moves that preserve existing skills

role redesign

Business Systems Analyst Lead

Training horizon: 2-5 months. Skill overlap 78. Wage preservation signal 104.

  • Own requirements quality
  • Direct AI-drafted documentation
  • Run stakeholder workshops
Moderate
adjacent role

Solutions Architect

Training horizon: 6-12 months. Skill overlap 64. Wage preservation signal 122.

  • Deepen integration patterns
  • Design system blueprints
  • Evaluate build-versus-buy tradeoffs
Moderate

Comparison guides

Compare the next move before you commit

What the AI risk score means for Computer Systems Analysts

The displacement pressure score for Computer Systems Analysts is 46. That score blends task exposure, automation pressure, augmentation potential, wage vulnerability, transition feasibility, and source confidence. It is designed to help workers and workforce teams decide where to act first, not to claim a specific date when a job will disappear.

For this role, the clearest risk pattern is visible at the task level. Document procedures and standards carries 44% automation pressure, while Analyze needs and design systems carries 70% augmentation potential. That means the best response is usually a targeted redesign of work: move away from repeatable production tasks and toward judgment, exception handling, coordination, stakeholder context, and accountable use of AI tools.

Labor-market context and wage risk

Median wage: $105,850 (May 2025, US national). Employment context: Bridge role between business needs and technical systems. Typical education: Bachelor's degree common.

Wage vulnerability is 28, while transition feasibility is 76. A high wage-vulnerability score means workers should pay close attention to salary preservation before making a move. A high transition-feasibility score means there are adjacent paths that can reuse existing skills without requiring a complete career reset.

  • Moderate displacement pressure
  • Spec writing is automating
  • Needs discovery stays human

Upskilling priorities

Skills that make this role more resilient

The safest upskilling plan starts with skills already close to the work. For Computer Systems Analysts, the strongest near-term skill priorities are listed below. These are useful whether the goal is to stay in the role, move to a redesigned version of the role, or transition into an adjacent occupation.

Priority 1

Requirements discovery

Build proof of this skill through a work sample, checklist, dashboard, case note, workflow map, or portfolio artifact tied to the transition paths on this page.

Priority 2

Systems design

Build proof of this skill through a work sample, checklist, dashboard, case note, workflow map, or portfolio artifact tied to the transition paths on this page.

Priority 3

Stakeholder translation

Build proof of this skill through a work sample, checklist, dashboard, case note, workflow map, or portfolio artifact tied to the transition paths on this page.

Priority 4

AI-assisted documentation

Build proof of this skill through a work sample, checklist, dashboard, case note, workflow map, or portfolio artifact tied to the transition paths on this page.

90-day transition plan

The most practical next step is not to wait for a layoff or a full role redesign. Use the next 90 days to create evidence that you can operate in a safer, more AI-augmented version of the work.

  1. In the first 30 days, document the repetitive tasks in your current work and identify where AI can reduce drafting, lookup, classification, or reporting time.
  2. By 60 days, complete one small project connected to Business Systems Analyst Lead, such as own requirements quality.
  3. By 90 days, compare internal openings and external postings for Business Systems Analyst Lead or Solutions Architect and update your resume around measurable workflow outcomes.

FAQ

Questions about AI and Computer Systems Analysts

Will AI replace Computer Systems Analysts?

Requirements documentation, system diagrams, and cost-benefit drafts are heavily AI-assisted. Needs discovery, stakeholder translation, integration judgment, and implementation troubleshooting keep the analyst function valuable. The better planning signal is not full replacement, but which tasks become automated, which tasks become AI-assisted, and which responsibilities still need human judgment.

Which parts of Computer Systems Analysts work are most exposed to AI?

Document procedures and standards and Analyze needs and design systems show the strongest automation pressure in this model. Analyze needs and design systems and Document procedures and standards are better treated as AI-augmented work.

What should Computer Systems Analysts learn next?

Start with Requirements discovery, Systems design, Stakeholder translation. The most practical adjacent paths in this model are Business Systems Analyst Lead and Solutions Architect.

How should this score be used?

Use it as a planning signal, not a prediction. Confirm local hiring demand, wages, licensing, credentials, and employer adoption before making a career move.

Sources

Evidence trail