3 ms·
The problem I see over and over is that the new "job relevant" interview formats are always way easier than the old interviews. It is not even close, maybe as h
by brhsagain 4y ago
The problem I see over and over is that the new "job relevant" interview formats are always way easier than the old interviews. It is not even close, maybe as high as by a factor of 10.
People argue that we should make interviews more relevant to the actual work you do on the job. But in practice it looks a lot like we're really just trying to pass more people. Half the new "practical" questions are literally like make an http call, iterate through the array of objects and do some basic data transformation using map and filter. Or something. The actual thinking part is usually about leetcode easy, maybe low medium.
Seriously, any time I see a "modern" non-leetcode interview I basically start rehearsing salary negotiations in my head. I suppose you could argue that's all that's needed to do 90% of modern software development, and so the new questions are measuring the right thing... but then doesn't that just indicate that modern software development is a joke and the job is not actually hiring developers to do anything difficult?
- notpachet 4y ago> but then doesn't that just indicate that modern software development is a joke and the job is not actually hiring developers to do anything difficult? You just said the quiet part out loud. Most of what we're doing is just slinging CRUD code. Some of the worst developers to work with are the ones who think they're God's gift to programming, because they're the ones who twist the codebase into knots in pursuit of cleverness points. Guess which type leetcode filters for.
- brhsagain 4y agoYes, this is true and a real problem. The empire-building types. My personal favorite non-leetcode interview format is having the candidate spend 2-4 hours building a toy version of your product from scratch. It's hard, relevant, and filters for straightforward code (or you won't finish in time).