The short version
The argument everyone’s having is the wrong one
Most of what you’ll read about AI in a job search is stuck on a binary: is using it clever, or is it cheating? That framing misses the thing that actually determines whether it helps you. The real line isn’t AI or no AI. It’s whether the words are yours — drawn from what you’ve genuinely done — or borrowed from a model that’s averaging everyone.
The evidence backs this up from an angle people don’t expect. When researchers ran a controlled interview experiment, candidates who used AI actually scored higher on the content of their answers — but lower on how honest they seemed (Wiley, 2025). The tell wasn’t a robotic delivery. It was a faint sense that the person couldn’t fully stand behind what they were saying. That’s the whole problem with fabrication in one finding: it isn’t that you get caught by a detector. It’s that you can’t defend a story that was never yours.
Recruiters are anti-generic, not anti-AI
The fear that AI will get you flagged and rejected is mostly misplaced. Detection tools are unreliable — OpenAI quietly retired its own for low accuracy, and academic work shows they wrongly flag clear and non-native-English writers at high rates (Stanford HAI) — so recruiters rarely rely on them. What they react to is genericness: the interchangeable, detail-free application that could have been written for anyone. Surveys are consistent that employers are fine with AI-assisted, personal work and turned off by copy-pasted output. The failure mode isn’t assistance. It’s sounding like everyone else.
The three questions people actually ask
Can they tell?
Not reliably — and it’s the wrong thing to optimize. Chasing an “undetectable” score misses that the real risk is generic content, not a detector. See can employers tell if you used AI?
How do I keep my voice?
Feed AI your own material and edit hard — the voice is the part that gets you hired. See how to use ChatGPT without sounding like ChatGPT.
Is it cheating to prep with it?
No — preparing with AI is smart; the line is generating answers live and passing them off as your own. See should you use AI to prepare for an interview?
How to use AI well
- 1
Point it at your own experience.
Give it your real stories, results, and the way you actually talk. Its job is to retrieve and organize what you’ve done — not to make something up. - 2
Delegate structure, not voice.
Let it tighten and shape. Keep the specifics and phrasing that could only have come from you. - 3
Keep the concrete details.
The number, the turning point, the thing someone said. Specificity is the human signal — and the thing generic AI output strips out. - 4
Prepare; don’t perform.
Use it to rehearse before the interview, not to generate answers during it. You have to be able to defend every word in the room. - 5
Read it back out loud.
Cut anything that sounds like it could have been written to anyone. If it doesn’t sound like you, it isn’t done.
Where ELOQ stands
This is the whole idea behind ELOQ, and why it exists: AI pointed at your own experience — helping you remember what you’ve done, shape it, and rehearse it until it comes back naturally — never at inventing someone you’re not. Used that way, the question of who wrote it stops mattering, because the answer is you. For the argument in full, read AI Can Help You Remember. It Can’t Help You Pretend.