TruaceTracing the truth around AIMonday, September 14, 2026
TRV-2026-1073Certified recordJournalism

Can you futureproof your career by choosing an AI-resistant degree?

Futureproofing your career with an AI-resistant degree is a tough ask, says Charlie Ball, an expert on graduate employment for Jisc, the UK’s higher education digital, data and technology agency. “What you’re trying to do is futureproof a 45-year career in a time of rapid technological change – and that’s really quite hard to do. What’s likely is that jobs that hinge a lot on human, face-to-face interaction are unlikely to be replaced.” He warns however that the discussion should focus less on identifying specif…

Labor · The Trace — both readings · certified 2026-09-14 · v1 · article view · machine-readable

Current reading — gain

Roles centered on human interaction, responsibility and physical oversight in medicine, nursing, engineering and education are expected to persist because people prefer humans for care, difficult news and large-scale physical work.

Current reading — problem

Entry-level laboratory work and routine design and modelling tasks in STEM and engineering are likely to be affected as AI becomes embedded in those workflows.

What this doesn’t fix

Forecasting which degrees will stay safe over a full career is highly uncertain due to rapid technological change, and the article offers expert judgment rather than measured employment outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1073, v1: “Can you futureproof your career by choosing an AI-resistant degree?.” Truvace, 2026-09-14. /record/TRV-2026-1073 (accessed at citation time). sha256 994131b3f9f59836

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1994131b3f9f5

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1073 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.