Not to knock this content, anyway. I found this repo to be well organized and genuinely interesting -- just not super relevant for me...
Being able to parrot the crap you where taught in college is only useful for interviews, which is a sad reflection of what interviews actually test for.
You are completely right about what you said but I'd like to add one thing is the most important for any software engineering roll at any company: your ability to learn as you continue practicing in our field. That should be the highest priority. How do I familiarize myself with all my tools and resources not so I can do my job really well but so I can move to any task and execute it well?
That should be the focus of any practicing software engineer. To be able to learn and adapt as requirements and goals change.
I agree that the emphasis Google puts on algorithmic interviews is a bit dumb, but that how their hiring system works. So anyone who really wants to get a job at Google needs to work on that, regardless on whether it will be useful inside the company or not.
There are millions of programmers, most of which will never get a job at Google. Is their time perhaps better spent optimizing their existing careers instead of doing "dumb" things for a chance at the gold-plated goose?
1. they have a lot of applicants to pick from.
2. they do it for cultural reasons rather than purely for on-the-job performance reasons.
Culture is a long term investment.
Pretty sure tons of content have been written about all of these topics, and not particularly hard to find.
Read Shapiro's "Corporate Confidential". Despite the rather click-baity (read-baity?) title of the book, it's an fairly good explanation of career management and politics of mid-size to large companies. I'd recommend it to all new graduates entering the workforce.
As you say, almost none of your actual job depends on knowing any of that material in any way. However, you aren't even getting in the door unless you know it all, which is indeed arbitrary and a waste of everyone's time and energy.
Thus, good engineers who didn't happen to study academic CS at Stanford or MIT must regrettably waste months of their lives self-studying CS trivia which they will never use again except at other interviews. Being good engineers, they have studied how the system works and taken the rational and necessary step to participate in it. That's why so much ink is spilled on it.
This is the key to only one (admittedly pretty) door, though. Are the benefits of getting through that particular door truly worth the cost?
I think this question is even more important when so many other companies are now moving away from algorithmic interviewing techniques since they aren't Google.
I'm slowly learning that despite how much more money I've earned by skipping between companies, skipping is not a path to knowledge. It provides better earning opportunities (to a point), it provides new challenges on a regular basis, but I've lost the ability to go deep into a topic. The depth that can't be achieved in two or three years.
I guess I'd really like to see a bit more ink spilled on "congratulations, you got a job; now what?" What interpersonal skills are most important? What are good resources for continued learning? What do C level people actually do? How can I help the company succeed? What career opportunities are possible for me without having to skip jobs? What can I learn from this company before I go to create my own?
That would be much more valuable, IMO, than a primer on how to pass an interview process.