Live data from Hacker News

Ask HN: When did 7 interviews become “normal”?

news.ycombinator.com

791–800 of 833 posts

Re: Ask HN: When did 7 interviews become “normal”?

#791
post #769

Earlier quoted context omitted.

We don't do take home, leetcode, live coding either. We walk through past projects and ask very pointed questions. We ask about difficult problems we've faced in the past and how you might solve it. I role play a junior programmer describing a situation I have and then ask junior programmer level questions of how to solve the problem. You get to talk to two very senior software developers, and two very senior enginee…

So you screen out everyone who cares about their online privacy?

No, an online presence can either accelerate the interview process or cut it short. No online presence extends the process and makes me leary of making a bad hire, so I'm looking for tells in a weak signal source of an in-person interview where someone adopts a persona to get the job.

I've had to interview a candidate where I am literally handed the resume and said "can you take over? blahblahblah had to ditch." which is unprofessional but you do what you have to do. I walk in, sit with the candidate for about, maybe ten minutes total, whilst I am poking into his online presence and explaining what I am doing, whilst my colleague grills him on various aspects. After ten minutes I write on the resume "Hire this guy before someone else does", thanked the candidate for his time, explained that my colleague would take over, and politely left the interview. Poor guy thought he'd failed the interview. I will admit I handled that aspect of it badly. We made him an offer within the hour. He was an absolutely fantastic hire.

I've also looked at many social media posts by candidates and then put a strong "NO HIRE!" on their application. It isn't about skillset or education or capability, but there are things that people say on social media, in unguarded moments that make them unhirable in a modern work environment due to prejudices and their willingness to express those prejudices.

You should absolutely care about your online privacy. I have made myself "very findable" and if you go through any of my social media posts, you might take umbrage at some things I say (especially about recruiters), but I try to be a cross between Mr Rogers and Ted Lasso. If Mr Rogers said "F*K" an awful lot. I might think some things in the private thoughts of my own head, and thank goodness those aren't automatically transcribed by Google or Siri at this time, but when it comes to posting some very disparaging things in public, some people cannot help themselves and that can tell us whether those thoughts might spill over in the workplace as hidden prejudice or overtly expressed that would land the company in legal hot water.

Re: Ask HN: When did 7 interviews become “normal”?

#792

Earlier quoted context omitted.

Quoted post unavailable.

And yet, when you fail these interview processes it's racism from Chinese or Japanese interviewers. Very interesting. https://news.ycombinator.com/item?id=30520988

Yeah probably because of racism. Can’t prove it and didn’t think of that angel until I saw the discussion from HN.

Re: Ask HN: When did 7 interviews become “normal”?

#793

Earlier quoted context omitted.

IQ-style tests are the norm in parts of Asia. Straight up 200 arithmetic problems in 10 minutes, draw as many perfect squares as possible in 30 seconds, “what’s the best synonym for this word” type of stuff preceding a tech interview. Plus some old sweaty guy in a suit to berate you for not doing something perfectly and question why your 32nd square is slightly tilted to the left while the others are to the right, an…

Huh. I am working in IT in Southeast Asia (Indonesia and Vietnam mostly) and I have never heard about this.

It is very common in India. Especially the service based companies

Re: Ask HN: When did 7 interviews become “normal”?

#794
post #790

Earlier quoted context omitted.

> their bad work could cost the company multi-millions They is false and hyperbole to justify your argument. If a single employee can cost a big company like Google multi-millions, then there is a company structure problem. You make it sound like there are no system of checks. The very definition of being 1 in 10,000 employees at big corp is that no one is important enough to cost the company multi-millions.

You can tell when someone hasn't worked at a google sized company when... Yes, it happens all, the, time. It's just not public information.

[deleted]

Re: Ask HN: When did 7 interviews become “normal”?

#795

I had 6 interviews with Amazon only to be told NO at the end. And I thought I got the jab lol. Then just recently, I was looking to jump to smaller organization. After 5 interviews they told me no. Again I really thought I got the job. So now I am just wondering wtf happened. I got no feedback. They should be paying us for all the wasted time and energy.

I did a couple of interviews with Amazon and I similar experience as yours. The worst part was there is no feedback and one amazon recruiter scheduled a call (which she reschedule two times) just to tell me that I am not selected.

Re: Ask HN: When did 7 interviews become “normal”?

#796
post #761

Earlier quoted context omitted.

This isn't a guaranteed full time job. For all intents and purposes, it's a short term contract with very little notice. Dev time is like anything else, if you buy in bulk (say... 2000 hours a year) and on a regular schedule, you can get some pretty good discounts. I'm in the mid-west, and that's a little under my rate for short-term low-notice (read: emergency) contract work. I can't imagine anyone on either of the…

> I can't imagine anyone on either of the coasts is going to jump at it. So for clarity, they will jump to do 10 hours for 5-7 technical interviews at $0 but won't do 10 hours of paid contracting work where they get $2,000? I can't speak for anyone other than myself but $200 / hour is pretty damn competitive for any contract work no matter where you live. That's $192,000 a year if you put in 20 hours a week (half the…

> So for clarity, they will jump to do 10 hours for 5-7 technical interviews at $0 but won't do 10 hours of paid contracting work where they get $2,000?

It's a 30 hour contract, or at least the comment I was reading said that.

I would. I can just stop showing up to interviews if I don't like the company via the normal interview process. Once I agree to a contract, I have to do the whole thing (I take my contracts fairly seriously).

> That's $192,000 a year if you put in 20 hours a week (half the normal 40 hours that most folks put in).

192k presumably 1099 work. Which is roughly equal to 95k W2 work. Even with that it's not the same. They aren't offering me a guaranteed 20 hours a week of work ever week for a year. If they were, that might be something I would take (unless I particularly disliked the company for some reason).

Extrapolating out a short term contract to full or part time work is dishonest, it ignores all the work you have to put in to find that many short term contracts (lowering your effective hourly rate).

Re: Ask HN: When did 7 interviews become “normal”?

#797
post #44

Having 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,…

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…

I'm a HM at a big tech company as well. We do 3 one hour slots.

In a previous company we pair interviewed, 1/2 hour screen + 2 one hour slots. I liked that format a little bit better.

I've been interviewing people for about 40 years now, I was just reflecting on my first ever interview that I participated in when I was still a teenager.

I would say there are some factors that are not going to come out in any number of interviews. Conversely there are factors that are immediately noticeable.

I can tell in 10-15 minutes how strong someone is technically. At least I can tell the difference between "weak", "maybe", "strong" in 10 minutes.

Going back to my first ever interview. The guy was brilliant. He was technically good. He ended up being a not so good hire for reasons that would have been very hard to discover during the interview. It was partly the intersection of very smart without the experience to match and partly that he was just weird in some other ways. He was hired, he left within a year or so.

I think the science says the best predictor is an IQ test. The rest of our practices are not really evidence based. We tend to want to hire people that are like us, that know the things we know, we have all sorts of biases during the interview process, and throwing more people/time at it doesn't really seem to make a big difference.

I would say the most important thing you can do to get good people is to make your company a place that good people want to be. I.e. what matters is more what enters the pipeline then the interview process. I would bet that having 7 interviews vs. 3 has a difference that's completely in the noise and that at least there's no solid evidence that it gets you anything re: the quality of people working in a company. Every company says it has the best people. Mostly channeling Joel Spolsky here but I've seen this principle in action.

EDIT: Another random thought is that there are other factors that influence whether someone is going to be successful in a given role. Even the best software engineer can fail if the conditions for him to be successful aren't there.

Re: Ask HN: When did 7 interviews become “normal”?

#798
post #191
post #138

Earlier quoted context omitted.

how is it better than alternatives? this seems like a huge straw-man given almost every company that hires developers thinks they’re a large tech company and mimics their hiring process. it doesn’t seem like serious alternatives have been explored.

PIPing and firing is a huge time and emotional energy suck, and it sucks for people on both sides. To reduce the amount it happens is worthy. You can’t in practice just say, “this guy sucks, lets fire him next week” And it shows, barely anyone in my entire career has ever been fired. I only personally have been close to one.

> To reduce the amount it happens is worthy

The point is that there is little, if any, evidence that a given interview process does this.

Re: Ask HN: When did 7 interviews become “normal”?

#799
post #44

Having 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,…

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…

Multiple interviews is annoying as a candidate, but how they are used (or appear to be used) is the bigger problem. Instead of being used to strengthen a consensus they tend to be a series of filters where any "fail" invalidates everyone else's input. After all, why hire someone who everyone doesn't love? But that is the same logic as combining bad mortgages into tranches reduces their risk - sounds good on paper but doesn't work in reality.

Since you have a chance of getting cut at each round as an interviewee you are left hoping not to run into: some esoteric corner of programming you could learn in 10 minutes but haven't seen before; an interviewer who always asks a pet question (even if told not to do this); a personal dislike that is illegal but not challenged (age, gender, race, etc., waved away as "a bad fit").

If multiple interviews were used only to strengthen assumptions about a candidate and each interview had a narrow intent, they COULD help companies avoid more bad hires. But after interview #3 you are probably just filtering reasonable or even exceptional candidates based on random chance.

On the other hand, this may be a fantastic method to strengthen a "hive mind" culture, but that doesn't sound like a worthy goal.

Re: Ask HN: When did 7 interviews become “normal”?

#800

Earlier quoted context omitted.

> Is it annoying for candidates? Yeah, but we pay you a lot of money I had to go through 8 interviews for a senior position at Facebook and ended up not getting the offer. I wasn't paid a dime and had to use a few vacation days at the job I had at the time in order to take the interviews. Technically I lost money interviewing at FB.

I went through the same interview for senior at Facebook and failed. Thankfully I got a Google offer a couple of hours after I got my Facebook rejection. What pushed me over the bar for Google was probably making fewer mistakes on the technical loops but also having more people vouch for me on the inside (they like refs that work at Google).

Yep that's similar to how I got my current job. Strong referral from someone else inside the company, we had worked together for about 4 years. I had one phone screen which was a combination "culture fit" and general talking about my experience programming. One technical interview which was way less abstract than the FB ones. And a final meet-the-team interview which was more of a hangout.

The pay isn't Facebook-tier but is still pretty darn good, and I'm enjoying it a lot, which I'm not sure I would have at Facebook. It was probably the better path for me overall.

Post reply on HN