My Slashdot posts on being interviewed at Google

The actual interview process at Google is covered under NDAs, but I posted a few messages to Slashdot today (subject "Google's Ph.D. Advantage") being careful to not discuss details of the interview process; here are my posts:

To be honest, when Google flew me to California for an interview, I was luke warm about the idea of working for Google because I love my life style living in the mountains of Northern Arizona.


However, after spending a day being interviewed by 6 extremely bright and creative people, I very much wanted the job (I did not get it, oh well). It is true that bright people want to work with other bright people. Anyway, it may sound strange, but I view the interview process as a very positive experience (also, after 30 years of working, it was the only job that I tried for that I did not get, so I was able to set most ego stuff aside). In addition to the interviews themselves, I got to have lunch with Peter Norvig and before I left the Google campus a nice person let me ride a Segway :-)


It really is true that a few very good people are way better than many above average people.


One of the most fun times in my career was when I had a boss who has a PhD from MIT and hired many other PhDs and MSs from MIT - some of the best colleagues that I ever had.


Personally, I think that I am going to invest in Google stock, but I am likely to wait for a few months after the IPO (or make a low bid for the IPO).

...and later, I added:
One more thing: in just one very long day of interviews, I had my attitude adjusted re: software development:


I am a hacker (at heart), and I always look to rapidly coding something that works and is solid.


At Google, it seemed to me that their main focus is on algorithmic development. In the few months since I was at the Google campus, I have found myself "slowing down" and spending much more time thinking through issues of scalability and efficiency (and not just use a "good enough" algorithm, or pull my copy of Cormen/Lieserson/Rivest Algorithms book from my book shelf and not do much original thinking).


Anyway, I thought that it was cool that an investment of one day actually changed some of my own attitudes about software development (and I am an older guy, coding since the 1960s :-).

Comments

Post a Comment

Popular posts from this blog

My Dad's work with Robert Oppenheimer and Edward Teller

Robert Oppenheimer and Edward Teller facilitated my Dad getting a professorship at UC Berkeley when I was 3 years old. Oppenheimer left Berkeley but Teller was a good friend of my father and I remember him being in our home. Three weeks ago, my wife and I were just leaving to see the new Oppenheimer movie when my Dad called. He mentioned that when I was in grade school he was invited to give a talk at Princeton. After his talk Oppenheimer talked with my Dad and invited him to have dinner at his house. My Dad said Oppenheimer was not well (I think he died of throat cancer soon afterwards) but his wife Kitty carried the conversation. My Dad, Ken Watson, passed away 10 days ago on August 18, 2023.
Read more

Time and Attention Fragmentation in Our Digital Lives

  As humans we have evolved over a few million years to be both attentive and reactive to danger, live in social communities, and spend much of our time being in the present moment gathering and eating food and socializing. The behavior of rapidly changing short attention to content on social media, too many good short form things to watch on streaming video entertainment platforms, are all rewiring our brains in an unnatural and unhealthy way. I fight back, but in really simple ways that entail little ceremony: Almost every morning I spend 30 minutes scanning Hacker News (about 10 minutes), Apple News (about 5 minutes), and the remaining time on Twitter and Mastodon finding interesting new (mostly tech) things. I make notes in a temporary Apple Note: links of things I may want to research, try, or simply read that day. I like to get this all done at once, and then not feel like I need to interrupt my activities during the day to “catch up” on what is happening in the world. In a way,
Read more

Ruby Sinatra web apps with background work threads

In Java-land, I have often used the pattern of writing a servlet with an init() method that starts up one or more background work threads. Then while my web application is handling HTTP requests the background threads can be doing work like fetching RSS feeds for display in the web app, perform periodic maintenance like flushing old data from a database, etc. This is a simple pattern that is robust and easy to implement with a few extra lines of Java code and an extra servlet definition in a web.xml file. In Ruby-land this pattern is even simpler to implement: require 'rubygems' require 'sinatra' $sum = 0 Thread.new do # trivial example work thread while true do sleep 0.12 $sum += 1 end end get '/' do "Testing background work thread: sum is #{$sum}" end While the main thread is waiting for HTTP requests the background thread can do any other work. This works fine with Ruby 1.8.7 or any 1.9.*, but I would run this in JRuby for a lon
Read more