Software Engineer applicants have rated the interview process at IBM with 2.4 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 68.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 30 days to get hired, when considering 5 user submitted interviews for this role. To compare, the hiring process at IBM overall takes an average of 25 days.
Common stages of the interview process at IBM as a Software Engineer according to 5 Glassdoor interviews include:
Phone interview: 50%
One on one interview: 25%
Skills test: 25%
Here are the most commonly searched roles for interview reports -
The interview was over the phone, with about 3 different people asking technical/behavioral questions. Interview was about 45 minutes long. Just make sure to review any programming languages that you have stated on resume, be good with run time analysis. Just relax and be yourself, if you are not sure of anything don't be afraid to clarify things with the interviewer. Best of luck!
Interview questions [1]
Question 1
-Run time analysis q's, data abstraction in Java q's, Javascript q's
-Behavioral questions, handling conflict, problem solving, working in teams, leadership
I applied online. The process took 2 weeks. I interviewed at IBM
Interview
I applied online. After a week or so I got an e-mail from the hiring manager to schedule a call. I talked with the hiring manager. We discussed the position and whether it would be a good fit. There were no specific technical questions. We both agreed it would be a good fit and decided to move forward with an onsite.
Between the call and the onsite there was an online interview and coding test. The interview was a bit strange. I had to record video answers to written questions with no feedback from a real person. The programming questions were fairly standard. There was a decent editor and the ability to run some test cases (they defined the test cases). Two of the problems were fairly straight forward (like you would see in an interview prep book). One of the problems was a bit more complex. They gave me an hour and it took pretty much the whole time. The whole coding test took about 3 hours.
The onsite was about 5 hours and included lunch. I met with a few managers and one engineer. The managers asked some behavioral questions ("Tell me about a time when..."). And the engineer asked more technical questions. Since the coding test was focused on algorithms the engineer interview was more focused on architecture and object-oriented principles. Everyone was very nice and enthusiastic about the project, which was much appreciated.
A few days after the interview I got an informal verbal offer from the hiring manager and set up a meeting with the VP in charge of the group who gave me the salary numbers and explained the project at a higher level. About a week after the interview I got the formal offer letter in my e-mail.
Interview questions [1]
Question 1
The coding test was fairly standard algorithms questions from books like Cracking the Coding Interview. They weren't too hard, but if I didn't study I may have had a time crunch. One of the questions was a bit more complex with a page long specification and some unique requirements.
The onsite was mostly behavioral ("Tell me about a time when...") with some software engineering questions relating to architecture and design.
I applied online. The process took 2+ months. I interviewed at IBM (New York, NY) in Aug 2015
Interview
Neverending coding challenges online where they watch you code through your webcam. Very creepy and overly invasive just to make sure you don't "google anything", because apparently the engineers at IBM Watson never forget anything and all have photographic memories. Absolutely ridiculous and not worth what they're paying considering they're in NYC.
4
Top companies for "Compensation and Benefits" near you