Ask HN: When did 7 interviews become “normal”?
31–40 of 833 posts
Re: Ask HN: When did 7 interviews become “normal”?
#32> 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.
Re: Ask HN: When did 7 interviews become “normal”?
#33Re: Ask HN: When did 7 interviews become “normal”?
#34I entered the software industry as a developer about 4 years ago, and I have been running interviews for the past 2 years or so. Interview hell is all I have ever known. Could you elaborate on how things worked differently in the past? I legitimately have no idea what a developer interview "loop" would look like without 5 to 7 interviews, but I desperately hope it can exist.
I think 3 interviews is probably reasonable. A leetcode style tech screen, a design one, and then a general work style/culture fit interview.
Also, I don't know why more companies don't record interviews. Probably a legal and/or HR thing. But it'd definitely cut down on the need for repeated questions.
Re: Ask HN: When did 7 interviews become “normal”?
#35Re: Ask HN: When did 7 interviews become “normal”?
#36I’m used to phone screen —> technical screen -> full day many panel on-site. With maybe a take home thrown in there somewhere around the technical screen.
Re: Ask HN: When did 7 interviews become “normal”?
#37Well I can say in my experience firing people is such a pain nowadays that I feel a need to be a lot more careful in hiring. I've seen a bit more than half of fired employees come back with some form of discrimination lawsuit threat after being fired.
Re: Ask HN: When did 7 interviews become “normal”?
#381 recruiter screen: discussing background with recruiter to make sure your experience is relevant
1-2 phone screens: technical interviews with a SWE to see if it's worthwhile to bring you on site
4-6 on-site interviews: combination of technical and behavior interview sessions
I think product management loops will be similar in terms of length, and so 7 interviews is maybe on the long side but not atypical. PM interviews may include a "take-home project" component before the on-site where you e.g. build a slide deck; this is uncommon for SWE interviews.
Regarding the question "When did a hiring manager lose their authority and the trust of the organization to do their job?", it is very common (and a good idea in my opinion) for interview loops to mostly consist of people who are not on the hiring team. Typically the only future teammate you will see in an interview is the hiring manager (this is not guaranteed; I met my current manager when I started my job). The idea is to have the same bar for all roles at the company instead of inconsistent hiring quality team-by-team.
Re: Ask HN: When did 7 interviews become “normal”?
#39For one thing, the company is not the only one doing the interviewing; the candidate is also interviewing the company. Before making a commitment to join a team, I think it's valuable to speak to a number of members of that team to get a sense of what they're like.
On the company side, I have also witnessed several people who might have looked alright in just one interview, but when exposed to several it became clear they were adjusting their story significantly for each interviewer to the point of dishonesty.
There is clearly some line beyond which more interviews would present seriously diminished returns, but I think six or seven interviews, each 30-60 minutes, is much more likely to result in a better outcome for a professional engineering position than just one interview with a hiring manager.