Real, anonymous reports from people who interviewed for Software Engineer at Bajaj Finance, newest first and distilled into what to expect across the loop.
After the recruiter call, I went through a multi-round process that felt very deliberate: technical discussions first, then management-style evaluation, and finally an HR conversation about fit and logistics. I also had salary expectations discussed early, and we reached a mutually acceptable number before documents became the focus. For me, the process felt professional while it was actively moving.
I sat down expecting a normal chat, but the tone felt off from the start. The interviewer quickly moved past introductions and basically pushed straight into a coding problem of the LeetCode-medium style. I started coding right away and it took longer than a couple of minutes, but I didn’t get much chance to walk through my thinking or even explain any pseudo-code.
The interview process typically follows a structured flow starting with an aptitude test, followed by technical rounds that include coding and project discussions, and concluding with an HR interview. Candidates noted that the sequence felt deliberate and organized, contributing to a professional experience overall.
Technical interviews often emphasize core concepts such as OOP, SQL, and coding challenges, with a mix of theoretical and practical questions. Candidates reported that the technical rounds were rigorous, with some focusing heavily on database knowledge or specific programming languages relevant to the role.
Candidates experienced coding challenges that varied in difficulty and format, often conducted under time constraints. Some reported feeling rushed or pressured during these sessions, which impacted their ability to communicate their thought process effectively.
The communication throughout the interview process was noted to be inconsistent, with some candidates experiencing delays in feedback and updates, particularly after the documentation stage. This lack of timely communication led to frustration for some candidates.
Interviews included discussions about candidates' previous projects, where they were expected to explain their roles and the technologies used. This aspect was seen as a way to gauge practical experience and fit for the role, with a focus on clarity and understanding rather than purely technical prowess.
Candidates reported mixed feelings about their overall experience, with some finding the process professional and well-managed, while others felt it was overly intense or disorganized. The outcomes varied, with several candidates not receiving offers despite positive interactions during the interviews.