Infogain Interview Questions
& Process

HR first mentioned that there would be four stages: an initial HR screening, a Technical Round, a Technomanagerial Round, and a final HR discussion. After the HR screening, my resume got shortlisted and my first technical interview was scheduled. Even though the interview was scheduled for 45 minutes, it ran for about an hour and 5 minutes. During this time, I answered about 90% of the questions about Python, SQL, AWS Lambda, Flask, and my projects. Twenty minutes later, HR told me I passed with excellent feedback and they scheduled the next round. The second round also took 45 minutes, and I answered all the technical questions confidently. However, at the end, the interviewer asked an analytical question not related to the technologies. I provided an approach, but he didn't seem happy. Twenty minutes after the interview, HR informed me that the round didn't go well, but they couldn't give a specific reason. In the end, even though I performed well overall, my application was rejected, seemingly because of that one analytical question.

The interview process begins with you applying for the job. Recruiters will look at your resume to see if your skills and experience match what they're looking for. If they like your resume, you'll typically have a short call with HR. This call is to go over your background, when you can start, how much you want to make, and if you meet the basic requirements. The HR round is also where they check your communication skills, attitude, and if you'd fit in with the company culture. They'll also talk about salary, your start date, and other job terms.

My experience with the interview for the Data Engineer role at Infogain was pretty disappointing for a few reasons. The recruiter seemed like they didn't really know much about the job requirements. They hadn't even looked at my resume before we talked, which made the whole thing feel pointless. Also, they didn't seem very interested, making it feel like they were just going through the motions to hit a quota instead of actually trying to see if I'd be a good fit or tell me anything useful about the company or job. Because of how unprofessional it was, I wouldn't recommend this interview to anyone, as it just didn't feel respectful or engaging.

The interview questions were mostly basic concepts, ranging from easy to medium difficulty. They asked a few coding problems, basic Java 8 stuff, and core Java topics like string mutability, heap vs. SCP, and the final keyword. The questions were pretty elementary, like the interviewer's own understanding. But the whole thing was unprofessional. The interviewer, XYZ, was really bad at communicating and totally lacked professionalism. He talked down to me like he was the boss and I was nothing. It was super uncomfortable and weird for an interview. He also seemed unsure about the questions, which was confusing. If any managers see this, please do something about this. Interviews need to be respectful, clear, and professional, and this was the opposite. Hope this helps for future improvements.