Nisum Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 40 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Nisum.
Nisum
Software Engineer
Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check Offer
Interview formats
Technical Coding Behavioral
The interview process at Nisum involves technical and HR interviews. There might be a coding test or assignment. Technical interviews will cover basic concepts, coding skills, and knowledge of technologies like Java, possibly with scenario questions. The HR interview checks for cultural fit and behavioral aspects. Some positions might also require client interviews.
Confirmed questions3 questions
- Can you introduce yourself?
- What makes you a good candidate for this role?
- Describe your main strengths and weaknesses.
Nisum
Software Engineer
Mid Average Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call Background check
Interview formats
Technical Behavioral
The interview process has 3 rounds. The first round is a technical round focusing on basic to mid-level technical questions across various subjects. The second round is another technical round, also with basic to mid-level questions, but the lead might ask random questions depending on their mood. They might still ask about areas you've said you don't have experience in. The third round is with the client or HR, which is usually smooth and straightforward. I passed all these rounds and completed the document verification and got the salary breakup. The role was also confirmed. However, I haven't received an offer letter yet.
Confirmed questions1 question
- Basic and mid-level questions are asked until the lead or managerial round, but during the lead round, questions might be asked on topics you don't have experience in, based on their mood, even if you mention it.
Nisum
Senior Software Engineer
Senior Average Negative experience No offer 3 rounds
Interview process
Technical screen Recruiter call Onsite Background check Offer
Interview formats
Technical Coding Behavioral
So I interviewed with Nisum like 20 days ago. First, there was this technical round that took more than an hour. They hit me with a bunch of deep questions and a coding challenge, which I totally aced. Got good vibes and they said I passed. Then came the Managerial Round, which also went pretty smooth. After that, they told me the client would do the last round, but it took like two weeks to even set up. The client interview, I got technical questions again and two coding problems. I only solved one, but overall I thought I did alright. But then, another week later, they hit me with the news that the client rejected me because I didn't solve the coding problems. It feels like a total waste of time and effort when Nisum leads you on with good feedback, only for the client to just shoot you down in the end, especially if their say-so is the main thing. If it's all about the client, they should just handle the interviews from the start. It would be way more honest and save us candidates a lot of hassle and disappointment.
Confirmed questions1 question
- Can you discuss your experience with frontend development, backend development, and databases?
Nisum Software Engineer Interview Questions
Quoted word for word from Nisum interview reports.
“Given the string 'cabebaf', what is the first character that repeats? If there are no repeating characters, return '-'.”
Read reports →“How would you go about removing three or more consecutive identical characters from a string?”
Read reports →“Can you explain what the virtual DOM is in React and what benefits it offers?”
Read reports →“What are some of the advantages of using a microservice architecture?”
Read reports →“What are strategies for managing a Singleton pattern in a clustered environment?”
Read report →“Could you explain the difference between an array and a linked list?”
Read report →“Can you explain the implications of making a class static?”
Read report →“Can you describe the handshake process for HTTP and HTTPS?”
Read report →“Could you explain the internals of the JVM?”
Read report →Formats, difficulty and experience
Across all 40 Nisum interview reports.