[varelse]

And this is just it, I was indeed senior level. I do not have the patience to play a cultural game internally just to get to a project that makes use of my skills. My bad.

If that makes me a bad cultural fit, G O O D! If a company isn't smart enough to pair me with a problem I am adept at solving, then plenty of other companies are, and that's why I left after only 4 months. Got a raise too.

Google's hiring process is toxic[1]. It's probably costing them big bucks that they can't quantify properly as a line item in their budget so they probably won't consider changing. All I know is that whenever I recount my days at google on HN, lots of people upvote my story, a lot. I suspect others have similar tales to tell.

[1] Not that other companies don't have their own personal poisons, but yeesh, why not try something new once in a while?

[ChuckMcM]

I had an interesting conversation with Alan Eustace (who was in charge of engineering at the time) about this. We had just hired, abused, and lost a guy who had been the CTO of his previous company, got hired in and forced to clean up message catalogs in i18n code, and quit after the slotting committee decided he was really 'junior engineer' level and should be put on a performance improvement plan so that he could learn to "step it up."

I don't know how common his situation was, I was fairly outspoken (no surprise) and he had reached out to me early on when he was trying to figure things out. The PIP (which is basically a pre-cursor to being fired) basically put him over the edge, and he quit. The sad thing was of course this guy was really smart, had excellent design sense, and knew more about the way Java worked than I did and I was one of the original developers of Java at Sun! A real top notch kind of guy.

He had been caught in the 'perfect storm' of which there were many, of a manager whose project was strategic to the company and understaffed, a skillset that waaay out ranked his assignment, so even doing perfect work it wouldn't begin to show his capabilities, and a 'peer review' system that primarily tested social engineering skills rather than technical skills. Everybody lost. He lost his job, Google lost a great engineer, the system lost an opportunity to improve.

The essence of the discussion with Alan boiled down to "Its a complex system and its going to have some failures, but by and large it works well so unless you can come up with something better we're stuck with it."

So in some ways the interview process is a good test to see if you might be the kind of person that would do well at Google.

[varelse]

Well, given that I aced the interview (plenty of evidence besides the job offer I got within 24 hours of it and some of it I probably shouldn't know but I do), I should have been a wonderful fit then, no?

Tell ya what, how about trying one of those infallible(tm) A/B tests where half the incoming people get the Hogwarts hat and the other half get to meet their team upfront before accepting a job? Do this for a year. Now one year after that measure which set of employees is happier/present/more successful.

[ChuckMcM]

I did say "might" :-) if it were a perfect predictor neither you nor I would have been hired.

I like your suggestion, you should put it on the Alumni list.