So many interviewing red flags. The author does not seem to be interviewing critically – figuring out the skills to test and how to test them – but rather apply

So many interviewing red flags. The author does not seem to be interviewing critically – figuring out the skills to test and how to test them – but rather applying the techniques they have heard about or experienced themselves without consideration. There's a difference between programmers-who-google, and programmers that can only google, and I don't think the author is on a path to identifying one from the other, but rather has decided that googling things is wrong. I've conducted a lot of programming interviews, and I've always let candidates google and even encourage them to ask me for my thoughts and opinions. It's clear from what they ask, what they search for, and how they apply that information, how they go about solving problems and whether they truly understand the problem they are solving. Also by being present the whole time it's also obvious if the candidate works at the level of copy/pasting answers from the internet. The best engineers know how to ask questions and search for things in order to boost their productivity, while knowing enough about the problem to not be limited.