MIM Software Software Engineer Interview Questions
& Process

First I was sent a coding assessment with 2 algorithm problems and 1 debug problem. Then I had a call with 2 engineers where they asked basic OOP questions and about my past projects, and also went over my coding assessment. The next round involved interviewing with 3 separate teams. The first team focused on behavioral questions. The second team provided some code and asked me to figure out what it does and how to improve it. The third team asked more in-depth algorithm problems, specifically about trees/graphs and DFS/BFS. The whole process was good until the final round. The last team I met with had two engineers who had been there for 10+ years, and it was really clear they didn't want to be interviewing. They'd say things like "....cool" multiple times. I didn't feel any connection, and I suspect their attitudes might be why I got rejected without a response. I was ghosted after this round, and there was no chance to ask for feedback. If this experience is any indication of how they treat their employees, I'd think twice about applying.

The interview started with a CodeSignal Coding Assessment, which had 4 questions: 1 debugging and 3 coding ones. These coding questions tested basic algorithm knowledge, and knowing hashmaps was super helpful. Then, there was a Two on One Interview where two Engineers grilled me on Object Oriented Programming and Data Structures – definitely brush up on your arrayLists, LinkedLists, and HashMaps. The next stage involved three Two on One Interviews. The first one focused on choosing the best data structure for a specific problem and how to traverse it (BFS, DFS, and Trees are key). The second one involved looking at a program and explaining its function and how it works, similar to the CodeSignal task. The last interview was about Java specifics and some straightforward coding problems, like transposing a matrix. I didn't do great on that last one because I was new to interviewing and didn't expect the difficulty level.

First, there's a coding test. After that, an initial phone interview with two developers. Then, you set up a final round interview, which is actually three interviews happening back-to-back. Some of these involved Java questions on memory management and other language-specific topics, followed by some basic algorithm questions. They asked for pseudocode, which I kinda wish they'd just asked me to code out, that would've been just as simple. One interview was purely DSA. I thought the question was pretty easy, they don't make you code it out, but you have to explain the solution in a lot of detail. The last interview covered OOP principles and a basic grasp of Java.