Want To Work At Google? 458
ramboando writes "In an article on the ZDNet site 'chief culture officer' and HR boss Stacy Savides Sullivan describes the kind of traits that she's looking for in potential Google employees. If you're thinking about applying, she also goes over what kind of questions one might be asked in an interview, Google's 'happiness survey' and the best perks that makes employees tick and stay with the company (Google ski-trips or paid paternity leave, anyone?). 'I think one of the hardest things to do is ensure that we are hiring people who possess the kind of traits that we're looking for in a Google-y employee. Google-y is defined as somebody who is fairly flexible, adaptable and not focusing on titles and hierarchy, and just gets stuff done. So, we put a lot of focus in our hiring processes when we are interviewing to try to determine first and foremost does the person have the skill set and experience potential to do the job from a background standpoint in addition to academics and credentials.'"
"Fit Factor" (Score:5, Interesting)
I ask because my own company puts so much store in the "fit factor" that they end up hiring people with less skills than the other candidates.
Do I want to work at google? Well now, that's between me and HR
Re:What they mean to say is... (Score:2, Interesting)
I'm going to start my own company, personally.
HR could use some help... (Score:1, Interesting)
If you look at my background and resume, I think you would concur that the positions I was interviewed for weren't a good fit, but because it was Google, I gave it a shot. But, fool me once, fool me twice and all that. If they call again, I'll let them know how I feel about the whole process.
Too much spin (Score:5, Interesting)
One of the top gripes I have with corporate culture is all the bullshit language that is employed. What is this 'Happiness Survey?' This smells of new-age rebranding. Aren't they talking about 'workplace satisfaction?' Don't most companies conduct workplace satisfaction surveys? The companies I have worked for do.
What is this Culture Czar position? You take workplace issues to HR, who coordinates with all other departments to implement the corporate workplace vision. Some companies are better at it than others, but rebranding the position doesn't make Google any better at it.
Google produces innovation based on incentive... which is basic capitalism. It's great that they want the incentives to be more than just cash, but this just feels like a while lot of cheerleading. These tactics don't strike me as being professional. It feels like more spin in an age of way-too-much-spin.
Regards.
Excise the Stanford out of Google first (Score:4, Interesting)
Odd for an organization that prides itself on the contrary through their bit on favoring exclusivist universities and the concepts that go with them. They would do well to take a few pages from the concept of Jante Law to have an honest effort at meeting those concepts. That includes doing away with everything that connects them to Stanford in terms of exclusivity as well, as that hasn't helped in that effort as well.
Google recruiter email (Score:5, Interesting)
your openness to new job opportunities and find out more about your past
work experience."
A few months ago I got a few like these (not copies of the same text). A bit spammish but with restrain. I remember being surprised and wondering how many people were getting these. I wouldn't want to relocate to another country so I never replied. I'm also not a big Google fan personally (call me paranoid). Especially the cultivated "kool-aid factor" (aka PR) ticks me off.
Anyone else been contacted this way?
Re:Google recruiter email (Score:2, Interesting)
Have they recently opened, or about to open a new office? I got mine shortly before they opened the London office, apparently they were having problems filling posts due to the very long and round-about process they had in place (involving multiple trips to the US).
Paternity leave (Score:4, Interesting)
Re:I had an interview with Google a few weeks ago (Score:5, Interesting)
Second question: Radix sort on disk.
Third question: Binary weighted tree in memory.
BTW I hate job interviews like this. I did one for RIM (in like 2002 ish) and at one point after answering like 5 different "puzzles" I turned around and asked the interview "here are two 1024-bit numbers, multiply them quickly." To which he replied "I'm asking the questions." I just got up and left. I don't want to work somewhere where I have to sit pretty and beg all the time just to get paid. I'm sure had I taken the job with RIM I'd be one of those "middle name" people (mass murderer) types eventually. Sure I have to please my boss by finishing my work, but I certainly don't kiss ass.
Next time you have an interview like that, just stump the interviewer, see how they like pressure.
In all honesty, if you don't have prior job experience and/or a portfolio of projects, they can't really tell what you're capable of anyways. High pressure interview questions do not reflect the job scenario in the slightest.
Tom
Re:Google recruiter email (Score:1, Interesting)
I am with Monkey Boy on this one.
Re:They don't reply to applications (Score:1, Interesting)
Politeness in technical companies is a choice, not a requirement.
If you think this is harsh or needless, consider what this says about what is important to you vs. what is important to them. Consider that Google may have been doing you a favor.
To be sure, there are plenty of workplaces were people play nicey-nice games, avoid confrontation, and focus on employee "messaging" rather than substantive content of communication.
Such companies are really pleasant places at which to work, for most of the year. Then in the winter you get your annual review and you spend a quarter wondering why you got blindsided because "things seemed to be going so well."
Re:Excise the Stanford out of Google first (Score:2, Interesting)
The "computer industry" has been so anti-degree of late it's not surprising this offends people. But, honestly, every other industry places value on a good degree, so why should we be special in this regard?
Is it just possible that the top 10% of students, after spending 4-5 years studying a field, might actually be more qualified than a high school graduate? I know this is pretty much blasphemy, but honestly, perhaps people should consider this more.
(Note, before anyone replies with a sob story, if you hire people that get C's, expect C work in the world)
3sat
Re:I had an interview with Google a few weeks ago (Score:5, Interesting)
Unless this is the sort of thing you've been doing before, it's unlikely you'd be able to do that - I'd have expected you'd need some time to work out the answers. I know I would, and I've been programming for 25+ years.
The first question is quite easy to answer -ish. I guess they meant 'as efficiently as possible' - not as 'effectively as possible' (in which case, as long as you got the right answer you'd meet the requirements). To get the basic concept isn't hard, but to get it "as efficiently as possible" you'd need some thought, which would be hard on the phone. (You go up in steps (eg 10 floors at a time) until the first marble breaks, then go back a step and go up one floor at a time until the second marble breaks - the "hard" bit is knowing what size steps to use for the first part to be most efficient)
BTW - the second question there was a bit meaningless - how can you 'sort a 100MB file'? Do they want the file in byte order (all the 0 bytes first, then all the 1 bytes) If so, then you could do that with 256 bytes of data RAM... Maybe they want it in BIT order - that would only need 8 bytes :) If this isn't what they want, then it would help to know WHAT you are sorting - eg a radix sort could be good here, but it might depend on the type of data
Were you allowed to ask how much memory was taken up by the OS, network stack and what programming language you were using to guess how much memory was taken up by the program?
For the 3rd question I'd have difficulty. AFAICS you'd have to use some form of compression to be able to do it (you have to hold 8M characters in 2M RAM - you could convert the phone numbers to 'real' numbers, but that'd still be 4MB in 2MB RAM). I reckon I'd be able to do it, but I'd guess it would take at least several hours to work out the nitty gritty - which sounds dumb for a phone interview.. (There's a cool way I can think of that would sort up to 10 million 7 digit numbers in 2MB RAM - but it would need 12MB to sort any number of 8 digit numbers - and this would rely on the numbers being unique, which isn't specified)
Could I offer to donate £50 from my first pay cheque to buy Google some more RAM? ;)
Re:HR could use some help... (Score:1, Interesting)
If you actually ask for the detailed feedback you'll get a second generic comment that might be a laughably poor fit for you as a candidate. There is a disconnect between the HR handler and the people who conduct the interviews -- your technical interviewers don't actually care [and aren't well enough trained] to give detailed feedback, but the HR handler is told how important it is for PR that everyone gets some meaningful and not-too-negative feedback. (Surveys have shown rejected candidates often refuse to use the company's product, and if you're Google with so many rejected candidates they rely on using the product, that's a problem!) Hence the somewhat duplicitous message -- it's not that the HR guy is lying about the importance of feedback; it's just that practically he doesn't have the feedback to give.
Re:If it were any other company... (Score:0, Interesting)
At another company, sure it might be like that. Though at the G, it's more like:
Flexible = You don't turn down opportunities to do a variety of interesting things.
Adaptable = Able to fit in well with a variety of people (the world doesn't revolve around you)
!Hierarchy focussed = Don't care for power games, politics and related bullshit. Happy to field requests from outside your dept.
Get stuff done = Like above, no power games but actually like to do your work instead of a multitude of 'meta-work'.
J.
Re:I had an interview with Google a few weeks ago (Score:2, Interesting)
The first question can actually end up using a little calculus - you need to advance by square-root of the number of floors IIRC.
Two I can't remember my answer for, but think there were a couple of variations.
Three requires you to realise that the numbers are unique, within a finite range, and you have sufficient *bits* for a radix sort.
Re:What they mean to say is... (Score:3, Interesting)
AMD would have been a bit nicer to work for if they had catered to the out of towners. Nothing like flying 3000 miles to then have to pay for the hotel and food out of pocket [expenses for out of country employees took 6 weeks to get at the least].
Where I work now it's fairly sterile too. We have a few posters up on the wall, but mostly it's a sea of beige and fluorescents. Fortunately, there is a pub just behind the office so I can sneak into there for a quick bite to eat when I get a case of the Mondays. That and we're tastefully colourful during lunch hour discussions [e.g. not PC-centric] so we can act like adults.
Tom
Re:I had an interview with Google a few weeks ago (Score:3, Interesting)
Over the years I have had more than my fair share of jobs and many of them I got even though I failed to answer the technical questions. What I did was explain my thinking, even on multiple choice tests, I write my thinking along side. You are never ever going to have to solve the marble problem, but they want to know if you have heard of things like a binary search and more importantly how do you respond in situations that are "out of the box".
It aims to demonstrate problem solving, communication, breadth of knowledge. They do not want you to sit in silence for 5 minutes and then given them the right answer, they want you to explain ALL the ideas you have about how to solve the problem, and then the criteria you may use for selecting a solution from the available ideas. Arguing the toss about the number of marbles, the mass of the marbles, etc. is not going to get you anywhere.
Am I the only rejectee who is not bitter? (Score:3, Interesting)
In fact, I was asked soon after my Google experience to help interview a group of candidates at my current company, and I decided to take the Google approach. While there were very few people who were able to ace the battery of questions, there was an interesting effect. That is, you learn very quickly by asking those types of questions the kinds of people that YOU would want to work with. There are those people who simple brush those questions off by saying, "I don't know that... I've never needed to know that..." and there are those who try to work through the problems and seem enthusiastic about learning the solution. Which of those two would you rather interact with on a daily basis?
-m
Re:I had an interview with Google a few weeks ago (Score:3, Interesting)
Do some back of the envelope calculations, take into account that the terminal velocity of a marble-sized hailstone is 45 ft/s, and you'll estimate that terminal velocity occurs within 15 floors.
Drop it at 7, and do a linear search on either side of that depending on whether it breaks or not. That yields less than 14.
In other words... (Score:2, Interesting)
I have no experience with google, but it is my experience elsewhere that in HR, "fairly flexible" means "will work long hours without compensation," "adaptable" means "will not make a fuss when his/her review date comes and goes without action" and/or "will accept that any bureaucratic injustices with the company do not exist, and if he/she has a grievance, it is actually the one filing the grievance who is in the wrong". And "not focusing on titles and hierarchy"...well that just means "not focusing on titles and hierarchy while those above him/her do."
Again, I don't know much about Google in specific, but this is the way HR tends to word things in most other companies.
But no, I'm not bitter at all.
Re:Google's bennies are not that great (Score:2, Interesting)
I think I'll take my nice work/life balance with a pretty darn good, although not earth-shattering, salary.
Re:I had an interview with Google a few weeks ago (Score:2, Interesting)
After 3 such phone calls, and a plane trip to one of their offices so they could grill me with such questions for 6+ hours all the more I got was 'we've decided to halt the interview process.' When I attempted to ask them why (really honstely so I could improve whatever skilset they felt I didn't have) I got no response.
Found it to be a bit on the rude side.
Re:What they mean to say is... (Score:5, Interesting)
Then I "moved up" for more pay to a mid size company, not bad. Pretty good actually.
Then eventually went to the largest privately owned company in the world. Benefits were great, but I was faceless. I was expected to do more work for less, but my heart wasn't in it. For some reason I couldn't help feeling used. Why? Because I felt detached from the company. Their goals were not my goals and they could have given a shit about my goals.
Maybe it was a personal issue, but at 30+ years old you simply come to a point in your life you make a decision. You either buy in and ass kissing becomes your specialty or you have a "life crisis" and try to find some sanity somewhere else. I chose the later and now work for a small company again. I don't think I'll ever go back to a large company, it just feels inhuman and unnatural.
But to each his own, some people don't have the same issues with authority that I have. More power to them.
Two Kinds of Judgement (Score:3, Interesting)
Re:Employee who just gets the work done?? (Score:3, Interesting)
They're not only an R&D house -- they actually have daily operations and need people to run things as well. If they only hired geniuses, they'd end up with a lot of bored geniuses in no time.
-b.
Re:I had an interview with Google a few weeks ago (Score:3, Interesting)
1) Make 256-element array
2) Iterate through file, incrementing array elements to count occurrences of each byte value
3) Iterate through array, outputting desired number of each value.
Total storage required: 256 x 4 bytes, supporting file sizes up to 4GB, working in O(n) time.
Of course they probably meant the file contained a list of strings or numbers, but then it's their fault for being too vague...
(I applied on their website, and didn't get past the first screenings... Guess my 2.9 GPA wasn't good enough, huh? Stupid history courses...)
Re:"Fit Factor" (Score:5, Interesting)
Interestingly, having spent the past few weeks interviewing, I tend to think desirability of 'quick learners' vs. 'skilled experts' depends upon the size of the company. Small companies prefer quick learners because there are always many more tasks to do than skilled employees available to handle the tasks. In this situation, quick learners have the advantage because they can more easily grow in a company where the jobs aren't always well-defined. If it turns out that the Java guy you just hired can also manage the corporate web site, this is a real plus in a small firm. Having people who can do lots of things, and do them reasonably well, is absolutely necessary when your company is limited by the number of resources available.
At large companies though, the situation is reversed; hiring managers in large corporations are often distanced from the actual work getting done, so their 'win' is to hire the person with the best current skills. This way, hiring managers get the most 'bang' for their corporate hiring buck because the expert employee is immediately productive in the job. In addition, larger companies spend much more time managing a workforce that expands and contracts depending on the economy. Human resources are just that -- something you aquire when you need to increase production, and get rid of when you don't. Overall, it's far easier to manage a large corporate workforce when employees have very narrowly defined skill-sets that you can swap in and out depending on the needs of the company.
In a nutshell, small companies want people who can get things done, where large companies want someone who can do one job and only one job, but still do that job better than anyone else.
Questions to ask Google (Score:3, Interesting)
Re:No interviews required (Score:3, Interesting)
First question was from my dim, distant past, close to the dawn of telecommunications. Nothing at all I would list on a CV that only highlights the best of my recent career. Cool, thought I, I know this because I did my thesis research in it. Now, I never finished my thesis, and never published my results because private industry came courting and I haven't mentioned this on a CV in at least 15 years. Some of my closest and geekiest friends understand it, though, so who knows.
Next two questions were about some technology I emailed some
The next question was straight from a forum where I've never used my real name, or any alias except for a gmail account that was linked through an invite at some point. Since I long ago made a conscious decision to never be professionally associated with that forum, and took extreme precautions to avoid posting from traceable IP addresses and the like. I kind of stammered through a half-assed response about knowing very little on the subject. At that point I suddenly realised that something wasn't right.
The rest of the interview alternated between topics on my CV and archaic systems I haven't admitted to knowing in a long time. Clearly the first interviewers from Google had access to information about my early career and life back to childhood. It was exactly like sitting a government security clearance interview, they already had the information, the interview was just to confirm you and your past were in agreement. I knew all the answers, because the first interviews were obviously running from a script that I could have written.
Later interviewers just wanted to know really detailed technical things that ranged all over and some of it I had to admit I didn't know. One interview lasted about 5 minutes, the guy knew I wrote some programs about 20 years ago, so he started asking questions as if I were still actively coding. When I told him I no longer write code, he wondered why I had applied for a job as a programmer, but then figured out I was being recruited for other things and politely ended the interview.
the AC