Tell that to managers - oh wait - hire on algorithms and performance review on BS such as commit count.
It doesn't, and it always baffles them when I don't even give them a whiteboard problem to solve. I don't need people who have memorized all graph search algorithms, I don't need people who can code them up in 6 languages without looking anything up. People who can google competently (or use a textbooks index) can do the former just as well, and LLMs can do the latter.
What I need are people who can take requirements, anticipate as much as humanly possible what else the client will do over time, and find a maintainable architecture that implements those and maybe is resilient when facing further changes down the road.
And that is a HARD skill, that leetcode and most of what CS curricula will not teach.
Requirements gathering gets short shrift, if it's mentioned at all. But really, it's the overwhelming majority of the job.