There 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.
You just have leetcode their next product idea. They'll rent some office space, put you in a room for 2 hours on a computer with no internet, and see how well you can grind through their problems. Your score will arrive via the Blockchain to save on physical trees and allow for ready verification by future employers.
Ask HN: When did 7 interviews become “normal”?
281–290 of 833 posts
Re: Ask HN: When did 7 interviews become “normal”?
#282Having 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,…
Why not extend this same criterion to the work itself? I mean you can’t really trust that any developer is writing the best code at any given point in time so it would seem at least a minimum of 5 or 6 developers should weigh in on any given pull request. Maybe that is the way it works there idk and probably never will.
And fixing a bad commit doesn't require 6 months of emotionally draining work.
Re: Ask HN: When did 7 interviews become “normal”?
#283> How is a process like this in any way shape or form efficient or productive? Because hiring the wrong person becomes a colossal waste of time and money.
If the hiring process is faster, then the time wasted bringing in the wrong person is decreased significantly.
Re: Ask HN: When did 7 interviews become “normal”?
#284Earlier quoted context omitted.
I think part of the reason is also that tech has matured to the point where it's so complex that nobody can handle it alone or even in a small group. A couple of people (no matter how supersmart) simply could not build and maintain even a single product of a large tech company. Similar stuff happened with other technology too. A couple people could build an early airplane but a modern jetliner is so tremendously comp…
And how much of that complexity is truly needed? Or is that another one of the lies proferred by its financiers?
Re: Ask HN: When did 7 interviews become “normal”?
#285Earlier quoted context omitted.
Quoted post unavailable.
I’ve worked in tech for decades and I’ve never experienced a process with “7 straight white guys” much less every time. 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…
Re: Ask HN: When did 7 interviews become “normal”?
#286tl;dr: I think you have every right to ask a company what their process is, and when they can expect to be at a decision point -- but I think there are reasons (good reasons!) why companies may wish you to have many conversations before making a hiring decision.
Re: Ask HN: When did 7 interviews become “normal”?
#287Earlier quoted context omitted.
I’m a HM at a big tech company with this format as well. Honestly, I really like it. I don’t want to hire the wrong person, it’s expensive and it makes my job awful for a while. It’s great getting data points on several programming interviews, system design, etc. That makes my sell interview so much easier because I can trust the process to assess their technical skills. You need multiple people because you’re consta…
“Is it annoying for candidates?” Not just annoying, it can be downright demoralizing going through the interview process when the standard is “reject for any one reason, only accept if all agree.” and no feedback whatsoever is given.
Discussing how many no’s it should take to reject a candidate is a worthwhile discussion. I can override specific no’s with good reason at my company, but not all companies have that.
My broader point is that this is a specific issue with the process we can iterate on. We don’t need to throw out the whole process.
Re: Ask HN: When did 7 interviews become “normal”?
#288Earlier quoted context omitted.
People get PIP’ed and fired routinely that make it through this process. I think there’s a lot of bias in your response. The process worked for you, you work at a large tech company and it gives you validation. It also makes you feel good to lord over the process and boosts your ego, reinforcing your priors.
YMMV, but it's actually quite difficult to get a PIP in many tech companies, and it's rarely if ever for lack of tech skills. The ones I've seen usually involve either motivation, output, or both plummeting to zero for extended periods of time due to burnout or a similar extended personal crisis.
Re: Ask HN: When did 7 interviews become “normal”?
#289Earlier quoted context omitted.
I don’t think that’s routine. While I know it happens, certainly I’ve personally never worked with someone who this has happened to. There will always be burning mistakes, or people who lie or are otherwise hard to predict will be a disaster. What else would you propose?
making the interview process similar to the job is a good first step. when I worked at Invitae this was my proudest achievement from my time there. I suggested that we change the interview process to a paired programming session that were situations from our day to day work. the candidate brought in their own laptop or was provided one (their choice). the session was 90-120 minutes and didn’t involve leetcode hard pr…