"Bad leetcode, great and relevant experience" - that's me after 20 years in the industry and at least 30% of that time working on very non-trivial systems. I us

"Bad leetcode, great and relevant experience" - that's me after 20 years in the industry and at least 30% of that time working on very non-trivial systems. I usually don't do actual leetcode actually, I review algo books before interviewing. In the last few years it stopped working for me even at no-name companies. But I find it nearly impossible to force myself to leetcode, it feels humiliating and stupid. Another thing I noticed is that they stopped asking questions about concurrent code or writing recursive-decent parsers. They seem to be strangely fixated on a narrow and not particularly practical subset of CS body of knowledge. We don't discuss OOP or its alternatives anymore. Companies don't seem to care about my actual hard-won real life experience even when it directly applies to the kind of domain/system they are building. Don't get me wrong, I expect people to know how to perform depth-first traversal or the general idea behind quick sort. But we are long past that stage even in small companies with average pay at least here in the SFBA.