NavVis 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 NavVis.
NavVis
Software Engineer
Mid Average Positive experience Accept offer 3 rounds
Interview process
Take home Technical screen Recruiter call Offer
Interview formats
System Design Coding Technical
The whole interview thing was super chill and ran really smoothly. Like, they were upfront about everything, and the HR folks were on point, always ready to help out. Started with a take-home task, then I had three interviews. After that, we had a feedback chat and then they gave me the offer.
Confirmed questions3 questions
- Tell me about a system design problem.
- Solve some Leetcode style coding problems.
- What are some core software engineering concepts you know?
NavVis
Senior Software Engineer
Senior Average Negative experience No offer 1 round
Interview process
Take home Technical screen
Interview formats
Technical Coding System Design
Complete waste of time! After spending around 2 days on their technical task, they returned with feedback stating that my assumption of the input files being stored on S3 was inappropriate and overlooking the crucial upload step :), also they complained that my solution design was simplistic and for a senior level they are expecting a more complex solution design! They are missing that this kind of task is to show expertise in different areas and as it is unpaid I am not supposed to spend a week designing, implementing, testing, and documenting such a technical task.
Confirmed questions1 question
- Design and implement a phone number parser solution
NavVis
Software Engineer
Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Behavioral Coding
I had a 30-minute call with a recruiter who contacted me on LinkedIn. She did most of the talking and we finished in 31 minutes, which felt rushed. She seemed more interested in interviewing many people than anything else. The next day, she sent a programming challenge, even though I told her I'd be on leave. I finished it on time, but didn't proceed because my work didn't meet their expectations. The challenge wasn't clearly defined, forcing me to make assumptions, and they even told me to make assumptions when I asked for clarification. Ultimately, they had expectations they didn't state in the description. Their behavior was unprofessional, but I learned a lot.
Confirmed questions2 questions
- Tell me about yourself.
- Could you solve a coding problem by making assumptions?
NavVis Software Engineer Interview Questions
Quoted word for word from NavVis interview reports.
“Regarding API Gateway, what is its quota and how can we upload larger files using a serverless setup?”
Read reports →“Design and implement a phone number parser solution”
Read reports →“Serverless compared to EKS: what are the trade-offs?”
Read reports →“What are the limits/quotas for AWS services and how can these be overcome?”
Read reports →“Can you provide details on the structure of the Navvis team?”
Read report →“Can you describe a tree traversal question?”
Read report →“Can you explain the time complexity of the functions you utilized and suggest ways to optimize them?”
Read report →“Can you recommend based on the previous discussions?”
Read report →“Can you answer some questions about computer science fundamentals?”
Read report →Formats, difficulty and experience
Across all 18 NavVis interview reports.