I can't tell you the questions because of NDA. But if you comfortable with algorithms (sorting, iterations, find), arrays, trees, linked lists and all this stuff - you should perform well. Only thing I should mention - practice in whiteboard coding before the interview to feel comfortable about that. In about 5 to 10 problems you'll become okay with idea of writing code on whiteboard(if you don't do that in everyday work of course), and this should help.
Nothing unusual or unexpected. Rather than college-type of drill, technical discussion about solving problems.
Design an event tracking system with a tracking function to monitor events. There will be two event types: high-priority events, which should be sent to the server immediately upon arrival, and low-priority events, which can be cached locally and uploaded in batches every 10 seconds or so. Ensure that validation and enrichment are performed when events are received.
iOS basics, experience questions, and some networking
Programming exercise was good- you had 1:15 hr in XCode to write a simple iOS application with data persistence, implement a shake motion gesture, localize it into french and spanish, and ensure the UI resized correctly. Then you had to write the test cases for your app. All told if you knew what you were doing you should have the basics done in under an hour. From there you can spend the rest of your time making the UI pretty.
Describe a challenging task you have worked on
Create an algorithm to find the solution of a maze. The starting point could be anywhere inside the maze.
The technical questions covered a wide range of areas which I appreciated. The areas included object oriented design, architecture design, problem-solving/algorithms, objective-c (blocks, view controllers, etc.), and mobile specific questions. The most difficult question I was asked was to design a document upload/fetcher system for mobile (kinda like dropbox for the iphone). The difficulty was really in all the details of the problem (caching, database modeling, security, sessions, etc). Algorithm questions ranged from binary tree search questions to array pattern searching. The most unexpected question was the interviewer gave me a stream of digits and asked me to find the pattern. I got really stumped on this problem, it was my last interview of the day and I just blanked out. I guess I did well enough throughout the day because I got the job. By no means an easy interview, but not extremely hard, I was extremely well prepared as I had been interviewing for a while. Id say its on the average to difficult scale, if you are bad at architecting systems then this interview would have been HIGH diff.
Viewing 11 - 20 interview questions