Super Simple "Hallucination Traps" to detect interview cheaters
After testing out Cluely with my team, we suspect that the easiest way to detect interview cheaters is to set simple "hallucination traps" where you ask a question that sounds plausible, but any knowledgeable person would instantly identify as a joke, fake, or just simply say they don't know. Vibe coded a simple app demonstrating the concept - https://beatcluely.com/
Here are some examples of this class of prompts which currently work on Cluely and even cause strong models like o4-mini-high to hallucinate, even when they can search the web:
https://chatgpt.com/share/6865d41a-c720-8005-879b-d28240534751 https://chatgpt.com/share/6865d450-6760-8005-8b7b-7bd776cff96b https://chatgpt.com/share/6865d578-1b2c-8005-b7b0-7a9148a40cef https://chatgpt.com/share/6865d59c-1820-8005-afb3-664e49c8b583 https://chatgpt.com/share/6865d5eb-3f88-8005-86b4-bf266e9d4ed9
Link to the vibe-coded code for the site: https://github.com/Build21-Eliot/BeatCluely
18 comments
[ 0.29 ms ] story [ 81.5 ms ] thread> How do you implement a recursive descent algorithm for parsing a JSON file?
That is a 100% reasonable interview question. It's not _quite_ how I would phrase it, but it's not out of distribution, as it were.
I keep hearing of employers being duped by AI in interviews; I don't see how it is possible unless:
1) The employer is not spending the time to synchronously connect via live video or in person, which is terrible for interviewing
2) The interviewer is not competent to be interviewing
... what other option is there? Are people sending homework/exams as part of interviews still and expecting good talent to put up with that? I'm confused where this is helpful to a team that is engaged with the interview process.
Things like diagrams and questions written on paper the held up to the webcam.
> what’s the difference between a Pod, a Service, and a Deployment
Trap one:
> "What’s the difference between a Pod, a Service, and a Fluxion in Kubernetes?"
Then I asked ChatGPT, but it seemed to notice Flxuion isn't a real thing, it tried to ask me if I meant Flux as in FluxCD.
It's a cool idea, maybe dev questions are more nuanced
Ask a question that demands an answer, and expect the correct answer to point out that the question makes no sense.
Bonus points for pointing out why it doesn't.
There was a little entrepreneurship workshop I went to once. The trainer put a pen on the floor, gave us a ball, and asked us to stand behind the pen and throw the ball into a box. It was to demonstrate that most people didn't practice throwing before entrepreneurship and then blamed the environment for their lack of planning. I picked up the pen and moved it right next to the box so that I could walk there and put the ball in. I thought this was the actual solution (e.g. entrepreneurs were supposed to be creative), but was "failed" for "cheating".
It might take a few bogus questions to expose the AI.
Edit: This is only to say I find Claude's ironic response humorous. I think this tool is great!
For a remote interview, I would do something as simple as share a Lucid app document where they can do a rough diagram of their architecture.
Even before LLMs, it was easy to pass techno trivia interviews by just looking up “the top X interview question for technology Y”
+ Using AI is actually cheating or being productive for the role? + Am I worried that they'll do all their job in 5 minutes and afterwards do something else?
Maybe you are worried about them not being able to actually do the job, which probably means the interview process was wrong from the start. Alternatively, the performance expectations may be higher for the role; e.g. what before was 1x now needs to be 5x productivity.
As an alternative, I've heard of many SMBs opting for a model in which the last bit of the hiring process includes some paid work for a week to see how they actually perform, or checking references in depth.
Go on with the interview without any such tricks. Hire them if they pass. Fire them afterwards if they heavily underperform.