Live data from Hacker News

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

chrlschn.dev

281–286 of 286 posts

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

#281

Earlier quoted context omitted.

That's because it is memorizing chess openings, or basically the same thing. Most Leetcode Mediums fall into the category where the type of solution is obvious (sliding window/graph search/etc), and the code isn't hard to write, but there's a "trick" embedded in the problem and if you don't already know the trick, you're never going to figure it out in 30 minutes. So the best strategy is to find a "Top N Leetcodes" l…

> Most Leetcode Mediums (...) there's a "trick" embedded in the problem and if you don't already know the trick, you're never going to figure it out in 30 minutes I am sorry to say, this is just not true. > but having a few dozen solutions already memorized should let you do some pattern recognition Chess opening memorization is pure "remember the moves, play the moves" that's it. No thinking or pattern recognition i…

Do you have any evidence that isn't true? How often do truly new problems come up? Nearly every problem I see is after someone gets an an algorithm named after them.

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

#286
post #266

Earlier quoted context omitted.

I had one that wasn't fabricated when I worked at Strip. There was an old bug in the requests library for Python where it was sending wrong data when posting a stream and the response had to be retried. The bug had already been fixed upstream. We cloned a repo, ran they tests, it failed, and the task was to identify why it failed. It was a tough process for me, since I've never really used Python debugging tools, so…

Thanks for relating your experience. I'm sorry to hear that it was uncomfortable and stressful, but it sounds like you must have reacted pretty well in those circumstances to get an offer. Do you feel like the skills assessed by the interview were reflective of what you ended up doing on the job (assuming you accepted) ?

There are always going to be parts of life that are uncomfortable and stressful. This one wasn't terrible, and I appreciated a new outlook on how to assess skills. The interviewer was very understanding and we meshed well, so I don't think it came off as negative.

Were they indicative? shruggie. I mis-typed, I interviewed there, didn't work there. And I haven't used the python debugger since, but I also haven't worked on much python code.

Post reply on HN