>> You're given weeks to refresh your knowledge ahead of a Google interview
Begs the question, doesn't it?
>> Binary trees are MOST ASSUREDLY on that list
Sure they are... and my intro to CS textbook was ~500 pages. I'll bet I could find something to trip up just about anybody, especially when coupled with the pressure of doing it in front of the class ^H^H^H people that have $$$$/power over you.
Another instance where silicon valley favors the young... he probably would've nailed this question if he'd been only a couple of years removed from school.
He also would've nailed it had he been given 10 minutes to do some research to refresh.
Silicon valley (and the numerous companies that mock the interview style) are testing for the wrong thing when they hire, then complaining about not being able to find good engineers.
I was on BOS around the same time patio showed up... It's amazing to see how "far" he has come. What he has mastered is marketing to developers, more than anything else. Of course it doesn't add up, because it's like all marketing: all sizzle, no steak.
I think you're overestimating how hot of a skill that actually is...
But even if you could make "boatloads" of cash consulting, not everyone desires the road warrior lifestyle that goes along with consulting.
We want someone who has less than 12 years of MANAGEMENT EXPERIENCE. The reason is that if you haven't been coding for 12+ years...you probably are not "hands-on" enough
This arbitrary cutoff makes absolutely no sense. I'd like to see your quantification of skill drop off per year of management.
If what you are wanting is a hands-on technical manager, then you need to say so.
And it shouldn't matter if the person has been hands on for 5 years or 20.
But I feel I'm being a little too generous regarding your motives here.
As i posted above... Lightweight processes were discussed as alternatives to waterfall way back in the 90s during my software engineering courses. "Rapid application development" and RAtional unified process were the "hot" lightweight methodologies when I started work in 1996. Scrum has been with us since 1995.
And yes, it's blatantly ageist... It falls under the disparate impact provision:
"In addition to prohibiting intentional discrimination against older workers (known as “disparate treatment”), the ADEA prohibits practices that, although facially neutral with regard to age, have the effect of harming older workers more than younger workers (known as “disparate impact”), unless the employer can show that the practice is based on an RFOA."
Nah... Lightweight processes were discussed as alternatives to waterfall way back in the 90s during my software engineering courses. "Rapid application development" and RAtional unified process were the "hot" lightweight methodologies when I started work in 1996. Scrum has been with us since 1995.