There was an introduction describing the project, its goals, and working environment.
After that, there was the technical part, which consisted of basic questions regarding OOP in C++ and STL. There were also lower-level questions related to C++ standards rationales or details related to CPU architecture and some pitfalls. There were no questions checking the way of thinking, algorithmic or analytical skills, or orientation in design patterns and OOP practices. Nothing about modern good programming methodologies/practices as well.
At the end, there was time for interviewee questions, which were answered with details and engagement. It appears they do want to apply recommended practices (for example, TDD, pair programming) but don't have people with such experience.
What data structure would you use for 2 million integers that would be inserted at the beginning and then searched many times?
The following metrics were computed from 1 interview experience for the Nokia C++ Developer role in New York, New York.
Nokia's interview process for their C++ Developer roles in New York, New York is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having mixed feelings for Nokia's C++ Developer interview process in New York, New York.