I got to interview a lot of people in the past 2 years, and I noticed that new grads are REALLY good at solving Leetcode type of problems.
The expectation in the industry is that Senior people would be even better at it, because of their years of experience.
This,however, is not what I’ve seen on the ground. Most senior devs that I interviewed, who were clearly smart and experienced took much longer than new grads to solve most of the questions. Personally, I try not to hold it against them, if they can clear the bar, but I wonder how many other people do the same.
Also, I know in music they do blind interviews, were people perform behind a curtain to avoid any biases they might have (gender, race etc).
May be it’s time to do something similar in Software, since we already are prioritizing white board interviews above anything else?
Edit: I am not advocating for Leetcode types of questions. I do believe that most companies hire like this (including my current company, where I get minor if any say in hiring process). So just pointing out my observations regarding the status quo.
> The expectation in the industry is that Senior people would be even better at it, because of their years of experience.
The fact that a person with years of experience solves an interview question more slowly than a fresh out of college grad should be a huge red flag that our interview questions are bullshit and don't reflect real world challenges.
Exactly. So the arbitrary line drawn by leetcode interviews filters in one particular way and benefits people closer to colleges age where these kinds of problems are fresher in the mind. As you get older the number of leetcode style problems you actually encounter in real engineering is pretty low.
Have a chat, discuss experience and see how well they actually understand the things they have put on their resume. Dig as deep as you can and see if they actually understand what they say they have done. Also, references are at least as important as the interview.
I can only speak for myself, but hires on my team are usually based on my recommendation and I mainly try to tease out whether the candidate has enthusiasm and strong opinions about the languages and frameworks we work with. If I ask what their favorite stack is, or how they prefer to organize a project, and they just mumble their way through the answer, I think they are probably not a good fit.
Depends on the experience level of the interviewee. If they are fresh out of school I expect them to know algorithms and data structures and maybe some specific topic they studied at an advanced level (like compilers, db, graphics, etc). If they are 5-10 years into a career, they should have a lot of knowledge about whatever it is they've been doing. If someone says they have 5 years of Android programming, I'm going to ask them a lot of Android API questions as well as Java.
In either case, there are questions that have multiple difficulties of responses. The more experienced/capable they are, the more nuanced and complete their answers will be. For example, ask a Java person how GC actually works. Most people have very little idea, but the best talent knows a good bit more.
But there are other variables. I've known perfectly intelligent and productive coders who took months to build a really complex well architected system that didn't solve the business problem and hence were a bad hire.
>I've known perfectly intelligent and productive coders who took months to build a really complex well architected system that didn't solve the business problem and hence were a bad hire.
That's an interesting statement. Isn't it usually the job of product managers (or someone in management) to determine whether or not what's being done is actually wanted? It is not typical for developers to be brought on under the broad banner of "make us money please" and then set loose to email users and determine 100% of their own direction. Wouldn't the fact that the wrong program was being built have been caught in an informal "let me see how it's going" sort of status update?
Human beings went to moon before we had this coding test. this online coding test itself is indirect age discrimination..this is insanity needs to stop..except for few high end jobs most jobs don't use any of these need deep algorithmic knowledge..this has led to a cottage industry of books, websites etc..some younger folks prepare for 6+ months, go for weekend mockup tests etc...older folks don't have time or motivation to do any of these.
If you can see that clearly smart, experienced developers aren't very good at leetcode problems, what makes you think an aptitude for leetcode problems is a good measure of a developer?
The question isn't how much you should hold it against older developers, but how much you hold it against leetcode as a way of assessing developers.
The expectation in the industry is that Senior people would be even better at it, because of their years of experience.
This,however, is not what I’ve seen on the ground. Most senior devs that I interviewed, who were clearly smart and experienced took much longer than new grads to solve most of the questions. Personally, I try not to hold it against them, if they can clear the bar, but I wonder how many other people do the same.
Also, I know in music they do blind interviews, were people perform behind a curtain to avoid any biases they might have (gender, race etc).
May be it’s time to do something similar in Software, since we already are prioritizing white board interviews above anything else?
Edit: I am not advocating for Leetcode types of questions. I do believe that most companies hire like this (including my current company, where I get minor if any say in hiring process). So just pointing out my observations regarding the status quo.