Live data from Hacker News

Ask HN: How do you deal with obvious AI assistant usage in interviews

news.ycombinator.com

11–20 of 26 posts

Re: Ask HN: How do you deal with obvious AI assistant usage in interviews

#11
post #10
post #5

Earlier quoted context omitted.

they'll just click the "close eyes" filter button soon enough

What's this?

I think that's a joke. You know how you can apply filters with different backgrounds etc.

Instead there would be a filter where it looks like you have closed your eyes.

Re: Ask HN: How do you deal with obvious AI assistant usage in interviews

#13
I'd bet that still to this day, most interview questions test recall (of XYZ) and recall is what LLMs are best at. "Explain the difference between X and Y" or "what would you do in scenario Z" are search queries now. A lot more streamlined than individual google searches people would patch together from their search journey...

If I'd ever be doing a hiring spree, I'd give them a real problem. Put them in a position to think out loud. Not "what's the answer" but "walk me through how you'd approach this." Probe the reasoning. When they hit a fork, ask why they'd go left instead of right. Ask about tradeoffs they see. The best/real candidates will naturally say "I'd need to know more about X before deciding" because they're actually thinking through it.

IMO acknowledging the lack of information (without coming from a place of uninformed/non-experienced) almost impossible to fake with an overlay. LLMs always have an answer. Good engineers know when they don't.

Re: Ask HN: How do you deal with obvious AI assistant usage in interviews

#16
I'll go the opposite direction: if your Sr Release Engineer will use AI assistants (Claude Code, etc) on the job, let them use it in the interview.

The best interviews test critical thinking and problem-solving, not recall. AI makes generating solutions easier, but it also makes validating those solutions harder. That validation skill is what _actually_ matters now. Focus on that. "How do you validate that your solution is correct?" is a great next question.

I also don't think it's wrong to say, "I know you're using an AI tool, that's fine, but I'd like you to answer _this_ question without it. I'm trying to determine whether you can validate whether an AI is giving you good information."

But today? The toothpaste is out of the tube, my friend. AI assistants are ubiquitous in 2026. Pretending otherwise isn't a strategy that's going to lead you to success. Instead, it's just filtering out candidates who've adapted to modern tooling. And isn't the ability to adapt to change one of the best qualities of an engineer?

My advice: learn to interview people who use AI well. You'll hire someone who knows how to leverage it effectively, rather than actively selecting against people who do.

(And if you're asking "absurd questions" to catch AI users, you're just wasting everyone's time. Ask real problems and evaluate how they approach solutions, with or without assistance.)

Re: Ask HN: How do you deal with obvious AI assistant usage in interviews

#18
post #3

Are you telling them upfront that AI usage is forbidden? If not it's fair game.

I'm not sure if it's fair game, but I recommend to say it explicitly at the beginning of the interview, so everyone is in the same page.

Re: Ask HN: How do you deal with obvious AI assistant usage in interviews

#20
Just to clarify - i should have said this originally - it's not about the use of Cursor or Claude at all. I mean that they were using something that was listening to the conversation, and then automatically spitting out something for the candidate to say. I'm all for the tools and yes, it's an expectation that you will be not just familiar with, but a power user of tools like Cursor and Claude. I object only to what seems like "cheatware" for the whole process of the interview.

Candidates are also not themselves in these scenarios - IRL interviews show that immediately.

Post reply on HN