After a brief phone screen that covered my personal history and projects, I was invited onsite.
There, I interviewed with a team of employees. The initial questions were somewhat generic, such as "Tell us about yourself," offering an opportunity to discuss any significant school or personal work I had completed.
Then we moved onto the technical portion, where they presented me with a scenario (building a website for a store to sell records) and asked how I would manage the data. This part went fairly well, with the team actively engaging me and asking additional questions during my answers, presumably to test how I handle working in a group setting.
I left feeling pretty good about my performance.
Some days afterward, I received a call informing me that all internships throughout the company had been put on hold and that they were not moving forward. I'm fairly certain it was a white lie to make me feel better, but I appreciated the consideration.
Say you were building a site that sells music records. If we wanted to keep track of customer purchases, what data would you track and how?
The following metrics were computed from 64 interview experiences for the IBM Software Engineer (Internship) role in United States.
IBM's interview process for their Software Engineer (Internship) roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for IBM's Software Engineer (Internship) interview process in United States.