4 ms·
Our process is not particularly difficult, I’m not doing Leetcode or anything. I just ask questions at interview which test whether people have a surface level
by physicsguy 4y ago
Our process is not particularly difficult, I’m not doing Leetcode or anything. I just ask questions at interview which test whether people have a surface level understanding or whether we’ll have to hand hold people through things.
For e.g. I’ve interviewed backend devs with 5+ years of Django experience who haven’t been able to tell me the general methods of how they might go about tackling a poor performing ORM query. I’m not asking them to even be able to write the code here, I’m just asking them to tell me roughly what their approach would be. If people aren’t able to talk me through that in general terms, they’re not going to help much.
I had one this week where a guy took user input on an API and then used “eval” to run it as code. Where do you even start with that? On CV terms, this person had 10 years of decent looking experience.
- anon50118810 4y agoOP here. Failing surface level tests is not an issue for me. I agree you should not pass through a candidate who can't demonstrate basic coding skills in front of you, or more specialized skills like simple Django knowledge if that's essential to the position. I've been on the hiring side and watched at least one otherwise qualified candidate fall apart in front of me on a simple coding exercise, probably due to nerves. It can be heartbreaking to watch but at some point you have to draw the line.