The process began with a short call with talent acquisition where we kept it simple: my background and a quick overview of the company. After that recruiter step, the scheduling moved quickly toward the main interview.
For the official stage, I went through an in-person interview that came bundled with an assessment. It felt like a single block meant to evaluate both practical skill and how I think under scrutiny. If they wanted to take it further, there was a subsequent online interview via Teams. Overall, the flow was very clearly structured, and the main thing that stood out to me was how quickly it moved from introduction to a physical interview plus assessment.
4 months ago
Easy Neutral Ottawa, ON
I kicked things off with a quick chat where they basically pulled details from my resume, then the round stayed pretty technical. After that intro, they asked me about some of the tools I listed—Python and JavaScript came up—and then they pivoted into computer networking topics. I remember getting questions specifically around DNS and the network stack.
Most of the rest of the Teams screen felt like a straightforward gauge of fundamentals. It ran about 30 minutes, and they asked basic checks like whether I knew what DDoS was. They also asked about pytest, and there were a few behavioral questions mixed in—how I worked on a team and a time I handled a difficult issue. I felt like my preparation for the networking basics and testing tooling paid off, and overall the vibe was calm and not overly tricky.
5 months ago
Average Positive Athens, Athens, Attica
My process started with an online test that leaned on both automation and networking knowledge. The coding part involved writing code in Selenium, and…
> 1 year
Average Positive Kanata, ON
I first got a call from them, and then they set up an in-person meeting. I was honestly pretty stressed, and I ended up postponing it, but they accept…
> 1 year
Easy Positive Timişoara
I showed up to an interview day where the structure was unusual but clear: we presented ourselves to the team in a circle, taking turns sharing person…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process is well-structured and moves quickly from an initial call with talent acquisition to an in-person interview and assessment, often followed by a Teams interview if progressing further.
Interview flowTimelineStructured process
Technical Assessment Focus
Candidates can expect a mix of technical assessments that include coding tasks, particularly in Python and Selenium, along with questions on networking fundamentals like DNS and TCP/IP.
PythonSeleniumNetworking
Behavioral & Fit Questions
Behavioral questions are included but are generally straightforward, focusing on teamwork experiences and motivations for wanting to work at Nokia, rather than complex scenarios.
BehavioralTeamworkMotivation
Assessment Environment
The interview atmosphere is described as calm and approachable, with interviewers valuing communication and basic technical alignment over high-pressure problem-solving.
Calm environmentCommunicationApproachable
Preparation Insights
Candidates recommend focusing on networking basics and familiarizing oneself with testing tools like pytest and Selenium to align with the technical expectations of the role.
PreparationNetworking basicsTesting tools
Overall Difficulty & Outcome
The overall difficulty of the interviews is perceived as manageable, with candidates reporting a smooth process and quick feedback, leading to a positive outcome for many.
