6 ms·
What does it mean for the industry when there's one of these articles on the front page every other week?
by Apocryphon 7y ago
What does it mean for the industry when there's one of these articles on the front page every other week?
- berdon 7y agoThat most people have a hard time viewing the world from different lenses. The article presents a picture of a guy “studying up” for a career and his adventures in interviewing. As someone who’s interviewed hundreds of candidates I noticed red flags right away. For instance, if someone asks you to design a micro service - you don’t say “I can’t”. No FAANGco interviewer wants you to fail. In fact, they want to help you. The best worst answer would have been “I’m not really familiar with micro services but I’ll give it a shot. Could you explain a bit more about them?” This shows the candidate doesn’t falter at a challenge, is willing to dive deep, and is committed to the task. The lens shift comes into play when 50% of the candidates can’t complete fizz buzz, another 25% simply lied in there resume about any relating experience, and the other 24% don’t have any real understanding about algorithms. There are software developers and then there are great software developers. It’s generally initiative and algorithms that separate the two.
- Apocryphon 7y agoAnd yet, virtually all boot camps allocate time to interview questions now. Hell, there are boot camps devoted entirely to whiteboarding interviews. Surely this cottage industry, similar to those for gaming standardized tests (SAT/GRE/LSATs/MCATs), is a red flag that the industry has fallen into a pit of Goodhart's law?
- berdon 7y agoHmm, perhaps. But interviewing has become big businesses for prep and passing. There are companies that will ghost interview for a candidate, even through actual onsite interviews. It’s a real problem. Tangentially, candidates should read “Programming Interviews Exposed: Secrets to Landing Your Next Job” for prep. It was recommended to me a long time ago and it was enough.
- caiobegotti 7y agoThere are N other separations I could think of besides the ones you pointed out: - someone who gets anxious and blanks out given hardcore requirements these kind of interviews have, smart people can also go bad at tests - someone who's having a tough day and would fare better taking the challenge home with quiet relaxing time like they would expect to have at work if they need to code complex algorithms - no interest in past code written that could potentially show other traits of the candidate a quick coding quiz can't - etc (no need to be extra creative here, just be humble and imagine what the candidate might be going through to get a dream job) The simple fact an apparently smart young person joining the industry gets burned out like that due to stupidly arrogant hiring processes like these is a sign HR are failing miserably in the computer industry, and it's not something that started last month. Simplifying the burden of such process for actual people looking for a job to show how they are worth is dehumanizing.
- berdon 7y agoFalse negatives waste far less time (dollars) than false positives. It’s unfair but worth it to not force a team to have to work with an unqualified candidate for a year or maybe more.
- Apocryphon 7y agoThe problem with an unyielding, fairly uniform obsession with interview problems unrelated to actual day-to-day development is that you're institutionalizing Goodhart's Law. Eventually the interviews will encourage false positives as candidates grind on CTCI and LeetCode and pass interviews without actually being able to excel at actual work responsibilities.
- berdon 7y agoI don’t think so. That’s why you’ll have candidates passing the questions but not the interview. We’re not looking got rote answers, we’re looking for comprehension, problem solving, and discussion.
- caiobegotti 7y agoThe HR folks do not care, it's not their metric to bother about.
- Apocryphon 7y agoBut the average HR rep doesn't determine the technical questions! The culpability falls squarely on the engineers who devise these tests.
- Benjammer 7y agoThis is honestly something I've been trying to discuss with peers recently, and it's interesting the push back you get when you simply bring up the concept of "well, it obviously isn't C suite or HR that is advocating for the algorithmic leetcode test, they couldn't begin to understand that shit, it's 100% just other engineers setting up gatekeeping scenarios."
- SpicyLemonZest 7y agoIs that true? I suppose the truly average HR rep can’t be, but I’ve never been given the freedom as an engineer to not ask a silly algorithm question. At most I get to decide which one I think is least silly. Maybe there are engineers somewhere who think the questions are great and high signal, but I’ve never met any.
- ticmasta 7y agoWell our Dev test was developed by the Senior VP and then tested on our developers; only 1 who aced it. Don't blame me and other workin' stiffs for that...
- Apocryphon 7y agoThat's fair, but I bet the SVP was head of engineering, and both of people ops.
- austhrow743 7y agoPeople misjudge where their high compensation package comes from.
- ajross 7y agoCynically: it means that there are a bunch of jobs that people want and that are hard to get, and the people who didn't get them don't like the process that rejected them. There's no world in which there is an elite (e.g. FAANG) tier of employers who reject most applicants and one in which no one complains about their hiring. That doesn't say anything about whether the hiring process is good or bad, obviously. But that is what it says about the industry.