Live data from Hacker News

AI Broke Interviews

yusufaytas.com

61–70 of 132 posts

Re: AI Broke Interviews

#61
post #20

I’ve conducted about 60 interviews this year, and have spotted a lot of AI usage. At first I was quite concerned, then I realized that in nearly all cases I’d spotted usage, a pattern stood out. Of the folks I spotted, all spoke far too clearly and linearly when it came to problem solving. No self doubt, no suggestion of different approaches and appearance of thought, just a clear A->B solution. Then, because they of…

I interviewed a guy in person and he paused for 5 seconds, then wrote a perfect solution. I tried making the problem more and more complicated and he nailed it anyway, also after a brief pause. We were done in half the time. Maybe he just memorized the solution, I don’t know. Would you fail that guy?

It depends, I had some interviews like this that I suspected. For context, most of the interviews I conduct are technical design related where we have a discussion, less coding. So in those it is quite open ended where we will go, and there are many reasonable solutions.

In those cases where I’ve seen that level of performance, there have been (one or more of):

- Audio/video glitches.

- candidate pausing frequently after each question, no words, then sudden clarity and fluency on the problem.

- candidate often suggests multiple specific ideas/points to each question I ask.

- I can often see their eyes reading back and forth (note; if you use AI in an interview, maybe dont use a 4K webcam).

- way too much specificity when I didn’t ask for it. For example, the topic of profiling a go application came up, and the candidate suggested we use go tool pprof and suggested a few specific arguments that weren’t relevant, later I found in the documentation the same exact example commands verbatim.

In all, the impression I come away with in those types of interviews is that they performed “too well” in an uncanny way.

I worked for AWS for a long time and did a couple hundred interviews there, the best candidates I interviewed were distinctly different in how they solved problems, how they communicated, in ways that reading from an llm response can’t resemble.

Re: AI Broke Interviews

#62
post #52
post #48

Universities and education overall also had their foundation detonated by AI. Some Stanford classes now do 15 minute tricky exams to reduce the chance of cheating with AI (it takes some time to type it so the point is to make the exam so short that one can't physically cheat well). I am not sure what the solution for this mess is going to be.

Several possible solutions: 1. Strict honor code that is actually enforced with zero tolerance. 2. Exams done in person with screening for electronic devices. 3. Recognize that generative AI is going to be ambient and ubiquitous, and rework course content from scratch to focus on the aspects that only humans still do well.

Only 3) could scale but then those exam takers not using AI would fail unless they are geniuses in many areas. 1) and 2) can't be done when you have 50-70% of your course consisting of online students (Stanford mixes on-campus with CGOE external students who take the exams off-campus), who are important for your revenue. Proctoring won't work either as one could have two computers, one for the exam, one for the cheating (done for interviews all the time now).

Re: AI Broke Interviews

#63
post #56

I’ve mentioned it before, but it’s not just that people “cheat” during interviews with an LLM…it’s that they have atrophied a lot of their basic skills because they’ve become dependent on it. Honestly, the only ways around it for me are 1. Have in person interviews on a whiteboard. Pseudocode is okay. 2. Find questions that trip up LLMs. I’m lucky because my specific domain is one where LLMs are really bad at because…

Rather than trying to trip up the LLM I find it’s much easier to ask about something esoteric that the LLM would know but a normal person wouldn’t.

Re: AI Broke Interviews

#64
post #56

I’ve mentioned it before, but it’s not just that people “cheat” during interviews with an LLM…it’s that they have atrophied a lot of their basic skills because they’ve become dependent on it. Honestly, the only ways around it for me are 1. Have in person interviews on a whiteboard. Pseudocode is okay. 2. Find questions that trip up LLMs. I’m lucky because my specific domain is one where LLMs are really bad at because…

Rather than trying to trip up the LLM I find it’s much easier to ask about something esoteric that the LLM would know but a normal person wouldn’t.

That basically amounts to the same thing. LLMs are pretty good at faking responses to conversational questions.

Re: AI Broke Interviews

#65

Earlier quoted context omitted.

What you're describing sounds to me like just caring for the place we'll be spending half a decade or more and will have the most impact on our health, financial and social life. I'd advise anyone to read the available financial reports on any company they're intending to join, execpt if it's an internship. You'll spend hours interviewing and years dealing with these people, you could as well take an hour or two to u…

kinda silly given the ability of most people to infer anything substantial through finances and marketing copy really company reviews is all that matters and even that has limited value since your life is determined by your manger best you can do is sus out how your interviewers are fairing are they happy? are they stressed, everything else has so much noise to be worse than worthless

"Is the company consistently profitable or not?" and "Are revenue and profits growing over time, stable, or declining?" are very important questions to answer, particularly if stock grants are part of the compensation package.

For developers who work on products, getting a sense of whether the product of the team you'd be joining is a core part of the business versus speculative (i.e. stable vs likely to have layoffs) and how successful the product is in the marketplace (teams for products that are failing also are likely to be victims of layoffs) are also very important to understand.

Re: AI Broke Interviews

#66

I’ve conducted about 60 interviews this year, and have spotted a lot of AI usage. At first I was quite concerned, then I realized that in nearly all cases I’d spotted usage, a pattern stood out. Of the folks I spotted, all spoke far too clearly and linearly when it came to problem solving. No self doubt, no suggestion of different approaches and appearance of thought, just a clear A->B solution. Then, because they of…

> most engineers contemplate ideas, change their mind, ask clarifying questions I don't disagree at all. I find it slightly funny that in my experience interviewing for FAANG and YC startups, the signs you mentioned would be seen as "red flags". And that's not just my assumption, when I asked for feedback on the interview, I have multiple times received feedback along the lines of "candidate showed hesitation and ind…

I work for a FAANG, have done interview training and numerous interviews. We are explicitly trained that candidates should be asking questions, second guess themselves etc.

Re: AI Broke Interviews

#68
post #62
post #52

Earlier quoted context omitted.

Several possible solutions: 1. Strict honor code that is actually enforced with zero tolerance. 2. Exams done in person with screening for electronic devices. 3. Recognize that generative AI is going to be ambient and ubiquitous, and rework course content from scratch to focus on the aspects that only humans still do well.

Only 3) could scale but then those exam takers not using AI would fail unless they are geniuses in many areas. 1) and 2) can't be done when you have 50-70% of your course consisting of online students (Stanford mixes on-campus with CGOE external students who take the exams off-campus), who are important for your revenue. Proctoring won't work either as one could have two computers, one for the exam, one for the cheat…

Well realistically exam takers not using AI will fail in any sort of real world technical / professional / managerial occupation anyway. They might as well get used to it. Not being able to use LLMs effectively today is like the equivalent of not knowing how to use Windows 20 years ago.

Re: AI Broke Interviews

#69
post #8

> Interviewing has always been a big can of worms in the software industry. For years, big tech has gone with the LeetCode style questions mixed with a few behavioural and system design rounds. Before that, it was brainteasers. Before Google, AFAIK, it was ad hoc, among good programmers. I only ever saw people talking with people about what they'd worked on, and about the company. (And I heard that Microsoft sometime…

IIRC Google had an even higher bar in their early days: candidates had to submit a transcript showing a very high GPA and they usually hired people only from universities with elite CS programs. No way to prep for that. They only gave it up years later when it became clear even to them it wasn't benefiting them.

> IIRC Google had an even higher bar in their early days: candidates had to submit a transcript showing a very high GPA and they usually hired people only from universities with elite CS programs.

Which sounds like a classic misconception of people with no experience outside of a fancy university echo chamber (many students and professors).

Much like Google's "how much do you remember from first-year CS 101 classes" interviews that coincidentally looked like maybe (among my theories) they were trying to make a metric that matches... (surprise!) a student with a high GPA at a fancy university.

Which is not very objective, nor very relevant. Even before the entire field shifted its basic education to help job-seekers game this company's metric.

Re: AI Broke Interviews

#70
post #20

Earlier quoted context omitted.

I interviewed a guy in person and he paused for 5 seconds, then wrote a perfect solution. I tried making the problem more and more complicated and he nailed it anyway, also after a brief pause. We were done in half the time. Maybe he just memorized the solution, I don’t know. Would you fail that guy?

It depends, I had some interviews like this that I suspected. For context, most of the interviews I conduct are technical design related where we have a discussion, less coding. So in those it is quite open ended where we will go, and there are many reasonable solutions. In those cases where I’ve seen that level of performance, there have been (one or more of): - Audio/video glitches. - candidate pausing frequently a…

The point is that I interviewed the guy in person and he nailed it 200%. If you interviewed him online you would likely come to conclusion he’s a fake per the criteria you specified, wouldn’t you?
Post reply on HN