Real, anonymous reports from people who interviewed for Software Engineer at Mistral Solutions, newest first and distilled into what to expect across the loop.
After an HR call, I was scheduled a short time later for a technical screen focused heavily on C and embedded/low-level thinking. I had to cover basics around microcontrollers and embedded systems, and the discussion went into how UART communication works, plus GPIO and PWM. Debugging techniques came up too, and I had the sense they wanted to hear how I reasoned about fixing things, not just which answer I picked.
My interview felt pretty fundamentals-oriented. It was an average-difficulty process where the discussion covered a broad mix of core topics, including both analog electronics and digital concepts, with an emphasis that having strong embedded knowledge mattered too. A lot of what I was asked stayed within basic building blocks rather than deep, niche problems.
The interview process is structured and typically progresses quickly through multiple rounds, starting with an aptitude test followed by technical interviews and concluding with an HR round. Candidates noted that the flow felt coherent and organized, allowing them to stay focused throughout.
Technical interviews emphasize core fundamentals in C programming and embedded systems, often including practical problem-solving and project-related discussions. Candidates reported a mix of basic and applied questions, with a clear expectation to demonstrate understanding rather than just recall.
Candidates typically begin with an aptitude test that includes both technical and general questions, setting the tone for the interview process. This initial assessment often includes sections on software and hardware fundamentals, with negative marking to encourage careful answering.
The HR round is generally conversational and focuses on the candidate's background, interests, and motivations for joining the company. Candidates found this part of the process to be relaxed compared to the technical interviews, allowing for a more personal dialogue.
Candidates described the overall difficulty as average but noted that the technical questions could be demanding, especially regarding constraints and implementation details. The interviews progressively raised the bar, requiring candidates to demonstrate a consistent understanding of concepts.
Candidates wished they had focused more on specific embedded systems concepts and practical applications of C programming. Understanding the core fundamentals and being able to articulate past project experiences were highlighted as key preparation areas.