Comment by mattkrause
2 days ago
> 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 longest palindrome.”
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 able to figure out on the fly?
[1] https://www.otherbranch.com/shared/practice-coding-problem
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.
Yeah, it's very intentionally not a typical leetcode problem, precisely because leetcode is nearly worthless for screening people these days. I was replying to someone who seemed to be objecting to my opinion of some candidates' skills on the basis that maybe they just didn't know the specific thing we ask.