The interview process consisted of a short phone interview and an on-site interview. The on-site interview was split into a business interview and a technical interview. All three interviews were with separate managers.
The phone interview was short and mostly involved questions about prior work experience and skills. I was also required to complete an online math quiz, although I was told it rarely mattered in the process.
The business interview involved questions about my ability to react correctly in specific business situations (e.g., "How did you react when a customer or client did this...").
The technical interview wasn't much of an interview but more of a lesson. The manager asked me a question and then explained in detail what I wasn't completely sure of. Other candidates being interviewed were handed code and told to determine what it did. I was told prior to the on-site interview to understand polymorphism and inheritance.
The process was difficult for me and many others who were hired on at the same time because IBM functions differently regarding bench time. Because of this, I had my phone interview roughly a month after applying, and the on-site interviews a month later. I was initially told my start date was the following month, but then I was informed it was pushed back repeatedly.
I finally started at my desk almost a year after the on-site interview. Being pushed back, from what I hear, is common, but many people told me I was a rare case.
Why is Java considered more secure for online transactions?
The following metrics were computed from 1 interview experience for the IBM Entry Level Java Developer role in East Lansing, Michigan.
IBM's interview process for their Entry Level Java Developer roles in East Lansing, Michigan is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having mixed feelings for IBM's Entry Level Java Developer interview process in East Lansing, Michigan.