
Nexthink Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 18 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Nexthink.
Senior Software Engineer
I was interviewing for a C++ developer role focused on a core software component. The first two rounds were with senior engineers from Switzerland, focusing on my C++ skills and problem-solving. Then, I had two more rounds with managers from India and Switzerland, which felt redundant as they covered the same topics. The final round was supposed to be with the VP of India, but my start date at my next organization was just a week away. They then told me they hadn't gotten headcount approval for the position and it would take 2-3 weeks, asking if I could wait. It made me wonder why they were interviewing if they didn't have approval.
- What are your salary expectations?
- Would you join Nexthink if the offered salary is the same as your current compensation?
- Is your interest in Nexthink driven by the compensation or the work itself?
Software Engineer
So after sending my resume, I got a call from HR, who was super friendly. We talked about my background, skills, and why I was interested in Nexthink. They then laid out the interview steps: a quiz, followed by interviews, and then hopefully an offer and starting the job. First, they sent a quiz that was related to the job, focusing on advanced Java and Javascript. It was challenging but solvable if you knew your stuff. I spent about a day on it. I heard back within a couple of days after submitting my quiz, and it was positive, so we scheduled an interview within a week. On the interview day, I first met with the VP of Engineering for an hour. It was a non-technical chat where they discussed Nexthink's product, culture, and mission, and we went over standard behavioral questions. Next, I had a technical interview with three engineers from the team I'd be joining. This lasted about an hour, and they asked about concurrency, algorithms, and databases, giving me challenges to solve for each. The algorithm question was particularly interesting and challenging. After the interviews, they said I'd hear back soon. I got the offer on Monday afternoon, accepting it right away because it met my expectations from the interview. The whole process, from the HR call to the offer, took about 10 days.
- Can you tell me about your experience working in a team and how that process went?
Software Engineer
It started with an HR call and an online test. Then there were 2 virtual interviews. The first was with a software engineer where we discussed my general technical stack and course schedule, and did a coding exercise (search in LeetCode). The second was with a software engineering manager about concurrency and Kafka different schematics. After that, I had a round with the engineering director about agile and team culture. Finally, I spoke with my future team manager about culture.
- Can you detect if there's a cycle in a given microservice dependency graph?
Nexthink Software Engineer Interview Questions
Quoted word for word from Nexthink interview reports.
“How is similarity search performed in a vectorDB?”
Read reports →“Can you detect if there's a cycle in a given microservice dependency graph?”
Read reports →“Can you implement a generic finite state machine in C++?”
Read reports →“Could you write a thread-safe queue in C++?”
Read reports →“Could you create an iterator class to sort elements within a vector of vectors?”
Read report →“How would you build a cross-platform command-line app that takes a directory and finds duplicate files based on content?”
Read report →“What is the schema for your vectorDB?”
Read report →“Can you explain the difference between multithreading and multiprocessing?”
Read report →“What are your insights on overfitting in LORA?”
Read report →Formats, difficulty and experience
Across all 18 Nexthink interview reports.