| I mean there’s two camps. One camp can do them easily or with practice, another camp can’t. The first camp is pretty “meh” about leet code interviews because for them you just study a bit and get a high paying job. The second camp is pretty vocal about how bad leet code is because it’s somewhat of a personal attack on their abilities. Personally I agree with the criticism that leet code can be learned with enough practice and so it’s not totally indicative of a positive hire. But then I also sorta feel like there’s enough examples out there that people should be able to ace these tests with practice. Some SWE just write code, they wanna make features and build a product. They don’t care about this stuff because things are fast enough without the extra thought — and if they turn out not fast enough they can still fix the issue. Other SWE are more careful with their code, performance, etc. this is more of a systems engineer personality. Writing C, managing memory, writing optimized code the first go round. Yah, being thoughtful and careful pays off here. No one’s right or wrong imo, or one better than the other. Should FAANG do leet code interviews? I dunno, there’s surely better ways to interview, but at the same time they’ve hired plenty of highly talented engineers so something’s working for them? Should SWE’s just spend a few weeks on leet code and learn the tricks? Ya, it’s pretty easy. But if you don’t want the job then don’t do it? All the endless criticism of leet code generally comes from people who fail it. Shrug. |