Bohemia Interactive Simulations Software Engineer Interview Questions
& Process

The interview was online and in English. They asked some basic questions about my expectations and a few algorithmic tasks. The whole process felt pretty long, but they did offer me a break.

First, I got a call and had to do an online programming test, which was easy with C++ skills. Then, there was an online pair coding session combined with a phone interview. The coding questions were easy, and some other questions felt like they came from a CS exam, with many O(n) questions. After that, I was invited for an onsite interview. I was told they weren't interested after the onsite. If I had passed, I would have gone for another onsite interview. I'm not sure how many more there would have been. They seemed more focused on your ability to answer questions than your actual work. The job description was a perfect match for my experience, and I had many examples of success in what they were looking for. I wasn't given any reasons for not moving forward, so I can only guess. Everyone was really nice, and I know this is how interviews are done now, so it's not just them. It's just tiring to go through this process and always be the most productive person but not fit the mold. I've studied for this type of interview before, but for this job, I wanted to show my work and let them decide based on my experience, instead of just spitting out answers that anyone who studies hard can get. There's a free online copy of 'Cracking the Coding Interview'. Study that book, and you'll get through their process. Very nice people, a nice office, and it seems like fun work, so it was worth the time and experience. It's just disappointing that so many companies need good people but don't know how to interview for them.

So the process was kinda like what someone else described, which was super helpful for me to even get this far. It kicked off with a C++ coding test, you get 80 mins, which should be plenty, I was slow and careful and still finished with 10 mins to spare. After passing that, they set up a phone interview. They gave me specific study advice for data structures, algorithms, C++, which was good but kinda messed me up later, as you'll see. Phone interview day came and they ghosted me! I had to call reception and email the manager to find out what was up. After a long wait (45 mins, yikes!), they apologized and we started. This disorganization should've been a sign, but I decided to overlook it. The phone interview was mostly "what's wrong with this code" type questions, some fill-in-the-blanks, others just verbal answers. Lots of O(n) stuff, linked lists, OOP, data structures, trees, all in C++. The interviewers were chill though. I passed and got scheduled for an in-person technical. That started with a chat about my resume, pretty standard. Then they had me whiteboard 2 problems. The first was super similar to a Google example on YouTube. The second was about sorting a massive number from a huge file with low RAM but lots of hard drive space. Again, pretty relaxed. Passed that too and was told the final interview would be behavioral, plus an office tour and lunch. I went, got the tour, met some cool people. Some key managers were missing though, so I ended up interviewing with the same guy from the first in-person, and they grabbed some random dev too. It was disorganized, the manager even admitted it. The first guy asked more resume questions and then had me whiteboard C++ classes for a program from my old job. This caught me off guard since they said it was behavioral and I'd already done 3 tech screens. It was frustrating, but I think he was just stalling. Then other managers came in for the typical "disagreed with coworker" questions and other HR stuff. We had lunch, and I thought it went well. Got rejected a couple days later. Feedback was: work on UML (weird, as the question was about C++ code, not UML) and get more C++ experience (also weird, since I passed 3 tech screens). My advice: follow guides, but be ready for anything, they're disorganized and things won't go as planned.