IDFC FIRST Bank Interview Questions
& Process

This interview process was really good and felt well put together. They were clear and professional in seeing if I was a good fit. The interviewers were nice and made me feel comfortable, but also kept things focused so the conversation was meaningful. A big part of the interview focused on behavioral and situational questions, really asking about things I'd done before. Most of the talk was about real situations I'd handled in past jobs, like dealing with tricky projects, solving problems when things were tough, and changing gears when priorities shifted. This felt like a good way to show how I actually work, not just give theoretical answers. It let them see my decision-making, problem-solving, and how I bounce back. One thing they really seemed to care about was stakeholder management. They kept asking for examples of how I find, rank, talk to, and influence people I work with, especially when interests clashed, people were resistant, or I needed to get different groups on the same page (like teams, bosses, or outside people). The questions were often like, "Tell me about a time when..." and they wanted detailed answers, maybe using the STAR method, to show what happened. This makes sense because the job needs good stakeholder skills to get everyone aligned, get support, lower risks, and make projects work in a team setting. They seemed especially interested in examples where I: - Juggled different priorities or set realistic expectations. - Used listening, the right words, and building connections to make people who were unsure become supportive. - Handled disagreements without causing drama but still moved toward what we all wanted. So, it was clear stakeholder management is a really important part of what they look for. Candidates who can share specific stories from their work history that show results – like better teamwork, projects finishing on time, less pushback, or better long-term relationships – will probably do well. Basically, it was a solid interview that looked at both the job skills and how I interact with people. The big focus on past examples of handling stakeholders shows this is a key area for doing well in this role. Having good stories about this would be a big help for anyone going through it.

So it was campus recruitment and a 3-step process. First, they did resume shortlisting based on some internal criteria. About 300-350 students from over 500 applicants got to take the OA. Then, there was an Online Assessment on HirePro with 3 sections: Mathematical Reasoning & Aptitude (which was tough given the time), CS fundamentals (medium MCQs), and 2 DSA questions (rotten oranges and a difference array problem). After that, we had offline campus interviews, and around 25 students made it. The interview itself had 3 technical rounds and then an HR round.

It was a technical round where I was first asked to talk about myself, and then we moved straight into Data Structures and Algorithms. He asked me about the DS concepts I know and based on that, he gave me 3 DSA questions. I successfully answered all three and wrote the solutions on paper, explaining them, which he seemed impressed by. After that, we covered core concepts like OOPS, CN, OS, and DBMS. The round lasted about 35-40 minutes. I thought I had cleared it, but out of 35 students, only 3 were selected for the next round, and interestingly, they were students who hadn't even been interviewed in the first round. Ultimately, no one from our college got selected, and we later found out they had already recruited from other colleges a few days prior.

The whole thing took about 3 weeks. It was an open campus drive, but they only picked the top 150 for interviews, saying more would be contacted later. I got an email for an online assessment (OA) with 3 coding questions, ranging from basic to hard, focusing on arrays, strings, and hashmaps. After clearing that, I was invited for an in-person interview at the Hyderabad campus. The in-person part had 4 days and 4 locations to choose from; I picked Hyderabad. There were 3 rounds in total: 2 technical and 1 HR. The first technical round had 2 interviewers who didn't look at my resume. They started by asking me to describe myself and my projects. Then, they moved straight to DSA questions to check my logic. I talked about my microservices, cloud, and system design project for about 40 minutes. After that, they asked a DSA question about writing the logic code to find a target value in generated Fibonacci numbers using a hashmap algorithm. I explained the logic but couldn't write the code perfectly. They told me that strong DSA is more important than just projects for SDE roles and advised me to try again next time.