Code Frenzy

About a year and a half ago (October 2005), I tentatively applied for a Software Engineer in Test position at Google. When, to my surprise, a recruiter actually emailed me moments later and scheduled my first interview, I panicked and dug out all my old Computer Science notes and textbooks from my 4 years at uni. I had read that Google’s interviews were tough, so I thought I had better get studying. Over the course of a few months, I stressed out heaps, reviewed all my old comp sci notes (really, who remembers how to implement B-Trees, A* Search algorithms and MergeSort after leaving university?) and had 5 hour-long hard-core technical phone interviews with software engineers and testers at Mountain View.

Anyway, although the recruiter I was dealing with told me I had done very well during my interviews and that everyone was very impressed, I was eventually given the bad news – there wasn’t really anything for me at that time. I was pretty gutted but glad that I had gone through it all for the experience – no interview from then on would ever be as difficult as the ones I’d just undergone.

How wrong was I? About a year later (December 2006), one of the recruiters I’d dealt with during my interviews emailed me and asked if there was any chance I could come in for an interview for the same position at their Zurich office while on my holiday in Europe. Apparently they were expanding their test team and thought of me :). Well, since I was going to be in the area anyway, I said sure. However, since I was going to be on a much anticipated holiday, study and stress were not an option. I just accepted the fact that this meant I was going to totally suck at any tricky technical interview questions – but I thought, what the hell, I might as well.

All I can say is: yikes. As you can probably guess, I didn’t get the job, AGAIN. But this time I felt I actually did quite well in the interviews, despite the lack of study. Google flew me (and Chris) down to Zurich from Copenhagen and put us up in a really flash hotel for a night. The following day I had a full day of interviews on-site at the Zurich office. Basically this translates to 5 hour-long interviews with 5 different software engineers and testers. The questions they asked were very technical and covered a lot of different technologies. Towards the end of the day I was totally knackered and found it really hard to think straight, whether in code or in plain old English. 5 hours of hard-core technical questions when you have only a few seconds to think up a good answer and write code on a white board is TOUGH, no matter how much of a geek you are. NOW I’m pretty sure I’ve experienced the toughest interviews I will ever have to.

Anyway, I guess the moral of all this is that if you are given an opportunity to try out for something you really want but are pretty sure you’re not going to get – give it a go anyway. Sure, it’s gonna be hard and you’re gonna stress about it. Sure you’re gonna feel pretty crap about it if it doesn’t work out. But you will gain SOMETHING from it – even if it’s just the experience. In my case, apart from being forced to review a whole bunch of pretty cool geeky stuff that I’d totally forgotten about, I got a cool trip to Zurich, paid for by Google, I got to meet a bunch of really fun and talented software engineers (who by the way took Chris and I out for a great Swiss-fondue dinner after my day of interviews in Zurich) and basically I feel pretty good about the fact that I even got the chance to interview with Google. And as I mentioned above, I am now confident enough to believe that I can sit through any technical interview known to man (or woman)

Posted General, Technology |