Methodology

How we score AI exposure

Every career on Auspex carries an AI-exposure band. It is a model of how automatable a job’s tasks are — built from public O*NET data, not an opinion typed into a spreadsheet and not a number from a language model. This page states exactly how it’s computed, so you can argue with it.

The short version

  1. Take each occupation’s 41 Generalized Work Activities from O*NET, with their Importance and Level ratings.
  2. Weight each activity by how exposed that kind of work is to today’s AI (the coefficients below).
  3. Dampen the score for jobs that need a body in a place — physical presence is structural protection.
  4. Rank every career and split them into five bands by fixed quota, so the score always carries information.

1. Sources — all public, all cited

  • O*NET Generalized Work Activities (Importance + Level) and Work Context — the U.S. Department of Labor’s occupational database.
  • The approach follows the published literature on AI task exposure — Felten, Raj & Seamans (AI Occupational Exposure); Brynjolfsson, Mitchell & Rock (Suitability for Machine Learning); Eloundou et al. (“GPTs are GPTs”). We are re-implementing a known method, not inventing one.

2. The score

For each occupation we compute a raw task-exposure score as an importance- and level-weighted average of its work activities’ coefficients:

raw = Σ( coefficient × Importance × Level ) ÷ Σ( Importance × Level )

An activity like Documenting/Recording Information carries a high coefficient; Assisting and Caring for Others carries a low one. A job made mostly of the former scores high; one made mostly of the latter scores low.

3. Physical damping

A job that needs a body in a place is structurally protected regardless of its information content — this is what separates a barista from an analyst. From O*NET Work Context we build a physical-presence index (standing, handling objects, face-to-face work, hazards, protective gear) and pull the raw score down by up to 55% for the most physical roles:

exposure = raw × ( 1 − 0.55 × physical-presence )

Context signals used: Spend Time Standing, Spend Time Walking and Running, Spend Time Using Your Hands to Handle, Control, or Feel Objects, Tools, or Controls, Spend Time Making Repetitive Motions, Spend Time Bending or Twisting the Body, Spend Time Climbing Ladders, Scaffolds, or Poles, and more.

4. A forced distribution

The old score put every career in “Moderate” — a field whose value never changes tells you nothing. So we percentile-rank all careers on the damped score and split them by hard quota. No band can hold more than 40% of careers; a build that violates this fails automatically.

BandPercentileShare of careers
Minimal01010%
Low103020%
Moderate307040%
High709020%
Severe9010010%

5. The coefficients — the only judgment call

This is the one place a human opinion enters the score, so it’s public and arguable. Each of O*NET’s 41 work activities gets a coefficient from 0 (untouched by AI) to 1 (fully exposed), with a one-line rationale. Disagree with one? That’s the point — they’re meant to be debated.

0.90Getting InformationPure information intake from documents/systems — squarely what LLMs do.
0.90Processing InformationCompiling, coding, categorizing, calculating information — core LLM competency.
0.90Documenting/Recording InformationTurning work into text/records is the LLM sweet spot.
0.85Analyzing Data or InformationBreaking down and interpreting data is strongly exposed.
0.80Performing Administrative ActivitiesPaperwork and administrative routine automate readily.
0.75Evaluating Information to Determine Compliance with StandardsChecking inputs against rules/standards is highly automatable.
0.75Interacting With ComputersScreen-based work is where software automation reaches first.
0.70Estimating the Quantifiable Characteristics of Products, Events, or InformationQuantitative estimation is model-friendly.
0.70Updating and Using Relevant KnowledgeKnowledge retrieval and application is a model strength.
0.70Interpreting the Meaning of Information for OthersExplanation and translation of information is well within reach.
0.65Scheduling Work and ActivitiesScheduling/optimization is automation-friendly.
0.65Drafting, Laying Out, and Specifying Technical Devices, Parts, and EquipmentCAD/generative design tools automate large parts of drafting.
0.60Identifying Objects, Actions, and EventsPerception/classification is increasingly a model task.
0.55Monitoring Processes, Materials, or SurroundingsSensor/vision monitoring is automatable, but often tied to a physical site.
0.55Organizing, Planning, and Prioritizing WorkCoordination is partly automatable; judgment on priorities is shared.
0.50Judging the Qualities of Things, Services, or PeopleEvaluative judgment partly automatable; consequential calls still held by people.
0.50Making Decisions and Solving ProblemsAI assists, but accountability and stakes keep a human deciding.
0.50Monitoring and Controlling ResourcesTracking automatable; allocation decisions carry accountability.
0.45Thinking CreativelyGenerative models encroach, yet originality and taste remain human-anchored.
0.45Communicating with People Outside the OrganizationDrafting automatable; the relationship and trust are not.
0.45Provide Consultation and Advice to OthersAdvice is partly automatable; accountability keeps a human advisor.
0.40Developing Objectives and StrategiesStrategy carries accountability and context AI doesn't own.
0.40Communicating with Supervisors, Peers, or SubordinatesRoutine messages automatable; real coordination is human.
0.40Staffing Organizational UnitsScreening automatable; hiring decisions stay human.
0.35Inspecting Equipment, Structures, or MaterialsJudgment is automatable but usually requires being physically present to inspect.
0.35Selling or Influencing OthersPersuasion partly automatable; closing and trust stay human.
0.35Coordinating the Work and Activities of OthersSome scheduling automatable; managing people is human.
0.35Training and Teaching OthersContent generation automatable; mentorship and delivery are human.
0.30Controlling Machines and ProcessesSome process control automatable, but tied to physical equipment.
0.25Resolving Conflicts and Negotiating with OthersHigh-stakes negotiation depends on human standing and read.
0.15Operating Vehicles, Mechanized Devices, or EquipmentAutonomy is immature and gated by safety/liability.
0.15Establishing and Maintaining Interpersonal RelationshipsDurable human trust doesn't transfer to a model.
0.15Performing for or Working Directly with the PublicIn-person presence and service resist automation.
0.15Developing and Building TeamsTeam-building is relational leadership.
0.15Guiding, Directing, and Motivating SubordinatesLeadership and motivation are human roles.
0.15Coaching and Developing OthersPersonal development is a relationship, not a task.
0.10Repairing and Maintaining Electronic EquipmentDiagnosis assistable, but the fix is physical.
0.08Repairing and Maintaining Mechanical EquipmentHands-on repair in unstructured settings.
0.05Performing General Physical ActivitiesBodily work in the world; robotics lags far behind software.
0.05Handling and Moving ObjectsManual dexterity is the hardest thing to automate.
0.05Assisting and Caring for OthersCare work — physical and emotional, deeply human.

6. What this is NOT — the limitations

  • Exposure is not job loss. A high band means a role’s tasks are automatable — not that the job disappears. History suggests exposed tasks are as often augmented as replaced.
  • This is a model, not a prediction. It measures task structure today, using ratings that update on O*NET’s schedule. It cannot see your specific employer, your seniority, or how a given company adopts AI.
  • High exposure can be good. If AI does the automatable parts, the human can do more of the valuable parts. Exposure tells you where change is coming, not whether it helps or hurts you.
  • Coefficients are debatable. They are our best reading of the literature, not settled fact. They are all listed above precisely so you can push back.

The model and coefficients live in the open in our codebase; the pipeline re-runs from the raw O*NET database on a single command. Questions? supportauspex@gmail.com. Explore careers →