[romanhn]

Leetcoding is certainly a big one. Having to jump through performative interview hoops is a tough pill to swallow for experienced folks. Took me many years to put my feelings aside and recognize it as the current normal.

Otherwise, plenty of reasons, many dependent on specific companies. Some examples based on both first-hand knowledge and hearing from others:

Facebook/Meta - tough performance culture, bad work-life balance, terrible public image

Amazon - toxic exploitative culture, bad work-life balance, sliding public image

Apple - secretive culture, bad work-life balance

Netflix - unique performance-oriented culture that won't fit everyone (see the infamous culture deck)... but interviews are team-specific and not necessarily Leetcode-oriented

Google - growth is difficult, sliding public image

Keep in mind that these are aggregate impressions based on many anecdotes. Some teams will not exhibit the same issues. Some people are also not bothered by the same issues you might be (and vice versa).

[olliej]

I’ve gone through multiple interview processes with apple and never dealt with leet code.

Interviews at google seemed 50/50 split leet code (or interviewer showing off being clever) and reasonable questions.

I recall thinking that my MS interview questions seemed perfectly reasonable, but that was too long ago for me to recall specifics.

As a someone who has been the interviewer I think that people really don’t understand what whiteboard interviews are doing, and a number of claimed “leet code” questions are not. Part of it is that if you’re interviewing at Apple or MS knowing basic algorithms and complexity analysis is important because working at those companies you will be the one implementing such things so other developers don’t have to.

A lot of what people are calling leet code on HN, Reddit, etc are what I would consider foundational knowledge, not anything crazy.

[amerkhalid]

I have been practicing leet code on and off for a bit. I understand all data structures and algorithms that these interviews supposed to cover. I can explain and teach these concepts to others.

But leet code questions are still riddles to me. I have also been watching videos of some famous programmers solving leet codes on YouTube and even they get stumbled and take almost an hour to solve some of these questions.

But once I have seen a solution and memorized general approach, I can solve it under 20 minutes. To me, leet code is more about memorization than actual problem solving skills.

[gaws]

> Leetcoding is certainly a big one. Having to jump through performative interview hoops is a tough pill to swallow for experienced folks. Took me many years to put my feelings aside and recognize it as the current normal.

If you're applying to, say, Google, you do this once then have a very well-paid job for life (theoretically). That, to me, is a good trade-off.

[romanhn]

Unless you're planning to spend the rest of your life at one company, your theory is not true. The next company is likely to follow a similar process, even if they're not Google caliber.