Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

chrlschn.dev

Post reply on HN
Print view View original

71–80 of 286 posts

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#71

Post by raincole »

bluehorizon2 wrote: post #26

People are forgetting why companies these days do Leetcode in the first place. The initial reason why we have Leetcode today is that Google originally determined through their interview research that the smartest candidates were the ones who were best at algorithms. Google wanted to hire the smartest people, not necessarily the best coders, so that’s why their interviews were mostly algorithmic. Of course everyone st…

How do they measure which candidates are the smartest? And if such a method exists why they don't use this method in interviews directly?

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#72

Post by commandlinefan »

> For hard problems, I may go for a walk, talk to a co-worker, research algorithms, build small toy codebases first

Everything about the JIRA/timetracking/project management regime is expressly designed to prohibit that - you're a programmer, program! Faster! Know the answer RIGHT NOW!

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#73

Post by coffeebeqn »

postalrat wrote: post #61
hcks wrote: post #30

Earlier quoted context omitted.

It’s just a proxy measure for IQ really. They could have handed out Ravens matrices and got better outcomes prediction.

Is memorization how we should measure IQ? If so then LLMs have already far surpassed humans.

A LLM would do pretty/very well in a leetcode interview

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#74

Post by mjohn »

kweingar wrote: post #68
mjohn wrote: post #66

I've never tried it, but in the age of AI why not ask candidates to interact with ChatGPT to solve a problem? In my (limited) interviewing experience the good candidates were the ones who had a good mental model for solving novel problems, were inquisitive and asked good questions. I think these attributes are also a reasonable indicator of general intelligence. The people who I hired that were less successful were t…

Could candidates opt out of using ChatGPT? I don’t think I’d be comfortable using it in an interview.

Sure, why not, I'm just thinking out loud to be honest and am probably biased towards feeling quite comfortable using something like ChatGPT. I don't ask ChatGPT to write code for me but regularly use it to explore, a bit like a rubber duck that talks back.

Just curious - why would you not feel comfortable using it in an interview? Interesting to hear a different POV.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#75

Post by codeTired »

brigadier132 wrote: post #65
codeTired wrote: post #49

Earlier quoted context omitted.

Because adults with hobbies and families have better things to do. How is this so hard to grasp? Bonus is that 90% of devs literally will not use most of that knowledge. My biggest problems are getting requirements, understanding the problem, working around a legacy system or deciphering old code, not actually writing code when requirements and documentation is on point.

> Because adults with hobbies and families have better things to do If you really valued your time you would spend a week studying for the interview that gives you a 50pct or more increase in salary so you can work that many fewer years

I never said I didn’t grind or I won’t grind to move up. It doesn’t change my opinion.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#76

Post by gedy »

hcks wrote: post #30
bluehorizon2 wrote: post #26

People are forgetting why companies these days do Leetcode in the first place. The initial reason why we have Leetcode today is that Google originally determined through their interview research that the smartest candidates were the ones who were best at algorithms. Google wanted to hire the smartest people, not necessarily the best coders, so that’s why their interviews were mostly algorithmic. Of course everyone st…

It’s just a proxy measure for IQ really. They could have handed out Ravens matrices and got better outcomes prediction.

Hell I wish they would tbh. I have a decent IQ (140), but can't (or just unwilling to) grind leet code

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#77

Post by bobobob420 »

indymike wrote: post #69

We use this process, and it has helped us hire some great developers without having to use third party staffing and headhunters: 1. Post well written job post on major job boards. 2. Immediately reply via text to every applicant (yes, we have opt in on the application) 3. Initial screening including several knock-out questions via text. Immediately let candidate know if they are not selected and why. 4. 30 minute can…

"Bring a side project, show us how it works." Can people in the industry stop this please? You have to be mentally sick to ask people to code review their side projects. It doesn't make any sense.

"Average developer tenure is two years, company is three years old." Got it. I don't think this statement says what you think it does.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#79

Post by farhanhubble »

bluehorizon2 wrote: post #26

People are forgetting why companies these days do Leetcode in the first place. The initial reason why we have Leetcode today is that Google originally determined through their interview research that the smartest candidates were the ones who were best at algorithms. Google wanted to hire the smartest people, not necessarily the best coders, so that’s why their interviews were mostly algorithmic. Of course everyone st…

I'd wager that the best mathematicians would fail on these "algorithmic thinking" interviews. Modeling a problem, even a simple one, as a computational problem requires time, trial and error beyond what you get in an interview.

Re: Interviews in the Age of AI: Ditch Leetcode – Try Code Reviews Instead

#80

Post by shortrounddev2 »

Dudester230602 wrote: post #54
shortrounddev2 wrote: post #32

Earlier quoted context omitted.

In my experience the biggest bottlenecks are in the network. Most optimizations are also very very low hanging fruit because the original code was written by a moron

Also, using scripting languages and misusing browser engines unironically yet expecting performance...

Using electron isn't a performance decision, it's a labor one. It's easier to write a website once and then just export to electron than it is to rewrite your application in QT or XAML or another native desktop framework and have to hire C++ or C# developers
Post reply on HN