Check out your Company Bowl for anonymous work chats.
Bowls
Get actionable career advice tailored to you by joining more bowls.
Followed companies
Stay ahead in opportunities and insider tips by following your dream companies.
Job searches
Get personalized job recommendations and updates by starting your searches.
NNG interviews FAQs
C++ Developer applicants have rated the interview process at NNG with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 73.5% positive. This is according to Glassdoor user ratings.
Candidates applying for C++ Developer roles take an average of 14 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at NNG overall takes an average of 22 days.
Common stages of the interview process at NNG as a C++ Developer according to 4 Glassdoor interviews include:
Skills test: 43%
Group panel interview: 29%
One on one interview: 14%
Presentation: 14%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 6 days. I interviewed at NNG
Interview
Tooks some days, make an test online then one test at them. All about was algorithms.
You got a codility test at first, then you go in the office, you got a laptop with visual studio and a task, and a face to face interview with leads
I applied online. The process took 3 weeks. I interviewed at NNG (Budapest)
Interview
The process consists of multiple rounds. The first round was a test with four small questions. One was to write a code snippet related to a binary tree, there was a 'what is the output and why' type of question mixed with bugfixing, another question was about sorting algorithms, and there was another code snippet writing in the topic of number systems.
The second round was an in-place interview with team leaders, the main topic was about the first round's test.
I applied through a recruiter. I interviewed at NNG
Interview
I took part only on the first interview, at an HR office. There were 4 problems which I had to solve on paper in 60 minutes. The first one was a "what is the output" like question, the second one was a basic what does the code and how could be rewritten to work faster. THe last two were easy problem solving, like find the deepest element in a binary search tree.