From Scorching Duck, 9 Years ago, written in Plain Text.
Embed
  1. Why Google Employees Quit
  2. Posted Jan 18, 2009 by Michael Arrington (@arrington)
  3. 0
  4. SHARES
  5. Next Story
  6. Lycos Europe To Shutter Lycos Mail, Tripod On February 15
  7. In 2008 Google HR set up a private Google Group to ask former employees why they left the company. We’ve been forwarded what appears to be authentic posts to the thread by a number of ex-Googlers, which we reprint below minus identifying information other than their first names.
  8.  
  9. The thread shows a brutal honesty about what it’s like to work at Google, at least from the point of view of employees who were unhappy enough to resign. Top amongst the complaints is low pay relative to what they could earn elsewhere, and disappearing fringe benefits seemed to elevate the concern. Other popular gripes – too much bureaucracy, poor management, poor mentoring, and a hiring process that took months.
  10.  
  11. A few of the posts are more positive, and frankly there isn’t a whole lot here that you don’t see in other big companies.
  12.  
  13. One message stands out though in most of the posts – employees thought they were entering the promised land when they joined Google, and most of them were disappointed. Some of them wondered if it meant they were somehow lacking. One person sums it all up nicely:
  14.  
  15. Those of us who failed to thrive at Google are faced with some pretty serious questions about ourselves. Just seeing that other people ran into the same issues is a huge relief. Google is supposed to be some kind of Nirvana, so if you can’t be happy there how will you ever be happy? It’s supposed to be the ultimate font of technical resources, so if you can’t be productive there how will you ever be productive?
  16.  
  17. The full thread is below.
  18.  
  19. From: Stephen
  20. Date: Wed, 28 May 2008 13:25:07 -0700 (PDT)
  21. Local: Wed, May 28 2008 2:25 pm
  22. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  23.  
  24. Actually, I hit the Send button on this before I intended to.
  25. I left Microsoft to work for Google in 2005. I stayed 10 months. I
  26. was demoralized. I shouldn’t have ever taken that job. I was
  27. disenchanted the whole time, and yes, like you, my regret over the
  28. poor bargain I’d made affected my performance.
  29.  
  30. As I was saying. Google actually celebrates its hiring process, as if
  31. its ruthless inefficiency and interminable duration were a sure proof
  32. of thoroughness, a badge of honor. Perhaps it is thorough. But I
  33. would be willing to wager that Microsoft’s hiring process, which takes
  34. a fraction of the time, does not result in a lower-skilled workforce
  35. or result in a higher rate of attrition. And let me say this: if
  36. Larry Page is still reviewing resumes, shareholders should organize a
  37. rebellion. That is a scandalous waste of time for someone at that
  38. level, and the fact that it’s “quirky” is no mitigation.
  39.  
  40. I was, like you, offered a considerable pay cut to go to work at
  41. Google. The relocation package was lame. So were the benefits. (I
  42. had worked at Microsoft. Microsoft was self-insured, so there were no
  43. co-pays.)
  44.  
  45. In one TGIF in Kirkland, an employee informed Eric Schmidt that
  46. Microsoft’s benefits package was richer. He announced himself
  47. genuinely surprised, which genuinely surprised me. Schmidt, in the
  48. presence of witnesses, promised to bring the benefits to a par. He
  49. consulted HR, and HR informed him that it’d cost Google 22 million a
  50. year to do that. So he abandoned the promise and fell back on his
  51. tired, familiar standby (“People don’t work at Google for the money.
  52. They work at Google because they want to change the world!”). A
  53. statement that always seemed to me a little Louis XIV coming from a
  54. billionaire.
  55.  
  56. I still can’t recall all the moralizing postures without a shudder of
  57. disgust.
  58.  
  59. From: Ben
  60. Date: Wed, 28 May 2008 14:43:09 -0700
  61. Local: Wed, May 28 2008 3:43 pm
  62. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  63.  
  64. Stephen wrote:
  65. > He
  66. > consulted HR, and HR informed him that it’d cost Google 22 million a
  67. > year to do that. So he abandoned the promise and fell back on his
  68. > tired, familiar standby (“People don’t work at Google for the money.
  69. > They work at Google because they want to change the world!”). A
  70. > statement that always seemed to me a little Louis XIV coming from a
  71. > billionaire.
  72.  
  73. I ran into a similar irritation while at Google, actually – during that
  74. time when the minikitchens were being stripped heavily. I heard that one
  75. of the reasons was cost – I remember figures mentioned like “thousands
  76. of dollars per day” – and it just didn’t jive well with me.
  77.  
  78. I mean, look at the profit numbers. Google’s net income for 2006, when I
  79. left, was 3 billion. 22 million a year? Less than 1% of their *profit*.
  80. “Thousands of dollars a day”? Even if it’s ten thousand, that’s still
  81. well under 1%.
  82.  
  83. Reduce profit by 2% to make your employees much happier . . . well, I
  84. know what I’d choose. In some ways it seemed like Google was getting
  85. increasingly pennywise/poundfoolish, and that just seemed like a dubious
  86. situation.
  87.  
  88. (Although, to Google’s credit, they opened up a new cafe that solved
  89. many of my food-related issues . . . after I left. Sigh.)
  90.  
  91. -Ben
  92.  
  93. From: Ted
  94. Date: Wed, 28 May 2008 17:39:06 -0700 (PDT)
  95. Local: Wed, May 28 2008 6:39 pm
  96. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  97.  
  98. Sounds familiar (I was at Kirkland too.)
  99. Google took longer than any company I ever worked for to get thru the
  100. hiring process (approx 5 months from resume to job start.)
  101.  
  102. The interview process was very mixed: They had me slated as a Windows
  103. Developer for some reason, tho everyone on my interview loop wondered
  104. why. I flubbed my first coding pretty bad but after that it was clear
  105. that no-one on my interview loop had enough experience or knowledge to
  106. level me. On the other hand they figured that out and scheduled a
  107. follow on interview with the head of the Kirkland office who asked
  108. reasonable and pertinent questions.
  109.  
  110. Unlike the previous posters, I was happy with my salary and (for some
  111. reason I can’t articulate) I kept my own private medical insurance…
  112.  
  113. Also I was surprised that Google seemed to be proud that they didn’t
  114. communicate from one interviewer to the next: at Microsoft it was a
  115. good opportunity to find more appropriate interviewers, etc. if a
  116. person seemed misslated. Oh well, I thought my interview and hiring
  117. process was an anomaly.
  118.  
  119. From: Laurent
  120. Date: Thu, 29 May 2008 08:10:08 -0700 (PDT)
  121. Local: Thurs, May 29 2008 9:10 am
  122. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  123.  
  124. I also left Google after only 5 months.
  125.  
  126. As soon as I got inside, I had the feeling of being swallowed by a
  127. giant borg :)
  128.  
  129. Really, I felt like I didn’t exist, watching people buzzing around
  130. with laptops.
  131.  
  132. I did however meet with Larry and Sergey during a product review
  133. meeting, and have only good things to say about these 2 guys.
  134.  
  135. Regarding compensation, I did have to negotiate quite a bit to get on
  136. par with what I earned before.
  137.  
  138. For options however, I didn’t get much (something like 180 options and
  139. 330 gsu).
  140.  
  141. What was strange with me at Google was: while outside, I had all these
  142. big ideas I could do if I ever worked there.
  143.  
  144. Once inside, you have 18,000 (at the time, Feb 2008) other googlers
  145. thinking the same things.
  146.  
  147. I think it’s a good move for them to have App Engine: they won’t need
  148. to hire that many people anymore, or buy small garage-guys because
  149. now developers will be able to develop over the Google OS for free for
  150. Google :)
  151.  
  152. One last thing: Google also thinks inside a box (the browser). I felt
  153. this a lot, and was another reason I left. (too constrained)
  154.  
  155. It’s no surprise that they push to extend what the browser can do.
  156. (Gears, Earth plugin)
  157.  
  158. Cheers.
  159.  
  160. From: “shuba
  161. Date: Wed, 28 May 2008 22:01:06 -0500
  162. Local: Wed, May 28 2008 9:01 pm
  163. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  164.  
  165. Hi Friends,
  166.  
  167. Yes, I do agree with Stephen about HR. I totally second the statement that
  168. Google’s Hiring process is slack. Agreed, they receive a record number of
  169. applications everyday, but still the feeling that the resume is lost in a
  170. ‘black hole’ when there is no reply in as long as 6 months, is terribly
  171. disappointing. Also, the whole exit process could be bettered and ironed
  172. out.
  173.  
  174. I understand when Eric Schmidt says, one doesn’t work for Google for the
  175. money alone. Job with Google is sure an experience. But, yes, bringing the
  176. perks on par with other bigwigs will bring down the attrition level to some
  177. extent, thou we all do understand that attrition is not a big problem for
  178. Google right now.
  179.  
  180. Keep writing!
  181.  
  182. Shuba.
  183.  
  184. From: Shelby
  185. Date: Thu, 29 May 2008 10:26:39 -0700 (PDT)
  186. Local: Thurs, May 29 2008 11:26 am
  187. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  188.  
  189. I had an equally ridiculous hiring process – although mine actually
  190. seemed normal (by Google standards) until the result. “And let me
  191. say this: if Larry Page is still reviewing resumes, shareholders
  192. should organize a rebellion. That is a scandalous waste of time for someone at that
  193. level, and the fact that it’s “quirky” is no mitigation. ” – this
  194. couldn’t be more true.
  195.  
  196. My experience actually in Aug. 2004 when I was interviewing for a
  197. sales position in the Seattle office was the typical 13+ interviews,
  198. including a day trip to MV where I was told that someone would take me
  199. to lunch and instead she took me in a conf. room and interviewed me.
  200. So I ended up not eating at all that day until I returned to the
  201. airport at 4pm. However, I passed my interviews with flying colors
  202. and was surprised 3 weeks later when I still hadn’t heard from my
  203. recruiter about the results of the hiring committee meeting. Finally
  204. he called to tell me that I was rejected because I was currently
  205. working as a Flight Attendant. A job I had started 4 months prior
  206. because it was a great opportunity to move into their management group
  207. but then the airlines started downsizing management and so I applied
  208. for the Google Travel Sales role instead. However, apparently the
  209. elitist hiring committee members believed that FA’s are stupid and
  210. there was no way they would be able to work at Google. Lucky for me
  211. the recruiter agreed it was incredibly sexist and fought with HR to
  212. bring me on as a temp. Three months later they resubmitted me to the
  213. committee and had me remove my former job – instead I mentioned that I
  214. was “traveling” for four months and bingo! I got hired full time. 3+
  215. years later I was promoted twice and named a Google Luminary! Good
  216. think Larry is such an excellent judge of character.
  217.  
  218. I have to say though, that level of bureaucracy remained pretty much
  219. the whole time I was at Google. I finally left after a lifestyle
  220. change moved me to Austin and they re-nigged on an offer to move me
  221. into the Travel Vertical role for which I was promised before the
  222. move. It’s a real bummer because I loved my co-workers and there are
  223. a ton of great people at Google. But the management has no power to
  224. influence change because they are micromanaged by the Execs.
  225. I’m very happy at my new company though – making twice as much and
  226. enjoying the benefits of a start-up culture again.
  227.  
  228. From: issara
  229. Date: Fri, 30 May 2008 08:50:45 -0700 (PDT)
  230. Local: Fri, May 30 2008 9:50 am
  231. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  232.  
  233. I was hired to work in Google’s Singapore office. I found out very
  234. quickly that Google International is not the same as Google-US. The
  235. offered pay was way too low to survive in Singapore, so I left after I
  236. got another job offer that I felt was better for me. I really do
  237. believe that Google is doing some important work with humanitarian
  238. mapping projects and digitizing libraries. But for me, I felt that
  239. Google’s popular image did not match its actions in the work place,
  240. and that some of the things they did were not very “Googly.”
  241.  
  242. Issara
  243.  
  244. From: “Lisa
  245. Date: Fri, 30 May 2008 15:16:20 -0700
  246. Local: Fri, May 30 2008 4:16 pm
  247. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  248.  
  249. I’m enjoying this group and this thread.
  250.  
  251. I had a far different hiring experience — it moved too
  252. quickly! I wasn’t actually ready to leave my previous position, but
  253. when the Google recruiter called, it would have been silly not to talk
  254. to her.
  255.  
  256. I had one full day of MV in-person interviews, a few phone
  257. conversations, and the next thing I know, they’re calling me to
  258. present an offer. In retrospect, I shouldn’t have accepted it. I spent
  259. all of 11 days working at Google before I returned to my previous (now
  260. current ;-) company.
  261.  
  262. I wish I had asked more questions and asked to meet the team I’d be
  263. managing (at least some of them!) before I jumped on board, but
  264. Google’s reputation as an employer is legendary. At the time, I felt
  265. conflicted, but then I’d think “Google wants me, and everyone knows
  266. how hard it is to get hired there. I should jump on this opportunity.”
  267. I don’t bear any ill will — I think Google is an amazing company, is
  268. doing some revolutionary things, and is full of smart people. And I
  269. bought shares in 2004, so I hope they continue to be very successful.
  270. ;-)
  271.  
  272. Cheers!
  273.  
  274. Lisa
  275. From: Pam
  276. Date: Fri, 30 May 2008 15:39:04 -0700 (PDT)
  277. Local: Fri, May 30 2008 4:39 pm
  278. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  279.  
  280. I have been sitting back, surprised at the level of negativity
  281. expressed by those on this thread, and wanted to share my very
  282. different experience. Sure, Google isn’t perfect, its management isn’t
  283. perfect, the HR department isn’t perfect, etc, but by and large they
  284. do things better/smarter/friendlier than the vast majority of
  285. companies out there.
  286.  
  287. My hiring process back in 2003 was, like some of yours, somewhat drawn
  288. out, and I was made to contract for almost 4 months before being
  289. hired, but Google gave me a chance, and I gave Google a chance. And
  290. I’m so glad.
  291.  
  292. Forget about the cool products I worked on over the years that are on
  293. the cutting edge of technology and impacting millions of people. We’re
  294. mostly talking about work/life balance and job satisfaction. I get
  295. such a kick out of thinking about the incredible stuff I got to do
  296. while at Google (watch Barack Obama/Al Gore/Hillary Clinton/Colin
  297. Powell/Malcolm Gladwell/Jimmy Carter speak, go to a trapeze class,
  298. hear John Legend play in Charlie’s cafe, go to a chocolate trufflemaking
  299. class, ski on Google’s dime year after year in Tahoe, to name
  300. just a few), not to mention enjoy a work environment at Google that
  301. was informal, comfortable, safe, and supportive — so different from
  302. the work environments of my friends in other industries or at other
  303. companies.
  304.  
  305. I wonder if post-Google bitterness is correlated to when you joined
  306. and/or how long you were at Google. It seems that it is. Maybe it’s
  307. the memories of Google in the first few years I was there that make it
  308. it seem magical, but I really do treasure the time I spent at Google.
  309. I left a few weeks ago, after almost 5 years at the company, because I
  310. wanted to pursue a markedly different career path. Sure, I had times
  311. when I was frustrated with the way Google was doing things, or when I
  312. felt that my particular project, or assignment was lacking, and I
  313. definitely had managers that I didn’t enjoy. But all in all — what a
  314. freakin’ amazing experience!
  315. —–
  316. And, separately, regarding the compensation issue, it seems to me that
  317. Google would do their research and pay market wages high enough to
  318. attract the best. If good candidates refuse to take the jobs because
  319. the wages aren’t high enough to live on, they’d be forced to raise
  320. compensation.
  321.  
  322. From: “Logan
  323. Date: Fri, 30 May 2008 15:56:47 -0700
  324. Local: Fri, May 30 2008 4:56 pm
  325. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  326.  
  327. I experienced the same painful hiring process all of you did. The
  328. reputation of Google is why I worked there for three and a half years. I
  329. took pride in where I worked and the work I was doing. I knew I could get
  330. paid more elsewhere but the caliber of people to my left and right was
  331. amazing. I learned a lot and have benefited from the time I spent at
  332. Google.
  333.  
  334. When asked by friends and family why I was leaving I came up with an
  335. automobile analogy.
  336.  
  337. One auto has a 5 star crash safety rating, with good gas mileage, low
  338. maintenance costs and good performance. Another, has bluetooth for your
  339. mobile phone, 10 cup holders, sexy looking instrument panel, premium sound
  340. system, DVD player and seat warmer but has poor gas mileage, poor
  341. performance, bad safety rating, expensive maintenance, etc.
  342.  
  343. Some will make a purchasing decision on what really matters; safety,
  344. performance, serviceability. Some will make a purchase based on “how many
  345. cup holders the car has”. Google is the car with all the sexy features
  346. but very little of what really matters. The amenities,extra-curricular(s)
  347. and conversastion peice of “working for Google” is what keeps most
  348. working at Google.
  349.  
  350. My $.02
  351.  
  352. From: Ted
  353. Date: Fri, 30 May 2008 16:27:35 -0700
  354. Local: Fri, May 30 2008 5:27 pm
  355. Subject: RE: So… Why’d you left, guys? I mean, seriously.
  356.  
  357. My bitterness is almost entirely because of my manager. He was in my
  358. orientation group in Mt. View and seemed like a good egg at the time. Just
  359. as Google can be a great place for the software engineer to do great work
  360. unencumbered, it’s also possible for a manger to be a complete jerk
  361. unencumbered. Tho the other members of the group (that didn’t leave sooner)
  362. thought that they could put up with anything to work at Google they did
  363. notice my manager’s particular irrationality when dealing with me. There
  364. were only two days of my six months there that I didn’t dread going to work.
  365. My manager made sure that no other manager would talk to me and as soon as
  366. the head of the office left town he tried to put me on a PIP. Life is too
  367. short to deal with jerks so I felt I had no choice but to leave.
  368. I do believe that I could have really enjoyed myself at the home office or
  369. with a different manager, etc. but I wasn’t given the choice of what to work
  370. on nor who to work for.
  371.  
  372. -Ted
  373.  
  374. From: “Greg
  375. Date: Fri, 30 May 2008 20:29:18 -0400
  376. Local: Fri, May 30 2008 6:29 pm
  377. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  378.  
  379. I wonder how much of a difference there is between
  380. engineering/non-engineering and MV/non-MV, in addition to the
  381. old-timer/non-old-timer split.
  382.  
  383. I started working at Google a while ago as an engineer when there was
  384. only the Mountain View office. (If I recall correctly, the NY sales
  385. office opened later that month.) Google certainly seemed like an
  386. ideal place to work at the time, and if I wanted to be an engineer,
  387. I’d probably still want to work there. But there were certainly
  388. issues, even back then, and I believe they’ve mostly gotten worse as
  389. the company has grown.
  390.  
  391. The hiring process:
  392. Google’s hiring process tends to have a lot of false negatives. If I
  393. had submitted my resume myself, rather than getting recommended by an
  394. employee, I don’t know if I would have gotten in. My GPA was a 3.7,
  395. and the cutoff (at least at one point in Google’s history) was 3.8 (I
  396. went to a tough school, the 6th 4.0 GPA in its history just graduated
  397. this year). I honestly don’t know if this cap is still there (I
  398. suspect not) but this is just one way Google arbitrarily cut down on
  399. the number of people interviewed.
  400.  
  401. After I had been working, I found out that I was lucky that one of the
  402. members of my team hadn’t interviewed me. My C++ skills weren’t
  403. really all that great, since I hadn’t used C++ in a couple of years,
  404. and I would have totally failed if he had interviewed me. He told me
  405. that he would have been wrong to do so, since I actually ended up
  406. replacing him on the team and automating most of what he had been
  407. doing by hand, so I hope that my example helped make at least one
  408. interviewer a little more reasonable. But the old-timers certainly
  409. felt like they had to have tough interviews, and in many cases “tough”
  410. equated to things like trivia questions or brain teasers, neither of
  411. which are completely relevant to what people were being interviewed
  412. for.
  413.  
  414. The Google lifestyle:
  415. Food at Mountain View in the early days was great. Things got a bit
  416. crazy when Charlie was cooking in the same tiny kitchen that he had
  417. cooked for 70 people in when there were something like 400 people
  418. eating in the cafe, although the food quality didn’t go down nearly as
  419. much as I would have expected it to. But this was just one of many
  420. examples of overcrowding in the offices that happened over the years
  421. at Google. (And honestly, keeping the cooks happy seemed like a good
  422. idea to me…)
  423.  
  424. But along with the food came the Google lifestyle: if you were staying
  425. for dinner, it better be because you were working afterwards. It was
  426. frowned upon to leave right after dinner. I think a lot of people
  427. spent quite a bit of time either just before or just after dinner
  428. hanging out and not really being all that productive, which is nice
  429. for the mostly 20-something crowd, but I can sympathize with the
  430. people who have families that didn’t fit in. I had my own reasons for
  431. not wanting to hang out at work, so I never really got that far into
  432. the Google social scene. And my experience was that the people who
  433. spent all their time at Google were the ones that ended up on the
  434. sexier projects or in charge of things. (Admittedly, some of these
  435. people were also workaholics, and I wasn’t willing to give up some of
  436. my non-work social activities, but there seemed to be a bit of
  437. favoritism going on as well.)
  438.  
  439. Engineers and everyone else:
  440. Unlike most other engineers, I had a job that required me to talk to
  441. people all over the company. I talked to the lawyers, marketing, PR,
  442. product managers, executives, engineers… And because I started
  443. early enough, I also knew quite a few people in sales. As far as
  444. salary went, my offer was 35% higher than my next highest job offer,
  445. so I think I lucked out there. That was certainly not the normal
  446. situation, though. Over the years I talked to plenty of people about
  447. what they thought about Google’s compensation… There’s a huge
  448. discrepancy between engineers and non-engineers. Most of the adwords
  449. support people I talked to complained a lot about their situation.
  450. Not only were they generally overqualified for the jobs (given what
  451. the work actually was, but Google has always prided itself on having
  452. people with extra education) but they could fairly easily have gotten
  453. higher-paying jobs elsewhere. The usual reason for sticking around
  454. that I heard was that after a few years at Google, their resume would
  455. look a lot better on the job market.
  456.  
  457. And that’s not counting the people who are contractors. I never
  458. understood why all of the recruiters were contractors, given that
  459. Google showed no signs of slowing down its hiring. All this meant was
  460. that a lot of the recruiters had to spend a lot of time training new
  461. recruiters, since they were replaced so frequently. (This, I think,
  462. goes at least partway for explaining why the hiring process was
  463. occasionally a bit slow.)
  464.  
  465. Management
  466. My biggest pet peeve was the management, or lack thereof, at Google.
  467. I went through many managers in my first few years. I ended up having
  468. at least one manager during this time that was an unpopular manager,
  469. and because of that, I was told many times over that I shouldn’t
  470. bother trying to get a promotion. When I left, I had never been
  471. re-slotted. This, in spite of the fact that my technical judgment was
  472. respected enough that I occasionally delayed launches until their
  473. logging systems were operating correctly. And in spite of the fact
  474. that I essentially consulted to other technical groups. I could go on
  475. about this for a while, but then I might actually sound like I was
  476. bitter.
  477.  
  478. Remote offices
  479. I worked in Mountain View for 3 years before moving to New York.
  480. Around that time, I started traveling a lot: I had college alumni
  481. activities in southern California, so I occasionally worked out of
  482. Santa Monica, and my brother lived in Seattle, so I worked in Kirkland
  483. a few times. The “Google experience” is substantially different
  484. outside of Mountain View. And being outside of the Mountain View
  485. culture bubble makes it that much harder to get taken seriously. I
  486. honestly have no idea what it’s like to work for Google outside of the
  487. US, but even when you’re only 3 time zones away, it’s sometimes hard
  488. to get noticed by Mountain View.
  489.  
  490. This e-mail has gotten a lot longer than I really meant it to. But my
  491. point is that there are plenty of good reasons people can have
  492. negative impressions of working at Google. Just like there are plenty
  493. of good reasons people have great experiences there.
  494. Greg
  495.  
  496. From: “Lilly
  497. Date: Fri, 30 May 2008 23:36:36 -0700
  498. Local: Sat, May 31 2008 12:36 am
  499. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  500.  
  501. I left to go to do a PhD. I liked the work I was doing at Googlea and, like
  502. Pam, I treasure the time I had there, but I also left exhausted and
  503. processing a lot of stress. I joined in June 2003 as an intern and 6 months
  504. later, my amazing manager, Jen, made me a full-time offer without any
  505. additional interviews. HR worked with me to make sure I could finish school
  506. and continue working at Google. I really felt like they had my back and my
  507. best interests in mind.
  508.  
  509. I think for me, some of the trouble was the crazy unaccountable product
  510. strategy processes that would tell you to work on high risk things on the
  511. one hand, but would hold you back for taking those chance on the other. I
  512. worked on Google Page Creator from the time it was just a 20% prototype and
  513. I also spent a lot of time believing in and doing some a lot of work to make
  514. Google Notebook something successful. I’m not sure taking on those
  515. high-risk, challenging projects was a good idea in the long run, but nobody
  516. told me “hey, we don’t think this project is really worth the resources.”
  517. I’m sort of a heart-and-soul into project person so this meant that I spent
  518. a lot of energy trying to good work on high-risk projects I believed in, but
  519. through the inconsistent support and wavering strategies I had no direct
  520. control over, I felt like a lot of my energy got wasted.
  521.  
  522. There was also a big management overhaul on our team about a year before I
  523. left and I felt like my team spent so much time trying to figure what was
  524. coming down the pipe next, who was leaving next, etc that it wasted a lot of
  525. energy. In user-experience design, there are a lot of smart, capable people
  526. who have to sort of surf the waves of having a really unclear relationship
  527. with product management.
  528.  
  529. But on the upside, I really did take advantage of 20% time. In the first two
  530. years, I really felt rewarded and appreciated for my work and in the last
  531. two years, I at least felt respected if not rewarded. Many days at work were
  532. really intellectually stimulating. And despite the management / exec
  533. culture being weird, I felt like Google’s managers are really among the top
  534. in terms of not being corporate world pillagers.
  535.  
  536. I had decided I wanted to go grad school in my first year at Google, but it
  537. was fun enough that I delayed going *twice* (that was a really awkward set
  538. of deferrals).
  539.  
  540. But in the end, I was pretty tired of the constant change, the inconsistent
  541. management, and I wasn’t sure if the kinds of people old Google hired —
  542. wearing many hats and workng butts off to take ownership of project’s
  543. success — is the kind of person new Google needed — people who were better
  544. able to step in line to keep the company marching under control. I was part
  545. of the chaos generation.
  546.  
  547. From: Luqman
  548. Date: Sun, 1 Jun 2008 01:34:53 -0700 (PDT)
  549. Local: Sun, Jun 1 2008 2:34 am
  550. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  551.  
  552. It looks like most of us have same story to tell….
  553.  
  554. My case resembles that of Bob ….
  555.  
  556. It took two months(lesser than others I guess) for my hiring process
  557. to complete, and I made it clear that I had an offer from IBM in hand
  558. which was paying me good … but I was offered the same salary as my
  559. previous employer … which always kept me de-motivated throughout my
  560. tenure. I joined the job due to company’s name and reputation as well
  561. as I had the option to work in day shifts.
  562.  
  563. There was no proper mentoring for 6 months and within 9 months of my
  564. tenure my manager was not happy with my performance, and mgmt always
  565. stressed on “Putting some Extra Effort” – in other words “Spending
  566. some extra hours” … this may not be the case at Google-MV but this
  567. is what it is in India.
  568.  
  569. If you don’t put extra hours then you won’t get promoted, no promotion
  570. means no salary hike.
  571.  
  572. I feel sad about my decision on choosing Google over IBM … Small
  573. pay, No work, No Team spirit, No Hike in 12 months, No balance between
  574. Family Life and work are few things which motivated my move out. I am
  575. still jobless after 5 moths of leaving Google, but I am happy with my
  576. decision(I feel like it is better be jobless than work for google as a
  577. Field Tech).
  578.  
  579. Coming to the positive side, I enjoyed helping fellow googlers fixing
  580. their PCs or Laptops and helping them with their queries. But Field
  581. Techs have to do all the crap apart from some good work.
  582. I like Logan’s example … good decision.
  583.  
  584. Cheers,
  585. Luqman.
  586.  
  587. From: “Marc
  588. Date: Sun, 1 Jun 2008 09:22:03 +0200
  589. Local: Sun, Jun 1 2008 1:22 am
  590. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  591.  
  592. I agree with Pam. I started working for Google in 2002 in Amsterdam to set
  593. up the Dutch and Belgium Sales office and these years were the best of my
  594. life!
  595.  
  596. I had to wait 9 months before they hired me, but it was definately worth is.
  597.  
  598. I had only three interviews then, but number three was Omid, so I might have
  599. been lucky back then. But waiting for 9 months was a challenge as well, but
  600. I knew at that time that Google was something very special, so I had the
  601. patience to wait and it was definately worth it!
  602.  
  603. I agree that the process of hiring is a pain in the behind, but i also agree
  604. that the hiring process should be hard as Goolge should keep up the process
  605. hiring people that are smarter than yourself. There aren’t many companies in
  606. the world that have so many smart and ambitious people.
  607.  
  608. The challenge is to keep up the energy within the company and enterpreneurial
  609. part and give people the opportunity to grow within the company. I do agree
  610. that the HR process has always been tough and I do agree that that should
  611. change. I do think too that Google is in the process of decentralising more
  612. and providing management with more authority, also ouside of US.
  613. But don’d forget that Google has existed only for almost 10 years with about
  614. 16,000 employees and a 20B dollar company and then you have growing pains as
  615. well.
  616.  
  617. With these numbers and the fact that Google has a model where
  618. you look closely at teh high performers and the quality of employees is
  619. extremely high, you have issues where you cannot make everyone happy at the
  620. same time. It’s a lot about numbers as well and we must admit Google is
  621. pretty good at numbers, right? :-)
  622.  
  623. Again, I worked for Google for 5.5 years and I had a great time growing from
  624. a small company of like 500-600 people to 16,000 now.
  625.  
  626. Again, I agree that HR should be more decentralised and not all be approved
  627. out of MV as the current long process of approvals from MV and little
  628. authority from local offices causes pain and time and influences the spirit
  629. within the company negatively.
  630.  
  631. And having worked for Google and leaving Google the right way without any
  632. issues should be a great jump in your career as with Google the knowledge is
  633. huge and not many other companies I know has this knowledge, so use that as
  634. good as you can!
  635. Marc
  636.  
  637. From: “Phil
  638. Date: Thu, 5 Jun 2008 12:38:10 -0700
  639. Local: Thurs, Jun 5 2008 1:38 pm
  640. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  641.  
  642. On Mon, Jun 2, 2008 at 5:30 PM, Dan wrote:
  643. > I’m somewhat tempted to reply with my own list, but I’m curious ..
  644. > what’s going to happen with all this info? Not obviously useful if no
  645. > one is going to do anything with it (e.g., gather and post a summary
  646. > back to the board, bring it to someone who cares).
  647.  
  648. At this point I think that the executive committee knows that there
  649. are people out there holding these opinions. In fact, I was at a
  650. couple of TGIFs where Larry and Sergey addressed questions about the
  651. hiring process and others where other execs talked about why they were
  652. making it harder for people to switch projects even though we’d been
  653. bragging externally that it was easy. I thought long and hard about
  654. how to talk about that during interviews. I think that a big part of
  655. is is that Googlers are supposed to be totally “A” players who just
  656. always make things work out well. And there’s some truth to that: for
  657. each of us here with a bitter story to tell there are other people who
  658. landed in pretty much the exact same situation and ended up loving it
  659. (and a lot more who put up with it and kept their mouths shut). So,
  660. until it gets hard for Google to hire top talent, I don’t think the
  661. kind of complaints that have been raised here will become a priority
  662. at the Googleplex.
  663.  
  664. There’s still a lot of value in this conversation though, if not for
  665. Google, then for the participants. Those of us who failed to thrive at
  666. Google are faced with some pretty serious questions about ourselves.
  667. Just seeing that other people ran into the same issues is a huge
  668. relief. Google is supposed to be some kind of Nirvana, so if you can’t
  669. be happy there how will you ever be happy? It’s supposed to be the
  670. ultimate font of technical resources, so if you can’t be productive
  671. there how will you ever be productive? The truth is that Google can be
  672. a really horrible place to work if you happen to run up against its
  673. shortcomings. Not liking it and/or not being successful there is not a
  674. good indicator of personal competence (and if you think about it you
  675. may realize that some Googlers are successful despite being
  676. incompetent, so it works the other way too.) With so much positive
  677. press about Google it is very difficult to put a negative experience
  678. there in perspective. This thread serves to balance the picture and
  679. gives us a, sometimes badly needed, lens through which to view our
  680. experience at Google and re-evaluate ourselves.
  681.  
  682. I think that it’s painful for some Google alum to read these posts
  683. when their own experiences were so positive and their sense of loyalty
  684. to Google runs so deep. I think that it would be a mistake to become
  685. cynical about Google. Something truly unique and magical happened
  686. there and may still be happening for all I know. But the magic was
  687. neither universal nor unflawed, and the Google experience left some of
  688. us with open wounds. I was going to say that it would be Googly to be
  689. respectful of that, but to be honest, Google culture just isn’t that
  690. mature. Not yet anyway. Nevertheless, the most positive thing for
  691. those of us who are interested in this thread to do is to understand
  692. and respect the experiences described here. Doing so will, in a small
  693. way, strengthen our own careers as well as those of the people around
  694. us. And eventually some little bit of the learning we do here will
  695. inevitably seep back into Google and do some good after all.
  696.  
  697. From: Aaron
  698. Date: Thu, 12 Jun 2008 13:48:41 -0700 (PDT)
  699. Local: Thurs, Jun 12 2008 2:48 pm
  700. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  701.  
  702. My previous employer was sinking fast, and Google seemed like a good
  703. opportunity to get out.
  704.  
  705. First, I was really disappointed with the salary that Google offered.
  706. During negotiations, they accommodated me a little, but not much. I
  707. was barely making more than I had been in the midwest, and the
  708. difference in CA state taxes wiped out almost all of that. Then
  709. there’s rent. My wife and I don’t have any debt, we pay cash for our
  710. cars, we live in a modest apartment, we only have one small child, and
  711. we don’t travel or live a luxurious lifestyle. Yet we were already
  712. dipping into savings during the second month just to pay the bills.
  713. Part of it was certainly my fault; I shouldn’t have accepted such a
  714. low offer.
  715.  
  716. The relocation and hiring bonus’ stated values were pre-tax! That was
  717. a huge unexpected blow to the pocketbook. It may sound strange to
  718. some, but Google’s the only company that has ever done that to me.
  719. Again, that’s mostly my fault; I made a naive assumption.
  720.  
  721. The relocation company told us it would take 8-12 days to get our
  722. stuff. It took 14 days. We managed as best we could for almost 2
  723. weeks with a 1-month-old baby in an apartment with no furniture, no
  724. extra clothes, and a rental car. Google should have taken more
  725. responsibility and initiative on this, but they stood very much
  726. aloof. Their only other option was the corporate housing option (move
  727. twice!). If I had known it would be this bad, I would have rented my
  728. own truck for 1/3 of what Google paid the moving company. I can drive
  729. from Indiana in 3 days; I’ve done it many times.
  730.  
  731. Anyway, Google should know that good engineers are in high demand.
  732. They get their market value, especially in the Bay Area. So after
  733. only 3 months at Google, I was aggressively recruited by another
  734. company that offered 2x my base salary (which has been increased
  735. repeatedly since then). The company also wanted to hire me to do what
  736. I am most skilled at doing, and I could never say that about Google.
  737. I took the job. I get invitations to interview at companies regularly
  738. (Apple contacted me most recently) but I turn them down every time. I
  739. like what I’m doing, I believe I’m well-paid, and we just released a
  740. very successful product.
  741.  
  742. There are nice things about Google. I met some intelligent and good
  743. people that will be lifelong friends. I got to see Ron Paul speak,
  744. and I have many fond memories. The bureaucracy and authoritarian
  745. “gods of coding rules and regulations” were crippling for an
  746. experienced developer, but are probably just the right thing for
  747. someone green out of college. To me, the food wasn’t that big of a
  748. deal. It was good, but I’m not much of an eater. However, I was
  749. really disappointed when the hot chocolate started disappearing from
  750. the mini-kitchens. I hope that 20 cents a day was worth it to them!
  751. As a full-time employee I prefer a good salary to graduallyevaporating
  752. fringe benefits and arbitrarily-sized bonuses. I started
  753. out in the dot-com boom, and I’ve seen those empty promises go
  754. unfulfilled time and time again.
  755.  
  756. I’m not bitter anymore; just disappointed that Google didn’t come
  757. close to what I thought it would be.
  758.  
  759. From: Juliette
  760. Date: Fri, 1 Aug 2008 10:54:42 -0700
  761. Local: Fri, Aug 1 2008 11:54 am
  762. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  763.  
  764. Google was my first job out of college. I was an English major at a
  765. prestigious college and was hired to work in HR. That is one of the problems
  766. I had with Google right there – is it really necessary to hire Ivy League
  767. graduates to process paperwork? I went from reading Derrida to processing
  768. “Status Change Request Forms” for X employees to go on paid leave. The term
  769. “Status Change Request Form” will forever haunt me.
  770.  
  771. The company is – unquestionably – an amazing business model. Despite the
  772. gripes some people may have at Google, employees are Google are coddled much
  773. more than at most other companies. I left after working at Google about six
  774. months (left without even thinking of a bonus) because my abilities were
  775. entirely underutilized and, of the three managers to whom I was assigned,
  776. two were complete nightmares. One was about six feet tall, and I secretly
  777. referred to her as Medusa or Medea, depending on my mood. But that is
  778. neither here nor there. Another reason I left was because I felt overmanaged
  779. in every conceivable way. I shared, for a large part of my experience, the
  780. same office as said manager of mythological Greek she-monsters.
  781.  
  782. I really have no hard feelings toward the firm. When I tell people I worked
  783. at Google, most people are incredulous that I would have left after such a
  784. short time. I want to make this response as objective and as helpful as
  785. possible, so I have three suggestions for the firm in how to prevent cases
  786. like mine from happening.
  787.  
  788. 1) Avoid hiring creative writing/art/film production majors into highly
  789. structured and highly interpersonal roles like HR. I spent most of my
  790. college life writing short stories – alone. Perhaps not the best indication
  791. that I care or even know how to be productive in a role that requires
  792. constant client-facing time. My manager used to always pride herself on
  793. being excellent at “customer service,” which she often said was her favorite
  794. aspect of HR. Service ANYTHING gives me the chills, as it does – I am sure –
  795. for most highly left-brain types.
  796.  
  797. 2) There is Google quirky, and there is too weird to ever fit into a
  798. corporate mold. Identify.
  799.  
  800. 3) Make it easier for people to switch managers if the fit is egregious
  801.  
  802. 4) Give a more accurate representation of Google to potential employees
  803. BEFORE you hire them. All I knew before starting at Google was “#1 Place to
  804. Work According to Forbes” and “Free Gourmet Food” and “Unlimited Sick Days”
  805. and “We Want You to Be Googley!” Like, properly, echoing in my brain. My
  806. twenty-two year old greedy magpie self was wholly drawn in by the idea of
  807. having sashimi anytime I wanted without paying a dime. But as nice as it is
  808. having a cushy 401K and unlimited sick days, I was not willing to sacrifice
  809. my personal happiness and career fulfillment, not even for all the free
  810. kombucha I could drink.
  811.  
  812. In short – I left for personal reasons listed above. Now is the time for my
  813. shameless self-plug. After bumming it around for 5 months doing odd jobs
  814. (like, properly odd… I did stints in PR, dog walking, babysitting,
  815. modeling) I finally landed the job I’d always dreamed of, which is to write
  816. for a living.
  817.  
  818. I now run my own fashion blog and host an online fashion “web show” at
  819. If anyone out there is interested in fashion,
  820. even as a passing thing, it might be of some interest.
  821.  
  822. -Juliette
  823.  
  824. From: Scott
  825. Date: Mon, 6 Oct 2008 12:37:03 -0700 (PDT)
  826. Local: Mon, Oct 6 2008 1:37 pm
  827. Subject: Re: So… Why’d you left, guys? I mean, seriously.
  828.  
  829. Hi there,
  830. Well I left Google three months ago so the scars are still fresh! I
  831. worked in sales and a bit of sales management (will explain) in London
  832. between 2004 – 2008.
  833.  
  834. I think with all these things, its the little bricks that make the
  835. house. I have yet to find a perfect job, so I was pretty bummed when I
  836. was pitched one when I joined.
  837.  
  838. Here is my two penneth
  839. Management – I strongly believe there were a lot of people who did
  840. very little in the way of people management. Due to the aggressive
  841. growth of Google, a lot of managers essentially learnt nothing about
  842. the products or issues with staff. Instead they ‘managed up’ covering
  843. their own patch or careers. I averaged consistent high OKR scores
  844. (despite the managing of the curve nonsense that creates more
  845. subjectivity than objectivity) and despite having 5 managers in 3
  846. years (all of whom knew nothing about my vertical) I watched newer
  847. employees join talk utter rubbish, speak in non sensical management
  848. talk, piss off agencies/clients (I know because they used to call me
  849. laughing) and get promoted.
  850.  
  851. Mostly because they loved doing business in a suit, if you were not
  852. wearing a suit and did a lot of brown nosing you were screwed. I did
  853. neither…hehehe – Maybe that has something to do with a change of
  854. culture. If that is the case then the rules to be Googley should
  855. change. It sometimes felt like the rules to being Googlgey were a PR
  856. strategy.
  857.  
  858. Culturally – In London I just felt the soul of the place change. A lot
  859. of people I worked with or knew there were deeply unhappy with the
  860. lack of fun (Still are , but they won’t talk to management because
  861. they know it is not important- see above). It all seemed to be
  862. contrived and a little false. Of course nothing stays the same but you
  863. when working with a team where politics, egos and bullshit didn’t
  864. exist and suddenly it did, you can’t help but feel confused.
  865. You read so much about how amazing it is to work at Google and for the
  866. first two years it was. I was empowered, promoted, treated with
  867. respect and honesty. Before I left it just was a place full of quiet
  868. moans, talented people being undermined and a structure that created
  869. hostility and politics.
  870.  
  871. I loved my time there. It was a real education. Not to mention my very
  872. risque TGIF routines in London. Actually I think that maybe while I
  873. was ignored. I was not going to compromise my personality by dressing
  874. like a business consultant. I was serious at my job without wearing my
  875. suit.
  876.  
  877. The food was amazing though.
  878.  
  879. Actually I have just read this back and it now appears I should of
  880. left years ago. Whatever – Google you have some amazing people there –
  881. start listening and responding. Wisdom of crowds….cough….splutter
  882.  
  883. CrunchBase Information
  884. Google
  885. Information provided by CrunchBase
  886. 0
  887. SHARES
  888. ADVERTISEMENT
  889.  
  890. ADVERTISEMENT
  891. CrunchBase
  892. Google
  893. FOUNDED
  894. 1998
  895. OVERVIEW
  896. Google is a multinational corporation that is specialized in internet-related services and products. The company’s product portfolio includes Google Search, which provides users with access to information online; Knowledge Graph that allows users to search for things, people, or places as well as builds systems recognizing speech and understanding natural language; Google Now, which provides information …
  897. LOCATION
  898. Mountain View, CA
  899. CATEGORIES
  900. Search, Email, Blogging Platforms, Information Technology, Video Streaming, Software
  901. WEBSITE
  902. http://www.google.com/
  903. Full profile for Google
  904. TechCrunch NEWSLETTERS
  905.  
  906. TechCrunch Daily
  907. Our top headlines
  908. Delivered daily
  909.  
  910. TC Week-in-Review
  911. Top stories of the week
  912. Delivered weekly
  913.  
  914. CrunchBase Daily
  915. The latest startup funding announcements
  916. Delivered daily
  917. View More Enter Address
  918. Enter Address
  919.  SUBSCRIBE
  920. LATEST CRUNCH REPORT
  921.  Xiaomi Unveils Their Drone | Crunch Report
  922. Xiaomi Unveils Their Drone | Crunch Report
  923. Watch More Episodes
  924. Google
  925. Popular Posts
  926. blog comments powered by Disqus
  927. UP NEXT
  928. Lycos Europe To Shutter Lycos Mail, Tripod On February 15
  929. Posted Jan 18, 2009
  930. CrunchBoard
  931. Job Listings
  932.  
  933. Growth Associate, Community & Events at Hometeam (New York, NY, United States)
  934. Startup Battlefield Manager at TechCrunch (San Francisco, CA, United States)
  935. Software Developer, TechCrunch at TechCrunch (San Francisco, CA, United States)
  936. Production Assistant at ONE Campaign (Washington, D.C., DC, United States)
  937. UX Designer at Quid (San Francisco, CA, United States)
  938. More from CrunchBoard
  939. ADVERTISEMENT
  940.  
  941. TechCrunch
  942.  
  943.  
  944.  
  945. News
  946. TCTV
  947. Events
  948. CrunchBase
  949. About
  950.  
  951. Staff
  952. Contact Us
  953. Advertise With Us
  954. Send Us A Tip
  955. International
  956.  
  957. China
  958. Europe
  959. Japan
  960. Follow TechCrunch
  961.  
  962. Facebook Twitter Google+ LinkedIn Youtube Pinterest Tumblr Instagram StumbleUpon Feed
  963. TechCrunch Apps
  964.  
  965. iOS Android Windows 8
  966. Subscribe to TechCrunch Daily
  967.  
  968. Latest headlines delivered to you daily
  969.  
  970. Enter Email Address
  971. Enter Email Address
  972.  SUBSCRIBE
  973. © 2013-2016 AOL Inc. All rights reserved. Aol Tech Privacy Policy About Our Ads Anti Harassment Policy Terms of Service Powered by WordPress.com VIP Fonts by <Webtype>