[oblio]

Leetcode problems doesn't mean leetcode.com problems in a narrow sense (aka copy paste).

It means reasonably complex algorithmic and data structure problems you're supposed to solve by coding under pressure, quickly, in interview conditions.

And if you think that's not happening, I have a bridge in Brooklyn to sell you.

[nobleach]

I suppose I AM confused then. I don't mind someone asking me complex algorithmic problems as long as we're WORKING toward a solution together. To me, leetcode means, "you have 45 minutes to solve these 2 or 3 problems... I'll watch".

Algorithmic thinking is kinda what I do. So solving those problems doesn't feel like a bad proxy for how I might perform on the job.

[oblio]

Yeah, we all solve problems using algorithms.

However, how often do you come up with high performance, close to optimal algorithms, on your own, within 45 minutes?

How often do you implement heaps and such as part of your day job, versus using standard libraries or common ones?