I’m not in a hiring position, but my take would be to throw in unrelated tools as a question. E.g. “how would you use powershell in this html to improve browser performance?” A human would go what the fuck? A llm will confidently make shit up.
I’d probably immediately follow that with a comment to lower the interviewee’s blood pressure like, ‘you wouldn’t believe how many people try to answer that question with a llm’. A solid hire might actually come up with something, but you should be able to tell from their delivery if they are just reading llm output or are inspired by the question.
It’s a fine line to walk, but I see what you’re getting at here. I wouldn’t want to come across as incompetent either, lest it reflect on the company. Your follow-up remark is brilliant. Delivery is everything, I suppose.
That was my body language cue. An ‘umm… 😅’ answer is a pass, as well as any attempt to actually integrate disparate tools that doesn’t sound like it’s being read. The creased eyebrows, hesitation, wtf face, etc is the proof that the interviewee has domain knowledge and knows the question is wrong.
I do think the tools need to be tailored to the position. My example may not have been the best. I’m not a professional front end developer, but that was my theoretical job for the interviewee.
I’m not in a hiring position, but my take would be to throw in unrelated tools as a question. E.g. “how would you use powershell in this html to improve browser performance?” A human would go what the fuck? A llm will confidently make shit up.
I’d probably immediately follow that with a comment to lower the interviewee’s blood pressure like, ‘you wouldn’t believe how many people try to answer that question with a llm’. A solid hire might actually come up with something, but you should be able to tell from their delivery if they are just reading llm output or are inspired by the question.
It’s a fine line to walk, but I see what you’re getting at here. I wouldn’t want to come across as incompetent either, lest it reflect on the company. Your follow-up remark is brilliant. Delivery is everything, I suppose.
Be careful tho because if you ask that with enough confidence I would think I am in the wrong.
"Powershell had OOP without me knowing for a few years so maybe it has hidden html usage too. "
That was my body language cue. An ‘umm… 😅’ answer is a pass, as well as any attempt to actually integrate disparate tools that doesn’t sound like it’s being read. The creased eyebrows, hesitation, wtf face, etc is the proof that the interviewee has domain knowledge and knows the question is wrong.
I do think the tools need to be tailored to the position. My example may not have been the best. I’m not a professional front end developer, but that was my theoretical job for the interviewee.