I recently interviewed with IBM for a position, and unfortunately, the experience left me disappointed.
Although I was initially hopeful due to positive interactions and feedback during the process, I was not selected, despite being given the impression that I was a strong candidate.
The interview process included discussions on my previous projects, Data Structures and Algorithms (DSA), and problem-solving questions. While I understand the need for rigorous evaluation, the questions felt overly complex and disconnected from practical, job-specific scenarios. Additionally, despite my honest effort, the feedback was vague, and there was no constructive critique to help me understand the rejection.
What I found most frustrating was the lack of transparency. They raised my expectations but failed to communicate openly about where I stood. After several rounds of preparation and what seemed like a good rapport with the interviewers, the rejection came abruptly without clear reasoning.
IBM is a reputed company, and I had high hopes for this opportunity. However, the way the process was handled felt disorganized and demoralizing. I hope they improve their feedback mechanisms and set more realistic expectations for candidates in the future.
Would I recommend applying here? Only if you are prepared for an unpredictable process with limited clarity.
Explain your project and how you plan to improvise it.
The following metrics were computed from 131 interview experiences for the IBM Software Engineer role in Bengaluru, Karnataka.
IBM's interview process for their Software Engineer roles in Bengaluru, Karnataka is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for IBM's Software Engineer interview process in Bengaluru, Karnataka.