Real, anonymous reports from people who interviewed for Software Engineer at IBM, newest first and distilled into what to expect across the loop.
My interview experience was a simple one-on-one conversation. The interviewer asked basic questions about the projects and programs I’d worked on, and it never felt adversarial. When I stumbled on parts of my explanation, she helped me understand where I went wrong and what to improve.
The coding assessment I did was a bit tricky and very math-forward. I was asked to count “ideal numbers” defined as products of powers, specifically numbers of the form 3^x * 5^y where both x and y are non-negative. The task was to count how many of those values fall within an inclusive low-to-high range.
The interview process typically begins with an HR screening followed by multiple technical rounds that cover a broad range of topics, including coding, system design, and behavioral questions. The structure is often described as comprehensive, with a mix of assessments and interviews that can feel lengthy and drawn out.
Candidates can expect a variety of technical assessments, including coding challenges on platforms like HackerRank, focusing on data structures, algorithms, and specific programming languages such as C++ and Java. These assessments often require not just correct answers but also an explanation of thought processes and complexity analysis.
Interviews often emphasize behavioral questions and the candidate's communication skills, with interviewers probing deeply into past experiences and thought processes. This approach aims to assess how candidates articulate their reasoning and handle follow-up questions.
The difficulty of interviews is generally perceived as average to challenging, with some candidates noting a pressure to perform under time constraints, especially during coding assessments. The intensity of follow-up questions can add to the overall pressure of the experience.
Many candidates report a lack of timely feedback and communication throughout the process, leading to feelings of uncertainty and frustration. Delays in receiving results or rejections can detract from an otherwise positive interview experience.
Candidates often describe the interview experience as organized yet mechanical, with a mix of positive interactions and frustrations related to the pacing and structure of the process. While some candidates felt the interviews were fair and informative, others noted a disconnect in the overall experience.