SBP Interview Questions
& Process

The process was long but flowed well. They talked about the actual job tasks. The interviewing team was large and seemed to have a lot of tenure. They were good at explaining the lower salary and the long hours required.

The interview process included a basic interview, a "tell me about yourself" question, and an inquiry into why I was interested in the company. There were also some behavioral questions covering teamwork and handling disagreements with coworkers. They also asked about my technical skills. The whole process took about a month, including two interviews and an offer.

It was great that I interviewed directly with the person this role reports to, instead of going through a HR screening, which isn't common anymore. The interview felt more like a chat than a formal process, nothing unusual. I thought our conversation went well, but I was disappointed to get a rejection the next day without any feedback.

The technical interview was on-site and involved three coding tests. The first test was an OOP challenge where you had to demonstrate superior OOP skills within 1 hour and 30 minutes. The second was a debugging problem, which was fairly easy but required consulting documentation, and you had 30 minutes for it. The third and most challenging part involved adding features to the debugged code, with 4 exercises in 2 hours and 30 minutes, and it seemed unlikely to finish all of them. The whole experience lasted from 9 am to 5 pm, which was very long and exhausting. After about 8 hours and completing most of the tasks, I was rejected without any feedback, which was a bad experience.