|
I'm preparing for an interview with Google (Hyderabad, India) for "Developer relations engineer" position. I've been told that they'll ask coding/analytic/design/algorithm and creative questions.. Can anyone please share some of the experiences and the questions? Any pointers would be quite helpful. Peter |
|||||||||||||||||
|
|
A good resource (written by a Googler) that sums up what you should know before interviewing for development positions at Google is Get that Job at Google, by Steve Yegge. If you like video lessons, you'll find MIT OpenCourseWare to be invaluable. Look at 6.00 - Introduction to Computer Science and Programming (they use Python!) and 6.046J - Introduction to Algorithms (not the most recent version of the course, but has video lectures). You can find many interview questions on the web. For example, GlassDoor.com contains many interview questions, and sometimes they have answers too. I don't know the details of your position, nor your background, but I would spend time on each of the points addressed in the first link and doing lots of coding exercise. You can find many interesting problems on TopCoder. They also have some useful Algorithms tutorials. Last but not least, good luck! |
|||
|
|
|
Expect questions that require dynamic programming. Scale is always a challenge in Google. So expect solutions of simple problems that become challenging when scaled. For example, how to implement short urls (tinyurl.com/xxxxx to full url). Hash tables are the obvious answer, but how do you scale them to billions of urls? They are interested in multi core, multi machine solutions. How to transfer huge files across 1000s of servers? They are also interested in graphs, traversal, coloring etc. |
|||
|
|
I don't feel sharing the questions would be fair (nor really useful to you). I interviewed for a different engineering position in a different office, so YMMV. In my case I had to solve an interesting algorithmic problem, do some low level C++ stuff, figure out how to build a simple service but with huge scale and tight performance limitations, talk about linux internals, and discuss ways to monitor services. Most of these required whiteboard coding, especially the first two. None of the questions were "puzzles" or "brain teasers", they were very fair. The interviewers were great, very friendly and helpful. It felt like a interesting conversation between colleagues, not like an interrogation :) |
|||||
|
