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

Mathematical Science Occupations, All Other

3,720 US workers · median $81,490/yr · Tech

EXPOSED verdict contested

This is a residual category — model validators, quantitative analysts, cryptologic and biostatistical specialists who don't fit the statistician, actuary, or data-scientist codes — and the modal worker spends the day writing and testing code, cleaning data, fitting and documenting models, and producing technical memos. Those are exactly the artifacts LLMs now draft at usable quality, and nothing about the work is physical or licensed. What holds is the accountable end: choosing formulations under ambiguity, deciding whether a model is fit for a consequential decision, and signing the validation report someone in risk or regulatory will lean on.

10-year outlook: Routine quantitative production work in this residual category compresses hard over ten years, while a smaller, better-paid tier of model validators and methodology owners in regulated settings holds or grows.

US employment, 2021–2025-6.3%
3,9703,720 workers

Most of this decline happened after 2021 — it is not the pandemic dip.

The job count is not the verdict

This line is counted by the Bureau of Labor Statistics — the one figure on this page that isn't a judgement of ours. Headcount moves on demand, offshoring, demographics and the business cycle, and automation is one term among several, often not the loudest.

So a falling line is not evidence that AI did it, and a rising one is not evidence that it won't. Both happen in this register: some occupations resist automation and shrink anyway, others are highly automatable and keep growing.

BLS projection, 2024–2034

+4%

Percentage only. The projection counts a different population from the 3,720 above — it includes self-employed workers, which for this occupation is most of them, so the two headcounts are not comparable.

Exposed, but growing

AI can already do a lot of these tasks, and the BLS still expects +4% more of these jobs by 2034. Demand for the output is growing faster than the work is being automated away — the mechanism BLS gives for software developers, and the combination people most often misread as an error.

Different clocks. The score is what current AI could do to this work today. The projection is how many of these jobs will exist in 2034. Everything between the two — how fast employers actually adopt, whether demand grows in the meantime — is why they can point opposite ways without either being wrong.

~300 openings a year on average, including replacing people who leave.

One email if this score changes. Watch as many occupations as you like from the same address — no account, and nothing is sent on a schedule, only when a verdict actually moves.

Also known as — 24 job titles this covers

Titles reported by people doing this work, from the US Department of Labor's O*NET survey. If your job title is here, this page is about your work even though the name doesn't match.

GeometerCryptanalystCryptologistData AnalystGeometricianBiotechnicianWeight AnalystData TechnicianBalance EngineerHarmonic AnalystResearch AnalystResearch ScientistSecret Code ExpertDatabase TechnicianLog Data TechnicianBiometrics TechnicianField Data TechnicianSubmission TechnicianBioinformatics AnalystMathematical ScientistMathematics TechnicianBioinformatics SpecialistBioinformatics TechnicianMuseum Informatics Specialist

This is a catch-all code, not a single job

The BLS uses Mathematical Science Occupations, All Other for work that doesn't fit any named occupation, so it covers roles that have little in common with each other. Two consequences worth knowing before you read anything below:

If a more specific occupation on the register describes what you actually do, that page is the one to trust.

Score — 34/100 resistance

Holding it up: judgment & accountability (12/20). Weakest point: liability shield (3/20).

Five dimensions, 0–20 each, summed. Higher means more protected. The arithmetic is shown so you can check it: 9 + 3 + 3 + 7 + 12 = 34. · Scored 2026-08-11, and re-examined when evidence accumulates rather than on a schedule.

Task resistance 9/20

Mixed — a routine tier and a judgment tier At 9 the split is visible inside a single day: the derivation setup, the choice of estimator for a badly-specified problem, and the argument for why a stress scenario is binding still take a person, but the Python that implements it, the backtest harness, the sensitivity tables and the SR 11-7 style write-up are now first-drafted by tooling faster than you can type them.

Embodiment 3/20

Fully desk- and screen-based A 3 reflects that the only physical constraints are a workstation and, for the cryptologic and defence-adjacent slice of this code, a SCIF or air-gapped terminal you must physically sit at — that limits where the work happens, not what the hands do.

Liability shield 3/20

No licence, no signature requirement There is no licence to strip: unlike the actuary who signs a Statement of Actuarial Opinion under ASOP, a model validator's report is absorbed by the CRO or model risk committee, and an SOA/CFA credential or clearance is a hiring filter rather than a legal barrier to anyone else doing the work.

Trust premium 7/20

Some relationship component At 7 you have a real internal relationship — the model owners and the traders or epidemiologists who consume your output know whether your challenge is credible, and examiners recognise repeat authors — but the deliverable travels as a document under an institution's name, and clients rarely ask for you personally.

Judgment & accountability 12/20

Meaningful discretion 12 is the effective-approve call: deciding a model is unfit for a capital decision or that a proxy variable invalidates a published estimate is a discretionary judgment with real consequences, but it lands inside a governance chain with committee sign-off, documented methodology standards, and an escalation path above you rather than terminating with your name.

The verdict on this page is contested. We scored this occupation twice, independently, and the two runs disagreed: 34/100 — EXPOSED and 31/100 — COOKED. Combining them doesn't settle it — the answer changes depending on how the halfway points are rounded, which is a property of our arithmetic and not of the job. Rather than pick the side that suits us, we've left the original verdict in place and flagged it. Read the dimension scores below and the reasoning attached to each; on this page they carry the information, and the one-word label does not.

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

What this job involves — and which parts are yours

The verdict above describes this occupation as a whole. Almost nobody does the typical version of a job — tick what's actually in your week and see how your own mix sits.

AI already does these at usable quality

These still need a person

Active moats on the surviving side: judgment, trust

How to future-proof this job

Where to go deeper on what this job runs on: Khan Academy — reading and vocabulary, all levels, free free · Coursera — active listening and communication skills free to audit · Purdue OWL — the standard reference for professional writing free · Coursera — critical thinking and logic, audit free free to audit · MIT OpenCourseWare — full course materials across every department, free free · MIT OpenCourseWare — problem-solving and analytical method courses free

All 35 skills ranked by how many jobs they open →

What would move this back up — beyond any one person

The moves above are yours to make. This is the other half: what would have to change in the world for the occupation itself to score higher. None of it is in any one person's gift, but it is where the floor actually comes from. Scores here are not a one-way ratchet. Only two of the five dimensions — task resistance and embodiment — track what machines can do. The other three track law, what buyers will pay for, and who is answerable, and those move in both directions, often in response to the same pressure AI creates. If every lever below landed, this occupation would score around 50/100, still EXPOSED.

4 specific changes that would raise this score
  • already happening judgment accountability +4

    Independent validation of AI/ML models becomes a mandated second line function under EU AI Act conformity assessment and NAIC/state insurance model-governance bulletins, so the role owns the go/no-go on deployment rather than advising on it — the validator's adverse finding blocks release.

  • already happening task resistance +4

    Task-mix shift: once code generation, data cleaning and memo drafting are absorbed, the residual day is formulation choice under ambiguity, identification/assumption critique, adversarial testing of generated models, and defending findings to regulators and examiners — genuinely two-tiered work where the upper tier is what remains. Also rises if validating AI systems built by others becomes the dominant workload.

  • plausible liability shield +6

    Model risk management rules move from 'effective challenge by qualified staff' to a named-individual attestation: e.g. if the Fed/OCC/FDIC SR 11-7 successor or an EU AI Act Article 17 implementing act requires a specifically identified model validator to sign that a high-risk model was independently validated, with personal accountability under a regime like the UK SM&CR / FCA Senior Manager attestations already applied to some model owners. Similar route via FDA biostatistics: a named responsible statistician signing the SAP and unblinding memo under ICH E9(R1).

  • plausible trust premium +2

    Narrow route only: cryptologic and classified-clearance work, plus expert-witness and regulatory-examination testimony, where the buyer needs a cleared or deposable human. Confined to a minority of this residual code.

The limit. Embodiment has no route. The liability route is the only large one, and it is uncertain because model risk regulation has historically attached to the institution, not to a licensed individual — there is no board, no license, no personal statutory duty to build on, so any attestation regime would be contractual or supervisory rather than professional licensure. Realistic ceiling in the low-to-mid 50s, and that requires the named-signer rule to actually land.

These are conditions, not forecasts — what would have to happen, not what will. Specific rules, cases and bills are named so you can go and check whether they exist and where they stand; verify before relying on any of them. Nothing here is legal or financial advice.

Where this work is, and what it pays there

BLS metro figures for 8 areas. The verdict above does not change by city — the rubric judges what the work involves, not where it happens — but pay and headcount do, and the national median hides a very wide range.

Most of these jobs

Chicago-Naperville-Elgin, IL-IN 1,100 $82,230 +1%
Seattle-Tacoma-Bellevue, WA 240 $72,710 -11%
Birmingham, AL 80 $62,630 -23%
New York-Newark-Jersey City, NY-NJ 70 $79,460 -2%
Oklahoma City, OK 40 $36,820 -55%
Phoenix-Mesa-Chandler, AZ 40 —
Atlanta-Sandy Springs-Roswell, GA 30 $93,320 +15%
Austin-Round Rock-San Marcos, TX 30 $97,190 +19%

Best paid

Austin-Round Rock-San Marcos, TX 30 $97,190 +19%
Atlanta-Sandy Springs-Roswell, GA 30 $93,320 +15%
Chicago-Naperville-Elgin, IL-IN 1,100 $82,230 +1%

Percentages are against this occupation's national median of $81,490. Counts are jobs in that metro, not vacancies. Metros where the BLS suppressed the cell are absent rather than shown as zero.

Who is actually doing this — nobody, on the record

We have no reported case of a named organisation automating this occupation. Not one deployment, not one announcement.

That is worth saying out loud next to a score of 34. The verdict above is about what the work exposes — what current AI could do to these tasks. It is not a claim that anyone has done it. For this occupation those two things have come apart completely: the capability argument is on this page, and the evidence column is empty.

Read that as a gap in the reporting we can see, not proof of absence — the dispatch runs on English-language feeds and misses plenty. If you know of a case, tell us, or add a field report from inside the job.

Quick take — do you do this job?

Has AI actually changed your work? One tap, anonymous, and the running tally is public. Nothing else is asked of you.

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

Field reports — what people say has changed

No field reports yet. A written account takes a paragraph rather than a tap, goes to an editor before it appears, and is the one thing on this page the rubric cannot produce on its own.

File a field report

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.

Watch this verdict
Kept current

Rather than check back: get the digest and we'll tell you what changed — or watch a single occupation from its own page.