Comment

Comment by austin-cheney

This is only a problem if you are really really bad at conducting interviews. I have had interviews in the past that treated me like a child asking basic code literacy questions. These kinds of interviews aren't helpful to anybody.

Instead the way to get past this foolishness is to ask open-ended questions expecting precise answers where the questions are themselves not precise. This presents too much variance. For example: Talk to me about the methods of your favorite Node code library. In that case the candidate has to pick, on the fly, from any of the libraries that ship with Node and immediately start talking about what like about certain methods and how they would use them.

Another example: Tell me about full duplex communication on the web. AI will immediately point you to WebSockets, but it won't explain what full duplex means in 3 words or less or why WebSockets are full duplex and other solutions aren't.

Another example: Given a single page application what things would you recommend to get full state restoration within half a second of page request? AI barfs on that one. It starts explain what state restoration is, which doesn't answer the question.

In other words AI is not a problem so long as you don't suck as an interviewer.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton