Earlier quoted context omitted.
I was going to say this. To add more: a single person (HM) might have biases for or against certain candidates. More people in the loop brings in diversity and helps to keep interviewers honest and consistent. Also these roles are usually high stakes and the cost of a bad hire is too high.
Quoted post unavailable.
Ask HN: When did 7 interviews become “normal”?
151–160 of 833 posts
Re: Ask HN: When did 7 interviews become “normal”?
#152Earlier quoted context omitted.
I would argue that 30 hours invested in interviewing at a single company is a lot more work than you put in doing a couple phone screens and a one-day onsite. I personally abhor take-home projects because they tend to balloon in scope (I'm a perfectionist and want to put the best foot forward). With an on-site loop, when you're done you're done.
Yeah, a valid philosophy is that a company should have to spend at least as many man-hours interviewing me as I spend interviewing.
Re: Ask HN: When did 7 interviews become “normal”?
#153Earlier quoted context omitted.
1. Often, legally, firing people is harder than hiring. 2. Hire more, fire fast sounds good on paper but will destroy morale as the team identity will be constantly influx. 3. Engineers will spend less time onboarding newer engineers to the detriment of everyone because well, they might not just last.
Basically everywhere in NA has allowances for probationary periods with at-will employment. Moreover, prospective hires could start on contract. Morale is improved when team members feel like they have some control over their membership. It seems like you're assuming that a great many people would be fired; why so? In my experience, having worked for several such companies, firing is rare because even minimal filters…
The processes you are questioning scale to thousands of people with varying backgrounds. It’s not an accident all of these companies do this. Your process places extreme trust in one group of people. It’s just so risky.
Also, resumes are mostly bullshit, IMO. Reference checks are complete bullshit, IMO. I’ve worked with my buddies at startups (who get lofty titles) and just have them give me reference checks. Other references have asked me for call scripts.
Also keep in mind that most of these big tech jobs are highly competitive. Your solution eventually requires a coin toss if you have limited spots. There’s only so much data you can collect from the process you propose. The natural thing is to then assess each candidate a bit more until you’re confident you’ve picked the right one. And then you’re here.
Re: Ask HN: When did 7 interviews become “normal”?
#154Earlier quoted context omitted.
I was going to say this. To add more: a single person (HM) might have biases for or against certain candidates. More people in the loop brings in diversity and helps to keep interviewers honest and consistent. Also these roles are usually high stakes and the cost of a bad hire is too high.
Quoted post unavailable.
First, how do you know the sexual orientation of interviewers?
Next, tech is like 50-70% Asian so it would be so weird to only have white guys doing programming interviews.
The guy pet is spot on as programming is way heavy in guys.
But I’m not sure why you would think that 7 interviews = 7 straight white guys.
Re: Ask HN: When did 7 interviews become “normal”?
#155There needs to be something like the SAT for computer programming. Getting a 1500 won't mean you're a genius but it will mean you can do the job, and then there can be 1-2 interviews for domain-specific skills and culture fit. I know many have tried this, some have built great businesses, but nobody has yet become "The Credential" but I do believe this will eventually exist.
(Turns out the company started as a 10% project of the first company I encountered that used it)
Re: Ask HN: When did 7 interviews become “normal”?
#156Re: Ask HN: When did 7 interviews become “normal”?
#157Having been an interviewer at a FAANG for many years, I can explain some of the logic behind it. I'm not saying this logic is valid , but it's how we got here, imho. First: we no longer trust the hiring manager alone, because probably they aren't a strong developer. We instead trust strong developers that are well trained at evaluating good devs. At the same time, we don't want to thrust a dev onto a hiring manager,…
Sorry, but if it can't, aren't you doing the interview wrong?
Re: Ask HN: When did 7 interviews become “normal”?
#158Earlier quoted context omitted.
I was going to say this. To add more: a single person (HM) might have biases for or against certain candidates. More people in the loop brings in diversity and helps to keep interviewers honest and consistent. Also these roles are usually high stakes and the cost of a bad hire is too high.
Quoted post unavailable.
Re: Ask HN: When did 7 interviews become “normal”?
#159Earlier quoted context omitted.
I was going to say this. To add more: a single person (HM) might have biases for or against certain candidates. More people in the loop brings in diversity and helps to keep interviewers honest and consistent. Also these roles are usually high stakes and the cost of a bad hire is too high.
Quoted post unavailable.
Re: Ask HN: When did 7 interviews become “normal”?
#160Earlier quoted context omitted.
I was going to say this. To add more: a single person (HM) might have biases for or against certain candidates. More people in the loop brings in diversity and helps to keep interviewers honest and consistent. Also these roles are usually high stakes and the cost of a bad hire is too high.
> these roles are usually high stakes and the cost of a bad hire is too high Really? High stakes? This fucking site. Have you ever worked as a software developer at a corporation? Nothing about it is high stakes. You spend most of your time dealing with useless idiots who report to other useless idiots, who report to other useless idiots, about a useless product they think is a great idea that every non-idiot knows i…