IMHO it is also the reason they can't generally make their own (good) products any more, without acquiring / copying -- that is not the type of people they hire (more artistic / risk taker types).
And part of a real job involves solving real problems. In an interview, you have a very limited time, so you have to come up with questions that test the candidate's ability to solve problems within a certain timeframe.
Another example is from my own "worst interview ever" where the guy asked me to implement a BFS and a DFS on a tree. I mentioned that I'd literally been debugging an issue with a DFS algorithm all day at $dayjob, so should be a piece of cake. I wrote out the DFS example in 10s, but then when I got to the BFS, I spaced out on how to write a for-loop. The interview literally just laughed at me, saying, "that sucks for you" so instead I simply showed him how a BFS works and his answer was, "I don't care, I want to see code."
As an interviewer, I get it. I expect you to know concepts, not be able to perform rote actions and put on a show.
Either way, if a candidate misses such a question it shouldn't be a negative. Using such a question as a filter is a bit ridiculous.
I haven't done a whiteboarding interview for a while, but I remember them vividly. Hot flashes, sweating, stomach churning, anytime I'd be asked a question I am definitely capable of answering, my brain would shut down and refuse to start back up again. The most apt thing I could compare it to is stage fright. Even something like simply multiplying 2's would seem impossible to me in that state of mind.
Aside from seeking professional help for dealing with anxiety, I'd recommend programmers with anxiety to avoid whiteboarding interviews [1] or at the very least let it be known ahead of time that you get stage fright.
That was a turning point for me, because as far as questions go it was very fair. And yet, it had the same effect. 20 interviews later I was acing far more difficult questions, being rather polished (and ahem, interview questions aren't generally very unique). So I guess I interviews at that place too early. Maybe its useful? IDK. For me personally, it seems like really good people have a track record of shipping good stuff (or doing other good things in life), and can generally explain what it is and how it works. They usually have former colleagues you can talk to as well. Some of them even have side projects you can look at. But ah when the interview mill is in full steam, its hard to individualize to the candidate. We have a feature factory sir, and what we need are some good cogs. That's how you maximize the value you achieve from a developer after all!
That's my big problem (both as an interviewer and as an interviewee) with the current "best practices" in tech interviews. We're evaluating the wrong thing. This is how smooth talking, charismatic phonies breeze through and we find out in 6 months they can't code. Unfortunately by then, they've often gotten themselves promoted to Director.
Unfortunately acknowledging that you are in any substantive way human is a huge turnoff to these companies.
And approaching them with the suggestion that the interview process should have at least some resemblance to a 2-way street will be seen as a huge red flag, and a sure giveaway as to what an incorrigibly self-entitled primadonna you must be for even brokering that suggestion, as well.
I've found you often need to directly ask the interviewer not to do what they're doing when they try this sort of thing. Sometimes they're just bored and want to talk because there has been a moment of silence, or because they're enamored with their interview question.
If it was trivial, there'd be no point in asking.
It's a beginning question to get you warmed up.
Google didn't reject the candidate, the interview loop he got rejected him for any of the myriad of knee-jerk split-second decisions made on the candidate's character in an unnatural and stressful environment.
I've been in hundreds of interview loops at $Megacorp. You can stack the deck with preparation, but sometimes you just hit a loop that doesn't click with you.
But that's not how problem solving works. You need work your way from what you do know to get to an answer for what you don't. It's not guessing -- it's taking the background knowledge you do have and applying it to the problem at hand (and every engineer should have some background knowledge, even if it's just basic arithmetic).
That's what these kinds of questions are testing. Someone who immediately gives up is probably not going to be resilient in the face of new challenges.
I've quit several interviews because of these particular questions since they are simply wasting my time and not testing my "skills".
Well that's the opposite of what the interviewers are looking for. They DO want to work with such people.
As a candidate, if I do not know, I say I do not know. I can offer my thoughts on "but if I were to design this from scratch" based on my experience, but only if the interviewer is interested in that.
As an interviewer, I hate when candidates pretend (or believe) that they know something when they actually don't, and just confidently make stuff up like ChatGPT.
Possibly, but I’m sure these aren’t exact quotes after 15 years and I expect they reflect how the author remembers feeling a lot more than the actual conversation.
Edit: to clarify, your advice is good, what you said isn’t dumb. That criteria is dumb, in my opinion. I don’t want my colleagues to spend a bunch of my time guessing on an answer I could easily lookup or find on a calculator.
Companies want to hire people that do things, not question everything, regardless of whether those things ought to be questioned. You’re being hired to achieve business objectives, full stop.
In fairness, following your stated requirements; no one would ever be hired.
There's a direct contradiction such that it can never be true.
Hint: Descartes Rule of Method
conversely, it's reductive to compare it to a generic ban on saying "I don't know"
my first job was a startup I built, starting from being a waiter. There's a lot of people who don't even try, sort of reject the premise of engaging with the question.
Saying "I don't know", then looking at the interviewer, is about the least valuable interaction you can have with an interviewer, and there's a shocking # of people who do that: whether it be freezing up, some sort of implicit commentary on the question, or a form of performance art, whatever the implicit intent is, in 99% of cases, it doesn't serve you at all.
If I ask you how to fluffle nuffle the snorbknobs, you can at least come back with "I don't know, I may have misheard you: I've never heard of fluffle nuffle. Can you give me a hint?". If you're at the end of your rope with tech interviews: "Excuse me, those aren't sensical words, I'm worried you're having a stroke"
"I don't know" and silence is NPC stuff.
Remember to take you Vyvanse so that you can stay focused, and make sure to throw in some beta blockers so that you stay calm during this toxic hellscape of modern interviewing.
I am sure you also go to your employers and tell them that asking super unnatural questions in a super unnatural pressure environment is also a super negative signal.
You do this right? Right?
But if that doesn't come naturally to them, "prospective interview candidates" might also consider if that's really a problem. There remain plenty of fantastic engineering opportunities that don't involve memorizing dance steps.
In my experience the only reason you should say "I don't know" is if you're going to follow it with "but if I had to guess" or similar. Sounds like the interviewer definitely came on strong but being able to ace the psychological part of an interview is often as important or more important than the actual solution.