5 ms·
> If I am running the company, I would MUCH rather operate short-handed than "fix" my recruiting problems by lowering the bar. Nobody is talking about lowering
by jjav 5y ago
> If I am running the company, I would MUCH rather operate short-handed than "fix" my recruiting problems by lowering the bar.
Nobody is talking about lowering the bar, but of putting the bar in the right zipcode.
An extremely high bar of leetcode testing is irrelevant to the actual job, so that's an irrelevant bar.
- mcguire 5y agoAnd yet, those companies seem to be more successful than others with "more relevant" bars.
- Retric 5y agoLeet code interviews only showed up late in these companies trajectories. Internally it’s no longer about what the company wants so much as what people inside the company want which presents huge conflicts of interest. Google for example has done significant research and found such practices wasteful, but internal culture is what it is. In practical terms the FAANG companies internal processes are horrible and they can’t seem to innovate at all, but as long as they continue to print money there is zero reason to risk change.
- mech422 5y agoGoogle actually admitted their 'elite' leet code interview process didn't actually help the outcomes... This is the first link I dug up about it: https://www.theatlantic.com/business/archive/2013/06/google-finally-admits-that-its-infamous-brainteasers-were-completely-useless-for-hiring/277053/ https://www.theatlantic.com/business/archive/2013/06/google-...
- dmoy 5y agoThat isn't about the leetcode interviewing. That's about the microsoft-era actual riddles, like "if you were reduced to the size of an ant and put in a blender, how would you get out?"
- mech422 5y agoeh - I wouldn't be surprised to see the same article about the leetcode stuff. Maybe using methods that have nothing to do with the job, just don't lead to good results ?
- xyzelement 5y agoSo let me get this straight, you cited a random "first link you dug up", unrelated to your point, and claim it as evidence because you "wouldn't be surprised" if some other article (that doesn't exist) supported your view?
- mech422 5y agoI didn't cite it, and I didn't say some other article existed.. What I said was basically "google admitted their old method didn't work, here's a link if your interested. I wouldn't be surprised if the new method doesn't work either, and we see articles about that in a few years" The I "wouldn't be surprised" part comes from both methods actually having very little to do with the job at hand, and therefore I think they would BOTH be bad predictors of performance at that job..
- xyzelement 5y ago// What I said was basically "google admitted their old method didn't work, here's a link No. Your previous post said they admitted their "leet code" interviews didn't work. leetcode means something specific. Also I'd draw the opposite conclusion. Sounds like Google is "on it" in terms of evaluating what works and what doesn't. They threw out brainteasers because they didn't work. That suggests whatever they kept does work.
- mech422 5y agoFair enough. Can't say I agree with your 'on it' conclusion, but I guess time will tell. It took them about 15 years to get rid of the brain teasers (1998 to 2013ish from what I can tell), so if they're consistent we should hear one way or the other in 2028ish :-)
- yellowfish 5y agoGoogle's opinions on anything are overrated
- jjav 5y agoOr you could look at it as those companies have so much money and fame that they have tens of thousands of candidates pounding at their door so they can afford to arbitrarily reject approximately everyone. But if you're running a startup (target audience of ycombinator), you'd do well to play a smarter game since you can't outspend or out-fame the FAANGs. A big part of that is to have better interviewing practices than they do.
- xyzelement 5y agoThis may seem coldly logical but in the absence of my own researched opinions, I am evaluating the merit of the opinion about these interviews based on their origin: You have - companies that settled on this process, who have been able to attract top tallent that has cleared this bar. You have - employees of these companies that were able to clear the interview bar. And then you have - people who don't work for these companies, proclaim to have no interest/ability to clear the bar, but claim to have a valid view into where the bar should be. In the absence of other data it doesn't seem like the last group is likely to be objectively right
- pianoben 5y agoPersonally I suck at leetcode questions, but nevertheless have snuck in to some of these so-called "top-tier" companies. And let me tell you! These questions have fuck-all to do with the actual work the happens there. Sure, you can usually find someone to tell you how much rainwater accumulates into a random bar chart, but I see as much brain-dead code at the top as anywhere else. As much great code, too, FWIW. Everywhere, the key skills that make for a successful IC are the same, and they definitely don't require implementing splay trees or skip lists from scratch and without references. 99% of the time it's shuffling bits around and using hash maps. Honestly the people I work with who advocate the hardest for leetcode are the ones who had to grind hard and, evidently, want others to suffer too. As if a sane process would mean their own suffering was in vain.
- xyzelement 5y agoI am not sure that's the whole picture. I don't care about leetcode type problems but if I was applying for a job where they were a barrier to entry, I'd go figure out what it takes to master them. The bar may simply be "sober enough to understand what it takes to succeed at this task", "committed enough to prepare" and "smart enough to solve them" These attributes correlate strongly with success, I'd imagine.
- xemdetia 5y agoI disagree with this point because most interviewers and interviewees are novices, and giving them a task that gives straight pass/fail feedback optimizes for the wrong solution for people that can solve puzzles but not think about systems well. I've had many candidates be able to zip through puzzles but when asked relevant questions about building an understanding systems they wash out immediately. Most systems are more than one code file and I don't need to waste my hiring expenses teaching them how to think about systems from near scratch and having to heavy hand review them to write good code. I have generally found the only leetcode grind types to be less self sufficient and not really a signifier to success. In my experience the leetcode grind type can't even expand on their own answers to answer any useful questions like 'where and why would you use what you just made' and 'what technologies have you used that might utilize this technique' ends up with crickets. Right now my interview has a wash out coding exercise that is beginner oriented to get the resume liars but other than that it's all systems.