# Answers about AI hiring and work

Question-first access to curated evidence records. These summaries are not original experiments, product tests or legal advice. Preserve scope and limitations; cite the primary source for its findings and the record for editorial analysis.

Gene Dai is a co-founder of Metix AI; that commercial relationship matters when reading the hiring analysis.

Canonical: https://digidai.github.io/answers/

JSON: https://digidai.github.io/answers/index.json

## Does an AI assessment still need job-related validation?

SHL's AI principles require reliability, validity and job relevance for AI assessments, as for other assessments. The document also treats explainability as a design requirement.

Scope: Publicly indexed excerpt of vendor AI-assessment principles; direct document retrieval failed during review. Not a technical manual for a named test or employer.

Limitation: Principles alone do not establish predictive validity, accessibility or subgroup performance for your assessment, language and applicant population.

Next check: Request the technical manual, validation cohort, norm group, accommodation process and monitoring plan for the exact instrument and scoring version.

Source: [SHL: Core Principles for the Ethical and Effective Use of AI to Assess Talent](https://www.shl.com/assets/documents/how-shl-is-using-ai-and-machine-learning-white-paper.pdf)

Source date: Not stated; checked: 2026-09-08; evidence: vendor_documentation.

Record: [SHL](https://digidai.github.io/research/ai-hiring/#shl-assessment-validity)

## Which input and output does the assessment actually use?

HireVue publishes an AI explainability statement describing its assessment approach. Treat that statement as a starting point for tracing candidate inputs, scoring and human decisions.

Scope: Indexed excerpt and publisher description of the named 2024 statement; full-PDF retrieval exceeded the review tool's size limit. It cannot automatically describe later products or a customer's current configuration.

Limitation: A public explanation does not verify the current model, enabled modalities, score use or retention settings in a prospective deployment.

Next check: Ask for the current statement, exact input modalities, model version, candidate notice, deletion controls and how an assessor can contest or override an output.

Source: [HireVue 2024 AI Explainability Statement](https://www.hirevue.com/wp-content/uploads/2024/09/HV_2024_AI-Explainability-Statement.pdf)

Source date: 2024; checked: 2026-09-08; evidence: vendor_documentation.

Record: [HireVue](https://digidai.github.io/research/ai-hiring/#hirevue-explainability)

## Who defines the criteria used to review applications?

Ashby documents job-specific resume criteria for AI-assisted application review, with organization-admin enablement and role-level permissions for editing criteria.

Scope: Documented configuration of application review, not observed screening accuracy or a guarantee of plan entitlement.

Limitation: A resume can omit a skill the candidate has. Criteria matching is not a validated measure of future job performance.

Next check: Test ambiguous and incomplete resumes; identify who can change criteria, how changes are logged and whether a reviewer sees the underlying evidence before rejecting anyone.

Source: [Ashby: AI-Assisted Application Review](https://docs.ashbyhq.com/ai-assisted-application-review)

Source date: Not stated; checked: 2026-09-08; evidence: vendor_documentation.

Record: [Ashby](https://digidai.github.io/research/ai-hiring/#ashby-application-review)

## Does the audit cover the feature you plan to enable?

Greenhouse's AI principles page says Talent Matching and AI Interviewer undergo independent monthly bias audits by Warden AI. This record captures the vendor's claim, not a review of those audit reports.

Scope: Named features and vendor-stated audit cadence on a public principles page.

Limitation: An audit cadence does not specify the dataset, tested model version, selection thresholds, exceptions or applicability to a customer.

Next check: Obtain the latest feature-specific report, auditor identity, test dates, sample sizes, excluded groups and documented limitations. Compare them with the deployment you are buying.

Source: [Greenhouse: Responsible AI in Recruitment for Hiring Teams](https://www.greenhouse.com/ai-principles)

Source date: Not stated; checked: 2026-09-08; evidence: vendor_documentation.

Record: [Greenhouse](https://digidai.github.io/research/ai-hiring/#greenhouse-ai-audit-claims)

## Can one employer's audit stand in for yours?

Workday publishes a Secretariat analysis of its own Spotlight deployment. Testing completed March 20, 2026; the stated applicant period is September 1, 2025 through February 28, 2026.

Scope: U.S. residents applying for greater-New-York-City roles in Workday's own hiring; selected high-volume job profiles and demographic-data exclusions are described in the source.

Limitation: Workday explicitly limits the analysis to its implementation and says the page does not satisfy a customer-specific legal obligation. It is not a universal fairness certificate.

Next check: Compare your job mix, thresholds, candidate pool and human review with the reported scope; request evidence for the currently deployed model and your own use case.

Source: [Workday: Responsible AI and Bias Mitigation for HiredScore Spotlight](https://www.workday.com/en-us/legal/responsible-ai-and-bias-mitigation.html)

Source date: Not stated; checked: 2026-09-08; evidence: vendor_audit_summary.

Record: [Workday / HiredScore](https://digidai.github.io/research/ai-hiring/#workday-spotlight-audit-scope)

## Which contracted module performs the promised workflow?

UKG publishes separate service descriptions for Pro HCM, Pro Workforce Management, Ready and AI-related services. A product-family name is not a complete statement of the purchased scope.

Scope: Public service-description directory, not an executed order form, statement of work or customer entitlement.

Limitation: A feature appearing in the portfolio does not prove it is included, configured, supported in a country or connected to the employer's ATS.

Next check: Map each promised action to a module, order-form line, implementation owner, data integration, country scope and acceptance test.

Source: [UKG: Services Descriptions](https://www.ukg.com/legal/services-descriptions)

Source date: Not stated; checked: 2026-09-08; evidence: vendor_documentation.

Record: [UKG](https://digidai.github.io/research/ai-hiring/#ukg-contract-scope)

## Can AI assistance improve measured output at work?

The published study reports a 15% average increase in issues resolved per hour after AI assistance was introduced, with different effects across worker experience levels.

Scope: Staggered introduction of assistance to 5,172 customer-support agents. This is the published QJE version, not the earlier 5,179-agent working-paper version.

Limitation: Issues resolved per hour is a task-productivity outcome in one setting, not an economy-wide employment, wage or headcount estimate.

Next check: Compare the work and experience mix with your team; count quality and escalations alongside throughput.

Source: [Brynjolfsson, Li and Raymond: Generative AI at Work (QJE, 2025)](https://academic.oup.com/qje/article/140/2/889/7990658)

Source date: 2025-02-04; checked: 2026-09-08; evidence: field_study.

Record: [Customer support productivity](https://digidai.github.io/research/ai-employment/#support-qje-2025)

## Did early-2025 coding tools always save time?

METR's randomized study found that permitting AI tools increased task-completion time by 19% in its sampled experienced open-source developers.

Scope: 16 developers, 246 tasks in familiar mature repositories; tools from February through June 2025.

Limitation: This result is not a ranking of current coding products and does not represent all developers, unfamiliar repositories or later models.

Next check: Read the 2026 follow-up before citing this as evidence about current tools; measure accepted changes and review time locally.

Source: [METR: Early-2025 AI and Experienced Open-Source Developer Productivity](https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/)

Source date: 2025-07-10; checked: 2026-09-08; evidence: randomized_experiment.

Record: [Experienced developer productivity](https://digidai.github.io/research/ai-employment/#metr-developers-2025)

## Can the follow-up settle the current speedup?

METR says its follow-up provides an unreliable estimate of current productivity effects because of participant and task selection, plus measurement difficulties with concurrent agents.

Scope: Update on the experiment begun in August 2025, separate from the early-2025 randomized result.

Limitation: Raw follow-up estimates should not be advertised as a clean causal estimate or a definitive reversal of the earlier result.

Next check: Look for revised study designs and report who declined AI-disallowed tasks. Count concurrent-agent time consistently.

Source: [METR: We are Changing our Developer Productivity Experiment Design](https://metr.org/blog/2026-02-24-uplift-update/)

Source date: 2026-02-24; checked: 2026-09-08; evidence: methodology_update.

Record: [Developer study selection bias](https://digidai.github.io/research/ai-employment/#metr-selection-2026)

## Does potential exposure mean jobs disappear?

ILO and NASK estimate that about one in four jobs worldwide is in occupations potentially exposed to generative AI; the source distinguishes transformation from replacement.

Scope: Global task-based exposure classification, combining occupational tasks, expert input, AI scoring and labor microdata.

Limitation: Potential technical exposure is not observed adoption, feasible whole-job automation or a forecast of layoffs.

Next check: Pair exposure with actual adoption, wages, employment and transitions in the geography being discussed.

Source: [ILO / NASK: Refined Global Index of Occupational Exposure](https://www.ilo.org/resource/news/one-four-jobs-risk-being-transformed-genai-new-ilo%E2%80%93nask-global-index-shows)

Source date: 2025-05-20; checked: 2026-09-08; evidence: exposure_model.

Record: [Global occupational exposure](https://digidai.github.io/research/ai-employment/#ilo-exposure-2025)

## What can an exposure indicator predict on its own?

ILO's 2026 methodological brief warns against reading exposure measures alone as predictions of job losses or labor-market outcomes.

Scope: Interpretive guidance on exposure indicators, rather than a new measured job-loss count.

Limitation: The warning does not imply no displacement; it specifies what this type of indicator cannot establish.

Next check: Identify which result is an exposure score and which uses actual labor-market outcomes before combining studies.

Source: [ILO: What AI exposure indicators reveal about jobs](https://www.ilo.org/resource/news/new-ilo-brief-explains-what-ai-exposure-indicators-reveal-about-jobs)

Source date: 2026-04-17; checked: 2026-09-08; evidence: methodology_update.

Record: [Interpreting exposure indicators](https://digidai.github.io/research/ai-employment/#ilo-indicators-2026)

## Are employment changes concentrated in particular groups?

Stanford's August 2026 revision reports a 19% employment gap for young workers in highly AI-exposed occupations relative to less-exposed peers, while reporting no widespread economy-wide displacement.

Scope: ADP payroll evidence through June 2026. Workers aged 22 to 25 in the two most-exposed quintiles are compared with similarly aged workers in the three least-exposed quintiles, relative to November 2022.

Limitation: The authors describe these as non-causal patterns, with education, pre-trends and representativeness caveats. The gap is not AI-caused layoffs, an unemployment rate or 19% of all young workers losing jobs.

Next check: Check the paper revision, cohort definition, comparison group and robustness checks before making a causal or national-population claim.

Source: [Stanford Digital Economy Lab: Canaries August 2026 update](https://digitaleconomy.stanford.edu/news/canariesaug26/)

Source date: 2026-08-12; checked: 2026-09-08; evidence: observational_study.

Record: [Young workers and employment](https://digidai.github.io/research/ai-employment/#stanford-canaries-2026)

## Do reported task benefits show up in average labor outcomes?

The March 2026 NBER revision estimates null effects on earnings and recorded hours at worker and workplace levels, ruling out effects larger than 2% in its study horizon.

Scope: Danish adoption surveys linked to administrative records, studying the first two years after ChatGPT. Previously titled Large Language Models, Small Labor Market Effects.

Limitation: Null average earnings and hours effects do not mean no task change, no benefit for individual adopters or no future employment effects elsewhere.

Next check: Use the revised title and estimates; distinguish the measured horizon from the publication date and the earlier version's estimates.

Source: [Humlum and Vestergaard: Still Waters, Rapid Currents (NBER 33777, March 2026 revision)](https://www.nber.org/papers/w33777)

Source date: 2026-03; checked: 2026-09-08; evidence: observational_study.

Record: [Earnings and recorded hours](https://digidai.github.io/research/ai-employment/#denmark-labor-2026)

## What does usage telemetry say about employment?

Anthropic's June 2026 report changes its sampling and classification pipeline to study hourly use and outputs, with separate reporting for Claude conversations and first-party API traffic.

Scope: Vendor-observed use of Claude products and first-party API; methods changed from earlier seven-day report samples.

Limitation: Claude usage is not a representative sample of all workers, a verified task-success census or a causal measure of jobs created or lost.

Next check: Read the methodology appendix before comparing report editions; keep platform use, self-reported benefits and administrative employment outcomes separate.

Source: [Anthropic Economic Index: Cadences](https://www.anthropic.com/research/economic-index-june-2026-report)

Source date: 2026-06-26; checked: 2026-09-08; evidence: usage_telemetry.

Record: [Observed Claude usage](https://digidai.github.io/research/ai-employment/#anthropic-cadences-2026)