3 ms·
Last I looked we are still in a market where there is supposedly more open positions than there are engineers to fill them. So why are firms that are hiring so
by cmrdporcupine 6y ago
Last I looked we are still in a market where there is supposedly more open positions than there are engineers to fill them.
So why are firms that are hiring so obsessed with producing more and more arcane barriers to entry?
As I always comment when this topic comes up: this process makes some sense at Google (where I work) where the sheer number of applicants is massive and false-negatives are perfectly fine because the potential applicant pool is so large. But at smaller companies, who can't pay Google compensation and feed you gourmet food, blah blah blah? And where your job will be mainly writing some JavaScript to drive web pages? Really?
I work around embedded stuff and spend a lot of time in low-level code, and I _still_ don't get to spend a lot of time writing algorithm and data structure heavy code. I actually really enjoy doing that kind of work, but on my own time, at my desk, with my headphones on, and some books and resources to reference as I'm doing it. This is how engineering / authoring / writing is classically done, by the way. Calmly, often solitary, and with space to gather thoughts and do trial and error.
Why should I be selected or deselected based on my ability to perform this activity in front of people in a high pressure situation? Often someone 15 years younger than me, fresh out of a CS program, and with a pile of hubris that goes with that?
For what it's worth I'm self-educated, not a CS grad, but got into this because it's what I like to do and spent many years privately studying on my own to get here.
FWIW I just this morning turned down a potential job opportunity because this is the interview process they wanted.
- notacoward 6y agoTake an interviewer who has the benefit of having worked through a problem literally a hundred times, further aided by internal training that represents thousands of iterations. Have them judge someone who hasn't had to solve that particular problem more than once or twice, twenty years ago in a different language (and certainly not on a whiteboard). That interviewer will form an inaccurate opinion of the interviewee's relative ability. Not maybe, and not by a little. Any interview process that does nothing to correct for that is broken.