I met with a manager at a Big Ten career fair who helped me narrow down which specific jobs to apply for. For all three applications I submitted, I was requested to fill out a HackerRank assessment.
The Frontend test had HTML/JS problems that were well above my level, so I turned it in mostly blank. With the Backend one, I felt much better, and it led to an interview. I never completed the third one.
The one interview I had consisted of the same manager I met with at the fair (as he managed the backend team) and two other interviewers who specialized in technical and HR questions. The interview was only an hour long: half was spent on a coding whiteboard, a quarter on reading code in an unknown language, and the last bit on typical interview questions. Because of this, there was not a lot of time to ask questions.
They initially said there was a short final interview to go through, but a few days later, I received a call saying they were drafting my offer letter. The manager was nice and offered an extra meeting so I could ask more questions about the program.
What do you do when you get stuck on a problem?
The following metrics were computed from 23 interview experiences for the IBM Backend Developer role in United States.
IBM's interview process for their Backend Developer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for IBM's Backend Developer interview process in United States.