3 ms·
Even so, why see which ones can solve problems that aren't the problems that the job actually calls for solving? I mean, if you're Google, and a small improvem
by AnimalMuppet 1y ago
Even so, why see which ones can solve problems that aren't the problems that the job actually calls for solving?
I mean, if you're Google, and a small improvement in algorithmic efficiency means needing a thousand less servers, yes, you want people who know that kind of stuff like the back of their hand. Most places aren't Google, though. Places that interview like Google that don't have Google-like problems have a mis-fit between their interview process and the roles they are interviewing for. So, places that aren't really on top of what they're doing as an organization.
- notepad0x90 1y agoLet's assume all the other candidates can get the job done, the problems that need solving can be solved by most competent programmers. They want to know if you can solve problems they haven't even thought of at that point. Salaried employment is not the same as a contract with specific scope of work.
- AnimalMuppet 1y ago> Let's assume all the other candidates can get the job done Let's not assume that. There are places that have trouble finding people that can code at all.
- notepad0x90 1y agoThose places don't use leetcode.
- AnimalMuppet 1y agoAnother assumption? Or a claim? If it's a claim, I don't think it's as true as you do. You made the claim, so you have the burden of proof. And if it's just an assumption, well, I don't assume that either...