There is an absolutely vast array of stuff you need to know to write software including networking, hardware, software, database, operating system, multiple lan

There is an absolutely vast array of stuff you need to know to write software including networking, hardware, software, database, operating system, multiple languages, mutiple tools, standards, testing, processes, and on and on and on and on. It goes on forever. BUT one of the things I've pretty much never needed is leetcode. That says something about recruiting processes that evaluate you on your leetcode. If you can't come up with an interview proecss that evaluates a developer against the bajllion things that developers have to do, then it says YOU the interviewer don't know what you are doing. I think leetcode interviews are lack of imagination on the part of the interviewer. Being good at programming does not make you good at assessing the capabilities of other programmers.