Software Engineer AI displacement risk — 3 moves to make in 90 days

Code-completion and agentic tools merge feature PRs at rates approaching parity with junior ICs (GitHub Copilot 2024; Anthropic Economic Index 2025). The defensible work is on-call judgment, security under load, and the architecture decisions whose blast radius is too high to delegate to a model.

Full software engineer role page Calls Brain accuracy table How we calculate this

Triggering signals

What the data shows for this role

Code-completion + agentic coding tools (Copilot, Cursor, Claude Code) measurably ship feature-implementation and unit-test PRs faster than a junior IC, with merge rates approaching parity (GitHub Copilot 2024 internal study; Anthropic Economic Index 2025).

Hiring managers are explicitly tightening junior pipeline and consolidating into senior + AI-leverage roles.

Architecture, on-call judgment, security, performance under load, and org-specific systems context resist automation.

Signals quoted verbatim from Career Runway’s career-moves rubric (V11.1). Each references peer-reviewed research, independent benchmarks, or large-N labour-market data — see citations on each move below.

Confidence band

AI exposure

42–58

grade C

⚠ Placeholder · Sample brief — confidence band shown is a representative midpoint, not an evidence-grounded computation. Take the assessment for a calibrated number.

3 Primary Moves

Highest-defensibility moves for the next 90 days

Verbatim from the career-moves rubric. Each move ships an observable artefact — not self-report.

Move 1 · Defensibility

Lead 3 architecture decision records (ADRs) on org-specific systems

High defensibility

Why it works · ADRs codify trade-offs in the language of the org's actual constraints; they become reference docs for years.

Time budget

4h / week

Prerequisites

at least one cross-team system in flight

Verifiable artefact

3 merged ADR markdown files in the repo with reviewer sign-offs, linked from the team's onboarding docs.

Citation: n/a

Move 2 · Defensibility

Become the primary owner of one knotted technical-debt domain

High defensibility

Why it works · accumulated context on one painful subsystem is precisely what an LLM does not have; it makes you the irreplaceable shepherd of that area.

Tracking layer

What execution looks like — representative example

Sample data, not a real user. The tracking layer in the product follows actual move-completion artefacts and recomputes defensibility from observed signals.

Priya completed Move 1 — “Lead 3 architecture decision records (ADRs) on org-specific systems” — over 6 weeks. Tracking-layer artefact recorded: 3 merged ADR markdown files in the repo with reviewer sign-offs, linked from the team's onboarding docs.

Defensibility

→

▲2 pts after artefact verification

Sample numbers. Real movement is computed from your task map + verified move artefacts when you complete an assessment.

Get your own Brief

Your moves depend on
your actual task mix.

This sample is the archetype for a software engineer. Your specific tooling, environment, and tenure produce a different Task Exposure Map — and a different ordered list of moves. About 10 minutes, free, no card.

Map my exposure View methodology

Other sample briefs

Business Analyst Compliance Officer Content Strategist Customer Success Manager Data Analyst Finance Manager Hr Manager Marketing Manager Operations Manager Product Manager Project Manager Sales Manager Supply Chain Manager Ux Designer