I wonder what’s so hard with my interview. 5 years ago, even interns could do it, one of them could even tell the difference between UTF-8 and UTF-16.
Anyway, I guess it depends what compute layer you're interviewing for, but it doesn't necessarily sound like your interview process is broken, exactly. Like, it could be testing for the right thing, but in the absence of that thing, maybe you just need to find another thing that is substitutable.
It should be our real-life test, but it’s too long. It’s our most complicated algo, and honestly it’s very simple in the end. But given all the variables scattered around in a string.contains() (I don’t even look whether the result is correct, I look whether it’s structured for intelligibility and how they debug the off-by-1 errors), I can’t suppose a more complex algo will be done cleanly.
Maybe I’m mot giving them their chance - It might have taken time for me to output clean algorithms.
This used to happen in the 80s. I went to interview at a startup company in Mountain View in 1987. There was some chit-chat. Then the interviewer asked me to wire-wrap a circuit (diagram was provided) and power it on - he went away for about 1/2 an hour while I did that. He came back and complemented me on my neatness. He took me over across the room to talk to the VP of engineering who asked me when I would like to start. Those were the days.