Glassdoor users rated their interview experience at Nokia as 100% positive with a difficulty rating score of 3 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Project Officer and rated their interviews as the hardest, whereas interviews for Project Officer and roles were rated as the easiest.
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 3 weeks. I interviewed at Nokia (Sunnyvale, CA) in Feb 2011
Interview
Phone screen, Fill out forms on web (they require current salary in form. put in $1.00 and tell HR rep "I don't give out that information... Here is what I want") Finally on site interview panel and then about 1-2 weeks before offer. Panel can be very tough.
Interview questions [1]
Question 1
Be ready to code on the black board. Be ready to talk about your past accomplishments.
I applied through a recruiter. The process took 2 months. I interviewed at Nokia in Apr 2009
Interview
The interview itself is not very difficult, it depends much on the skills of the hiring manager and how well versed they are in terms of proper interviewing. however, it is not that difficult for a candidate with the right skills. the challenging part is the assessment center if the position you are applying for is a managerial position. I had to undertake a day long assessment that luckily went well and I got hired but I would not be able to give any advice on this one except be yourself and prepare a little for the ability tests (verbal and numerical).
I applied online. The process took 2 weeks. I interviewed at Nokia
Interview
1. applied online
2. a call from hr to setup an interview
3. first interview with a nice old guy (near 60 yrs old i think), he was asking some basic C/C++ questions (C - mostly memory management and pointers manipulation, C++ - difference between virtual and pure virtual method, stl iterator types, operator overloading) and asked me to present some algorithms in pseudocode (can't remember exactly, but something like reversing a linked list and one sorting algorithm), few days after the interview I got an email, they said I did well and I should come to another interview
4. Interview with a developer, first question he asked was to analyze some assembler code, after that (I didn't do very well with assembler) he asked if i know something about differences in C structures memory alignment with different compilers, he wasn't happy with my answer
after that he asked me some questions about my studies (I was a student back then) and the interview was over
5. after few days got an email - they thanked me for applying and didn't hire me of course
I felt like the guy from step 4 didn't know that i was applying for a junior C++ developer
Interview questions [1]
Question 1
Differences in C structures memory aligmnent management with different compilers