Among many IT professionals, working at Google is seen as a dream job.
And no wonder. The burgeoning company is a driving force in Internet development. Its Web-based word processing app, Writely,
sends a shiver of nervousness through Microsoft. Its Adsense program is
changing e-commerce. And its acquisition of YouTube earned grudging
admiration from Big Media.
Heck, the very word “google” has entered the language, earning a coveted spot in the august confines of Webster’s Dictionary.
Working for Google means working for an organization that’s
extraordinarily well funded – the words “layoff” and “Google” aren’t
likely to be paired anytime soon. It also means working alongside top
talent. With as many applications as Google receives, the company has
its pick of the best.
If that’s not enough, Google serves a free lunch – every day – to its
employees. (“Yummy, and made with love,” according to the company.)
The good news is that Google is hiring. A lot. The company is hoovering
up IT staffers like a Boy Scout at an all-you-can-eat. Its job board lists scads of openings, and with the company’s breathless growth it’s likely there’ll soon be more.
The bad news is that getting hired at Google isn’t easy. It requires a
unique set of characteristics to land a gig with the search giant. With
that in mind, Datamation spoke with Google’s Director of Staffing, Arnnon Geshuri, about the company’s hiring process.
Google, being Google, doesn’t just call its staffers “employees.” No,
that’s far too traditional. So what’s its special term of endearment
for workers?
With a laugh, Geshuri spills the secret: “When they come on board, they become Googlers.”
However light-hearted, the term is revealing. It suggests a unique
corporate culture, especially in the tech world. (True, Microsoft
workers are called ‘Softies,’ but how many other big tech companies
give workers a nickname? After all, IBM staffers aren’t called
‘IBMmers.’)
And what makes a Googler?
“We have a core belief that a Googler has certain aspects to
themselves,” Geshuri says. “They’re really motivated, enthusiastic,
entrepreneurial.”
The word that stands out in that otherwise generic description is entrepreneurial.
While working in the IT department of, say, a large manufacturing
facility might not require entrepreneurial spirit, working at Google
most certainly does. With the search giant’s rapid growth – and its
aggressive moves in arenas held by competitors – the need for staffers
to possess self-starting business smarts seems clear.
Does that mean that an IT pro needs strong business skills to get hired?
“It’s always a plus, but it’s not necessarily itself a deal breaker,”
Geshuri says. Google prefers it when, “from a business sense, you can
relate to the technical aspects and look at the mission-critical needs
to the company, and really understand some of the context around why
we’re building some of the infrastructure.”
In short, “It helps if the person can align the business needs to the technology.”
This may be more important at Google due to the company's innovative
“20 percent time” policy, in which IT staffers are free to pursue
projects they're passionate about on company time. It takes an
entrepreneurial (and disciplined) spirit to use this unstructured time
in ways that benefit the bottom line.
If you’re wondering if Google has an opening in your particular tech area, the answer is probably yes.
“The great thing is that we have almost every type of IT opening
available,” Geshuri says. “From networking to security to sysadmins. If
you look at our job board, we have tons and tons of amazing openings.”
He’s not exaggerating. The openings range from the data center, global
infrastructure, and security to video conferencing, telecommunications,
and Web site engineering.
The locations, too, are diverse. “It’s not necessarily centralized, so
it’s a broad set of roles in all the locations we have,” he says. The
company has facilities from Phoenix to New York to Dallas, not to
mention Egypt, the Ukraine, Latvia, Ireland, Azerbaijan, and many
others.
(Azerbaijan? Does Google need outposts in every little corner of the world? Is it…planning on taking over the planet?)
“Not one location is hiring more than the other,” Geshuri explains. He
refers to the global growth of the company, how it’s always building
infrastructure, always trying something new, always innovating. “So
each location, we want them to be just as fully staffed as any other
location since we’re growing very rapidly.”
Google receives about 3,000 job applications per day, Geshuri says.
This number represents applications for all the company’s jobs, not
just tech positions.
However, “Because we’re always looking for great IT talent, a great portion of that [3,000 applications] is IT professionals.”
If your resume is one of those that attract attention, your phone will
ring. For IT job applicants, “It’s a phone screen first, with…a series
of folks internally,” he says.
“Once that occurs, the qualified candidates are invited to one of our
campuses to interview in that respective area.” If all goes well,
you’re on your way to becoming a Googler, and earning what Geshuri
refers to as “very competitive compensation and benefit packages.”
If you think you’re qualified, Geshuri stresses that Google is very
interested in hearing from you. “We are very open to new personnel and
new ways of doing things, and we’re always looking for the greatest
talent to come join the Google family," he says. “This is a wonderful
environment for someone to grow in.”
Free cafeteria food, annual ski trips to the Sierras and free
laundry are just some of the fringe benefits of working at Google.
Getting hired is the trick.
Every month, aspiring workers deluge the popular Mountain View,
Calif., search engine with up to 150,000 resumes -- equivalent to a
stack of paper at least 50 feet high. And the company claims to read
each and every one.
As one of Silicon Valley's hottest companies, Google has become a
beacon for job seekers. In just a few short years, the interest has
helped the company amass an arsenal of what is arguably among the
world's top technology minds.
"I would argue that definitely they have the best talent," said Joe
Kraus, a co-founder of the Web portal Excite Inc. who currently leads a
start-up, JotSpot, in Palo Alto, Calif. "They invest so much because
the more great talent you have, the easier it is to attract even more
great talent."
Google hires nine new workers a day. In less than two years, the number of employees has more than tripled to 4,989.
The growth spurt is being fueled by a gangbusters-like online
advertising market and Google's boundless ambition, including new
initiatives in everything from wireless Internet access to video
downloads. The goal is to keep the production line of new products
humming so that users spend more time on the Web site.
Getting rich is what drives some of the applicants. Many Google
workers became instant millionaires at the time of the company's
initial stock offering in 2004. To this day, prospective employees are
drawn by the promise of wealth, although their chances of striking gold
are a lot lower now that the firm's shares are soaring above $400,
making stock options less likely to appreciate by large amounts.
Competition for the best and brightest is fierce. Rivals Microsoft
Corp. and Yahoo! Inc., plus start-ups, are trying to reel in many of
the same job applicants, igniting occasional bidding wars.
Hiring is a major challenge
Yahoo!, in particular, has recently landed some workers who
interviewed at Google, such as Andrei Broder, a former research
executive at AltaVista and IBM. He says being at Yahoo!'s research lab
is an opportunity to have more impact because it's younger and smaller
than those of its competition.
Sergey Brin, Google's co-founder, has called hiring one of his
firm's biggest challenges. If it's unable to find enough top-notch
workers, he says the company's rapid growth could be hamstrung.
Google's also hiring superstars. This year, they include Vint Cerf,
one of the Internet's founding fathers, as chief Internet evangelist.
Kai-Fu Lee, a former Microsoft executive and expert in technology that
turns speech into text, now heads operations in China. And Louis
Monier, founder of the early search engine AltaVista, has an
undisclosed technical role.
To lure workers, Google offers perks, including free cafeteria
meals, free use of laundry machines, a child-care center, a free annual
one-night ski trip (resort destinations vary depending on office
location), dog-friendly offices and an on-site doctor. Engineers can
devote 20 percent of their time to projects of their choice. What's not
mentioned is that much of the largesse is designed to keep workers at
their desks longer.
In addition to posting job openings in newspapers and online, Google
recruits at universities, offers computer science students free pizza,
hosts a software programming competition and invites technology clubs
to hold their meetings at its headquarters.
Last year, the company won attention for publishing a booklet of 21
problems called the Google Labs Aptitude Test. Readers of several
technology magazines were asked to mail in their answers and promised
that Google would get in touch with them if they scored well.
One question asked: "In your opinion, what is the most beautiful
math equation ever derived?" The Gaussian integral, a complex
mathematical equation used in studying the kinetic molecular theory of
gases, among other things, has been suggested as a smart answer by some
on the Internet. Another question involved filling a blank rectangle
"with something that improves upon emptiness," leaving applicants
scratching for a subjective winner.
Judy Gilbert, Google's staffing programs director, says the
questions weren't really used for hiring. In any case, smart alecks
soon posted the answers online so they could be easily found by
cheaters.
Hundreds of recruiters keep the resumes pouring into Google. Many
are contractors, making them easier to dismiss if the company scales
back its hiring needs.
Jobs available as of last week include someone to negotiate video
licensing deals with Hollywood studios, someone to lead user studies
for guiding product design and an attorney to manage the firm's real
estate. More posts are likely to open in announcements this week, as
the company is creating 600 new jobs in Ireland and up to 100 in
Pittsburgh.
To land all-stars, Google's recruiting machine goes into overdrive.
Secrecy is sometimes critical. If tipped off, companies from which
Google is trying to poach could start a bidding war or retaliate
against a potential defector.
The risk can be worth it for a top executive of Lee's caliber. He
ultimately accepted a compensation package of more than $10 million,
igniting the legal battle between Google and Microsoft.
To fill positions lower on the pecking order, Google has created an
extensive college-hiring program, among other efforts. Recruiters
visited 60 schools this year to show off the firm's technology, hand
out T-shirts and interview prospective job candidates.
Interviews at Google usually begin on the telephone. If successful,
applicants are invited for face-to-face meetings with up to 10 people,
a process described as excruciating by people who have gone through
them because of the length of time it takes and the mental gymnastics
necessary.
Recent job candidates described questions as being on topic, whether
about software code or business. In many cases, they were asked to
brainstorm and role-play to show how they think. For instance, how
would they market a product? Those who conduct the interviews
frequently challenge applicants. Questions about algorithms, Java
software and computer networking are common for applicants seeking
technical positions.
Google has created its own software system for tracking job
candidates that allows employees to share comments on each applicant.
Because so many people must sign off on new hires -- Larry Page, one of
the firm's famed co-founders, approves each one -- the process can be
lengthy, even excessively so, several applicants said.
Some were shocked to learn the importance Google gives to college
grade-point averages in deciding whom to hire. The emphasis draws
complaints from some older candidates, who believe the measure is
irrelevant for them because they have been out of school for so long.
In general, Gilbert says Google seeks applicants who show they are
willing to take risks, are highly motivated by a range of topics and
want to be part of something bigger than themselves. The profile is in
line with the firm's carefully crafted iconoclastic image.
Historically, Google has paid workers less than the industry standard and showered them with stock options.
That paid off for approximately 1,000 Google employees in 2004, when
the company's high-profile initial stock offering made them instant
millionaires. Although the firm's current pay structure is a closely
guarded secret, one can assume hundreds, if not thousands, more have
become worth seven figures, at least on paper, considering that
Google's stock is now hovering above the $400 mark, a nearly fivefold
increase from its premiere.
After its initial public offering last year, the company has had to
offer more money upfront because options aren't as valuable,
compensation experts say.
Many competing firms claim Google has driven up salaries for software programmers by nearly 50 percent in recent years.
According to one source who wanted to remain anonymous, the
beginning salary for programmers is now about $45,000. How accurate
this is cannot be known, but at least it's a clue.
BENEFITS GOOGLE TEST QUESTIONS
A test published by Google last year in several magazines was used as a recruiting tool. Questions included:
1) Solve
this cryptic equation, realizing of course that value for M and E could
be interchanged. No leading zeros are allowed: WWWDOT -- GOOGLE
DOTCOM
Answers: 777589 -- 188106
589483 or 777589 -- 188103
589486
2) How many different ways can you color an icosahedron with one of three colors on each face?
Answer: 58,130,055
3) Which of the following expresses Google's overarching philosophy?
a) I'm feeling lucky
b) Don't be evil
c) Oh, I already fixed that
d) You should never be more than 50 feet from food
e) All of the above
Answer: b
-- San Francisco Chronicle
BENEFITS
Workers at Google get a range of benefits that surpass those at many other companies. Here's a sample:
Free cafeteria meals
On-site dry cleaning
Coin-free laundry room
Free annual ski trip
Dog-friendly offices
On-site doctor and dentist
Free commuter shuttle service to several Bay Area locations
Source: Google Inc.
A short warning: There is a lot more information here than what is just
about Google. Specifically, possibly boring details of plane travel,
Bay area real estate, etc. Feel free to skip sections that don't sound
like they interest you. By skipping sections you'll miss a few little
details that are in the section that might be more interesting, but
that's probably not a big crime.
The Plane flight out
I flew out of RDU airport on a Sunday evening, First Class on America
West airlines, courtesy of Google. The first leg of the trip was on a
brand new Airbus A315. The flight landed in Phoenix Arizona, where it
was 99 degrees. When you stepped out of the cabin, you were basically
hit in the face with the heat. It was a "dry heat", you could say, as
it wasn't sticky, but it sure was hot. I transfered planes to a rather
old Airbus A320. :) The plane I transferred to was old enough to have
ashtrays that had been used. ;) There was some difficulty with the Aux
power units on the plane working, so the AC on the plane wasn't very
comfortable at first. The crew tried 3 times unsuccessfully to start
the plane w/ the Aux power units, and each time, the entire electrical
system would shut down, and the plane would go completely dark. It was
a rather unnerving experience, even with the knowledge that the Aux
power units had nothing to do with keeping the plane in the air after
we took off. After we got off the runway, the plane cooled down and the
rest of the flight was rather uneventful.
The hotel
Upon landing at SFO, I took the train over to the rental car location,
and picked up my rental from Budget, also courtesy of Google. I then
drove down US101 to CA85, then to El Camino Real, where the hotel I
would spend the next two nights in was located. I got checked in by
11:30 and went up to look around. The place was very unusual in a lot
of respects. It definitely had style, everything was decorated with
paintings and artwork by 20s and 30s Russian artists (according to one
sign), but the whole place had a very "square retro" feel to it. There
was no overhead lighting in the room, just lots of lamps attached to
various bits and pieces, including the headboard, the desk, etc. They
were all of a similar style, with highly conical frosted shades, that
were tapered unevenly at the end (i.e. cut through the cone at an
angle). They were all controlled by local dimmers on the lamp bases,
and made for an interestingly lit, yet dim, room. There was a desk with
a very comfy Suede covered desk chair, and a squared off retro living
room chair with a round green leather ottoman reminiscent of ones my
parents had when I was a child. The sink bears mentioning as well. It
was an above counter sink, with a really cool design, and a faucet that
stuck up high enough to be able to pour water into the above-counter
basin. This had the interesting effect of reducing the counter space
consumed by the sink, as where it met the counter was farther down the
taper of the sink, so in a home environment you could actually put
things "under" the lip of the sink without problem. I eventually got to
sleep by 12:15 or so. As a reminder, that's 3:15am according to my
biological clock at he time - a rather long day. :)
Apartments
I woke up the next morning, got a shave and shower, and planned a short
trip up to Google HQ and past the one possible apartment near there.
This trip gave me a good feel for how long it would take to get to
Google for the interview, as well as a first look around their campus.
It took about 7 mins to drive from the hotel up to Google, and on the
way back I got my first look at apartment living in the Bay area. The
complex was nestled in the back of a residential area, and looked a lot
like all of the other houses in the area. The units were single floor,
and grouped in sets of maybe 4 to 6 at most. The all had a nice
pleasing green color, that went well with the foliage surrounding them.
The looked a bit older than I might have liked, but not terribly so. I
didn't notice it at first as an apartment complex, it took a bit to
"find" it even though I was right out in front of it. After that, I
headed back to the hotel to plan a longer route to look at some other
various possibilities for apartments in Mountain View. I planned out a
big circle, going north on 85 to US101, then down the San Tomas
expressway, back down across El Camino Real, then down to Cupertino to
check out one place down there, then back up to El Camino Real and the
Hotel.
Silicon Valley
The bizarre and wonderful thing about this trip was not the various
apartment complexes I saw, although I'll touch on that in a minute. The
startling thing was all of the businesses I passed. Places like NVidia,
Sun Microsystems, Canon, Hitachi, Network Appliance, Oracle, Microsoft,
Apple, and I'm sure dozens of others that I've since forgotten about or
didn't even notice. This really brought home one of the key things
about the trip. When I moved from Greensboro to Raleigh, I found this
thriving flourishing Linux community, and hundreds of wonderful people
who shared my goals and interests, and a thriving business environment
for the type of work I like to do. Driving around the bay area made me
realize that moving from Raleigh to there, would be just like moving
from Greensboro to Raleigh, up an order of magnitude. This change in
environment continues in my mind as one of the primary advantages to
moving to the Bay area.
As for the Apartments, there were numerous things I saw, based on
somewhat unusual criteria Deborah had defined in an online search.
Specifically, places that were cat friendly, that had either washer and
dryer, or washer and dryer hookups. So, needless to say, it's possible
that what I saw was a bit skewed, but it seemed to be a rather unusual
mix. There were a couple apartment groupings that were relatively
similar to the current place we live, in that they were rather new, and
2-3 story, nicely kept locations. One of the complexes was gray, and
the other was in the apparently more common style of south-western
adobe / orangey-brown. Some were older, and a couple certainly didn't
look like places we wanted to live. Generally though, my impression was
that it'd be quite reasonable to choose one of the places from the list
and we could live comfortably and happily in the rent range of $1400 -
$1800 per month.
The Interview
On the way back around my loop I had Taco Bell (yeah, I know, a rather
uneventful ~$3 lunch even when Google was paying up to $30 / day in
food expenses, silly me). I made it back to the hotel at about the
appointed time (12:30) to change and head over to the interview by
1:15. I erred a bit on the side of caution, and arrived at about
1:00pm. I met Stacie, my recruiter / guide for the next few mins, and
she informed me of some of the details of how the proceedings would go.
I was escorted to a small "interview room", which judging by the signs
on the wall there may have been quite a few of. I sat down with Stacie,
who informed me that I would be meeting with 4 pairs of individuals,
for about an hour each. I met with 3 pairs of tech folks, and one pair
of managers. The tech guys basically grilled me for the entire time on
various tech aspects, ranging from file system internals, to
networking, to service level questions on things like apache, DNS, etc.
Their purpose wasn't just to see what I knew, I think, but also to see
how I reasoned out solutions when they found corners of the *NIX world
that I didn't know cold. Specifically things like the inner workings of
TCP Syn cookies, how EXT2 inodes handle storing filesystem permissions,
data, blocks, etc.
There were also interspersed questions asking "Why do you want to work
for Google", "Why did you want to be a System Administrator, etc". They
also asked a few open ended questions such as, "Are there any questions
we haven't asked you, or is there any aspect of your experience that we
may not have seen that you want to talk about?". There were also
opportunities for me to ask questions of each of the various
interviewer groups. I probably should have taken better advantage of
that, and reversed the question in the form of, "If (or when) you were
in my position, what question would you ask of Google that I might not
have thought to ask?" :) Unfortunately I wasn't the clever on my feet.
After the Interview
After leaving the interview I was so brain-fried that I tried to talk
to Deb on the phone about it while driving, and I couldn't really get
past the physical details. My mind wasn't very good at processing
information after all of that, it had started to shut down. :) I got
back to the hotel and took a nap for an hour or so, and again foolishly
passed up the ability to go out and get food on someone else's nickel.
I suppose I wasn't up to the task, as my mind was still mulling over
the afternoon. I ate a bag of beef jerky that I had brought with me (it
started as a snack, honest...) and vegged on the laptop for a bit, then
fell asleep.
Getting home
I set the alarm back to 7:00am the next morning, and woke up at 7:05,
bizarrely not to the alarm. As I was telling myself that I had to get
up or I'd miss my plane back, the alarm went off at 7:07. I checked the
setting of the alarm again, and it was still set to 7:00. So strange.
*shrug* I got packed up as quickly as possible, woofed down some
breakfast at the hotel's breakfast room, and hit the car. I got into
the car and onto the road about 7:35 or so, and traffic was really
messy. It's disturbing how people are completely unable to merge in the
Bay area. Traffic on US101 would be fine, up until we'd get near an on
ramp, and then it would grind to a halt. It was especially bad as we
went past the enormous and gorgeous Oracle building. Eventually I made
it up to the rental car return around 8:00, got the car dropped off
very quickly (which was a blessing in disguise), and then went up an
elevator, jumped on the train, went down an elevator, over a ways, up
an escalator, etc, etc forever too far. I finally got to the ticket
counter, tried to check my rolling bag, and was told that it was too
late to check baggage for my flight (not surprising, as the wheels up
time was only 25 mins away). I wasn't sure if they'd stop me for my
lock picks, but I stowed them in my laptop bag and went over to
security. They closed the security lane I was put in at first, right in
front of me. I got into the other lane behind two old ladies who were
taking forever, and apparently the security guy took pity on me as he
opened up another lane just to run me through quickly (and turned away
the half dozen people that tried to follow behind me). :) So they
scanned my baggage, and I was off for the dash to the gate. I got there
as the next to last person to get onto the plane, and apologized
profusely to the poor gate agent. :) While working for US Airways I've
heard them chat about how they hate people who show up late, so I
always feel bad.
Anyway, safely aboard, the transition in Phoenix went rather smoothly,
with some time to recharge the laptop and iPod so I'd have time to
continue writing this on the second leg of the flight. I snarfed down a
bratwurst with sauerkraut from one of the airport vendors and I was
good to go for the rest of the afternoon (well, except for the Mrs.
Fields cookie I couldn't resist from the flight attendant). :)
Thoughts on the process / What's next
All in all my confidence level of the interview was very high, although
I won't know any details about that until the middle of next week some
time. The process goes something like this. The 8 people I met with
will fill out some form, evaluating me, which seems to involve a score.
They take that information, add it to the previous information of my
resume and my phone interviews, and then it goes before a hiring
committee. That committee meets twice per week, once on Tuesdays and
once on Thursdays. Given the time frame, I probably won't hear back
from them until after next Tuesday. I look forward to hearing how the
salary and other associated stock / bonus benefits stack up, to
determine if it's financially realistic to move to the west coast. That
along with the decision of position (junior, intermediate, senior sys
admin, etc) is all decided by the hiring committee, based on the
available information at hand. At the moment my thinking is that if it
is financially logical, I think I'd like to go for it.
Why Google?
My mother has asked me several times if it's as cool a place to work as
I thought it'd be, and why. I tried to explain to her the quality of
the people I was simply interviewing with, not to mention the rest of
the Google crew that's surely as knowledgeable or more. Regardless of
whether it's reasonable to move out to Mountain View, I'm curious
simply to see what their opinion of me is. Do they think I'm a senior,
intermediate, or junior administrator, compared to their ranks? :) I
suppose that's just my ego talking.
The Google Campus (aka The GooglePlex)
In addition to the cool people, there's the whole atmosphere of Silicon
Valley, which I babbled on before, and of course the amazingly cool
GooglePlex. There were actually 6 people playing volleyball on the sand
volleyball court when i arrived for my interview at 1:00. There are
fridges full of drinks as well as numerous snacks, etc in the kitchens
which are scattered around all over the place. True to what I'd read on
the web, they all seemed to be a little different, with slightly
different stuff in various places, but each having the basics (water,
soda, some juice equivalent, etc) covered. The whole complex itself is
architecturally interesting, from the floor to ceiling windows on one
side of the building which allows you to look in and see the thriving
workplace and all of the work areas. Speaking of work areas...
There are cube walls, but they're not laid out in the traditional
manner. There are groupings, of what looked like usually 4 people, who
share a mostly open work area in the middle, and are surrounded by nice
cube work which has glass windowing around the top. This would seem to
have the dual benefit of allowing you to see through across the entire
area, while still keeping noise distractions mostly contained. Also by
the whole wall not being clear you wouldn't be distracted by motion
behind your monitor or some such. As for monitors, I saw a lot of LCDs,
and I don't think I saw a single conventional CRT, but I didn't go
walking through cube land too much, and I don't know if the area I was
in (Building 41) was at all representative of where the Admins work.
From the information available, it seems that Google has 11 buildings
in the immediate vicinity, with 4 being on that same lot (not separated
by official roads, just surrounded by the parking lot and internal
sidewalks, etc. There seemed to be internal parking under at least one
of the buildings (43) that I imagine is a perk of some fashion, as
there is also external parking (where I parked) which seemed to be
occupied by some staff. The original building design and layout doesn't
really lend itself to a "guard house" or any kind of entrance control,
so their solution was sort of novel. They erected pylons in front of
one entrance, so that you can't drive a car through it. Then, at the
other entrance, they stationed a guy with a little chair and umbrella
who checks visitors coming in and directs them to the appropriate
place. Presumably this deters the casual walker through. That coupled
with mag-locks on all the doors which require a Google card to be
swiped past to open, presents a fairly secure environment. I didn't
venture to the other buildings, so i can't comment on their setup
personally.
Anyway, I think that about covers the details of my trip. If I get some
frequently asked questions after this, perhaps I'll make an amendment.
:)