Every time I see complaints like this I can't help but think the posters have a chip on their shoulder from being rejected by Google or a similarly selective company. It's never a commentary on any fundamental issues with these types of interview questions and no one ever comes up with a better process that is equally scaleable and effective for hiring generalists. In my experience interviewing with dozens of small, medium and large companies, the vast majority of technical roles require these types of questions now. These come off as criticisms against Google specifically for asking hard variants of these questions.
I don't personally have any issue with companies asking questions like these as long as they don't simply look for "a correct and optimal solution coded up perfectly whilst under stress in under 30 minutes", but rather the process of solving the problem.
> If you don't come up with a close-to-optimal solution in about 5 minutes
Disingenuously hyperbolic. I was only given a single problem to solve in each of my 45 minute "coding rounds" at Google and Facebook. If you approach these interviews like a competitive coding competition you will absolutely not get the job. By that I mean arriving at a non-optimal solution as fast as possible while writing messy code and not explaining your thought process. Not to mention that senior roles involve an increasing number of interviews that focus on design rather than algorithmic questions.
This all seems like nonsense coming from individuals who are (understandably or not) frustrated at an interview process that doesn't align with their strengths.
In one of my interview rounds at google I was under huge time pressure, despite coming up with an optimal solution in seconds. That was an outlier as the interviewer was not aware of this solution, so explaining it took a long time. But still.
The valuable part from the competitive coding background is not the coding, but "inventing" solutions. In quotes because it's mostly a pattern-matching process. And it's a _huge_ advantage.
Personally I'm perfectly happy with the current process, as I took about half a year to become good at it, and the payoff is nice. :) But I'm convinced that's what this process selects for first and foremost - amount of preparation.
This all seems like nonsense coming from individuals who are (understandably or not) frustrated that others would suggest that their success was only due to an interview process that aligned with their strengths, rather than their obviously superior skill and intellect.
I'm not sure how this is a valid rebuttal to my comment since it addresses none of the point I made. Do you really think the secret sauce to getting into highly competitive jobs is by incoherently speed running through algorithm questions?
That way of interviewing is good, because it weeds out people who don't prepare and thus might be lazy or just looking for an easy paycheck. But it also tends to confuse good memory of technical and abstract questions as competence, and if you're not careful you'll end up with a lot of copy pasted humans that are really good at inverting binary trees, but suck at everything else. Also people who have already passed it tend to hold on to it as pride, and might fail an otherwise amazing candidate, just because of a failure on a question that has no practical use outside of a textbook. Those are my thoughts on it, and I'd wager the thoughts of many others who are critical of the model.
> Do you really think the secret sauce to getting into highly competitive jobs is by incoherently speed running through algorithm questions?
No, the real secret sauce is having a friend or relative on the inside. If you don't have that it's a gamble most of the time imo.
What you've basically told him is: "Your experience is false, you're just biased and whatever your success was is a lie."
I think so too, look at this angry (it says "fucking" 3 times) comment over at Reddit:
> It’s a waste of fucking time. I’m a really talented programmer [...] I’ve been eliminated based solely on messing up some dumbass arbitrary puzzle.
https://www.reddit.com/r/programming/comments/kcwqij/every_s...
And the only reply that to me somewhat seems to understand what's going on, getting lots of downvotes, so it got collapsed and you cannot easily find it:
> They just play a numbers game, and are able to discard perfectly capable candidates with this kind of questions, and still get a bunch of great candidates
https://www.reddit.com/r/programming/comments/kcwqij/every_s...
(although it started in a bit weird way with "Lmao", however the other replies weren't any more polite were they?)
Max himself later opened up[0] and admitted to being difficult to work with. It is entirely likely that he was rejected based on his personality and not his ability. As someone who contributed to Homebrew many years ago I would not be surprised if this was the case. In their own words: "I am often a dick, I am often difficult, I often don’t know computer science". I am not sure why any company would want to hire someone like that and put the culture of the team in jeopardy.
[0] - https://www.quora.com/Whats-the-logic-behind-Google-rejectin...
But yeah, other than the "sexiness" of CS concepts it's only because of the "narrative" we want to push.
This is a response I wrote elsewhere:
I've been growing Engineering teams for the last 10 years as hiring managers in different startups. At some point in our startup we had those kind of HackerRank questions as filters.
The thing we realized is that those sort of interviews optimize to hire a specific type of very Jr Engineers who have recently graduated or are graduating from CS. That is because those are the people that have the time to churn these types of "puzzle" problems. Particularly, there are 3 types of recent graduates from CS or related fields: The ones that don't know crap, the ones that focus on these sort of problems, and the ones that are "generalists" because they dove into all sort of subjects during their degree.
I found out that the Jr people that excel at those sort of problems have a huge learning curve to climb to be productive in "production", real life environment. On the contrary, the "generalists" work better.
We stopped doing those sort of algorithm puzzles interviews after that realization, and we started getting really good Engineers with great real-life experience.
or maybe the person struggles to work things out in an extremely stressful situation
I speak as somebody that finds interviews Extremely stressful and if working there is regularly my interview levels of stress then please do reject me.
"Dev ops was too busy out counting all the street lights in the United States"
If it was a Consulting interview any one would have gotten in. Thankfully no one asks these at G.
> Did they try to fix them by inverting a binary tree?
>> Yeah maybe implementing a quick LRU cache on the nearest whiteboard will help them out here
>> Did they try checking what shape their manhole cover is?
>> Dev ops was too busy out counting all the street lights in the United States
[1] https://www.reddit.com/r/programming/comments/kcwqij/every_s...