Senior Software Engineer applicants have rated the interview process at Nokia with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 68% positive. To compare, the company-average is 72.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 19 days to get hired, when considering 42 user submitted interviews for this role. To compare, the hiring process at Nokia overall takes an average of 22 days.
Common stages of the interview process at Nokia as a Senior Software Engineer according to 42 Glassdoor interviews include:
One on one interview: 23%
Phone interview: 20%
Skills test: 15%
Group panel interview: 14%
Background check: 12%
Personality test: 7%
IQ intelligence test: 4%
Presentation: 4%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 7 weeks. I interviewed at Nokia (Wrocław) in Sep 2012
Interview
No HR interview with typical questions, only an interview with four developers. This position was mainly about software design in C++, but there were no questions on software design. The interviewers seemed to be in hurry. Many questions unrelated to the position. They expect dictionary definitions as the answers.
Time and money wasting for experienced looking for a better paid job. It takes them extremely long time to make and inform their final decision, you have to ask them for that from time to time. Rude interviewers. Unprofessional and _no_reimbursement_.
Interview questions [5]
Question 1
Testing techniques (black-box, white-box, regression, unit testing - they expect the answer from the book, not from your experience and the real-world programming), testing strategies (not assertions, mocking and so on... but answer as it is defined in one of the books they have probably read before).
Implement an algorithm to find balance point of the array. Proposed one, with average complexity of O(N-1) but it seems they were looking for another one solution (which I have found on Stackoverflow later).
What is polymorphism (in-deep question (vtables, vptrs implementation details) with example on whiteboard, marking as virtual in base and not-marking as virtual in derived - what would happen)?
What comes along with copy-constructor? (Silly question, correct answer is assignment operator). Plus standard questions on memory leaks, mutex and semaphore, difference between stack and heap, overloading of operator new, etc. No questions on "advanced" C++ features like templates.
Single 1.5h teams call. HR, PM, and engineer on one call. A few generic HR questions, then a brief project description from PM. C++ position, many OOP questions, and three C++ tasks involving STL.
Interview questions [1]
Question 1
C++ position, many OOP questions, and three C++ tasks involving STL.
Two rounds of online interview, but the positions got cancelled. After completing the interviews no offer was extended.
A successful interview is a two-way conversation, showcasing your skills while learning about the role and company. Be prepared, concise, and authentic. Highlight relevant experience, ask insightful questions, and demonstrate enthusiasm to leave a lasting impression.
I applied online. The process took 4 weeks. I interviewed at Nokia
Interview
3 technical rounds of general java, design questions which went positive.
Though my current and expected was already known by recruiter beforehand. At the 4th round, Manager was surprised by current and expected CTC. Then HR person didn't respond. Overall , not a good experience.