The process began with a general phone screen by HR. There were no technical questions, beyond asking, "How many years of experience do you have with...?", and no behavioral questions.

Next, an on-site interview followed, consisting of two one-on-one interviews with other engineers. This portion was 100% technical.

They did not open the floor for my questions, nor did they seem to consider that they would need to "sell" the job to me. In fact, they did not ask any general questions, only those from their pool of technical questions.

For this particular position (though this might differ depending on the job), the questions leaned towards the academic side. They touched on discrete structures and algorithm analysis – generally topics one learns in school and doesn't frequently need in practice. If such knowledge is required, a reference book is usually readily available.

It only takes one interviewer to end your candidacy, so you must impress every interviewer, not just the majority.

Design a web search engine that searches web locations for anagrams of a given string.

Design a 2D dungeon crawling game. It must allow for various items in the maze:

• Walls
• Objects
• Computer-controlled characters

(The focus was on the class structures and how to optimize the experience for the user as they travel through the dungeon.)