5 ms·
> Today's interview process seems eminently gameable by grinding LeetCode and watching YouTube videos on system design. That is a feature. You look at what the
by Jensson 5y ago
> Today's interview process seems eminently gameable by grinding LeetCode and watching YouTube videos on system design.
That is a feature. You look at what they worked on before to see if they are senior material. Then you do leetcode and system design to see if they are smart. A smart person would most likely learn whatever tech and problems they worked on, so if they do well on leetcode you just assume they did well in their past jobs. If they can't learn leetcode then you assume they did poorly in their past jobs. If they didn't practice leetcode then you got no signal on their smartness, so no-hire due to unpredictability.
So we get these possible results and what you do with it:
- Good leetcode, great and relevant experience: Hire at high level, this guy is smart so he likely learned a lot of things during his past experiences.
- Bad leetcode, great and relevant experience: no-hire, he might be smart but we don't know so we don't know if he actually performed in his past jobs.
- Good leetcode, no/minor expereince: hire at junior level, this guy will likely learn fast
- bad leetocde, no experience: don't hire, there are no positive signals.
This works really well actually. The only bad part is that some experts needs to brush up on this when they want to find a new job, but for a well paying company that isn't a problem as millions of candidates gladly brushes up for the pay bump.
- JackMorgan 5y agoAs a former director of engineering who has hired many great developers and many terrible ones, I can safely say that grinding leetcode isn't a valid signal for smart, just for conformity, ego, and time. Some of the worst developers I know could crush leetcode all day. Yes, it's an easy signal, it makes an unpredictable and messy process feel neat and binary. However, it is a false signal, and no amount of personal comfort changes that it has about as much effect on future employee productivity as hiring by height or favorite color. Unfortunately, software productivity is never going to be measurable. Therefore we will never ever have a reliable metric to even prove to ourselves that we are more or less productive than our coworkers, much less worth hiring. This fact should sober our prideful arrogance about hiring and introduce some humility. Our best practices are a farce with absolutely zero data to back up their validity. Ask yourselves where are the studies that prove candidates who crush leetcode perform better than those who couldn't? Where is the double blind research? We need a heaping dose of recognition that most of our best practices are there to validate the egos of the interviewers and give a neat binary decision without any mess. We have a toxic fraternity hazing ritual to make candidates bend the knee, with exactly zero evidence it works. We have the gall to call ourselves scientists, and we don't even measure a single thing.
- michaelrpeskin 5y agoYes! See my earlier comment about how we hire. Want to add agreement that grinding leetcode is a terrible metric. The ideal candidate probably already has a full time job and if you add in a family and other responsibilities, they don’t have time to focus on leetcode. Heck, they probably are tired of thinking at work all day and don’t have the mental capacity to task switch into leetcode after work (I know I don’t!) I think leetcode is an antisignal
- Mezzie 5y ago> Unfortunately, software productivity is never going to be measurable. Therefore we will never ever have a reliable metric to even prove to ourselves that we are more or less productive than our coworkers, much less worth hiring. This fact should sober our prideful arrogance about hiring and introduce some humility. Our best practices are a farce with absolutely zero data to back up their validity. Ask yourselves where are the studies that prove candidates who crush leetcode perform better than those who couldn't? Where is the double blind research? I think there is something similar to art in GOOD software development, as somebody who does both. The primary reason I don't like coding for a living is the same reason I don't like writing fiction for a living: I really dislike being creative on demand and on a schedule. I find it stressful. I can't make myself get a story idea any more than I can make myself find an elegant solution to a coding issue. Sitting and staring at the screen more isn't going to solve the issue for me. Software development is to math/CS what painting is to color theory. There is science, but there's also creation. That's why it's so hard to measure and hire for. Imagine trying to judge 1000 newly graduated oil painters who had all taken the exact same classes. How would you decide who was 'best'?
- moneywoes 5y agoI agree wholeheartedly. However, what is the alternative? There are way too many developers out there and too few jobs
- JackMorgan 5y agoI think the opposite is true, we're doing the same thing doctors and lawyers do: artificially restrict the supply, driving up demand and pay. Not top down and centralized, but individually and decentralized. There's plenty of jobs, almost every company reports a 10% shortage, but the developers won't let in anyone.
- tester756 5y ago>so if they do well on leetcode you just assume they did well in their past jobs. wat? how did you draw that crazy conclusion? even competitive programmers says that there's probably negative correlation between good engineer and competitive programmer and I'm saying this as a person who doesn't mind having to solve algo questions
- Jensson 5y ago> even competitive programmers says that there's probably negative correlation between good engineer and competitive programmer They don't. I've worked with some of the best competitive programmers in the world, they do think it is a positive and look for people with a strong competitive programming background. However, if your interview process only selects for ability to solve algorithm problems, then people with a lot of practice solving algorithm problems will over perform relative their level of talent, so when you run a dumb regression analysis it might look like competitive programming experience is a negative signal. So if someone has competitive programming experience then you want to bring them in for an interview, but you should probably be harder on them in the interview than regular candidates to account for this effect.
- tester756 5y ago>They don't. I've worked with some of the best competitive programmers in the world, they do think it is a positive and look for people with a strong competitive programming background. That's fair I'm unable to find what I've been reading, probably some thread on spoj (edit I found this [1]) or this https://codeforces.com/blog/entry/17302 https://codeforces.com/blog/entry/17302 for now I only found this https://www.youtube.com/watch?v=F4rykKLcduI&t=435s https://www.youtube.com/watch?v=F4rykKLcduI&t=435s by https://codeforces.com/profile/Errichto https://codeforces.com/profile/Errichto _____________________ [1] - https://discuss.spoj.com/t/spoj-a-praca-i-zycie/26380 https://discuss.spoj.com/t/spoj-a-praca-i-zycie/26380 https://en.wikipedia.org/wiki/SPOJ https://en.wikipedia.org/wiki/SPOJ Title: SPOJ & work and life It's written in Polish, but as I see that was about kinda different thing >How were SPOJ and programming skills useful in the context of your studies? >Virtually not at all. I will say more - these skills were an obstacle in obtaining the title of engineer. ><rant about higher edu institution> >... >How useful are SPOJ and specific, classic algorithms at the programmer's work? >Wandering around the labor market, I got the impression that it was easier to become a programmer with a vague idea of algorithms and extensive experience in creating specific projects than being a master of all kinds of algorithms, but without experience in coding something bigger. So the point was kinda different than I remember _____________________
- tkiolp4 5y ago> but for a well paying company that isn't a problem as millions of candidates gladly brushes up for the pay bump. This is the only relevant part of your comment. 90% of the tech companies out there should not rely on leetcode.
- Jensson 5y agoThe bottom 90% cargo cult this and don't get good results doing it, yes. I'm just explaining why the top companies run this.
- 62951413 5y ago"Bad leetcode, great and relevant experience" - that's me after 20 years in the industry and at least 30% of that time working on very non-trivial systems. I usually don't do actual leetcode actually, I review algo books before interviewing. In the last few years it stopped working for me even at no-name companies. But I find it nearly impossible to force myself to leetcode, it feels humiliating and stupid. Another thing I noticed is that they stopped asking questions about concurrent code or writing recursive-decent parsers. They seem to be strangely fixated on a narrow and not particularly practical subset of CS body of knowledge. We don't discuss OOP or its alternatives anymore. Companies don't seem to care about my actual hard-won real life experience even when it directly applies to the kind of domain/system they are building. Don't get me wrong, I expect people to know how to perform depth-first traversal or the general idea behind quick sort. But we are long past that stage even in small companies with average pay at least here in the SFBA.