Real, anonymous reports from people who interviewed for Software Engineer at IBM, newest first and distilled into what to expect across the loop.
I applied through the IBM portal and got an automated email almost immediately inviting me to complete an online coding assessment on HackerRank. The assessment wasn’t proctored and I had about 60 minutes to finish two problems. It felt pretty straightforward on paper—two LeetCode-style questions—though the time pressure still made me move carefully.
For this role, my experience started in a much more personal, lighter format than I expected. I had a coffee chat-style conversation where most of the discussion revolved around the projects on my resume and the experiences I’d already done. There were no coding questions at all, and it felt more like a genuine conversation than an interrogation.
The interview process typically starts with an online coding assessment, followed by a series of technical and behavioral interviews, often taking about a month or more to complete. Candidates noted the pacing varied, with some experiencing delays and a lack of communication post-interview.
Candidates generally faced a coding assessment focused on algorithmic problems, often resembling LeetCode questions, followed by technical interviews that included coding and system design discussions. The emphasis was on problem-solving skills rather than trick questions.
The interviews included a significant behavioral component, focusing on past experiences and fit for the role, with many candidates reporting a relaxed atmosphere that encouraged open discussion. Interviewers often asked about teamwork, leadership, and project contributions.
The final round often involved a manager interview that could shift in tone, with some candidates experiencing a more intense focus on specific technical details, which could impact the overall impression of the process. This round was crucial in determining fit and communication style.
Candidates reflected on the importance of thoroughly preparing to discuss their projects and technical choices, as well as being ready for varied interview formats, including presentations and deep dives into their resumes. Clear communication and alignment with the role were emphasized.
Overall, candidates found the process to be manageable but thorough, with a mix of straightforward and challenging questions. While many did not receive offers, the structured approach and emphasis on clear communication were noted positively.