| ▲ | mlyle 18 hours ago |
| Sure, random cognitive tasks are correlates of technical job performance. But there's plenty of people with high intelligence and problem solving that aren't good programmers, so we probably want to try to hone in on that a little bit instead of picking something with positive correlation. There are also tall people who are not great basketball players, and vice versa. If you can't do anything but measure height, maybe you should pick for your team that way... but if you aren't so restricted there's surely better ways to go. |
|
| ▲ | tkamat29 17 hours ago | parent | next [-] |
| Why would you want to hone in on finding "good programmers" though? Programming is not the end-all be-all skill of being a good software engineer, this was true even before AI but is even more true now. Leetcode is popular because: 1. It gauges problem solving ability and pattern recognition, which are essential to any job, and particularly useful for software engineers. 2. It is language agnostic - most jobs would rather have a strong engineer that doesn't know their particular language/tech stack than a weak engineer that is familiar with the stack. 3. It has objective evaluation criteria (correctness + time/space complexity). It's certainly not perfect, but I have yet to see an alternative that accomplishes all of the above. The one thing I can see potentially complementing it is the new style of AI-assisted assessment where you are dropped into an unknown codebase, and asked to make fixes/features that are assisted by an AI agent. This solves the language-agnostic issue with pre-AI versions of these interviews, where you had to have memorized specific tech stack features or language syntax in order to accomplish the task. Now AI can take care of that stuff, and the interviewee can focus on the problem solving aspect. |
| |
| ▲ | timr 17 hours ago | parent | next [-] | | > It gauges problem solving ability and pattern recognition, which are essential to any job, and particularly useful for software engineers. Proof of claim required. Leetcode primarily measure's someone's ability to memorize leetcode problems, and secondarily measures their ability to vomit this knowledge up in a stressful situation. There's an entire test-prep industry surrounding this interview method. Any undergrad will tell you that the way you pass leetcode interviews is to "grind". You'd have to be oblivious to not realize that the system has been gamed to hell and back. Since you are just asserting things, I will assert a simpler explanation: the primary reason Leetcode is popular is because it is cheap. If you have the problem that you have too many applicants and don't want to spend money interviewing them all, you have to come up with an efficient filter that doesn't violate hiring laws. You don't particularly care if the false negative rate is high, so a test of superficially relevant trivia is what you do. Even better if the trivia can be validated by computer! Setting aside the fact that almost no companies actually had this problem outside of FAANG, thanks to AI, the approach has gone from "somewhat relevant" to "completely irrelevant" within a couple of years. It's time to take it out back and shoot it. | |
| ▲ | 01CPMD3174 14 hours ago | parent | prev | next [-] | | Leetcode is popular because it gives hiring teams an objective 1)getting people to self select out of the process and 2)shortlisting the people who do opt-in. I’m sure the companies know that Leetcode is not a great indicator for likelihood to succeed in the role. If they had a perfect information about people, then would stop interviewing at all and just take the best people who applied. They don’t have perfect information. The information is highly asymmetric. The companies are just trying to not be efficient and not get burned. It sucks for candidates. But it makes sense for companies when they thousands of applicants they know effectively nothing about. | |
| ▲ | filipdobro 16 hours ago | parent | prev | next [-] | | Leetcode interviewing is popular because it barely requires any effort by the interviewer. It is a small, localized knowledge check of your DSA skills. No other profession requires you to invest this much time into the interviewing process. How about we look at past achievements, contributions and certifications, like in any other field? | | |
| ▲ | TeMPOraL 14 hours ago | parent [-] | | > How about we look at past achievements, contributions and certifications, like in any other field? In other fields, those things aren't nearly as meaningless and easy to game as they are in ours. | | |
| ▲ | filipdobro 10 hours ago | parent [-] | | I don't agree with that. No mechanic shop will test if you actually know how to change the brakes of a car. They have to gauge it from the interview process without doing the actual work. | | |
| ▲ | mlyle 5 hours ago | parent [-] | | The mechanic shop will figure out you don't know what you're doing really, really quickly though. Whereas when we hire someone it's often much longer before we get quality feedback. |
|
|
| |
| ▲ | jjav 14 hours ago | parent | prev [-] | | > Leetcode is popular because: Well, no. It rewards ability (and free time) to repeatedly work through problems and memorize the solutions. And it rewards acting skills so you can perform like you're discovering solutions on the fly, that you've actually memorized. That's all it does. |
|
|
| ▲ | tgma 14 hours ago | parent | prev [-] |
| Weeding out smart non-programmers is quite easy. Obvious by their resume and their non-coding interviews. I bet in an unlikely scenario that you fail to detect that, you probably have a pretty good hire who'll learn in a heartbeat. What you really want to weed out, at least at top-tier companies who can afford to be more selective, is people who have a resume, but are not that great at fundamentals. Most loud complaints seem to be of this nature: guy had N years of experience at previous company/is author of popular software, but couldn't get through basic linked list/recursion/BFS--as if this is not an acceptable bare minimum expectation of a professional in the field. Often people are too polite to say it out loud, but realistically, that is exactly when it is working as intended. |
| |
| ▲ | miroljub 14 hours ago | parent [-] | | It's not. In 99,99% of programming jobs you will never have to implement a linked list. And yet, interviewers pretend it's important to be able to write it on the blackboard. | | |
| ▲ | tgma 13 hours ago | parent [-] | | Not the point. If you have way more applicants than roles and you are paying well, given the choice between a programmer who cannot implement a linked list [really?] and one who can, you would hire the one who has that ability, even if all they do all day is to stare at Claude Code. |
|
|