Hey—we've moved. Visit
The Keyword
for all the latest news and stories from Google
Official Blog
Insights from Googlers into our products, technology, and the Google culture
How I got to Google, ch. 1
4 octobre 2005
Posted by Michael Krantz, Google Blog Team
-- via craigslist, and thanks for asking. Our engineers, though, tend to come by more varied, and occasionally odder, routes. Some get recruited out of grad school, or by friends or former colleagues. Others just send their resumes to jobs@google.com. For a few engineers, though, the path has been more interesting.
Peter Bradshaw
, for instance, built “a music playing system based on printed cards with barcodes and webcams. Includes lego!” (No, I don’t know what that means, either.) Over the next few weeks, we’re going to post some of their stories.
Like this one, from Systems Administrator Aaron Joyner:
My story started when I came into work one morning and was unable to look up something on Google. Being the sysadmin for my company at the time, it was my responsibility to resolve the problem, so I started poking around. It turned out that our DNS server [ed: all the jargony stuff you'll hear in this anecdote refers to the software that websites use to connect and talk to each other] was returning an error when trying to look up google.com, specifically a server failure error. Just as I’d convinced myself that it wasn't our problem but Google’s, the problem suddenly resolved itself. I promptly forgot about it and went back to my regular work.
But then I came in the next morning and had exactly the same problem, so I started looking at Google's DNS responses very closely. It became clear that the specific combination of delegations and glue records they were returning [ed: see note above] would result in an eventual error approximately once per day, and this would then take it about five minutes to give up and try again. Not entirely convinced that I should point the finger at Google yet, I posted
a message
to my local Linux Users Group asking if anyone had had problems with resolving google.com addresses and got a couple "Yeah, I did have a problem like that once recently" responses.
Thus reinforced, I headed over to Google.com, found the "Contact Us" page and the "Report a problem" link, chunked in a brief problem description and a link to the
archived copy
of the long technical description from that same mailing list thread, and thought to myself, "Gee, I'll never hear about that again." But then one afternoon a week later I get an email that said, basically, "We've received your problem report, and forwarded it on to the appropriate department, if they need any further information they’ll contact you. Thanks." Again, I thought, "Gee, how nice. I'll never hear about that again."
But that evening I got an email from Dave Presotto (the guy who wrote the DNS server for Plan9) saying that he was looking into it and would get back to me. Forty-five minutes later I got another email, this one describing how he believed they had accidentally fixed the problem earlier in the week due to general code cleanup, and asking what I thought of the solution. After I recovered my senses and stopped bouncing around the room, I had a few email exchanges with Dave, in the course of which I asked casually if they needed any good sysadmins out in Mountain View. He referred me, and the rest is history.
Libellés
Africa
19
Android
58
April 1
4
Asia
39
Europe
46
Latin America
18
accessibility
41
acquisition
26
ads
131
apps
419
books + book search
48
commerce
12
computing history
7
crisis response
33
culture
12
developers
120
diversity
35
doodles
68
education and research
144
entrepreneurs at Google
14
faster web
16
free expression
61
google.org
73
googleplus
50
googlers and culture
202
green
102
maps and earth
194
mobile
124
online safety
19
open source
19
photos
39
policy and issues
139
politics
71
privacy
66
recruiting and hiring
32
scholarships
31
search
505
search quality
24
search trends
118
security
36
small business
31
user experience and usability
41
youtube and video
140
Archive
2016
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2015
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2014
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2013
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2012
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2011
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2010
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2009
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2008
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2007
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2006
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2005
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
mars
févr.
janv.
2004
déc.
nov.
oct.
sept.
août
juil.
juin
mai
avr.
Feed
Google
on
Follow @google
Follow
Give us feedback in our
Product Forums
.
Follow
