Live data from Hacker News

The Last Technical Interview

steve-yegge.medium.com

111–120 of 291 posts

Re: The Last Technical Interview

#111
I’ve seen this before. The result is a revolving door of temporary work. Because soon companies will be “you already put 6 months in, we don’t have enough signal work 6 more months” and at the year mark they swap you for a new candidate.

And before you say that this is inefficient consider that despite being terrible for morale and efficiency (proven in un’etica studies) companies still maintain the bottom 10% out or up or out policies.

Companies always love their power on their employee over efficiency.

Re: The Last Technical Interview

#112
I don't think this works, and other comments have also pointed out the same. You open a position, you receive 200 CVs. Ok, then what, get them all to come in for a couple days work? A company that needs only one position can't possible handle that.

Now you're amazon/google. You have 200 open positions in a certain site/country. You receive 10000 CVs. Same problem, different scale.

So ok, you need to filter CVs, mmm, which sucks, right, so perhaps we do a screen interview? mmm, low signal, maybe....

Re: The Last Technical Interview

#113
post #13

The gold standard in hiring qualification is work-sample testing. It works fine. You do not need to "make hiring a profit center" or "provisionally hire" or do internships. Work samples done correctly demand less time from candidates than interviews and scale better than interviews. They are standardizable and iterable. What I feel like I'm reading here is someone who has been poisoned by FAANG hiring practices --- a…

I'm a little bit more on the fence with the work sample interviews having designed them and also interviewed through them. I've also done my fair share of "traditional" tech interviews, all at startups, never FAANG. As an interviewer, I much prefer the signals generated through a work-sample interview. I'm much more confident in the hiring recommendation than I get from a 1 hour zoom session. However, if I look at te…

Work sample interviews don't have to be take home. We ran our technical interviews as close to work samples as possible and in person.

Re: The Last Technical Interview

#114
post #112

I don't think this works, and other comments have also pointed out the same. You open a position, you receive 200 CVs. Ok, then what, get them all to come in for a couple days work? A company that needs only one position can't possible handle that. Now you're amazon/google. You have 200 open positions in a certain site/country. You receive 10000 CVs. Same problem, different scale. So ok, you need to filter CVs, mmm,…

Even smaller and niche companies are getting 700-1000 CVs now for an open position. Every company I've talked to says hiring is completely broken.

Re: The Last Technical Interview

#115
post #13

The gold standard in hiring qualification is work-sample testing. It works fine. You do not need to "make hiring a profit center" or "provisionally hire" or do internships. Work samples done correctly demand less time from candidates than interviews and scale better than interviews. They are standardizable and iterable. What I feel like I'm reading here is someone who has been poisoned by FAANG hiring practices --- a…

I'm a little bit more on the fence with the work sample interviews having designed them and also interviewed through them. I've also done my fair share of "traditional" tech interviews, all at startups, never FAANG. As an interviewer, I much prefer the signals generated through a work-sample interview. I'm much more confident in the hiring recommendation than I get from a 1 hour zoom session. However, if I look at te…

> I'm not sure the outcomes were that noticeably better.

It's not just you. At the end of the day interviewing has been demonstrated to be close to a crapshoot in the best of circumstances, and very few interview schemes are the best of circumstances. Work samples are part of the optimal strategy [1] but even then the signal is quite low.

[1] https://psycnet.apa.org/record/1998-10661-006

Re: The Last Technical Interview

#116

> One day, the recruiters gave us a special round of packets to review. In these special packets, we were able to read the interviewer notes and candidate responses. All personal details were stripped out, and we were told it was a “calibration exercise.” We had to do our regular voting job with these special packets, and see how it went. I think we may have assumed they were from another site, since cross-site calib…

The idea is that if you are already in and doing a good job but can't pass the interview, then the interview is bad. Specialists hiring is a bit different if no specialist are on the team yet.

Re: The Last Technical Interview

#117

The "provisional employment" idea sounds good at first, until you think about how it would actually work in practice. You have 100 applicants for 1 position. Which one do you provisionally hire? Ah of course, we have to do a traditional interview loop to evaluate 10 candidates before we can pick one. So you do the traditional interview loop, and then you have 6 months of provisional employment. You haven't replaced a…

It seems the benefit would be one sided - that initial 100 -> 10 (ATS/interview/coin-flip) filtering processes would as usual have a large percentage of both false positive and false negatives.

The false negatives suck for both candidate and hiring company who have accidentally rejected someone they would have like to have hired.

The benefit of the "provisional employment" process would be that even if it doesn't help avoid the false negatives, it would weed out the false positives so that the company at least ends up hiring people who are qualified and a good fit (even though due to the false negatives they may have rejected even better candidates).

Re: The Last Technical Interview

#118

Signals I've got from this post: - Steve's company got acquihired by Amazon, granting him a free ticket in without all the torment of the multi-stage interview pipeline. - It's a well known fact that it's easier to jump from one FAANG to another, so while interviewing at Google he had significant advantage, plus the blog gaining popularity. - All of this has caused a deep down imposter syndrome, which resulted in an…

- "This attracts strong candidates to you, because even your rejections are worth something to them." That's some solid gaslighting right there! You're right Steve, I would rather be rejected by your team than wasting my time by doing something positive with my career.

I interviewed at Google last year and they said something similarly magnanimous: that they rejected people who wouldn't have been successful at Google and that the rejects actually thanked them for the wisdom. My eyes rolled all the way back in my head. I cancelled the rest of my loop and went to a different FAANG. When I sent the cancellation email I thanked the recruiter for sharing his wisdom.

Re: The Last Technical Interview

#119

Earlier quoted context omitted.

> I gave the feedback at one Google interview that they should send Google employees through to see how many get hired. Good to see they basically tried that. They did, but not with the intention of doing anything about the problem. This is a question of reliability , the conceptual 'correlation' of a measurement instrument with itself when measuring the same thing. Reliability is one of two major concepts in psychom…

Serious question, tell me what you think of using IQ tests to hire SWEs? Should we just do that instead?

Why not do that for all jobs. Forget resumes and work experience/accomplishments, and just hire based on a test score?

Perhaps we could administer this IQ test at age 12, so that the low-scoring individuals can go straight into the fast-food industry, and the rest can pick between the doctor/lawyer/SWE offers that will be showered upon them?

Re: The Last Technical Interview

#120
> There is a material difference between the signal from an internship (~7 weeks of usable work time after ramp-up) vs a co-op (5 months actually working)

And that's why the trades require you to perform years of work as an apprentice before you're ever qualified to pass an exam to become a journeyman. Not only is it like a years long internship, but you're paired with someone who has already passed a high bar. You're learning directly from vetted people, and those people can vouch for you.

> University of Waterloo famously sends their Computer Science students through a total of six internships, giving them roughly 2 years of real-world work experience before they graduate.

Still less time than an apprentice is required to work, but it's better than nothing. Most trades require you to be an apprentice for 4 to 5 years.

> The reason is, hiring engineers has historically been so competitive that you couldn’t convince a senior engineer to do an internship [...] So the industry converged on not requiring it.

Which is one reason the trades made it the law that you have to follow the apprenticeship in order to become a journeyman. "The contracting companies don't feel like hiring licensed workers" isn't an option. Companies don't do the right thing unless they're forced to.

This is why we need professional engineer certification for software engineers. We need a rigorous, time-tested, reliable process to ensure engineers have actually done the job in the right way. Otherwise it's a bad guessing game like Steve is explaining.

This is also why we need a software building code. We need to explicitly define exactly how you're supposed to engineer, so that we can create a certification that people can pass. Otherwise designing and building software is completely subjective. Engineering should not be subjective.

This is not some mysterious experimental idea that nobody knows if it'll work. Trades have been doing this for decades. It's not perfect, but it's much better than the alternative.

Post reply on HN