Google Sr Software Engineer interview questions

As a graduate apply for Google Beijing. After one phone interview, two onsite interviews follow and then another two. In each onsite one you are expected to solve two basic problems and one of the onsite interviews have a system design question. The questions are easy if you are familiar with basic algorithms and understand then clearly. Just think aloud and write the code on whiteboard, paper or computer.

There were a number of separate interviews with separate developers through the day with a lunch-time non-counting interview. The questions were all about puzzles that you could easily look up (I had seen them all before in the various books), and only one interviewer at the end of the day in the last five minutes of that interview even bothered to quiz me about my unique skills, a specialty that I was told Google was looking for and why I even chose to accept the interview in the first place. I went through the puzzles, writing my answers using brute force solutions rather than jumping to the conclusion not only because I felt it fair but also because I began to see the whole day as a waste of my time since it became apparent they were more interested in playing games than testing my skills.