Initial phone screens consisted of a general review of past projects, technologies, etc. that seemed related to the job description. This was followed up with an in-person interview with two different groups and two different interviewing styles.
The first group was much more data structure and algorithm oriented, with big "O" questions, recursive algorithms, tree search (depth and breadth), etc., done at the whiteboard. There was a professional but adversarial feel to these interviews.
The second group was much more "experience" oriented, concentrating on the what/how/why questions of previous projects. They still did some whiteboard work, but mostly for design/implementation diagrams. These interviews were professional and much less adversarial than the former group. I got the feeling they were much more interested in hiring smart people that could adapt to change.
Write recursive breath and depth tree listing methods.
Constraints: no use of explicit arrays, queues, etc.
The following metrics were computed from 1 interview experience for the Nokia Principal/Senior Software Engineer role in Burlington, Massachusetts.
Nokia's interview process for their Principal/Senior Software Engineer roles in Burlington, Massachusetts is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Nokia's Principal/Senior Software Engineer interview process in Burlington, Massachusetts.