One person I knew at work had a question he used to always ask in interviews. One day while discussing this I asked him to show me some working code for his question. He struggles for a while then gives up(Note, this is his own question). Then he repeats the same trite - "We are just testing their approach".
And I was like "Oh sure, Their approach towards something whose answer you don't even know, to evaluate against."
Which correlates nicely to "You didn't solve it the way I would have, so you're obviously wrong."
The only answer in your Quora link that has a lot of upvotes is by the author of CTCI and she is saying just the opposite, and instead of blaming the interviewer she is putting all of the blame on the person being interviewed. I find this quite disturbing, and you are right there isn't accountability on the interviewer, here are the things the author of CTCI is saying:
> Maybe you came off as arrogant
> A number of different things could happen. But when someone asks this question -- why did I get rejected even after doing well -- the problem is nearly always in the second part: You didn't do well
> If you were interviewing with a big tech company, they have basically infinite programming spots. They don't reject someone because they found someone better; they just hire both.
> So despite what you think about your performance, you probably didn't show good algorithmic problem-solving skills
I'm all for self-introspection to assist in self-improvement but her persistence in ignoring the fact that interviewers are fallible is troubling, she is the go-to resource for probably most interviewees and interviewers and I don't like that she assumes that the thing that went wrong is "almost always" the fault of the interviewee. It's some grade-A BS.
- Are you an employer complaining there is a shortage of good developers?
- How many candidates have you rejected in the past?
- How many of those were because of a bullshit interview question? (Eg: Find the maximum subarray of an input array in O(n)...cannot be brute force....within 20 mins)
- If you have faced a shortage of developers, have you considered calling back the people you rejected for bullshit questions?
- If you don't have a problem finding engineers who can solve bullshit problems, your technique succeeded right? How many of those successful bullshitters have you fired or been disappointed by their performance at work? If the answer is zero..great. Don't ever fire them. Else, review your interview process.
Thanks
I've been in that situation: Once, at an old job, I had put in for a new role that had been created. There was also an outside candidate who'd applied for the role. Management felt that having me interview this candidate would have been a conflict of interest, considering, so I wasn't asked to participate.
I knew within 30 seconds of meeting him that he wouldn't last. He didn't. They gave him three months, and we all agreed in retrospect that he shouldn't have been hired at all.
In the interim, I did my old job, as well as his job (in the form of handholding him through everything he did more complicated than surfing the web), and was very quickly given the title of "Senior $role", with him as a direct report.
The other engineers and I spent hours, daily, working hand in hand with him, correcting his code, repeatedly suggesting the same things he could do to avoid having those problems with his code in the first place, &c.
That's just one example of what the thing I thought the grandparent meant by "false positive" can cost you. I'm sure there are worse.
I'm familiar with the argument. Erring on the side of caution is wise. Thinking that the current interview process saves you from this is stupid.
Gameable systems are won by people who focus on the game. They are not necessarily going to do well if the job requires something different
The current interview process is a GAME.
From the employer perspective, they can never be sure if they hired someone who memorized stuff for the interview or a really smart guy.
It's very similar to the current US election process. Everyone thought the forefathers made a rock solid constitution. The few cracks it had was fixed with amendments. Lo and behold, the only person who could make it to the top was the one who gamed the system and not someone with real merit.
Aren't the parallels strong?
P.S.: Not claiming Hillary is meritorious, but at least she's not one to make radical decisions without counsel
Exactly what I've been thinking about recently.
Isn't this true for a variety of things? The education system judging on the outcome of exam scores, elections, making money, marketing etc.
I wonder whether all this can be really be 'fixed'.
In interviews today, the expectation is that the candidate should be perfect, do this, that, don't forget to do this. But the interviewer has no such requirement. The interviewer can reject you because "They had a bad day".....seriously, this is what companies say. Look at some answers here: https://www.quora.com/What-are-the-possible-reasons-of-being...
So the candidate has to be PERFECT but the interviewer can reject because they are just HUMANS? How the hell does this make sense?
Maybe we need yelp for interviewers. A rating system will weed out bad interviewers and bad company policies.