Earlier quoted context omitted.
I've seen plenty of HN threads where good alternative processes were described. I'm not going to be exhaustive here: writing a program over a few hours that is reflective of the kind of work that the company actually does, coming up with and debating the architecture of a system, mock code reviews, etc. You might say these don't scale as well as standardized testing of university classical algorithms knowledge. The g…
At big tech companies, "writing a program over a few hours that is reflective of the kind of work that the company actually does" is not really a good, representative performance measure. Often times, you will be solving problems across multiple domains, outside of your area of expertise. You have to take on the role of PM, data scientist, SWE, researcher, etc. Internal restructuring of the company may even take you…
This is a stretch. It's unlikely that an interview process would test such disparate skills directly, and a competent company will avoid moving an engineer into a role that requires a drastically different skillset without separate verification that they can handle the new role.