This is just, like, your opinion. Your future employer may think otherwise, and look for people with algorithmic skills. "But leetcode is actually evil" is just your rationalisation of your cheating.
This is just, like, your opinion. Your future employer may think otherwise, and look for people with algorithmic skills. "But leetcode is actually evil" is just your rationalisation of your cheating.
But then of course, since FAANG did it, everyone else jumped on the leetcode bandwagon and started asking ridiculous DSA-exam-type questions that had nothing to do with their actual work, even if they had the capacity to conduct proper interviews for their candidate volumes.
I am an employer and would much rather have in person interviews than leetcode.
It doesn't test for anything that AI can do already if not faster otherwise.
Its almost useless as a way to learn how to be a better coder, as most of the "fastest" answers are unreadable.
But if you are using it as a basis for interviews, you are more likely to bump into someone who has trained on that particular question.
I'm not sure what the answer is, as other said, pair programming is kinda the answer. Maybe debugging something in your code base.
No, also mine.