3 ms·
I wouldn't call them "dangerous," per se, but they are mostly done to fool AI screeners, these days, and are nothing more than a few data points and buzzwords.
by ChrisMarshallNY 5y ago
I wouldn't call them "dangerous," per se, but they are mostly done to fool AI screeners, these days, and are nothing more than a few data points and buzzwords.
> The first thing I look for in a resume is a GitHub URL. If I can find that, I stop reading the resume and start reading code. Doing open source is not a be-all and end-all by any means, but it's a good starting point. After five minutes of reading through a candidate's code I have a good handle of their skill level and style, making the interview run much more smoothly.
My experience, is that interviewers don't look at this stuff at all. It's downright crazy. Instead, they rely on leetcode tests.
These are short, academic tests, using algorithms that are seldom seen IRL (I have been coding for over thirty years, and have never seen one single binary tree. I've seen one or two roughly similar structures in some image processing algorithms, but only in a couple of ones that weren't very performant, and we ended up removing these).
But they can be practiced, and are quite familiar to folks just barely out of college.
I've not bothered to practice these. I can do OK on them (they are usually just common sense exercises), but some kid that has spent most of the last month (of their current employer's time) practicing these, will absolutely kick my ass. It's not worth it.
Also, I have noticed that interviewers are looking for rote answers, which also applies to more practical exercises, like take-home tests. They don't like unusual approaches. They are controlling for conformity. That's interesting, as some of the companies doing this, are crowing about "disruption."