Several students I have been trying to help enter the field are facing greater barriers than I have ever seen. Not just leetcode but dozens of interviewing rounds. The problems that they are asked also feel increasingly hard and it seems like interviewers are using AI during the interview while forbidding the interviewee from leveraging any external aids.
We are really burning the next class of developers with the current interview process
I cannot believe that companies are still using leetcode. That's just complete idiocy. The game is all about reading and understanding code now. Anyone who is still conducting timed code trivia examinations has completely lost the plot.
Stop cargo-culting your interview process, and use your brains!
[1]: Purely technical. There may be social reasons or legal consequences like "disparate impact" theories coming at you.
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.
Literal psychologists have done the research on this: A good, predictive interview is a small representative test of what people do in the normal job. Only us techbros seem arrogant enough to want to be the exception to decades of research.
Well then. If the "classic fallacy" is that job interviews should reflect the actual job, then what does it really matter what we do? Let's just have a big pub quiz. That measures "intelligence", too.
> You could test people on random cognitive tasks and predict their job performance.
Show me a single piece of evidence that memorizing code golf answers from a book is a valid proxy for intelligence, and we'll talk.
(Hint: You'll have better luck convincing me that it's a stealth way of discriminating against older, more experienced applicants who are further from undergrad and less willing to re-memorize Cracking the Coding Interview for the 150th time. Because it actually is.)
In any case, I do not understand this...Stockholm syndrome...that some programmers seem to have for the idiotic interview system.
I hadn't actually thought about it this way, but it makes sense. I'm in my early 50s and hella experienced and talented (if i do say so myself), but I refuse to do any interviews that require me to do any more preparation than researching the company I'm applying to.
It's obviously absurd, and while I almost understand it for a company that doesn't know you, you'll get hit with this stuff when you've been referred internally, by people you worked with in the past.
There is a century of data and studies that suggest cognitive ability is positively correlated across tasks. Conducting IQ tests for hiring is practically illegal in the US. Leetcode is the closest you get to an IQ test without tripping some laws.
Please use your intelligence to see the argument I am making, instead of nitpicking the example.
> Conducting IQ tests for hiring is practically illegal in the US. Leetcode is the closest you get to an IQ test without tripping some laws.
No, it isn't. Disparate impact is. Any test that has a disparate impact on a protected class is de facto illegal, but there's case law surrounding IQ tests.
By the way...ironically enough, Griggs v. Duke Power established that any intelligence test must have relevance to the job responsibilities, which sort of blows a hole in your entire theory of the case that this is a "classic fallacy".
I think I'm gonna get a stroke reading this. The classic fallacy is the nonsense you're spouting — that there's anything besides the job itself that is relevant to it. You're hiring people for x, so the only thing you care about is their ability to do x. This is obvious.
The perfect test is just hiring someone on the spot and seeing how they perform. We don't do this because it's expensive but obviously it would be the perfect test, measuring exactly what you're hiring for, by definition.
So then any test that goes further and further away from that ideal becomes worse and worse at predicting job performance. The trick is figuring out a good enough test that's still reasonably quick and cheap to do.
Deliberately going out of your way to test your canditates for something unrelated to the job is insanely stupid.
It's essentially just arrogance. Arrogantly asserting that you know for sure your particular "generic" test actually selects for ~all traits you want while also rejecting ~all traits you don't. I assure you, the chances of you having a good enough model of reality to do this are laughable. Pure arrogance.
Again, easiest to see by thinking of the opposite example to before — the worst test possible would of course be something completely unrelated, so idk, having a chef play ping-pong. I'm sure you could convincingly argue it tests something, but why in the world would you not just have him make a dish, since you know, that's what you're hiring him to do? (it's not actually by the way, now that's a classic fallacy — that the job is the mechanical subset of it and not the job as a whole. Soft skills, anyone? sigh).
I've seen someone suggesting that since a lot of programmers like playing Factorio, why not interview people by having them play Factorio? Ah, because then you're selecting for Factorio players. Do you have a good model of what makes a good Factorio player? Hell, do you have a good model of what makes a good performer at your job? You absolutely do not. Why select for Factorio players when you can select for your-job players?
Another common example of this utter arrogance is thinking that a candidate's performance during a highly stressful, unnatural, and artificial classic interview grilling environment is indicative of their perfomance in the every day feeling-secure-in-their-job state of mind. Oh, look, this fool I'm basically abusing from my position of power is stammering and squirming, must mean he's a good-for-nothing loser! Hah, another fraud found!
So sure, keep putting people in as much stress as possible and asking them how many golf balls fit in an airplane. BTW, I walk out of such interviews immediately. Have fun with your new Leetcode grinder performative actor hires though — you get what you test for.
Leetcode could be replaced by learning a made up language, memorizing a huge list of numbers, or reciting an epic poem.
The Leetcode game is mostly memorizing pre-existing solutions and then practicing applying them to lots of variations of the same problem.
The real filter is psychological: will you jump through hoops even when they don't make sense?
The argument that you can use the the artifact of the coding challenge as a starting point for further discussion is perhaps true, but it's like saying that you can use an applicant's resume as a starting point for discussion, once you've filtered out everyone who failed a keyword search.
So maybe we should try testing for that skill. This is not a hard thing to do, and there are many, many functional responsibilities and traits that a professional developer requires, which go beyond this.
Here are but a few, off the top of my head: spoken communication, written communication, time management, organization, focus, creativity, system design (aka architecture, as you suggest), planning.
It's always been painfully idiotic that we've used code golf for interviews, but the rapid advance of code robots has thrown it into sharp relief.
I wish you were correct. The trend is that nobody reads code anymore, AI writes it and people rubberstamp it with barely a glance (if even that, some companies might have AI rubberstamp it and off it goes into production).
My colleagues use the LLM to do that...
Unfortunately that means we may see more of these brain teaser / gauntlet style interviews.
Interviews are so hard
Though, there's a competing effect: as AI gets better, the amount of skill drops. Maybe the demand for seniors will turn into demand for juniors as AI improves at architecture, and the work shifts towards manual testing.
I'm already remotely prompting Claude through the "senior engineers" where I work. I'm not saying anything, but the company would probably be better off without them. The level of disconnect with the code has effectively turned them into dead weight. They'd be better off replacing them with manual testers.
The reality is that staying in a job and shipping what the managers ask for takes less skill.
The question is how long it will take management to notice and decide to do the next round of layoffs.