The guy didn't get lucky, the guy has experience and has worked hard. The same thing happens in software, the developer with extensive experience across many areas, that has studied tons of different things is more likely to solve a novel problem than the developer that is one dimensional and master of one tool.

I often see people say things such as, "I have tons of experience with language Y and framework Z and that's all that matters, who cares about trees, graphs and all that ridiculous interview questions..." The big tech companies are looking to innovate and lead, and that's why they ask these questions.

If someone is new to programming and begins by telling me what framework they are considering learning, I often tell them to forget about the framework and learn the language. The language is the foundation that frameworks are built on. Algorithms & Data structures are the framework on which software is built on.

The only time I frown upon such questions is if someone is testing you for exact syntax of the language instead of making sure you understand the nature and solution of the problem.

You pretty much argued the opposite of your point.

Asking algo and whiteboard questions completely ignores the "extensive experience across many years". I can spend years gaining deep expertise in an area, and that means absolutely nothing. All that matters is I practiced for 2 months white boarding algo questions under time pressure.

Or to put it another way. Spent 5 years getting a PhD? Who gives a f*ck. Can you code a DP problem in 20 minutes? You're hired!

So you only need to spend 2 months practicing, and yet you refuse to put in the effort ?

I am sorry but this is insulting. You should practice what makes you better at your job, not jump through hoops for someone else’s entertainment. So yes, some of us, are logical enough to not join the hazing ritual. Just cause you want to do it doesn’t mean others should.

Just think of it as part of the job. The trade off is minimal, while the benefit is clear. If you still don't want to do it then its cool, less competition for those who want.

My point was that the interview process is flawed. It's really just a proxy for an IQ test (a gameable one). I think for a company like Google, it is somewhat understandable - they have very mature processes, strict coding guidelines, and overall very little choice in the tech you use. They are hiring for a "smart cog" rather than "innovative/experienced engineer".

I never thought about algorithms this way. However I would argue it’s much better to study functional patterns and understand why those patterns are useful.

Architecture is also another part that most programmers fail to grasp.

I think of algorithms as good to know but rarely used. It’s has an answer to every question. So what you get is a bunch of people cramming questions and answers until they memorise it; defeating the entire point.

Seredendipity -- when preparation meets opportunity.