I talked to the recruiter on the phone and he scheduled an interview for the very next day. When I got there he talked with me briefly and reiterated what he had told me on the phone, that they are looking for only very senior software engineers. He then turned me over to an engineer for the rest of the interview. After a brief discussion about the company's products the interviewer presented a Java programming problem for me to solve on the whiteboard. The problem was this: given a class that is a Collection of Collections (let's call it CofC), code an Iterator for the CofC class. Implement the next() and hasNext() methods and the constructor. The only method in Collection that you can use is iterator(). That is to say, you cannot use size() or any other method. During the exercise the interviewer interacted with me, made some suggestions. pointed out some errors. I wouldn't call this a trivial problem but it is not that difficult and probably is a fair test for the amount of time alloted. I made some mistakes early on and didn't focus well enough so I didn't do that well. I strongly suggest doing this exercise at home and timing yourself and paying attention to your process. My impression was that process, and not just the correct answer, was important. They emailed me later the same day to say they would not proceed to the next step with me. It was nice that I got that information right away, compared to most companies who either never contact you at all or contact you weeks later to say they are still interviewing other people.