Intern applicants have rated the interview process at IBM with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 71.4% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
3 parts, recruiting is pushed and not clear on parts. screening call, info call about background then technical interview. Transparent about pay and duration. not much else to say like standard interview processes these days
Interview questions [1]
Question 1
Experience with networks and plans upon completion
smooth, easy to understand, slow in getting next steps, but consistent. the questions and tests were very difficult. im trying to fill the word minimum so i can use mt account.
Interview questions [1]
Question 1
Describe your previous experience and how it will help here
I applied online. The process took 1 week. I interviewed at IBM (Austin, TX) in Oct 2022
Interview
This was for the X-Force RED Intern position. They use Knockri, which is a automated/AI candidate-filtering software that basically means that you have to talk about yourself like you're also a robot, since there is no actual human component involved. The software itself is fine. It's easy to use, lets you try a few practice questions, has a nice interface, etc., however if you are the type of person who gets nervous easily, or has a habit of saying "um" or "uh" a lot, you can count on the fact that the system is taking points off from your "confidence" value. At the end of it all, I had to go to the application portal to find out I had been denied after it was all said and done. It's been around 3 weeks, still haven't gotten an email from them besides the usual promotional mail they send you about other jobs that you have no interest in.
Interview questions [1]
Question 1
Imagine that a customer is having an issue with some software your company sells, and the customer is becoming upset about the issue. They are blaming it on the software, however you believe it to be user error. How would you handle this situation?