So let me get this straight, you cited a random "first link you dug up", unrelated to your point, and claim it as evidence because you "wouldn't be surprised" if some other article (that doesn't exist) supported your view?
I didn't cite it, and I didn't say some other article existed..
What I said was basically "google admitted their old method didn't work, here's a link if your interested. I wouldn't be surprised if the new method doesn't work either, and we see articles about that in a few years"
The I "wouldn't be surprised" part comes from both methods actually having very little to do with the job at hand, and therefore I think they would BOTH be bad predictors of performance at that job..
// What I said was basically "google admitted their old method didn't work, here's a link
No. Your previous post said they admitted their "leet code" interviews didn't work. leetcode means something specific.
Also I'd draw the opposite conclusion. Sounds like Google is "on it" in terms of evaluating what works and what doesn't. They threw out brainteasers because they didn't work. That suggests whatever they kept does work.
Can't say I agree with your 'on it' conclusion, but I guess time will tell. It took them about 15 years to get rid of the brain teasers (1998 to 2013ish from what I can tell), so if they're consistent we should hear one way or the other in 2028ish :-)
"It took [Google] about 15 years to get rid of the brain teasers (1998 to 2013ish from what I can tell),..."
During which time the company grew from what to what?
(Actually, when I interviewed in ~2003, I didn't get any brain teasers. All of the questions where either fundamental computer science knowledge or related to the (SRE) position---although they would all be considered "leetcode" by someone without the background. I was pretty impressed.)
https://www.theatlantic.com/business/archive/2013/06/google-...