NavVis Interview Questions
& Process

I applied online and after about a month, I had an HR screening. Then, I talked to the Hiring Manager and had a technical interview. The technical interview questions were pretty basic, but the interviewer seemed disengaged and tried to end the call early, likely because HR scheduled it. When I asked a security-specific question, the interviewer didn't answer or wouldn't. Later, HR told me my technical skills were good, but I couldn't move forward due to a 'structural decision.' Since it was a technical role and I thought the interview went well, I'm not sure why I was rejected.

It was a really well-organized, clear, and professional interview process. Started with a chat with HR about my background, why I wanted the job, and if I'd fit in. Then, I had interviews with the Line Manager that covered technical stuff and business aspects, and they went over what they expect, what the job entails, and the region I'd be working with. They kept me in the loop well, and I got feedback pretty quickly. It felt like a respectful and interesting process, and I got a good sense of the role and the company.

I really liked interviewing with NavVis. Every part helped me get a clear picture of the business, what they're trying to do, and what doing well in the job looks like. Meghan, my recruiter, was great - always on top of things, communicated well, and kept things moving. I always knew what was coming up and never felt confused about what was next or when. The interviews felt like chats, but everyone I talked to was ready with good, interesting questions that helped me understand the job and also showed I'd be a good fit for the team. It was a pleasant and professional experience!

So I started with a quick call with Rina, the recruiter, to go over my background and pay needs, just the usual stuff. The next day, she sent over a coding challenge. It was a C++ task where I had to code something simple and also review someone else's code. I think the main point was building a solid software structure that's easy to test, handles errors well, and performs efficiently. Once they looked at my code, I got invited to a 1.5-hour technical interview with the team lead and another engineer. They introduced themselves and asked me to do the same, and they seemed really interested in what I'd done before. I wasn't totally ready to present my PhD work since it was a while ago, but I did my best to show them the pictures from my papers. Then came the technical questions about ROS, C++ fundamentals like smart pointers and interfaces, debugging, how to measure performance, and dealing with memory allocation issues. They also asked about my code challenge submission. The other engineer then went deeper into SLAM, Visual SLAM, using IMU data, and combining Visual and LiDAR data. They saved the last five minutes for my questions. A couple days later, I heard back that I didn't make it because they found someone whose experience was a better fit. I asked for more detailed feedback, which they kindly provided. Obviously, I was bummed about not getting the role, but I really appreciated how open they were and how smoothly the whole thing went.