Bohemia Interactive Simulations Interview Questions
& Process

So after they looked at my portfolio, they sent me a take-home UX challenge. I went ahead and did the challenge, making sure to include lots of documentation and even working prototypes, thinking that might give me extra credit. I basically turned in a full UX project instead of just a few screens or basic mockups, which is apparently what they were expecting. I got it done and sent it to the Product Designer who was in charge of the challenge. They said they'd get back to me after reviewing it. I waited for weeks, and still nothing. So I decided to follow up with emails to the person who gave me the challenge. After a bunch of emails and waiting for over a month, I finally got a generic rejection email with no explanation. Really frustrating!

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.

After I sent in my resume and cover letter, I had a remote interview through Google Hangouts with two people. Following that, I was invited for an in-person interview with three interviewers, one of whom was from the first interview. They mentioned there would be a third and final interview on-site, which was supposed to include a conference call with senior management overseas. Sadly, I didn't get called for that third interview, so this review focuses on the second interview.

The interview process was pretty good, with three main stages. First, I had an online interview with HR and the Hiring Manager where we talked about my studies and personal projects since I don't have work experience yet. After that, I got an Angular task to complete within a week, which was fun. Once I submitted it, they called me back for an in-person interview at their office. This final interview was about two hours long and involved many technical questions, some harder than others, but it went well overall.