8 ms·
Consensus seems to lean toward this being satire. However, that’s actually part of the problem with online discussions of interviewing right now: Everyone loves
by PragmaticPulp 6y ago
Consensus seems to lean toward this being satire. However, that’s actually part of the problem with online discussions of interviewing right now: Everyone loves to read and write about how developer interviewing is flawed, but no one wants to go out on a limb and make suggestions about how to improve it. It’s easy to be a critic and it’s fun to be smugly dismissive of those companies who rejected you after long interviews, but it’s hard to actually step into the hiring manager position and find the best candidate without disappointing some people along the way. Writing satire or criticism is an easy way to win clicks and views because you’re not going to alienate people with the tried and true “all interviewing is bad” claim.
Sadly, many of the implied alternatives to coding interviews are becoming a regression toward credentialism: People who have already secured good jobs, impressive internships, or prestigious university degrees would much rather coast on those credentials than be challenged for a few hours during an interview. This feels good if you’ve already made it or you grew up with the right connections, but it’s far from ideal you’re a promising developer who doesn’t yet have the right credentials on your resume to unlock the job. To many people, the coding interviews is a chance to break the traditional mold and land a job that would have been out of reach otherwise.
- irq11 6y ago“ People who have already secured good jobs, impressive internships, or prestigious university degrees would much rather coast on those credentials than be challenged for a few hours during an interview. This feels good if you’ve already made it or you grew up with the right connections, but it’s far from ideal you’re a promising developer who doesn’t yet have the right credentials on your resume to unlock the job.” Perhaps we could interview different people differently? I don’t know why we have this obsession with subjecting experienced candidates to the same whiteboard gauntlet as a new grad. In fact, after a candidate has a bunch of experience you’d better be screening for other factors, since the role of an experienced developer can/should be dramatically different than someone with a few years of experience. But no, still with the “challenges”. If you can’t do obscure puzzles with the same fidelity as you could six months out of college, it’s a no-hire!
- shaftway 6y agoI can't tell you how many people I've interviewed that were "experienced" developers that were just terrible terrible engineers. My favorite interviews were when we were trying to hire a senior level engineer, and we were only interviewing people with 10+ years of development experience. We'd ask people to build a priority queue. Items with a higher priority need to be handled before those with a lower priority, but otherwise items should be handled in order. Can you guess what the most common methodology people chose was? Did you guess an XML document? These are people with degrees in comp sci, some claiming 15 years of experience as a developer, trying to get a role at a top 10 bank in New York City. Of course technical interviews shouldn't be the only test used for hiring, but they absolutely should be included. Maybe it's demeaning that you have to jump through these hoops. Or maybe you're bad at them. Or they're "beneath you" in some sort of way. But don't blame the interviewer, blame the hundreds of other people trying to get a job that they aren't qualified for.
- learc83 6y agoDid you ever actual hire any of those people? Did you ever verify that they actually had the experience they claimed? Did you follow up with their references? Were they able to walk you through projects they worked, or discuss solutions implemented? Every job gets applicants that aren't qualified. Only software engineering out of every single non-performance based (musicians, actors etc...) industry out there has white board interviews.
- shaftway 6y agoActually, yeah, we did. The hiring manager got tired of waiting for us to find a good candidate, so he just picked one that he had screened and seemed best on paper. It was an unmitigated disaster. Constantly had to double check his work and redirect him from doing things bad ways (like using mutable objects with changing hash codes as dictionary keys kind of bad). Eventually I quit the job (for other reasons). On the last day he cornered me in the elevator and offered me $100/hr to do his work for him under the table so that he could claim it was his. > Did you ever verify that they actually had the experience they claimed? Employer would only verify employment dates and eligibility for re-hire. > Did you follow up with their references? Yeah, but when you ask someone for references they're not likely to give you people who wouldn't speak well of them. > Were they able to walk you through projects they worked, or discuss solutions implemented? Yeah. I can walk you through projects that I was involved in as a junior as if I had been the lead because I paid attention during meetings.
- _qulr 6y ago> This feels good if you’ve already made it or you grew up with the right connections, but it’s far from ideal you’re a promising developer who doesn’t yet have the right credentials on your resume to unlock the job. I've never understood why these two different groups, long experienced developers and unproven newcomers, are competing for the same jobs. That's the insanity of the system. I suspect the answer is that many people believe (mistakenly IMO) that experience doesn't really matter, and "raw talent" overrides everything else.
- TuringNYC 6y agoPart of it is the conveyor belt of new frameworks and technologies, and binary litmus tests from first-line recruiters. Someone who could very well have invented javascript yet doesnt know ExpressReactVue[*]JS or framework du jour cannot get past first-line recruiters who are searching on Linked In keywords. Thus, both groups are in the same bucket. I wouldnt be surprised if some recruiters turn down python 3.6 candidates because they dont have python 3.7.
- sokoloff 6y agoMy prediction: Somebody with a realistic chance of inventing whatever the next javascript will be will do fine. Recruiters who screen them out are hurting their company not that candidate.
- TuringNYC 6y agoI agree, i was exaggerating a bit but there is a spectrum between, say, Brendan Eich (on one extreme) and an average code camp graduate (on the other extreme). Think about those in the 75 to 50% region.
- _qulr 6y agoI don't know, almost every day I regret the invention of JavaScript...
- marta_morena_28 6y ago
- akdas 6y ago> Everyone loves to read and write about how developer interviewing is flawed, but no one wants to go out on a limb and make suggestions about how to improve it. I've spend this year writing about hiring[0], both to talk about the problems and provide suggestions on how to improve the process. My suggestions are sometimes high-level, and sometimes very detailed. Some examples: - Be specific about the requirements [1] - Tailor the requirements to the role you're hiring for [2] - The types of non-technical issues that can cause a candidate to perform poorly, and how interviewers should correct for them [3] - Let people work independently [4] But above all, my primary thesis is that it comes down to looking for strengths, not trying to discover weaknesses [5]. Having been on the hiring side, this is the specific suggestion that I believe will have the most impact, especially to those who want to land a job that would have been out of reach otherwise. [0] https://hiringfor.tech https://hiringfor.tech [1] https://hiringfor.tech/2020/03/02/are-you-asking-candidates-to-read-your-mind.html https://hiringfor.tech/2020/03/02/are-you-asking-candidates-... [2] https://hiringfor.tech/2020/06/22/hiring-for-the-role.html https://hiringfor.tech/2020/06/22/hiring-for-the-role.html [3] https://hiringfor.tech/2020/05/25/letting-the-little-things-slide-remote-interview-edition.html https://hiringfor.tech/2020/05/25/letting-the-little-things-... [4] https://hiringfor.tech/2020/08/03/reducing-interview-stress-with-independent-work.html https://hiringfor.tech/2020/08/03/reducing-interview-stress-... [5] https://hiringfor.tech/2020/02/10/false-positives-and-false-negatives.html https://hiringfor.tech/2020/02/10/false-positives-and-false-...
- fractionalhare 6y ago> But above all, my primary thesis is that it comes down to looking for strengths, not trying to discover weaknesses [5]. I strongly agree. I think a generation of software engineers has been trained to calibrate their interviews by looking for reasons not to hire someone, instead of looking for reasons they should. This perpetuates all sorts of biases in the hiring process, and it insidiously serves as a form of self validation as well.
- pc86 6y agoThe problem is that you can find a reason to hire almost anyone. Now most companies just need someone to write boring line-of-business applications so maybe that's okay, but if you're working on anything novel hiring the wrong person can be very expensive. I don't think there's any intrinsic negative in keeping a high bar for hiring.
- jfarmer 6y agoI think it is and it isn't. The author definitely believes in testing for people's IQs, so I think the whole section on "identifying talent" is meant to serve as a reductio ad absurdum. Some of the author's tweets about identifying talent, IQ, and temperament: · https://share.getcloudapp.com/YEuyyKbE https://share.getcloudapp.com/YEuyyKbE · https://share.getcloudapp.com/z8uYY5gZ https://share.getcloudapp.com/z8uYY5gZ · https://share.getcloudapp.com/E0urr8B5 https://share.getcloudapp.com/E0urr8B5
- walshemj 6y agoAnd working memory isn't part on an IQ test I score fairly high on IQ but have poor short term memory.
- borroka 6y ago- "but it’s hard to actually step into the hiring manager position and find the best candidate without disappointing some people along the way" Hear me out: the quality of (hiring) managers in tech is ridiculously bad for the money they make. Little quality, poor ideas, and little personality. Mostly, they are of the nerdy type, like the vast majority of people working in tech, so by inclination and culture are not leaders, but followers or the aloof type, and they much prefer to work on their own than in teams. It pays off to go with the flow in corporate. Source: I had managers (including Directors and VPs) at some of the tech companies everybody talks about that were they to take any decision in which life and livelihood of people are at stake, it would be one of those dreams after which you wake up drenched in sweat and you make the sign of the cross you are just working in a tech company.
- walshemj 6y agoI am trying to understand what your saying - that managers would not make decisions.
- borroka 6y agoLet me clarify. Most managers I have seen in tech are sub-par. So, it might be that it is not that the hiring problem is a process problem, or a market problem, but a manager-quality problem. Of course, I can present only anecdotes from my own experience; but I can confidently say that, before getting into tech, I was expecting the quality of managers and decision-makers to be much higher, especially considering the money they make. Instead, I have noticed the usual skewed distribution: a bunch of brilliant decision-makers that move the company in the hopefully right direction, and a ton of minor managerial figures who are surprisingly terrible at being managers, when not total frauds. I hope it is clearer now.
- sngz 6y agothere's plenty of suggestions and there are companies / teams that adapt those suggestions. Just big companies and startups, and clueless management refuse to. I can't control how my company hires people but I can control how I interview internal candidates.
- Dangeranger 6y agoThe author has stated that this article was not meant as satire, even though some parts are exaggerated[0]. I do not like much of this advice, even if some of it may be true. For example, I believe that the sum of a team can be greater than its parts, and hiring for talent alone can result in a poorly functioning team. [0] https://twitter.com/dsafklasdfnas/status/1315699986403786753 https://twitter.com/dsafklasdfnas/status/1315699986403786753
- dennisgorelik 6y ago> Consensus seems to lean toward this being satire. I think "How to interview engineers" is a set of actual Slava Akhmechet's recommendations about hiring, sprincled with occasional satire about hiring games.
- jjav 6y ago> but no one wants to go out on a limb and make suggestions about how to improve it. That's not really true, plenty of suggestions on how to improve it. Many of those based on experience doing it for the long haul. Personally I always advocate for a technical discussion of their experience. Read the resume in detail. Talk about it. Pick some past project to go deep. Also let them pick a favorite past project to go deep in detail. It means the interviewer needs enough technical depth to follow along. This works. I've never said "yes" to a hire and later thought that was a mistake, in ~25 years of doing interviews. Just the other day here someone was saying they received over 50 resumes for a role so they had to interview over 50 people. No. Don't do that. You can't go deep, so it just leads to meaningless puzzles. Read the resumes, pick the top 5 or so, interview them personally. Hire the best of those. Done, move on with getting work done.
- bJGVygG7MQVF8c 6y ago> would much rather coast on those credentials than be challenged for a few hours during an interview. You misspelled "at best incompetently assessed, at worst hazed in ways which adversely impact women and underrepresented minorities in tech"