Skip to main content

Google Developer Relations Jobs

I work as a developer advocate at Google. I think it's the most exciting job at the most interesting company in the world, but of course I'm biased ;) In fact, when I came to Google, it turned out to be roughly twice as good as I was hoping it would be. We have a bunch of openings right now. If you're both a hardcore coder as well as a hardcore extrovert, you should think about applying (through me, of course!).

By the way, the interview process is somewhat challenging. You should definitely plan on spending some time in front of a whiteboard. I heartily recommend two books, Cracking the Coding Interview and RESTful Web Services.

The video below is from Google Developer Day 2011, Moscow. Not everyone has to go to Moscow, but I think it conveys part of why I find this job so much fun :)



By the way, we also have other positions within developer relations as well as within Google as a whole.

Comments

hermy said…
Would love to apply but in the future when I'm not so nooby and have at least my B.S. degree. But I have been looking into Restful web services, thanks for the book suggestion.
jjinux said…
Enjoy the book! If you're interested, here's my review of it:

http://jjinux.blogspot.com/2008/12/books-restful-web-services.html
hermy said…
Thank you! Any other readings you might suggest? Also, any word on Google IO. Would love to go to see the android talks. But I know they've said something along the lines of a coding challenge to keep the "I'm going for the free stuff" people out.
jjinux said…
> Thank you! Any other readings you might suggest?

Sure, this blog post is pretty famous. It talks about getting a job at Google: http://steve-yegge.blogspot.com/2008/03/get-that-job-at-google.html

> Also, any word on Google IO.

All I have is this: http://googlecode.blogspot.com/2011/11/google-io-2012-extended-to-three-days.html
hermy said…
Gotcha, thanks man!
Dave Doolin said…
Shannon, thanks for speaking at East Bay Ruby last night, and thanks for taking the time to answer questions 1 on 1 afterwards.

I just ordered "Cracking the Coding Interview." This will be good for staying focused.
jjinux said…
Thanks for coming to the talk ;)

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p