Real, anonymous reports from people who interviewed for Software Engineer at IBS Software, newest first and distilled into what to expect across the loop.
My process started with campus recruitment. The early round was mostly fundamentals—Java basics and OOP ideas, especially around classes and objects. We also talked about object-oriented programming and how those concepts show up in real code and scenarios.
My interview started smoothly enough: it was described as an HR round plus a technical interview, and even though I was told a full panel would be there, only one interviewer actually showed up. The whole thing still played out in the expected order, with the technical portion first.
The interview process typically follows a structured sequence starting with an aptitude test, followed by technical interviews, a managerial discussion, and concluding with an HR round. This multi-step approach allows candidates to demonstrate their skills progressively, with each round serving a distinct purpose.
Candidates can expect a technical round focused on coding challenges that assess problem-solving abilities, often involving Java fundamentals, data structures, and algorithms. The difficulty of these coding tasks can vary from average to difficult, with an emphasis on clear reasoning and practical implementation.
The HR round typically includes behavioral questions aimed at assessing cultural fit and communication skills, often focusing on candidates' past experiences and how they align with the company's values. This part of the interview allows candidates to express their motivations and career aspirations.
Interviews often delve into candidates' past projects, requiring them to explain their technical choices and the application of concepts like OOP, multithreading, and design patterns. This aspect tests not only theoretical knowledge but also practical experience and understanding of real-world applications.
Overall, the difficulty of the interview process is perceived as average to difficult, with some candidates feeling challenged by the depth of technical questions and the need for clear explanations. Many candidates report not receiving offers, indicating a competitive selection process.
Candidates often reflect on the need for better preparation in specific areas, such as system design and articulating their thought processes during technical discussions. Practicing coding problems and reviewing project experiences can enhance performance in future interviews.