TRV-2026-1383Version 1 · Certified

Written 2026-10-15 01:08:57 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-1383
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-10-15T01:08:57.735643Z
status: published
lens: p_space
sector: labor
headline: Dystopian and dehumanising: that’s what it felt like when I was interviewed by an AI assistant | Giselle Au-Nhien Nguyen
dek: Over the past 15 years of my working life, I’ve done a lot of interviews for a lot of different jobs and industries: call centre operator, social media manager, bookseller, copywriter, library worker. Recently, after completing my first year of a master’s degree in early childhood and primary teaching, I applied for a preschool education role and experienced a first: being interviewed by AI. I’d heard of this practice and was aware of its shortcomings, from how demoralising it is to the risk of discrimination. Y…
gain_title: (none)
problem_title: An AI interviewer ended a candidate's interview when she paused to think, could not answer her questions about the role, and left her without any human contact, so she withdrew from the application.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: An AI interviewer ended a candidate's interview when she paused to think, could not answer her questions about the role, and left her without any human contact, so she withdrew from the application.
problem_evidence: I was booted off the interview entirely
quick_read: A teaching student who applied for a preschool education job at a not-for-profit kindergarten was shortlisted, then found the interview would be run by an AI assistant over video. During the session she was removed after pausing to think. Her own questions were answered only by repeating the job ad, and she was told to speak to a manager for anything more.

The account matters because it shows how automated screening can feel to applicants, particularly in a caring profession, and how little recourse they may have. It is a single personal essay, so it cannot show how common such interviews are or how they affect hiring outcomes. The organisation's view is not given.
limitation: The piece is a single first-person account, and she says she does not know whether the AI interview was only a first stage of the recruitment process.
tag: Evidence-backed problem
key_points: The writer has 15 years of work history and was applying for a preschool education role after one year of a master's in early childhood and primary teaching. | She was cut off from the interview after pausing to consider a difficult question and had to restart it. | The AI repeated the job advertisement in response to her questions and referred her to a manager for clarification. | The organisation's website reportedly used AI photos of educators, which made her wonder about labour erasure. | She withdrew and emailed her reasons, but over a month later had received no reply.
rundown: The interview was with a disembodied voice that greeted her by name, with a video window showing only herself. She described the setup as disconcerting, and she noted she had been alone the entire time.

After the experience she asked on early childhood forums whether others had been through it. Industry peers, including senior people, reacted with shock and said they could not believe it was happening.

She links the practice to the ongoing childcare crisis in Australia and argues that giving recruitment for such an essential, human role to a machine is lazy at best and negligent at worst. She mentions risks such as discrimination as known shortcomings but does not document them here.
sources:
- journalism | The Guardian | https://www.theguardian.com/commentisfree/2026/oct/13/dystopian-and-dehumanising-thats-what-it-felt-like-when-i-was-interviewed-by-an-ai-assistant | 2026-10-12
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
5afc994bb0655bf2239e41e308958597a27a34f0030841345673f55da309b431
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1383 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.