3 ms·
Ironically, HN frequently touts the benefits of "just talk to someone about their work" over the impartial whiteboard interview. I far prefer the Software Engi
by renewiltord 6y ago
Ironically, HN frequently touts the benefits of "just talk to someone about their work" over the impartial whiteboard interview.
I far prefer the Software Engineering industry's focus on design and coding interviews. Impartial. Unrealistic. But fair.
- Retric 6y agoSoftware coding interviews can be extremely subjective. I have seen someone rate similar responses vary differently based on their overall assessment of the candidate. It’s also extremely difficult to be equivalently helpful when answering questions. Even deciding what’s a fair assessment is difficult. Should you give someone more slack if they haven’t used a language in 2 years, but remember most things well enough?
- renewiltord 6y agoFair enough but "just talk to them" is clearly worse.
- shard 6y agoUnfortunately once you move past the lower working level software/engineering jobs, either vertically to team lead positions or horizontally to product management or marketing or sales, whiteboard interviews are not that helpful, as soft skills becomes as important if not more important than technical skills for success at work.
- Gene_Parmesan 6y agoNot only that, but whiteboarding very rarely tests for skills actually needed at the job. As you progress in your career, things like "I have held down the following software development jobs for X years...." are going to be far better ways to judge technical capabilities that are actually relevant to the job than 30-60 minutes of whiteboarding. Many many different industries have jobs that require technical skills -- not tech as in technolgy -- and they get away just fine with managing to hire people. Nurses need to be able to nurse, a highly technical skillset; no one is having nurses give fake shots on test dummies during interviews. They use credentials and experience, and accept the risk that a hire might not pan out. The fact that we want senior level developers to have to refresh/cram before interviews on how to implement graph search algs and hash tables just so they can pass some artificial whiteboarding section is a bit crazy. Their actual job experience over the past N years should be what counts. Now, conversations about how one would solve technical problems of a sort actually faced on the job are totally on point, and really should be a part of any job interview in any field. edit: Really, what we want as engineering types is for there to exist a way to gauge ability in a purely objective way. But there isn't one; it doesn't exist. Furthermore, you are building a team of people. IMO the focus should really be on fit and soft skills regardless. Make sure they meet a minimum bar of technical ability, then work to verify whether they'll be a productive, beneficial teammate.
- sokoloff 6y agoCredentialing for software engineers (such as licensing and continuing education for nurses) has its own set of problems, both in terms of gate-keeping but more importantly in the type of work being entirely different. There’s a spread in performance from the +1σ to the -1σ nurse, but both will be functional in a nursing role, so checking credentials is a mostly sufficient evaluation of occupational ability. The spread in software ability is so much larger that the -1σ candidates (the least-effective ~15% of people who have ever worked in computer programming jobs) are worth trying to select against in a way the least effective ~15% of nurses probably are not. (I’m not in medicine so I’m not sure; apologies if the same effect is at play there as well.)
- dragonwriter 6y ago> The spread in software ability is so much larger that the -1σ candidates (the least-effective ~15% of people who have ever worked in computer programming jobs) are worth trying to select against in a way the least effective ~15% of nurses probably are not. This isn’t an argument against credentialling since it is literally the direct effect of not having credentialling in software. Credentialing cuts most-to-all of what would be the low tail of the profession off before it ever enters. Nurses and lawyers who can’t do their profession’s equivalent of fizzbuzz mostly wash out of the exams to enter the profession (or earlier), they don’t show up in job interviews, except where the inability is produced by some kind of post-entry decline in capacity. And even then, decertification is a real possibility, which further purges the low end of the distribution. So, yeah, a -1σ software developer (or at least software developer job applicant) is worse compared to basic expectations than a -1σ nurse, because a nurse as below expectations as a -1σ software developer is would be compelled to find a different profession because of credentialling requirements.
- sokoloff 6y agoYou make a good point about an idealized credentialing mechanism cutting off the left tail of the distribution, but the spread in performance will still be much higher in credential-holding SWE than nursing and, because of the high leverage, still worth selecting for. You can only be so much better at nursing than the average qualified nurse. How many more patients will the best nurse save? You can be several multiples (whether it’s 10 or not, I won’t get into here, but I think it’s at least 3) more effective than the average in SWE.