When I got there, I was greeted by my first interviewer who started asking me questions about SONET. I stumbled for a moment then commented that I could try to guess a few answers, but I didn't have any experience with optics. The interviewer looked back and forth between me and his paperwork a few times, got flustered, then asked if I was interviewing to be a network architect.
No, I didn't expect to be.
Well, that's what they had me scheduled for. He asked me a few more questions about things I'd never heard of, then we sat back and chatted about valley life for the rest of the hour.
The trip to MTV was fun, but it would've been more interesting if I'd gotten to interview for a job I actually knew about.
Unfortunately, I've read similar anecdotes on HN. Pretty disrespectful of the candidates time.
On top of that, if you're going to throw out dickish comments like the article states (paraphrase: "ask your friend, he'll know the answer"), I wouldn't stick around. Is that the atmosphere at the company? Agree or disagree with the interview style, comments like that would piss me off to no end. Start a game of needling and insults? You know what, I've had enough.
That's the problem with large companies. There are companies where I would just walk out of an abusive interview, because the brokenness represents their whole company. Then you have massive, mega, ultra-sized companies like Google where even though this particular team is beating you with the interview bat, you may still want to work for other teams.
This is probably confirmation bias speaking, but by far I hear the most "primadonna interviewer" stories come out of Google. I'm not sure if that's just my impression or if there's really something going on there.
If you are scheduled, many people must refrain from screwing up.
It even took them months to figure out that they hired an ex convict, after he personally disclosed the fact multiple times.
I had great hopes for Google to innovate in sense of culture. I saw Larry Page and Sergey Brin as intellectuals. Turns out they just went and built a high school elite club, for geeks. Another bloated company ran by a corps of smug geeks that like to claim how they are holier than thou.
I am really sad about it.
A couple months later Rackspace cold called me to work there. It's a usual thing, I think, and I don't hold it against them.
But if I'm Google or Rackspace, and I'm reading about this process from your side, I have to be asking myself "why am I paying these clowns?"
Hiring is one of the most important things companies do. If they are this disorganized, and if their cultural commitment to hiring is so poor that people are regularly brought in and interviewers are not present or available or confused about why either of you are there, then there is a huge amount of waste going on and there's a huge amount of missed opportunities.
I don't know you, but let's assume you are really good at what you do (and going by the number of people you had recommending you, you're probably pretty good at what you do). The fact of the matter is that Google totally missed the boat here and burned a lot of extra money in the process. Beyond that, for the two years or so that they were jerking around, you could have been a part of the team, making solid contributions. Instead, you were elsewhere making solid contributions that they may have had to defend against. So, the real waste is in the opportunity cost.
What I'm getting at is, if I'm a senior executive at one of these companies, I have to be looking at my hiring process and going "WTF?". Because that's what it deserves. Something is seriously broken and it is potentially a strategic threat.
If I show up to an interview slot (for which I'm spending my 15-30m), and the candidate speaks up about a mis-scheduling or whatever, and convinces me it's not worth our time to meet, I'll be happy to regain my time and complain to the HRbot/hiring manager about scheduling issues (aka please don't waste the my/company's time by messing up the scheduling).
End of story and if you catch them early enough in the interview you can be back at work happily coding the latest story in current sprint.
You should do what's best for you but understand why the folks on here are defending google; it's a big place and they are mostly powerless when it comes to direct influence or manipulation. Understand that and it will give you insight into how to hack their system for your benefit both before you are hired there AND after multiple interviews when you find that right team when but need to deal with ingrained systems; which rules must be followed and which rules everyone ignores, when to ask for forgiveness later and when and how to cover your ass from the start.
They freak out. I got blacklisted at a cellphone company for doing that a couple decades ago. I found that out via a friend on the inside. Basically I was looking for, and applied to get a lab bench job (basically a spectrum analyzer / communication analyzer jockey, beneath my ability, but it was an exciting growing company etc) and they wanted me to be a junior roving field tech, basically I'd help the real field techs carry heavy stuff into the building and then (literally) mow the lawn while the real tech worked. And I went to school for X years to run a lawnmower... uh huh...
If you think its mortifying for the candidate, imagine how the HR rep looks when you walk out, thus making a fool out of them. Note that I wasn't sarcastic or caustic or anything when I left, after all, I had lots of friends / acquaintances on the inside and telecom is a very small world. Lots of hand shaking and "you have a nice facility here but I'm not interested in the position" and so on. I got word from my inside contacts that the HR girl was fuming with rage and swore after I made a fool of her by walking out, that my resume would never pass her desk again in any capacity, etc.
Companies are always doing stupid stuff, just hopefully not too often, and they're at least partially interested in how you'll respond. So imagine you work there and someone in upper management makes the worlds dumbest presentation to the division, they're terrified you're going to laugh at them and walk out.
When I was younger and (even more) stupider, stuck at an interview I decided I didn't really want, I started flirting with the attractive HR staffer, which didn't work out, but it was fun at the time. Times were different back then, now a days politely asking a woman out at work would probably get you fired or arrested.
I was actually going to bring this up. I have a lot of friends who are interview pros. They say if an interviewer decides earlier on you're not going to get hired, they basically fold up their sheets and ask non-related general questions to pass the rest of the time.
As an interviewee, I have, more than once, thanked my hosts for their tea and cake and left early when I detected that the interview was turning into a chat.
Would a collegiate interviewing model not work better for an intellectually driven organisation like Google? Each team interviewing for their own positions, but with some form of 'tenure track' process for the longer term?
At a broader level, the problem with this is that the delays inherent in doing a lot of hiring and relocating people means that you can't have teams doing their own hiring and then waiting for people to arrive and come on-line - there need to be candidates in the pipeline before the exact seats open up. Otherwise you're talking about a 3-6 month delay from when a seat opens to when there's an engineer sitting in it, which sucks.
With that said, it doesn't change my opinion of it being a time waste for me. I have a career, I know, more or less, what I want to work on next, and I have no interest in devoting a month (seriously, Google recommended taking that long to come up to speed on interview questions) of study to interview for who knows what position, especially when the whole system is gamed towards rejecting false negatives.
Welcome to reality in most of large corporate america. I've seen insane 6-9 month interview processes at places like Cisco and that's not even a successful hire. Likewise at other large SV companies.
If you can get it down to 3 months, it's below par and better than the competition.
You are also going nowhere for a long, long time.
Also, with decent performance you can transfer after a year, occasionally even earlier if another team really wants you.
The 'tenure track' is a great idea. How would you implement it though? Just curious.
As I said a few levels above, I am not a programmer. I'd imagine it might work like academic departments, a series of short contracts (well paid!) leading if successful to a more permanent place with some ability to direct own work.
I get the impression people are dealing with firehoses rather than trickles (talk of 'recruitment pipelines' like in a tyre factory) so perhaps the collegiate model just won't work.
Microsoft has more employees and the three times I interviewed with them (and got accepted) it was a great experience, with perfect communication from their recruiters and interviewers. The one time I interviewed with Google (and got accepted, but I rejected them for MS) I pretty much went through a similar experience as the blog post, although the interviews themselves weren't bad, just the recruiting process.
So yea, size isn't an excuse.
Whenever I pointed out that the bigger the company, the more teams there would be to absorb and place incoming employees, the googlers in question would just ignore the response and emphasize that blind allocation was necessary because no other method of placing employees would scale to Google's size.
Sigh...
Microsoft's HR departments are completely siloed by business unit, and they don't share notes. If the rec you're applying for dries up, they do F-all to guide you into a new one. Each time you engage with a different BU you're completely back to square one.
I failed the first phone interview spectacularly because he asked about data structures and estimating powers of two, and I haven't done any of that after 4 years in the industry. I guess fair enough; if that's what they expect of their employees, I'm not their man.
Overall, a disappointing experience.
I'm all for CS fundamentals, but in many places it's clearly being used as an approximation of good-code-shipping-ability.
I think part of the problem is that you're not really allowed to interview people in a way that holistically assesses their ability, so you end up doing cargo cult-y things that sort of, kind of sounds like they're relevant. For example, when I was at Amazon, we specifically were disallowed from using real-time typing/sharing tools to conduct coding questions.
Nowadays I find that pairing with someone on a limited-scope coding problem, as well as talking deeply about software design and architectural decisions, is the best way to assess. But then again, I'm also no longer interviewing complete newbies - which I think Amazon/Google/Microsoft's recruiting systems are heavily optimized for.
When faced with a candidate who has a dearth of real-world things to dig into, of course you fall back on data structures and algorithms. When you apply this to experienced professionals, who have a long track record that they can talk in depth about, it becomes silly.
When he eventually called back and started the interview, he did not even seem to respond my answers to his questions - it honestly sounded like he was playing a computer game on the other end of the line...
It was blatant disrespect towards me and my time. I'm glad I found an opportunity elsewhere.
Out of curiosity, was there a reason you decided to continue the interview process after this?
They have a post-interview review process, and I gave the recruiter an appropriately negative review.
Some companies have a mythology that every job in their company is like that, even if the actual job being interviewed for is the opposite.
Hardly limited to megacorp CA tech companies. No different than a boring old bank requiring janitor interview candidates to wear a suit and tie.
To be fair, these were "Data Structures 101" type questions. One was literally design a graph structure and write a deep-copy procedure, and that's it. Not exactly "novel." Since I haven't done these in ages, and didn't even pay that much attention when I had the class, I did badly.
Another was a simple string manipulation question that I bombed because I was already stressed out from failing the first so badly, similar to your situation.
I was head-hunted by them initially. Had a casual phone interview within the week. Then scheduled and re-scheduled a technical interview (their fault, three more weeks). Then two weeks later I had another casual phone interview. Then waited two weeks for the on-site six-interview bonanza. I finished those 4th thru 9th interview two weeks ago, and recruiter just told me yesterday to wait for the hiring committee to give a decision in another week.
First, given you understand your limitations as an interview, you're probably a better interviewer than most -- including myself :-)
An employer I worked for made it very difficult (but certainly not impossible, implausible, or even socially unaccepted) to stop interviewing altogether. Instead, they'd take a different approach: in addition to trying to match interviewers with candidates, they would also perform analysis on interviewer's previous feedback (e.g., are they constantly voting down candidates that go on to receive an offer after additional review, or vice-versa?) and weigh the feedback accordingly.
I'd be highly surprised if Google doesn't do this.
I do agree that usual "watch an experienced candidate do the interviews" approach to training is insufficient: this is much like expecting one to become a better candidate by watching a strong quickly "get" an algorithmic question with an a-ha insight, it looks easy when you already know the answer. I love the anagrams example from Programming Pearls -- it appears as "aha" problem, seems obvious to those who already know the answer -- but the book describes in detail on how it represents an entire class of problems and how to achieve that seeming insight using a more structured approach.
As an aside I actually finding interviewing others to be much harder than being interviewed myself -- if I screw up as a candidate worst thing that can happen is I don't get an offer, if I screw up as an interviewer people other than myself (the candidate, the company) will be affected. There's plenty of sites that talk about how to prepare for being interviewed, candidates spend dozens of hours before going for an interview, but there's less material out there for individual engineers who want to become better interviewers. Joel and Yegge are prominent exceptions, but most other pundits say only the obvious, e.g., "ask questions that can tell you if the candidate can do the job?"
I had a friend who interviewed at Google, who is an excellent software engineer I've worked with for years, but who got rejected with extreme prejudice because he was interviewed for the wrong position. He was going for software engineer, they interviewed him for networking/systems reliability, and asked him all of these sysadmin/network-admin style questions. Even after he told them they had set him up with the wrong set of interviewers, they still kept the schedule.
Given the sheer size of Google however, I'd expect lots of false positives and negatives in their filters.
Also recognize that regular Googlers are selected to do these interviews, and some of them have little training in giving interviews. If you're unlucky, you might get a bad interviewer. I consider myself a relatively poor interviewer and I usually decline to do them unless they intersect my subject area (compilers, GWT, etc)