I agree with what you're saying, but it can be immensely frustrating when you're rejected for a job when the interviewer themselves is actually wrong, which has happened a few times. I've been given technical questions in interviews, and I answer the questions correctly (I always double-check when I get home), and the interviewer pretty much tells me that I'm wrong.
For example, in an interview once I got the typical "design Twitter" whiteboarding question, and it's going fine, until the topic of databases and storage comes up.
I ask "do we want consistency or availability here?"
The interviewer says that he wants both. To which I say "umm, ok, but I thought you said you wanted this to be distributed?", and he said yeah that's what he wants.
So I have to push back and say "well I mean, we all want that, but I'm pretty sure you can't have stuff be distributed or partitionable while also having availability and consistent."
We go back and forth for about another minute (or course eating away at my interview time), until I eventually pull out my phone and pull up the Wikipedia article for CAP theorem, to which the interviewer said that this is "different" somehow. I said "it's actually not different, but lets just use assume that there exists some kind of database X that gives us all these perks".
Now, in fairness to this particular company, they actually did move forward and gave me a (crappy) offer, so credit there, but I've had other interviews that went similarly and I'm declined. I've never done it, but I've sort of wanted to go onto LinkedIn and try and explain that their interview questions either need to change or they need to become better informed about the concepts that they're interviewing for. Not to change anything, not to convince anyone to suddenly give me an offer, but simply to prove my point.
Not sure how the dialog went irl, but if the conversation was that adversarial and with as little diplomacy applied, I'd not hire the person nor accept the role if I was on either side of it...
For example, in an interview once I got the typical "design Twitter" whiteboarding question, and it's going fine, until the topic of databases and storage comes up.
I ask "do we want consistency or availability here?"
The interviewer says that he wants both. To which I say "umm, ok, but I thought you said you wanted this to be distributed?", and he said yeah that's what he wants.
So I have to push back and say "well I mean, we all want that, but I'm pretty sure you can't have stuff be distributed or partitionable while also having availability and consistent."
We go back and forth for about another minute (or course eating away at my interview time), until I eventually pull out my phone and pull up the Wikipedia article for CAP theorem, to which the interviewer said that this is "different" somehow. I said "it's actually not different, but lets just use assume that there exists some kind of database X that gives us all these perks".
Now, in fairness to this particular company, they actually did move forward and gave me a (crappy) offer, so credit there, but I've had other interviews that went similarly and I'm declined. I've never done it, but I've sort of wanted to go onto LinkedIn and try and explain that their interview questions either need to change or they need to become better informed about the concepts that they're interviewing for. Not to change anything, not to convince anyone to suddenly give me an offer, but simply to prove my point.