> Most "leetcode" questions they ask are just easy level programming puzzles. As a senior developer currently looking for work, I have mixed feelings about lee

> Most "leetcode" questions they ask are just easy level programming puzzles. As a senior developer currently looking for work, I have mixed feelings about leetcode-like questions. Here's my take: Pro: They rule out most/all applicants who lack basic programming competence. Con: Any timed or live programming test can make some applicants fail because of performance anxiety. Pro/con: Some of the problems require (a) very high intelligence or (b) familiarity with how people have solved that specific problem in the past. I think (b) is a major source of complaints, because for most people the only solution is Leetcode grinding, which outside of the interview process isn't a good use of one's professional development time. Con: At least for timed problems on Hackerrank, you have a dilemma: A simple, straightforward solution takes little time to code, and is easy to explain. But it might also take too long to run on some of the test cases, which then requires you to guess at the source of slowness, and try to fix it. But in multi-problem Hackerrank tests, you don't necessarily know if you have enough time to do that, because the other problems in the set might or might not require lots of time as well. And you can't revisit an earlier problem once you've submitted a solution.