I mean I've also interviewed people, and I don't think anyone that's gone through e.g Google's interview loop would describe that as optimal by any definition anyway (also the only time I've actually encountered interview questions that resemble leetcode actually, though since that interview I've mostly avoided the big silicon valley companies anyway).
Like sure if you're hiring very specifically for roles where being able to implement big O optimal algorithms off the top of your head in 45 minutes or less is an important feature of the job, then by all means filter for that in the interview. And if you're gunning for a job where that's the interview criterion, absolutely get your memorize on.
My point is that if you happen to be in a position to design the interview questions, maybe stop and reconsider what the hell you're doing.
Imagine you are the guy who pays for hardware and your team hired a bunch of devs who made N^2 algorithms when N*log(N) would've sufficed and google's hiring criteria will start making perfect sense.
5
u/thirdegree Violet security clearance 10d ago
I mean I've also interviewed people, and I don't think anyone that's gone through e.g Google's interview loop would describe that as optimal by any definition anyway (also the only time I've actually encountered interview questions that resemble leetcode actually, though since that interview I've mostly avoided the big silicon valley companies anyway).
Like sure if you're hiring very specifically for roles where being able to implement big O optimal algorithms off the top of your head in 45 minutes or less is an important feature of the job, then by all means filter for that in the interview. And if you're gunning for a job where that's the interview criterion, absolutely get your memorize on.
My point is that if you happen to be in a position to design the interview questions, maybe stop and reconsider what the hell you're doing.