Indegene logo

Indegene Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 29 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
48.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Indegene.

Showing 3 of 29
Indegene logo
Indegene

Technical Lead

Engineering · a year ago

Lead Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Take home Presentation
Interview formats
Behavioral Case Presentation

So, there were three rounds in total. First was a 30-minute call mainly about my resume, the role, and some behavioral stuff like why I'm interested in this job and why they should pick me. Then came the case study round. They gave me a case study and asked for wireframes, MVP, and solutions within two days. After that, we had a 30-minute call to present it. They didn't hire me because my presentation wasn't great, even though my logic was spot on. Crazy, right?

Confirmed questions2 questions
  • Why should we hire you, and why are you interested in Indegene?
  • Regarding the case study, which involved automation and process improvement, how would you implement digital solutions for the given scenario?
Indegene logo
Indegene

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Background check Offer
Interview formats
Technical Coding Behavioral

I applied via my college placements and went through 3 rounds: an aptitude test, a technical interview, and an HR interview. The technical interview was about 30 minutes and covered programming language concepts, OOPs, and included 2 coding problems. The HR round involved background checks and document verification, with some situational questions. Overall, it was a good experience.

Confirmed questions2 questions
  • Can you explain the differences between a queue, a stack, a linked list, and an array?
  • Write code to determine if a string is an anagram.
Indegene logo
Indegene

Software Engineer

Engineering

Mid Difficult Negative experience Decline offer 5 rounds
Interview process
Technical screen Technical screen Technical screen Technical screen Technical screen Offer
Interview formats
Technical Technical Technical Technical Technical

Waste of time, first day they called for a machine test which I cleared. After that, they told me they would call for the next round. They gave 3 rounds of technical interviews, and again I was told they would call for the final round. In the final round, there were again some 2 rounds of technical interviews which I was able to clear. Finally, they said they would be sending an offer letter, but instead of sending an offer letter, they gave new excuses every week for why they were delaying in sending the offer letter. I was irritated at the end; either Yes or No would do. This whole thing went on for almost a month. Finally, I had to tell them not to send an offer letter as I was so much irritated because of HR, and I wasted my time and energy attending interviews almost every week.

Confirmed questions4 questions
  • What do you know about .net Mvc?
  • Tell me about your experience with sql.
  • Do you have experience with javascript?

Indegene Software Engineer Interview Questions

Quoted word for word from Indegene interview reports.

Could you explain how the enhanced for loop in Java keeps track of the index?

Read reports

Could you explain why Java is a platform-independent language?

Read reports

Can you explain the difference between structured and unstructured databases?

Read report

Can you explain the concept of event looping in JavaScript?

Read report

Can you define Drupal and elaborate on its migration process?

Read report

Describe fundamental front-end technologies such as jQuery, JavaScript, HTML, and CSS.

Read report

Formats, difficulty and experience

Across all 29 Indegene interview reports.

Interview formats

Technical 45.8%
Coding 23.6%
Behavioral 23.6%
Group 1.4%
System Design 1.4%

Interview difficulty

Easy 20.7%
Average 62.1%
Difficult 17.2%

Candidate experience

Positive 48.3%
Negative 24.1%
Neutral 27.6%