Live data from Hacker News

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

news.ycombinator.com

401–410 of 833 posts

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

#401
In the dark ages, I did coding and systems work for a large money center bank. Hiring back then was at most three interviews - a team member, manager and perhaps the next manager up. There were no "tests," though pertinent questions were asked - often related to the hardware/development environment and familiarity with business and process.

I don't recall any of the people that I worked with directly, or knew from other groups, being incompetent.

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

#402

Earlier quoted context omitted.

> PIPing and firing is a huge time and emotional energy suck, and it sucks So is the 7 interview gauntlet. But I guess it just shifts the burden on the candidates and externalizes cost.

In my experience, it seems to take a company about 1-1.5 years to fire someone that's well intended but ineffective in their role. 15 or so "wasted" person-hours up front is well worth avoiding thousands of wasted person-hours, especially considering maybe 1 in 5 candidates that make it to a full interview are a good fit.

How do we know this isn’t blind faith and the numbers are “made up”?

Other than fiat wealth generation, what gains are there to treating each other like this?

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

#403
I see a lot of responses in here that try to justify the practice using empirical data/logic. What we’re failing to consider is the trade off between “efficiency” and “equitability.”

Just because something is 100% efficient in allocating resources (time, money), doesn’t mean that it’s worth doing. What this thread shows is that somehow, we’ve become sympathetic to megacorps, in winner take all markets, who want to build a world where their time and money is seen as the most valuable.

Instead, we should account for the fact that these companies, with CEOs making $200mm+ per year, should have a civic duty to take on more risk giving people a basic right- access to a job.

Credit card companies aren’t allowed to underwrite based on certain factors heavily correlated with race, religion, or other things (I forget the rest) that were deemed unfair to be judged by. In an efficient world, we would have collectively decided that companies should be able to infer your ability to repay debts based on the zip code you live in, or the college you went to, or the demographics of your friends. It makes sense to not allow this from an equitable standpoint. Why can’t the same be said about hiring people?

Who has the luxury of going through 4 interview rounds? Who has the privilege of studying hours and hours of leetcode? Who has the privilege of staying up to date on the latest web frameworks? I think you get my point.

What won’t surprise me is that the data may suggest the youngest are most suited for many jobs, if one were to judge by interview readiness and performance. If that becomes to norm, would the future version of yourself deem the mechanisms of finding a job market acceptable?

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

#404
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…

On one hand, I don’t want to ever get hired for a position and in a culture where I am not a match, so I myself believe that the more datapoints, the better.

On the other hand, I struggle with impostor syndrome. While fairly successful in my day-to-day, I will likely fail whiteboarding sorting algorithms etc. Imagining a series of five interviews stresses me out and I’m not even looking right now :)

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

#405

Earlier quoted context omitted.

You seemed to skip their second paragraph, which is what I was replying to. Someone who can review diffs and even write a serious change every now and again isn't the most knowledgeable person on the team. The person who is writing and reviewing all of the serious diffs is. And for many L6 EMs, you'll have three of those people reporting to you, they're all working on different projects, each of which you have partia…

I made a concrete statement about what I think the minimum technical bar for EMs is up to at least L7. I also remarked that "clearly this isn't your main focus" at that seniority, which you seemed to skip. The second paragraph, the one you seem to have an issue with, a combination of 2 things: - a few examples of extremely senior, extremely successful engineering leaders who stayed at or near the top of the game tech…

> - a few examples of extremely senior, extremely successful engineering leaders who stayed at or near the top of the game technically, and those are but a few examples from a very long list

But all of these are the exception, not the norm. You said you've been in a FAANG style org, so you've been able to view the org-chart. For every Jeff Dean or John Carmack, there's three-dozen directors and VPs who manage large orgs whose names you've never heard of and who haven't checked in code in half a decade. They're still usually very good managers.

(A reasonable opinion I've seen, btw is that if you're managing a team of say 5 or more people, if you have time to make regular code contributions,you probably aren't focusing enough on your other managerial responsibilities and are letting your reports down)

> - an observation that in other fields, law for example, they call in the highly-knowledgable, highly-expensive, person capable of solving problems few in anyone else in the organization can and that this person carries titles like "partner" and makes the most money.

This is pseudo-true. Partners are called partners not because they're capable of solving problems no one else can, but because they carry an ownership stake, and I'm not a lawyer (and presumably neither are you) but the impression I get is that law is far more delegatory than software, where a partner may call in some favors to address a problem, but will also have 20 Jr. associates investigate 20 different possible approaches and write 20 different briefs to then choose between.

> When I'm wearing my hacker hat I have no interest in reporting to an EM who couldn't do my job in a pinch,

Maybe we have different definitions here, but I've never, or perhaps once, had a manager who I felt could do my job in a pinch, and I was a new grad and he was the worst manager I've had at the time (although he very quickly got better as he learned to be more hands off). A manager who could do my job in a pinch is too micromanaging. Maybe you mean something different in that they could, given a week or two to turn-up on the project take over, but that's not really what I'd consider "in a pinch".

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

#406

Hiring manager here. IMO the current tech hiring norms are gross and not sustainable. It feels like a weird hazing ritual and with the current market, is the single biggest reason you can't hire. Why on earth would someone burn a weekend on a take-home test for your startup when they have 15 other irons in the fire? At my current employer we got rid of all that ridiculousness. No take home test. No live coding. We've…

This sounds very forward thinking and I like it. Would you be willing to share a bit more on the process? What does it entail? In the past I was hired on just 2 interviews, and all we did was talk as peers. It felt comfortable and honest. It's the reason I said yes to switching positions.

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

#407
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…

It may work well for hiring young people.

I can guarantee that you will never see me in one of your interviews. Would I be valuable to your company? Maybe, but we will never know because the process is too long.

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

#409
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,…

That's probably true, but I think at least part of it is just smaller companies doing what bigger companies do, in a kind of cargo cult ritual.

The last company I worked at had 8 interviews, which I thought was a lot. My current company (about 100 people) had no less than 11 scheduled interviews!

Of those, only the first 2 were with people in my department — my manager first, then my manager and immediate coworkers. There was another group call with people in a related team I might conceivably be expected to liason with eventually. Fair enough.

The remaining 8 calls were with leadership in every other division in the company, most of which I would never work with. People with jobs where I don't even know what they do, and I'm sure they had no idea what I do. I just politely made conversation with them and answered their (very general) questions.

Now that I've worked there a while, I have never spoken with these people again, or worked in any way with the teams they oversee.

I've also participated in a few interviews at this company now, from the other end of the Zoom call, and I know how it works: literally every branch of the org chart gets a meeting for every interviewee, regardless of what they're applying for. Everyone has a chance to say "no", but in practice nobody outside the relevant teams is going to exercise that veto, because they are well aware that they are unqualified to judge the candidate's skills, and will never have to work with them anyway.

It's just a big waste of time for everyone involved.

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

#410

As someone who's played all roles in this story (candidate, interviewer, hiring manager, person designing the process) I'm going to argue that symmetry is more important than length. By symmetry, I mean that at any point in the process, you and the company have invested the same amount and learned the same amount. If you're going to give me 5 interviews where I'm answering 90% or 100% of the questions, go away. If yo…

How’s that solving leetcode att 30mins pace in 5 of 7 45mins rounds can get a candidate know about company. No wonder Blind is more vivid than interviews.
Post reply on HN