Live data from Hacker News

The Last Technical Interview

steve-yegge.medium.com

141–150 of 291 posts

Re: The Last Technical Interview

#141
Most interviews are just referrals then confirming the bias, even if you fail some questions, you are likely in. If you came from no where, they are not gonna like you unless you get all the questions right.

If you want to know if someone is good at your company in 3-4 interviews, it’s tough, the best they can do is ask these technical questions. Talk to you about your past work, ask you technical what ifs. Most dumb ass companies will ask you to do trick coding leet code crap.

Re: The Last Technical Interview

#142

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?

Yes I do think it has merit. I think some kind of specialized IQ test which measures for aptitude can be used for for screening. Of course it's not a be all and end all but it should significantly reduce the 'grinding-leetcode' situation.

Re: The Last Technical Interview

#143
The proposal does not make sense. Candidates do not benefit from accumulating and parading rejections until they reach a company that accepts them. If they have offers, they can and already do tell recruiters. Furthermore, this practice of spending days at a company is expensive in opportunity cost; you will have to burn your vacation time, and be able to interview at fewer companies. In sum, the proposal benefits companies, not candidates.

Re: The Last Technical Interview

#144
post #138

Earlier quoted context omitted.

All these objections rely on removing agency from the professionals applying for jobs. You look at the work sample. You use your professional judgement. You decide if it's reasonable to execute it to what you think a professional standard would be in the time allotted. You make a decision. This isn't a college application.

Why would you design a hiring process that scores unprofessional people (by your own definition) higher than professional ones?

Again: I am responsive to the concern that hiring processes can demand too much of candidates, and particularly to the idea that work-sample challenges are unreasonably demanding compared to interviews. That's why hiring processes I've designed over the last 10 years have all been budgeted against the time typically allotted to an interview loop. And then, to people who say "the challenges take more time than the budget, so I'm forced to spend more time", I say "if you believe that to be the case, don't do the work sample challenge".

The rest of this I'm not interested in. For as long as we've been talking about hiring processes on HN, there have always been staunch defenders of interviews. Lots of people have spent time getting good at them, there are classes on it, there are books, there are drilling exercises. I don't anticipate talking those people out of their investment in interviewing.

Re: The Last Technical Interview

#145
I normally get jobs thru people I have worked with already. It reduces everyone’s risk quite a lot. Obviously I had to bootstrap, and that was in the far easier hiring time of the 1990s when all the people who wanted to be rich weren’t trying to do programming. I still interview and have people look at my public git hub and so on, but the context is much more “do you understand the problems we are trying to solve and do you have ideas or experience that relate” than “can you do this programming puzzle” (which no, I can’t, my particular forte in software is identifying where systems or solutions almost line up and a little bit or torqueing with a glue layer or two will enable this awesome work to be used in this novel problem space; even larger green fields is just taking open source libraries and frameworks and pipelines and combining them into a useful thing designed for exactly the use case at hand, which will never not be a far more useful product than some big generic product, quicker to change to meet the customers shifting sense of delight and more fun.)

Re: The Last Technical Interview

#146

Earlier quoted context omitted.

- "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.

Yah this was the part that really threw me as well. "People would be pleased to have a rejection from us. They'd be proud to carry it sounds with them. Lucky them!" It's funny, I see an article from Yegge and thought "I like that writer, I haven't read any of his stuff in a while, I'll see what he has to say." Then got to the end and see the links to gas town and gas city and remembered it was the same Yegge that whi…

Counter: I failed a rigorous interview at Facebook years ago and the project lead of their mesh internet Aquila was one of my interviewers. I still was pleased to not have the job because I didn’t really want to be marked with being a Facebook employee.

Re: The Last Technical Interview

#147
post #61

Earlier quoted context omitted.

2 anecdotes ... 1) The worst interview I ever had (BY FAR) was at Google--disrespectful people, no respect for time, I could go on and on. And I went back to try again to get that money showered on me. Worth it in the long run. 2) Their new system for "performance management" is a hoax. Just like at all other places, it "documents" what you should do so they can fire you more easily with unspoken rules and all sorts…

Oh I've had a terrible interview at Google too! They told me it was all about pseudocode and how I think in advance, then on the actual interview they were being annoying about variable names and spaces after comma, while I was supposed to come up with some clever optimisation that boiled down to: "do you know this obscure theorem already? Cool you pass"

Same for me. I applied for engineering manager. Was told it was going to be a code review. I found a bunch of things that it could be improved, detected a very slow part / quadratic loop, but couldn't come up with the best algo to use. It was just leetcode in disguise.

Re: The Last Technical Interview

#148

Earlier quoted context omitted.

- "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.

[deleted]

Re: The Last Technical Interview

#149
post #135

Earlier quoted context omitted.

If you run an interview process where candidates who take 6-8 hours and claim to have taken 4 hours score highest, those are the candidates you will hire.

All these objections rely on removing agency from the professionals applying for jobs. You look at the work sample. You use your professional judgement. You decide if it's reasonable to execute it to what you think a professional standard would be in the time allotted. You make a decision. This isn't a college application.

I think you're answering a different objection than they're making. Their concern is that people will choose to spend 8 hours on your 4 hour problem but then tell you they only spent 4. Then you'll think they're a leet hacker because their solution is so awesome and they did it so fast.

Re: The Last Technical Interview

#150

Earlier quoted context omitted.

The only candidates who would be willing to sign up for that would be ones who were currently unemployed, and with the financial reserves to be able to risk being back out of work in 30/60/90 days. Given how arbitrary in terms of talent mass layoffs are, there are of course tons of highly qualified out-of-work candidates (and due to age discrimination, maybe some of the best/most-experienced ones!), so this certainly…

I was being facetious, sorry if that wasn’t clear. That’s just how Regular Employment works. You don’t even need to tell the employee the implications of being on the 90 day plan. You tell them up front what the expectations are for the role, and if they don’t meet them in 90 days, you fire them. Does not need to be more complicated than that. 30/60/90 is pretty standard stuff. It’s literally the documentation and ju…

> You tell them up front what the expectations are for the role, and if they don’t meet them in 90 days, you fire them.

In the US at least, firing people for cause is difficult to do. More likely you just wait for next RIF and include your low-performers on the list.

So, yes, this is business as usual to some extent, but it's not a very cost effective or efficient way of hiring. If you really have work that needs doing, then you want to hire someone able to do it, not have a haphazard hiring process where it's a crapshoot and "if they don't work out we'll just fire them in our annual RIF, and try again".

Post reply on HN