7 ms·
For the sake of argument: What if they have multiple candidates and they want to know which ones can solve problems better with code instead of hiring by vibes.
by notepad0x90 1y ago
For the sake of argument: What if they have multiple candidates and they want to know which ones can solve problems better with code instead of hiring by vibes.
- AnimalMuppet 1y agoEven 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...
- theoldgreybeard 1y agoThe topic is leetcode. I've written code during interviews and in reasonable takehomes before. If your choice of candidate is boiling down to fizzbuzz I'm not interested.
- notepad0x90 1y agoI can respect that, you must have enough talent and experience to allow to pick and choose opportunities. The job market is rough these days and for most, they need to eat and pay bills.
- JonChesterfield 1y agoLook at the code those people have put into production instead. Or accept that you're filtering for pain tolerance of nonsense and the people you get will put up with grindy nonsense in your company. Which could be a blessing or lethal, depending on what you're doing.
- jimbomins 1y agoIt strikes me that software has become a bit like law and accounting used to be. "We had to suffer and so must you". Making it pointlessly hard to keep people out. Rather than dealing with people on real problems. I'm currently getting interviews. For work that I know from having done it for twenty years that coding is only a small subset of. But the emphasis is far more on coding than application of experience gained to overcoming similar problems quicker the second, third or fourth times I'd be working them. It's sad. I'll certainly just say no to leetcode for the kind of engineering I'm looking for. Rather go do some (paid) gardening.