Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What is the marginal value of the fourth or fifth deep hour that you wouldn't grok by hour 3.5?


30 mins chat with a recruiter who'll try to suss out whether they can afford you, make sure you're actually interested, and check you've got the right to work in the country.

1 hour hiring manager interview the first person who actually understands those acronyms on your CV

1.5 hour technical/coding interview, to check you know how to program

1 hour behavioural interview to check if you've ever gotten into a fistfight about database schema design

1 hour chat with your boss's boss's boss, who feels he ought to have a conversation with someone before approving a six-figure paycheck.

This lengthy and bureaucratic process is vital to ensuring prospective hires have the patience needed to get through all the other lengthy and bureaucratic processes their job will entail.


I appreciate your comment as its intended defense and understand why a committee approach is a CYA risk-assessment measure (which ultimately turns job placement into a popularity contest as technical ability and team desiredata take a back seat/lower weight to fisticuffs assessments by HR).

However, parent commentator mentioned wanting to _go deep_, and needed 4-5 hours to do it, indicating that the typical committee pattern is out of alignment with what they were advocating.

Further, your time assessments are too long. You can assess fisticuffs in 10 minutes along with a background check. Technical doesn't have to be 1.5 hours. Also, 90 day probation policies exist to address as well.


I wondered that myself, when I had my 12th interview for a position in Nvidia's DevTech team.

(Didn't get an offer, in case you're curious:)


N.B.: Despite the peculiar number of interviews, I was left with a lot of respect for the team members and their work.

If anyone sees an interesting posting for that team, I'd definitely suggest applying.

And their 2 take-home coding projects reminded me why I love performance optimization.


Jeez. Should they not expect each interview stage to at least whittle down 1 applicant for every 2 that reach that stage? That's 4096 people who got to interview.

Or I guess they decided on a "mixture of experts" and put everyone through to multiple "final round" from different domain experts? All of whom are somehow adding value?

I don't think I've ever said this before, but that sounds like a job for a management consultancy.


IIRC, they were scheduled in something like 3 total batches.


Wow, and I thought the 8 interviews (each around 45 minutes iirc) I did for Apple was excessive.


You can get them to meet a more sizeable chunk of the team which helps keep individual bias down and ensures people are fine with the new hire.


I mentioned this in another reply -- while this is true and common, it's not what the grandparent commentator mentioned. They wanted 4-5 hours to "go deep" which is really unreal from an interviewing perspective.

It's a date, not an interrogation!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: