Narvar Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 30 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Narvar.
Narvar
Software Engineer
Senior Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical
The interview was for a Senior Software Engineer role and involved a 2-hour session. It was split into 1 hour of coding and 1 hour of review. The panelist was a Senior with over 5 years at the company but seemed unaware of their role. They were impatient, trying to finish the 1-hour interview in 40 minutes. They had fixed ideas for solutions and didn't allow for discussion. They also expected over-engineering for straightforward problems.
Confirmed questions1 question
- Narvar scenario based coding question in Golang.
Narvar
Software Engineer
Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Coding System Design Behavioral
Applied via linkedin and got shortlisted in a week. The recruiter explained the process and set up the first 2 rounds. After passing those, the next 2 rounds were scheduled. The first round was Algo/DS with medium-level problems. The second was System Design. The third round focused on my past work, and the final round was a mix of cultural/behavioral/System Design. The interviewers were friendly and open to discussing different approaches. Recruiters and HR were also responsive. Overall, it was a very smooth and well-organized interview process.
Confirmed questions2 questions
- Can you describe the architecture of the existing applications you've worked on?
- Tell me about the projects you have worked on.
Narvar
Software Engineer
Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Coding System Design
The recruiter contacted me first. Then I had a phone screen, followed by an onsite interview. The phone screen had typical Leetcode easy to medium problems. The onsite consisted of straightforward programming questions and then some system design questions. It wasn't overly difficult, but it's wise to review your data structures knowledge. The most significant issue was the company's really poor culture regarding candidate treatment. They went completely silent after the interviews and didn't respond even when I tried to contact them multiple times. It's baffling how a company thinks this is acceptable behavior towards candidates, which really says a lot about their internal culture.
Confirmed questions3 questions
- What are your thoughts on Leetcode easy to medium programming questions?
- Can you explain how to solve simple programming questions?
- Tell me about system design questions.
Narvar Software Engineer Interview Questions
Quoted word for word from Narvar interview reports.
“How do you sort and reverse an array in JS?”
Read reports →“How would you implement a highly scalable rate limiter?”
Read reports →“Design a system (server) to handle multiple client servers downloading large files.”
Read reports →“Can you explain the mechanics of solr faceting?”
Read reports →“How do memory and time efficiency relate to estimated delivery dates?”
Read report →“Could you detail the search process within solr?”
Read report →“What is the High-Level Design of Zoomcar?”
Read report →“Tell me about the gas station problem from LeetCode.”
Read report →“What conceptual questions do you have regarding validation metrics for ML systems?”
Read report →Formats, difficulty and experience
Across all 30 Narvar interview reports.