And what's the deal with doing code interviews in Google Docs? I don't know if that's how it's done now, but it was extremely high-pressure. Given that he could see every keystroke and was pretty un-cooperative, it made for a super unpleasant interview with the constant feeling that I couldn't think or explore the problem given.
Needless to say, I didn't progress.
Thankfully, the person I dealt with was generally pleasant and made for one of the better interview experiences I've had.
Yahoo used collabedit.com, which was much more pleasant (but still realtime).
I had a similar experience as yours - got a guy that seemed uninterested, and who then proceeded to give me interview questions that firstly were totally irrelevant to the position, and totally outside of the area the recruiter had told me I was meant to be asked about. Secondly they made it clear that the guy interviewing me had a very specific idea of what answers he wanted, but didn't have sufficient knowledge of the field to realise that his questions were ambiguous or incomplete.
After the interview, I was just annoyed. I didn't see any point in waiting for feedbackm and fired off an e-mail to the recruiter, telling her I'd lost interest if that was how they managed their tech interviews. I also gave her the details of the questions and answers I had issues with (which was most of them).
She got back to me a few days later, and informed me she'd discussed the interview details with a few people, and everyone agreed with the points I'd made, and she had gotten it set aside and offered me to proceed to the next stage.
But at that point I declined - I'd had interest from a couple of prospects I saw as more interesting, and the (glacial) pace at which the process had been progressing and the issues with the phone interview (conducted by one of the engineers in the group I'd be managing if I'd been offered the position) gave me a fairly negative impression. I've talked to a number of Google recruiters over the years, both people approaching me to get me to interview, and in other situations, and _every one_ of the ones I've talked to have been totally exasperated over the recruitment process they have to deal with.
Second interviewer didn't read feedback from first, repeated one or two questions. Got to third round and withdrew.
That last person I spoke with never introduced himself, asked essentially an open ended question with no real answer. I presented what I thought was reasonable, he said "that's wrong", and never answered what he thought the approach/answer should be. Relayed this to a friend there just after the interview - her response was "that is an idiotic question and actually your answer was correct".
I was declined for the position, but still get calls by google recruiters on a regular basis. I relay the story and politely tell them no thanks.
Combined with the fact that Google ties roles with geographic location, and doesn't reveal what post people will work on during recruitment, this assertion is quite amusing. I suppose he thought he was an expert too! That interviewer is selecting for hubris with this question at least - often those willing to call themselves experts are anything but.
If the best people in x live happily in Toronto and Bangkok and the team is in Mountain View, Google won't be hiring them or even probably interviewing them because of their opaque and broken interview process, which is a shame for Google I guess. The insistence on relocation and the refusal to recruit for actual roles must put an awful lot of good people off.
Funny. One of the Google recruiters told me that expert at technology X meant you either wrote a book on or invented X.
People in my life think I'm arrogant when I say I'm not interested in working for Google, but it's more just that it's not a "good fit" for either of us.
It might be apocryphal, but at one point candidates filled a "rate yourself from 1 to 10 in technology X, Y, Z" to help guide the interviewers in choosing questions. The general consensus was "if you rate yourself as a 10 in Python, there's a non-zero chance you'll end up with Guido on your interview panel"
I had the distinct feeling that the outcome of the hiring process really had nothing to do with the interview so long as I answered competently enough.
One interview I nailed, got to the second round phone interview nailed it and then didn't get a call back...ever.
Out of curiosity I send some emails off, turns out the recruiter had quit or "was no longer with the company" or whatever and they had filled the position, please feel free to apply again.
Regardless, it didn't really matter, I had a good time, it was fun, I didn't get the job, but meh. I didn't have to go through the hassle of relocating either.
The few other SV type company interviews I've been on have been similar. Not terribly hard, a few brain teasers, lots of vocalized processing of my thinking process, but even with the ones I got an offer for, came away with the distinct impression that the interview particulars just didn't matter all that much. They were simply confirming some predisposed hiring assumptions and would probably go with whoever went to the best school or whatever arbitrary metric they were using.
They were looking for X, using a hiring process that looks for Y, and it all ended before a committee that hired for Z anyways.
I think this is the most important factoid that's come out of this all is this realization that Google finally had after crunching years worth of data (which was already common knowledge among the rest of the world):
"G.P.A.'s are worthless as a criteria for hiring, and test scores are worthless. ... We found that they don’t predict anything."
Well, they do predict that people who are given near term ranking and validation of their work will work their asses off to get that ranking and validation.
A little etymology: valedictorian, from valediction, from Latin valere
validate from Latin validus (see valid) from valere
So it's no wonder that valedictorian and validate have the same root. A high achiever is by definition somebody who's efforts have been validated against the measure of achievement (whatever that measure might be) and confirmed to be valere "well", "strong".
It's too bad that what a company needs is an employee that does their job, not one that needs to be constantly validated in their efforts.
And thus a hiring system, put together by validators, who designed the hiring system to validate and filter for people who focus on validation, forgot to look for people who get shit done and don't need to be thanked for it.
And as a result, Youtube becomes more and more unusable every single day.
I'll walk you through it.
Valedictorian used as a noun in 1832, adj in 1834. American English. From Valedictory adj. and -ian variant of -an, Middle English -ien from French loan words, -an "pertaining to" from Latin -anus.
Valedictory first used in the 1650s, from the Latin valedictum from valedicere and -ory from Latin -orius, -oria, -orium "to have a quality proper to the action accomplished by the agent".
valedicere from vale, imperative of valere "be well" and dicere "to say". See also "Valediction" from 1610s.
Validate v. from 1640s from Latin validatus, from validus, from valere "be well", "be strong" (connoted)
I'll add that the Latin vale can be used to mean "farewell", which is usually how it's translated, but if you dig down the etymology rabbit hole, they come from two different language families and not surprisingly don't mean the same thing.
"farewell" is from somewhere between 1200 and the 14th century middle English, a composite of faren "fare" and wel "well". The phrase used to be "fare thee well" but was contracted later. All have Germanic roots.
"fare" is old-English fær means "to go forth on a journey" and still hangs around in some words like "sea-faring", "wayfarer" and "farewell" ("fare" eventually turned into the more modern meaning "payment for passage or conveyance", but that's a digression).
"well" in the sense of "farewell" these days connotes good health (as in "are you well?") but originates also in Germanic tongues to mean "satisfactory".
"thee" is also proto-Germanic in origin and I won't belabor it.
Swedish speakers may recognize this in the modern form as "farväl" and Dutch as "vaarwel"
A "valedictory" is usually translated as "a farewell address" and the act of the speech the valedictorian gives is called a "valediction" (a farewell). But this isn't strictly correct. "valedictory" means something more like "words for good health".
So it's more like we commonly translate "hope you feel well!" to "have a safe trip!" which isn't really quite right.
It's interesting then that:
a) "well" has come to adopt the Latin meaning "health" in the sense that "valere" means "well" i.e. "health" (similar to "valetudo" or "valetudinis"). "valere" more strictly translates to "health" (which all the other meanings connote e.g. "strength" "well" etc.). Also found in words like "convalescence" with the "strength" connotation ending up in words like "valiant" and "validity". When we "validate" something, we are proving it to be strong, which is a connotation of "healthy". So it really means "to prove to be healthy".
b) We define Latin words in terms of Germanic explanations, but not the other way around. e.g. if you look up "farewell" in the dictionary it's not defined as a "valediction". Which would come as no surprise to those that know that English is a Germanic language.
I interviewed with Google about 2 years ago. First technical phone interview, the guy sounds really grumpy and irritated, and starts off with "I see that you have a Master's in CS. Are you an expert?". I replied something to the effect of "well I think it'd be pretentious for me to call myself an expert, I like to let my work speak for itself.". He responded "well we only hire experts at google".
The interview went downhill from there; several times he told me my solution to his question was incorrect, and I stepped through the code with him and showed him that he was mistaken and my solution was valid. He was just super grumpy the whole time.
Who knows, maybe my name reminded me of his ex wife or something. Regardless, it was a terrible experience.
I don't think that I sucked that hard because 2 weeks later I interviewed with apple, made it all the way to the onsite, and their questions felt harder. Their process was much more pleasant and efficient overall.