← Risk register SOC 15-1221 · reviewed 2026-08-11

Computer and Information Research Scientists

37,200 US workers · median $140,300/yr · Tech

EXPOSED

The daily substance of this job — literature review, prototype code, ablation scripts, results tables, paper and grant drafting — is exactly the text-and-code work frontier models already do at usable quality, and this occupation is uniquely exposed because it builds the tools that automate it. What resists is choosing which problems are worth attacking, designing experiments whose results are actually informative, and owning claims that a lab, a funder, or a product organization will bet on. The modal worker is a PhD researcher in industry or a federally funded lab, not a tenured professor; no license protects the role, and headcount concentrates around the people who set research agendas rather than execute them.

10-year outlook: By 2035 the field produces far more papers and prototypes per researcher, with hiring concentrated on agenda-setters, evaluators, and those bridging research to deployed systems while junior implementation roles thin out.

Score — 40/100 resistance

Five dimensions, 0–20 each, summed. Higher means more protected. The arithmetic is shown so you can check it: 12 + 3 + 2 + 8 + 15 = 40.

Task resistance 12/20

Mixed — a routine tier and a judgment tier. A 12 reflects the split inside a single working week: the implementation half — writing training loops, sweeping hyperparameters, running ablations, building the results table, drafting related-work sections and NSF/DARPA narrative boilerplate — is already being done by coding agents at rates a first-year grad student can't match, while the half that holds is formulating a hypothesis that isn't already saturated, deciding what baseline would actually falsify it, and recognizing when a benchmark gain is measurement artifact rather than signal; it sits below 14 because that formulation work is itself text, not an act the tools are structurally barred from.

Embodiment 3/20

Fully desk- and screen-based. A 3 covers the little that isn't a laptop and a cluster queue: standing up GPU nodes, physical robotics or HCI apparatus for the minority of researchers in those subfields, and conference travel — nothing that requires your hands in an uncontrolled setting, since the SLURM job runs whether you're in the building or not.

Liability shield 2/20

No licence, no signature requirement. A 2 is close to floor because no jurisdiction licenses computer scientists: your PhD is a credential, not a practice permit, and when a published result fails to replicate the consequence is a retraction and reputational damage, not a board action — the only formal exposure is IRB approval and export-control or classification rules on specific projects, which attach to the institution rather than to you personally.

Trust premium 8/20

Some relationship component. An 8 is earned by the parts of the role that are genuinely relational — the program officer who funds you because your last three grants delivered, the product VP who greenlights a research direction on your read of it, the coauthors and students who work with you and not a substitute — but the primary output is a paper or a repo evaluated blind on its merits, and citations accrue to the result regardless of who you are.

Judgment & accountability 15/20

Exists to be accountable for ambiguous calls. A 15 is where it lands because you are the person who says a research direction is worth eighteen months of a team's headcount and compute budget, that a safety or capability claim is sound enough to publish under an institution's name, and that a negative result should kill a program — calls with no procedure to follow, made on incomplete evidence, and traceable to you when they turn out wrong.

Confidence: medium · reviewed 2026-08-11 · how scoring works

Tasks already automatable

What survives

Active moats: judgment, trust

How to future-proof this job

Who is actually doing this

The score above is about what the work exposes. This is reporting about real deployments in this occupation — the difference between "could be automated" and "somebody automated it."

Meta

Field report — do you do this job?

Has AI actually changed your work?

Self-reported and unverified — a sentiment signal, not a survey. One response per person per occupation; you can change your answer.

From people who do this job

Nobody has filed one yet. If you do this work, you know things the rubric can't see.

What has actually changed in your work?

Concrete beats general: a tool that arrived, a task that moved, a headcount decision you watched happen. Don't include anything that identifies you or your employer if that would put you at risk.