Live data from Hacker News

AI killed the tech interview. Now what?

kanenarraway.com

341–350 of 651 posts

Re: AI killed the tech interview. Now what?

#341

Company A wants to hire an engineer, an AI could solve all their tech interview questions, so why not hire that AI instead? There's very likely a real answer to that question, and that answer should shape the way that engineer should be assessed and hired. For example, it could be that the company wants the engineer to do some kind of assessment whether a feature should be implemented at all, and if yes, in what way.…

The even bigger challenge is that hiring experts in any domain requires domain knowledge, but hiring has been shifted to HR. They aren't experts in anything, and for some years they made do with formulaic approaches, but that doesn't cut it anymore. So now if your group wants to get it done, and done well, you have to get involved yourself, and it's a lot of work on top of your regular tasks. Maybe more work because…

HR are experts in HR, which is to say they have a broader view of the institutional needs and legal requirements of hiring staffing than you do. It's always annoying when that clashes with your vision, but dismissing their entire domain is unlikely to help you avoid running into that dynamic again and again

Re: AI killed the tech interview. Now what?

#342
post #176

Earlier quoted context omitted.

I suspect many people who don't have strong networks for whatever reason resent that. To which you could probably tack on not having gone to the "right" schools or having a public portfolio.

also hard on introverts who already get punished in workplaces that promote ppl based on proximity and visiblity.

Believe it or not, extroverts also have to develop professional skills, sometimes even things that don't come naturally to them.

Re: AI killed the tech interview. Now what?

#343

Earlier quoted context omitted.

> A lot of these people … just suck. Another possibility is that their job subtly drifted. I wrote a lot of code as a grad student but my first interviews afterward were disasters. Why? Because I’d spent the last few months writing my thesis and the few months before that writing a very specific kinds of code (signal processing, visualization) that were miles away from generic interview questions like “Make the longe…

We don't ask "make the longest palindrome". We ask "convert this English into code that does what it says". If you want to make the discussion more concrete, we have a public practice problem [1] that we send out with our interview bookings so that people know what to expect. The real problems we ask are very similar to it. Do you feel like there's anything there that any reasonably skilled programmer shouldn't be ab…

That's not a typical leetcode problem though. Most companies ask things like "solve this slightly modified knapsack problem" which takes 5 minutes if you know the solution and 50 minutes if you don't.

Re: AI killed the tech interview. Now what?

#344

The problem isn't AI, the problem is companies don't know how to properly select between candidates, and they don't apply even the basics of Psychometrics. Do they do item analysis of their custom coding tests? Do they analyse the new hires' performances and relate them to their interview scores? I seriously doubt it. Also, the best (albeit the most expensive) selection process is simply letting the new person to do…

Might as well use https://en.wikipedia.org/wiki/E-meter

Re: AI killed the tech interview. Now what?

#345

Earlier quoted context omitted.

> Most people have still written code for school or a hobby project School was years and years ago, and has nothing to do with my current skills. From the people i personally know, most do _not_ have a hobby project, even fewer have hobby projects that showcases their technical skills. Nor should they be expected to. Most people have non-programming hobbies. > I cannot understand how some developers have no code to s…

> It's really not that deep, I'm worried if you really cannot understand. I don't code outside of work, I'm not interested in doing it. I'm good at software engineering, not passionate about it. I have a bunch of other hobbies. There's no reason I'd have any code to show now or at any point in the future. It's like asking a dentist interview candidate to show you examples of fillings and crowns they did at home as a…

[flagged]

Re: AI killed the tech interview. Now what?

#346
post #335

The best interview process I've ever been a part of involved pair programming with the person for a couple hours, after doing the tech screening having a phone call with a member of the team. You never failed to know within a few minutes whether the person could do the job, and be a good coworker. This process worked so well, it created the best team, most productive team I've worked on in 20+ years in the industry,…

>The best interview process I've ever been a part of involved pair programming with the person for a couple hours... You never failed to know within a few minutes whether the person could do the job There is something funny about the "best interview process" taking "a couple hours" despite giving you the answer "within a few minutes". Seems like even the best process is a little broken.

Lightly ironic indeed! Though I’m not sure “broken” is exactly the word I’d choose.

I can only speak for myself, but I imagine myself as a candidate approaching a “couple of hours” project or relationship differently than I would a “few minutes” speed round. For that matter I can think of people I know professionally who I only know through their behavior “on stage” in structured and stylized meetings of a half hour or an hour—and I don’t feel like I have any sense at all of how they would be as day-to-day coworkers.

If we sat down to work together, you’d probably have a sense in the first few minutes of whether or not we were going to work out—but that would be contingent on us going into it with the attitude that we were working together as colleagues toward a goal.

Re: AI killed the tech interview. Now what?

#347
post #238

Earlier quoted context omitted.

> unless you're trying to make the non-tech parts of the role too interesting. Unless your role is trivial to replace with an LLM, you need to understand the business. Maybe not for really junior role, but everything above - you need to solve issues. Tech is just a tool.

You don't have to understand the entire business to start being productive. Particularly when you have experience from other, similar businesses.

I am not sure I follow - when you hire you search for someone who has 100% coverage of the tech you're using and also already works for your direct competitor?

Let's say you're hiring manager for a company that compares flight tickets, something similar to Google Flights or Skyscanner. You need three additional Rust engineers. You're located in Palermo, Italy.

How do you hire people that would not only know Rust, be willing to move to Palermo, or at least visit occasionally, but also know the airfare business?

Even if you're willing to have people remotely, in the same region, how many unemployed Rust developers that know that business are on the market? 0?

Re: AI killed the tech interview. Now what?

#348
post #250

Earlier quoted context omitted.

What is the functional difference between copying an AI answer and copying a StackOverflow answer, in terms of it being "cheating" during an interview? I think the entire question is missing the forest for the trees. I have never asked a candidate to write code in any fashion during an interview. I talk to them. I ask them how they would solve problems, chase down bugs, or implement new features. I ask about concepts…

> Languages are largely teachable, it's just syntax and keywords. That's only true for a subset of programming languages, and it requires you to already know how to program in at least another language of the same family. Knowing Java will not help you with Haskell, but it will help you with C#. I have to deal with students using AI to cheat on homework and exams, and I can't allow them to not even learn the basic co…

> That's only true for a subset of programming languages

That's true, but most of the industry is running on a subset of programming languages.

Re: AI killed the tech interview. Now what?

#349

Earlier quoted context omitted.

also hard on introverts who already get punished in workplaces that promote ppl based on proximity and visiblity.

Dealing with people and communication can be learned. I get it. By nature I was very much an introvert except for certain scenarios when I was in my comfort zone until at least my mid 30s. I was an only child, the stereotypical short, fat kid with a computer growing up in the 80s (still short, became a gym rat, part time fitness instructor and only stopped the latter as my other obligations became greater). Horrible…

Well put. I'm an introvert, I can't do math, I won't travel, etc. are all things that some people claim as if it's the unchangeable nature of things. If that's their chosen path, so be it. But they should understand it will probably be pretty limiting because the world they live in.

Re: AI killed the tech interview. Now what?

#350

The best interview process I've ever been a part of involved pair programming with the person for a couple hours, after doing the tech screening having a phone call with a member of the team. You never failed to know within a few minutes whether the person could do the job, and be a good coworker. This process worked so well, it created the best team, most productive team I've worked on in 20+ years in the industry,…

Some of us find the prospect of pairing with an unknown person in an unknown environment, and against the clock, to be very stressful.
Post reply on HN