Getting an Interview
Getting an Interview
Interviews for Top Jobs at Nokia
- Software Engineer (67)
- Senior Software Engineer (41)
- R&D Engineer (23)
- Project Manager (11)
- RF Engineer (10)
- Software Developer (10)
- R & D Engineer (9)
- Systems Engineer (9)
- Intern (8)
- Engineer (7)
- Engineering (6)
- Software Test Engineer (6)
- Graduate Engineer Trainee (6)
- Product Manager (6)
- Product Marketing Manager (5)
- Manager (5)
- Software Tester (5)
- Marketing Manager (5)
- Solution Engineer (5)
- IT Specialist (4)
- Specialist (4)
- Network Engineer (4)
- Senior Manager (4)
- Senior Engineer (4)
- RF Design Engineer (4)
- Program Manager (4)
- Technical Lead (4)
- Technical Writer (4)
- Telecom Engineer (3)
- Architect (3)
- No OfferNegative ExperienceAverage Interview
I applied through college or university. The process took 2 weeks. I interviewed at Nokia (Boston, MA) in November 2013.
1phone call and 2 onsite interviews
- asked mostly about data structures and java related questions Answer Question
- Declined OfferPositive ExperienceAverage Interview
I applied through college or university. The process took a week. I interviewed at Nokia (Burlington, MA) in October 2013.
They contacted me after we talked briefly at a job fair. They were pleasant and after a brief conversation asked to schedule an in person interview. I drove down to their Burlington, MA location, and they saw me promptly. The interview itself was with four people; all software engineers and software architects. They asked me 4 main questions, most of which led to offshoot discussions. They started the interview off with a logic puzzle type question. After that it seemed they had a long list of questions, but they asked at what point I was at in my schooling and which classes I had taken; then asked all further questions based on my answers. i felt what they did ask was relevant to my schooling, and all of them were incredibly pleasant and helped me work through the answers when I wasn't sure.
- The logic question at the beginning. The question was, "You're in a room with 3 switches. In the next room over are 3 lights. You can't see the lights in the next room. You can flip the switches as many times as you'd like, but you can only have one on at a time. How can you tell which light goes to which switch?" 1 Answer
Reasons for Declining
About a half hour before they made me an offer, my first choice company had called and made me an offer.
- No OfferNegative ExperienceEasy Interview
I applied through an employee referral. The process took 1 day. I interviewed at Nokia (Burlington, MA) in June 2011.
I was interviewed by five different people that would've been my peers. Except for the initial disucssion with the business manager, the interview teams seemed to lack any real training or preparation in interviewing and the questions seemed haphazard and disorganized. I felt like they were going through the motions of interviewing and that another candidate had already been picked. The interviewers seemed beaten, tired and lacking energy. A common question that was asked was about how I handled conflict management. I got a bad feeling about the Nokia given the low energy of the group, and the common question about conflict management.
- How do you handle conflicts? What is your style of conflict management? Answer Question
Helpful (1)Accepted OfferPositive ExperienceAverage Interview
I applied through an employee referral. The process took 3 days. I interviewed at Nokia (Burlington, MA) in March 2010.
Initial phone screens consisted of general review of past projects, technologies, etc. that seemed related to the job description. Followed up with in-person interview with two different groups and two different interviewing styles. The first group was much more data structure and algorithm oriented. Big "O" questions, recursive algorithms, tree search (depth and breadth) , etc. done at the whiteboard. Professional but adversarial feel to these interviews. The second group was much more "experience" oriented. Concentrated on the what/how/why questions of previous projects. Still did some whiteboard work, but mostly for design/implementation diagrams. Professional and much less adversarial than former group. 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 were no use of explicit arrays, queues, etc. 1 Answer
I didn't negotiate because the salary and work environment was better than previous position. I took the job with the second group basically because of the group dynamics.
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review