Moderate evidence
Published recordLaborProblem Space
More
First Impressions Always Last: How AI Disclosure On Job Descriptions Shapes Trust and Application Intention
- Truvace record
- TRV-2026-2572raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 42340a8874ff…check it
Artificial Intelligence (AI) is increasingly used to automate communication in organizations, including the creation of job descriptions. Yet little is known about how disclosing AI authorship affects potential applicants’ reactions. Drawing on signaling theory, this study examines whether authorship labels on job descriptions shape trust in the organization and intention to apply. We conduct a 3x1 between-subjects online vignette experiment (AI vs. human vs. no label) with 651 working-age participants from Germ…
The problem
In an online experiment with 651 working-age people in German-speaking countries, job descriptions labelled as AI-written reduced trust in the employer compared with human-labelled ones and lowered intention to apply compared with both human-labelled and unlabelled ones.
What this doesn’t fix
The study used an online vignette experiment with participants from German-speaking countries, so it measured reactions to hypothetical job descriptions rather than real application behaviour.
Sources
1 on file- Journal of the Association for Information Systemsaisel.aisnet.org
Cite this record
v1Truvace Impact Record TRV-2026-2572, v1: “First Impressions Always Last: How AI Disclosure On Job Descriptions Shapes Trust and Application Intention.” Truvace, 2026-11-12. /record/TRV-2026-2572 (accessed on the day you copy it). sha256 42340a8874ffeeca…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2572 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.
ace