Taro Logo

Software Engineer Interview Experience

October 16, 2015
Positive ExperienceGot Offer

Process

I applied online. After a week or so, I received an email from the hiring manager to schedule a call.

I spoke 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 interview.

Between the initial call and the onsite, there was an online interview and coding test. The online 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 straightforward, like those found in interview prep books. One of the problems was more complex. They gave me an hour, and it took pretty much the whole time. The entire coding test took about 3 hours.

The onsite interview was about 5 hours and included lunch. I met with a few managers and one engineer.

The managers asked behavioral questions ("Tell me about a time when..."). The engineer asked more technical questions. Since the coding test focused on algorithms, the engineer's interview focused more 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 received an informal verbal offer from the hiring manager and set up a meeting with the VP in charge of the group. They provided the salary details and explained the project at a higher level.

About a week after the interview, I received the formal offer letter via email.

Questions

The coding test featured standard algorithms questions, similar to those found in books like "Cracking the Coding Interview." They weren't overly difficult, but without prior study, a time crunch might have been a concern.

One question presented a more complex challenge, with a page-long specification and some unique requirements.

The onsite interview consisted mainly of behavioral questions ("Tell me about a time when...") alongside software engineering inquiries focused on architecture and design.

Was this helpful?

Interview Statistics

The following metrics were computed from 363 interview experiences for the IBM Software Engineer role in United States.

Success Rate

39%
Pass Rate

IBM's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive53%
Neutral33%
Negative13%

Candidates reported having very good feelings for IBM's Software Engineer interview process in United States.

IBM Work Experiences