Real, anonymous reports from people who interviewed for Software Engineer at IBM India, newest first and distilled into what to expect across the loop.
I moved pretty quickly from the coding stage into the rest of the loop. My coding interview was handled as HackerRank questions—two of them—and they felt like easy leetcode-level problems. Alongside that, the process also included multiple zoom interviews and questionnaire-style forms to fill out.
I started with an online, camera-and-mic style recording assessment. It came as a set of multiple prompts tied to my experiences, and the process felt high-pressure because I only got a single attempt and very little prep time per question. I had to think quickly about what I’d done before while staying coherent under the time constraint, and it didn’t feel like a typical coding vibe at all.
Candidates typically begin with an online assessment that includes 1-3 coding questions, often in a HackerRank format. The difficulty varies, with some reporting easy to medium-level problems, while others faced more challenging tasks, including dynamic programming and data structure questions.
Following the OA, candidates participate in one or more technical interviews that may include coding exercises, system design questions, and discussions on core computer science concepts. The focus is often on problem-solving skills and the ability to explain thought processes clearly.
Behavioral interviews are a significant part of the process, often focusing on candidates' past experiences, teamwork, and problem-solving approaches. These interviews tend to be resume-driven, with questions tailored to the candidate's listed projects and experiences.
The interview format can vary significantly, with some candidates experiencing structured, multi-round processes while others faced more casual or disjointed interactions. The tone and clarity of communication during interviews can greatly influence the overall experience.
Candidates have reported mixed experiences regarding feedback and communication post-interview, with some feeling left in the dark after assessments. The overall outcome often hinges on both technical performance and the ability to articulate experiences and reasoning effectively.
Candidates suggest focusing on both technical fundamentals and the ability to discuss past projects in detail. Practicing coding problems under time constraints and preparing for behavioral questions related to personal experiences can enhance performance.
