>It doesn't require a university degree but it really does help, the more people that have an idea of algorithmic performance both regarding memory and CPU resources the sooner we can get away from all these "web-applications" that barely work but still loads a few mb of unnecessary js libraries.

IMHO, this is exactly the kind of academic fetishization that makes these terrible interview questions so common in the first place: Knowing CS theory isn't going to slim down your build size or resource usage - knowing how to slim down your build size and reduce resource usage will do that.

And besides: no junior developer is going to be handed the kind of task where CS knowledge is remotely applicable. They are going to be building React/Angular/Etc components making backend CRUD APIs. They aren't going to be rewriting searching or sorting algorithms. For that matter, they aren't even going to be deciding what libraries to include that overload your phones resources.

I know more than enough CS theory to play the interview games. How much have I used it on the job? Maybe a couple of times a year, if that. In the first few years, never at all.