7 ms·
Glad you brought up the hiring threads on HN. Recently I've felt so many of these threads have devolved into "these stupid companies using whiteboard hiring are
by hn_throwaway_99 6y ago
Glad you brought up the hiring threads on HN. Recently I've felt so many of these threads have devolved into "these stupid companies using whiteboard hiring are all a bunch of idiots!" that I usually stop commenting.
What's most illuminating about those kinds of comments is they rarely even try to view thing from the hiring company's perspective. Having been in that boat, you'll find:
1. The cost of a mishire is huge. And, even worse than hiring someone who is downright awful is hiring someone who is just plain mediocre, or slow. I mean, I've hired diligent, hard-working, otherwise smart people who could only get stuff out the door at about a third the rate of other devs. Having a performance discussion with those folks can be extremely difficult, because oftentimes there is little they can realistically do to go faster.
2. Experience can have little correlation with proficiency. I've interviewed people who were "senior engineers" and "architects" at major corporation who couldn't code FizBuzz, moreover they could barely code a syntactically correct function in their chosen language.
3. Many companies want to diversify their employee base by going outside just friends/referrals and well known college programs, but to "take a chance" on other folks means they need to get a strong signal during the interview process.
I'm not saying there aren't problems in hiring, but given how there is a giant economic incentive to make hiring as accurate and efficient as possible it's at least valuable to attempt to understand why a company might interview the way it does.
- doctorbaum 6y agoBut how whiteboard interviews help (1)? I see them as unconnected and would prefer for that (for example) giving a sample assignment for 2 hours on/off-site
- xyzelement 6y agoI hope this insight helps you and others because it's key: What does an off-site sample assignment tell the company? That you can write code when given a spec. That's great, but that's insufficient for what they are hiring for. What it doesn't tell them: - Can you elicit clarity on a vaguely stated problem? These are conversations that top engineers have with their business counterparts and other technologists constantly. - Can you iterate with another person on a solution. The whiteboarding exercise is a dialogue, and while contrived, problems are often solved in joint manner like that. - How do you do under pressure? Something is going wrong and it's affecting millions of users. Can you carry your weight when the team is fire fighting? Obviously the whiteboard isn't perfectly correlated with the above, but it's as good an indicator as I can think of. Saying "just let me write something off-line" means people are oblivious to these other key attributes. FAANG devs aren't earning 300K a year for just being able to write code on a spec.
- philwelch 6y agoHiring threads are a microcosm of the classic forum disease: people who actually know what they’re talking about are busy doing it for a living, while the malcontents and loudmouths have all day to complain on the internet. HN is one of the better forums when it comes to avoiding that outcome but still not perfect.
- JMTQp8lwXL 6y agoNumber 1 wouldn't have to be a problem if we changed the social contract. The literal contract (nearly always) states your employment is at will. You can be let go at any time, for any reason or no reason at all. Employers should be more willing to (1) take a risk on a hire, and (2) let them go if it doesn't work out. Then, hiring doesn't have to be this grandiose, talk to 20 people over 2 days in 20 30-minute session, but actually the VP has a final call, sort of decisions.
- xyzelement 6y agoJMTQp8lwXL, LOL. So your proposal is instead of thoroughly interviewing, just give jobs out randomly and then fire people? That works aside for the fact that it's horrible for everyone: - The employee: they presumably quit another job to take this one and now they are out on their ass because the employer didn't bother to test for proper fit. - The team: they invest in training the new person, get to like them, only to have them fired. Meanwhile they are short a person as hiring effort has to be restarted so they lose a ton of time understaffed. - The company: dealing with all this terrible churn, stopping and starting the hiring effort, is there still severance in this world? How does unemployment work? This is just the craziest proposal I've ever heard. It's like saying "dating is too onerous, people should just marry randos and not hesitate to get divorced if it turns out the other person brushes their teeth in an annoying way."
- hn_throwaway_99 6y agoI certainly don't think this is the craziest proposal I've ever heard. Netflix, for example, is quite transparent that they have a "hire and fire" culture, and I for one wish that many tech companies would be more willing to have open, honest conversations with their employees and ensure everyone is up to whatever bar they set. I've seen it become incredibly demoralizing for the rest of the team when subpar performers don't get let go, and I've also seen rather disingenuous uses of "layoffs" as an excuse to finally cut people who should have been cut long ago. Still, there are practicalities that can make "hire fast, fire fast" difficult in the real world. First, many countries outside the US have much more onerous requirements to fire someone. Even in the US, it's quite trivial for any employee to take legal action if they think they've been let go unfairly, so most HR departments will require many months of detailed documentation (e.g. email conversation, performance reviews, PIPs) before someone can be let go.