Analystes QA Logiciel
Informatique et MathématiquesExposition à l'IA
- Source des données: BLSPublié: '26.08
Très élevée· relative
FaibleQuatre bandes relativesTrès élevéeValeur par groupe professionnel
Échelle, base et source
Quatre bandes relatives (Faible / Modérée / Élevée / Très élevée)
831 métiers détaillés du tableau des projections d'emploi du BLS. La valeur est attribuée par code de la National Employment Matrix (NEM), si bien que les métiers partageant un code NEM reçoivent la même bande
- Source des données: AnthropicPublié: '26.03
0.519
0.000Étendue des valeurs présentées ici0.745Échelle, base et source
- Source des données: ILOPublié: '25
0.53
0.09Étendue des valeurs présentées ici0.70Valeur par groupe professionnel
Échelle, base et source
Indice d'exposition à l'IA générative, 0–1 tel que publié
Groupe de base CITP-08 — tous les métiers partageant le code reçoivent cette valeur
Calculé par ce site, non publié par l'OIT : sur les 1 012 professions que ce site relie au jeu de données de l'OIT, 14% atteignent ou dépassent cette valeur.
Quelle est la nature de la valeur publiée par cette source
La catégorie BLS est un rang relatif et non un niveau absolu, et ce n'est pas une mesure de première main : elle regroupe en quatre bandes les rangs centiles du métier dans plusieurs études publiées. Ce n'est ni une prévision d'emploi ou de salaire, ni une probabilité d'adoption, et elle ne distingue pas automatisation et augmentation.
Task-level exposure
Tâches exposées uniquement| Task | Claude.aiRaw / share % | APIRaw / share % |
|---|---|---|
Identify, analyze, and document problems with program function, output, online screen, or content.15-1253 | 0.910071.1 | 1.620068.6 |
Modify existing software to correct errors, allow it to adapt to new hardware, or to improve its performance.15-1253 | 0.190014.8 | 0.340014.4 |
Provide feedback and recommendations to developers on software usability and functionality.15-1253 | 0.07005.5 | 0.02000.8 |
Collaborate with field staff or customers to evaluate or diagnose problems and recommend possible solutions.15-1253 | 0.04003.1 | 0.01000.4 |
Monitor program performance to ensure efficient and problem-free operations.15-1253 | 0.03002.3 | 0.20008.5 |
Identify program deviance from standards, and suggest modifications to ensure compliance.15-1253 | 0.02001.6 | 0.03001.3 |
Perform initial debugging procedures by reviewing configuration files, logs, or code pieces to determine breakdown source.15-1253 | 0.01000.8 | 0.07003.0 |
Store, retrieve, and manipulate data for analysis of system capabilities and requirements.15-1253 | 0.01000.8 | 0.02000.8 |
Test system modifications to prepare for implementation.15-1253 | 0.00000.0 | 0.02000.8 |
Document software defects, using a bug tracking system, and report defects to software developers.15-1253 | 0.00000.0 | 0.01000.4 |
Participate in product design reviews to provide input on functional requirements, product designs, schedules, or potential problems.15-1253 | 0.00000.0 | 0.00000.0 |
Document test procedures to ensure replicability and compliance with standards.15-1253 | 0.00000.0 | 0.00000.0 |
Develop or specify standards, methods, or procedures to determine product quality or release readiness.15-1253 | 0.00000.0 | 0.00000.0 |
Investigate customer problems referred by technical support.15-1253 | 0.00000.0 | 0.00000.0 |
Install and configure recreations of software production environments to allow testing of software performance.15-1253 | 0.00000.0 | 0.00000.0 |
Evaluate or recommend software for testing or bug tracking.15-1253 | 0.00000.0 | 0.00000.0 |
Conduct historical analyses of test results.15-1253 | 0.00000.0 | —0 |
Develop testing programs that address areas such as database impacts, software scenarios, regression testing, negative testing, error or bug retests, or usability. | —0 | 0.00000.0 |
Plan test schedules or strategies in accordance with project scope or delivery dates. | —0 | 0.00000.0 |
Install, maintain, or use software testing programs. | —0 | 0.00000.0 |
Conduct software compatibility tests with programs, hardware, operating systems, or network environments. | —0 | 0.00000.0 |
Coordinate user or third-party testing. | —0 | 0.00000.0 |
| Not observed on any surface — 6 task(s) — These tasks have no row in the source for this release. The 0 in the share row is a display-stage composition ratio; absence is what the — in the raw row states. | ||
Create or maintain databases of known test defects. | —0 | —0 |
Review software documentation to ensure technical accuracy, compliance, or completeness, or to mitigate risks. | —0 | —0 |
Update automated test scripts to ensure currency. | —0 | —0 |
Design or develop automated testing tools. | —0 | —0 |
Visit beta testing sites to evaluate software performance. | —0 | —0 |
Recommend purchase of equipment to control dust, temperature, or humidity in area of system installation. | —0 | —0 |
Values in this tab are predicted labels, not observations. Eloundou et al. (2023) published two rating regimes — human raters and GPT-4 — and the β shown here is derived from the GPT-4 rater basis alone; the same task can take a different value under the other regime. The unit and the meaning differ from the observed shares (%) in the other tabs, so do not place them on the same axis.
| Task | βE1 + 0.5 × E2 |
|---|---|
Design test plans, scenarios, scripts, or procedures.O*NET Task ID 14638 | 1.0 |
Test system modifications to prepare for implementation.O*NET Task ID 14639 | 1.0 |
Develop testing programs that address areas such as database impacts, software scenarios, regression testing, negative testing, error or bug retests, or usability.O*NET Task ID 14640 | 1.0 |
Document software defects, using a bug tracking system, and report defects to software developers.O*NET Task ID 14641 | 1.0 |
Identify, analyze, and document problems with program function, output, online screen, or content.O*NET Task ID 14642 | 1.0 |
Monitor bug resolution efforts and track successes.O*NET Task ID 14643 | 1.0 |
Create or maintain databases of known test defects.O*NET Task ID 14644 | 1.0 |
Plan test schedules or strategies in accordance with project scope or delivery dates.O*NET Task ID 14645 | 1.0 |
Review software documentation to ensure technical accuracy, compliance, or completeness, or to mitigate risks.O*NET Task ID 14647 | 1.0 |
Document test procedures to ensure replicability and compliance with standards.O*NET Task ID 14648 | 1.0 |
Visit beta testing sites to evaluate software performance.O*NET Task ID 14662 | 0.0 |
Recommend purchase of equipment to control dust, temperature, or humidity in area of system installation.O*NET Task ID 21681 | 0.0 |
β = E1 + 0.5 × E2 · E1 = tasks where direct LLM access alone cuts time by at least 50%, E2 = tasks where software built on top of an LLM cuts time by at least 50%. Values take only 0 / 0.5 / 1.0.
Data sources & licenses — O*NET®, Anthropic Economic Index, Eloundou et al. (2023): see full notices on the Credits page